Spreadsheet and Logger Actions

Where to Enter Observations

Quick log is hidden for compatibility; use the mobile logger or AppSheet for routine entry. Use the daily report for the care plan.

History is the canonical observation ledger. History view is its sorted projection. AppSheet staging and a local browser queue are not confirmation that a record has reached History. The AppSheet companion guide explains the bridge and receipts.

Identity and Common Fields

• P-ID identifies the tracked plant/container over time. Pot label is the physical label such as A1 or #2. Saved rows retain the label at entry, so an old label can be correct historical evidence.
• Observed at / Started at / Date means when the action or measurement happened. Backdate an observation to its real time when appropriate; Recorded separately stores when it was saved.
• In the phone logger, Observed at uses the current time when you save or queue an entry. Edit it to record earlier care, or choose Use current time to resume automatic timing. Queued entries and retries keep their original observation time.
• Pot setup identifies the whole weighed configuration. It is not the pot size in inches.
• Notes hold useful details not covered by structured fields. In a multi-event save, the note is attached to the first generated event rather than copied onto every row.
• Plant condition, Soil moisture, and Medium / substrate are different fields. Condition and moisture belong to Check; the growing-medium description belongs to Repot.
• A shared planter receives one observation identity per event. Weigh the whole container and name the relevant member in Notes when needed.

For example, select #2 / P20 once for a shared-planter weight or watering. The same applies to #6 / P30 and #9 / P35: their botanical pages share one pot entry. “Tan/brown Lithops firm; grey/green heads beginning replacement” belongs in P35's note. Find each planter's members in the container guide.

The 12 Selectable Actions

The single-plant logger exposes exactly these 12 event choices. Fields listed as required here describe the detailed web/AppSheet writer; Quick log offers a smaller set of structured fields.

Automatic Note Records and Inferred Actions

Note can appear in History even though it is not one of the 12 selectable event buttons. If an otherwise event-free submission contains only notes, the writer creates a Note record. Notes entered alongside a selected action stay on the first event; they do not necessarily create a separate Note row.

The writer also adds appropriate events from entered data: a weight adds Weigh, dimensions add Measure, and condition or soil-moisture information adds Check in the detailed form. Entering a weight never automatically adds Water. An entirely empty submission is rejected.

This means one click on Save is not always one History row. Review the event summary rather than interpreting several rows with the same save time as duplicates.

Water, Nutrients, and Weight Are Separate

Application Style

The exact choices are Flood / soak-through, Thorough, Partial, and Spot. Flood / soak-through is the default. Change it when that does not describe what happened. A blank historical application remains legacy/unspecified; do not relabel it without evidence.

Partial and Spot waterings remain real Water events, but do not qualify for the normal full-cycle forecast. Flood / soak-through and Thorough can qualify when the other model evidence is valid. Choose the label that describes the watering you performed.

Amount Fields

There is no separate Fertilize event button. The structured nutrient record belongs to Water. Do not create a fictional watering to document a different activity; use Other with an accurate note when appropriate.

Water + Weigh is a combination of events, not a thirteenth single-plant event. Water without a scale reading is valid. Weigh without Water is valid. If the weight represents the post-drain condition of that watering, it can be included in the same observation. If it is a pre-watering reading, save it separately at its actual earlier time and record the post-drain reading separately if taken.

The writer places Weigh before Water within a combined save for historical ordering. The shared save identity lets the cycle logic recognize that weight as the watering's Wet anchor. Do not rearrange rows or edit their timestamps merely to make the sheet look chronological.

Why You Do Not Choose Dry, Wet, or Routine

The Weight state field remains in the workbook for compatibility with older records and drafts. New weights are stored as Routine. Derived views identify the same-save watering weight, or the first eligible positive weight within five days when needed, as Wet. The final eligible non-Wet weight before the next Water can become the completed Dry endpoint. An unfinished cycle's latest low remains Routine.

A derived Wet/Dry label can therefore differ from a canonical History state shown elsewhere. This is expected. See the watering reference explanation.

Dimensions, Condition, and Repot Details

Measure

The mobile form accepts in or cm, with inches as its new-entry default. Height and width can be entered independently. History keeps normalized centimeters, the chosen entry unit, and derived inch values for consistent views.

Methods are Ruler, Estimated from photo, Estimated visually, Other, and Unspecified. Ruler sets measurement quality to Measured; photo and visual methods set it to Estimated. Other/Unspecified retain an explicit compatible quality choice, defaulting to Estimated when absent. A picture-based guess is not a ruler measurement.

Quick log dimensions are currently recorded with Estimated quality and Unspecified method because that sheet does not provide the detailed method controls. Use the detailed form when preserving measured provenance matters. Older pending payloads with no unit use the legacy centimeter interpretation; do not assume every old number is inches.

Check

The soil-moisture choices exposed by the detailed form are Dry, Slightly moist, Moist, Wet, and Unknown. These describe an observation, not a sensor reading automatically inferred from pot weight. Use Unknown when appropriate; a blank or Unknown field does not mean Dry.

Condition describes the plant, while medium describes what it is growing in. For example, new growth belongs with condition; the potting-mix recipe belongs with Repot. In a shared planter, mention which member or part of the root zone you checked.

Repot and Setup Boundaries

Use the detailed Repot form for its automatic setup advancement and structured old/new pot-size and medium fields. Enter the same physical pot size if the medium was changed while reusing that pot, and describe the actual change.

Quick log reads its Pot setup cell directly and does not provide the same detailed Repot preparation. Selecting Repot in that sheet alone should not be treated as equivalent to the automatic setup change in the mobile form. Avoid manually guessing a setup number or migrating old rows as part of routine entry.

A corrected gram typo is a correction, not a Repot. A lighting change can be Other, not an automatic new weighing setup. Significant mass/configuration changes need clear documentation so incompatible baselines are not silently compared.

Photos and Other Detailed Observations

For Photo, paste an existing Gyazo capture link, or use Open Google Photos and obtain the intended share link. Gyazo links use https://gyazo.com/ followed by the 32-character lowercase capture ID. A browser file-picker path is not a durable share URL. A saved photo link appears in the observation history; it does not automatically add the image to the plant's website gallery.

For Flower, describe whether a count refers to open flowers, buds, or something else. A text description can record spent blooms without forcing a positive count. For Pest, retain uncertainty in the issue description and distinguish observation from treatment. Clean and Prune also benefit from a short, specific note because they have no separate structured quantity field.

Do not add private account details, addresses, or other unnecessary personal information to notes or shared links. The workbook and public history are intended to be viewable references.

Which Actions Support Bulk Entry

In AppSheet Weigh rounds, populated per-plant weight fields determine the weighed plants. Water requires selected watered plants. Water + weigh requires selected watered plants and at least one entered weight; the bridge handles each plant's actual combination. A selected watered pot can have no weight, and an entered weight can belong to a pot that was not watered. Do not assume every weight field belongs to the watered selection.

Shared bulk details must really be shared. In particular, a common water-volume value is applied to each applicable plant's record, not divided as a total for the entire round. Split the entries when measured volumes, application styles, nutrient details, or observations differ.

Saving, Queues, and Corrections

Retry the existing request after a connection problem rather than immediately creating a new observation. The queue and bridge use request identities to avoid duplicating a confirmed save. In AppSheet, use the receipt and supported retry/correction path; staging rows are not a second editable History.

Correct entry operates on one event, not every row from the same Save. Choose whether to edit its details, move it to another plant, or delete it. Each action requires a reason, a preview, and confirmation. A move shows the destination plant, label, and pot setup before saving. The observation time, measurements, and other untouched details are preserved.

The correction dialog keeps its action buttons visible while you scroll the form. Open Entry details for the saved setup, historical label, and observation ID. Back returns from the preview to your edits; Close keeps an unsent draft available to resume.

Edits and moves append a replacement and exclude the original from active calculations. Deletion excludes the original and saves an excluded audit record; neither record contributes to care history or calculations. Event type remains fixed. Repot entries cannot be moved or deleted through this form because other observations depend on their setup boundary. A date change or move with an uncertain setup can also be refused; coordinated setup changes need a separately reviewed correction.

Do not delete entire History rows, overwrite a formula on a Pxx page, or repeatedly add “fixed” measurements without excluding the incorrect ancestor. See the correction runbook for recovery behavior.

Example Saves

These examples explain how to record care. Use the daily report policy and each plant's readiness checks to decide which care is due.

Sources and Implementation References

• Logger source — WEB_EVENT_OPTIONS, BULK_WEB_EVENT_OPTIONS, prepareWebObservation_, buildEventNamesFromList_, eventDetailsFromPayload_, storedObservationRows_, and appSheetBulkPayloadsFromRow_.
• Mobile form source — field controls, queue, progress indicators, and correction interface.
• Logging behavior — canonical records and event-specific data.
• AppSheet companion — staging, round actions, receipts, and read-only views.
• Daily care and Integrity — the retired calendar and maintained check indicators.