1. Greenhouse Management
  2. Features
  3. Observations and readings
Feature · Observations and readings

Observations and readings

Keep dated field measurements and nutrient application records with their field.

OverviewField observations
Greenhouse Management · Observations and readings

Field observations

Field observations

New
IdObserved atObservation typeValueUnitNotes
IDD-60105 OctOT-470400UNT-642Observation 1
IDD-17108 OctOT-544540UNT-331Observation 2
IDD-23309 OctOT-689850UNT-857Observation 3
IDD-95909 OctOT-869130UNT-404Observation 4
IDD-69211 OctOT-817200UNT-285Observation 5
6 of 6 records
IDD-601Field observations · FO-65088
Observed at05 Oct
Observation typeOT-470
Value400
UnitUNT-642
NotesObservation 1
Example screen with sample data

What you can do

Put observations beside the work

A field observation has a date, observation type, measured value, unit and notes. It links to the field, where a manager can compare it with current crop cycles and tasks. Nutrient readings record an applied input name, quantity, unit, date, field and named applicator. Together they help the team reconstruct what was seen and what was applied in the growing area.

Keep the distinction between the two records clear. A scouting observation captures a measurement or finding. A nutrient reading captures an application. The grower who applies an input should be represented by the applicator link to their person record so the manager can follow the record to the right person.

How the work is organized

  • Observe. Record a dated field finding with its type, value, unit and useful notes.
  • Apply. Record the nutrient input, amount, unit, field and applicator after application.
  • Compare. Read the history beside the crop cycle and field task context.

Neither record should stand in for a harvest. Harvest quantities and grades belong on harvest records, where a reviewer can check the linked cycle. Likewise, a nutrient reading describes application to a field; stock consumption against a particular lot belongs on the input use record tied to a task.

What to agree during setup

Set a small vocabulary for observation types, units and input names. They are text fields, so consistent spelling makes filtering and comparison useful. Decide which observations need notes and who reviews an unusual value. The team should agree how soon after an application the grower enters a nutrient reading and how to correct an entry associated with the wrong field.

For input use, decide when the same activity also needs a field task and stock lot record. A feeding task and nutrient reading can describe the same real work from different angles; the team needs a common procedure to avoid conflicting quantities.

Check the handoff on an actual case

A grower scouts a field during a growing cycle and records a dated observation with a measured value and unit. The manager reviews it alongside the field and current tasks and assigns a feeding task if work is needed. After approval and application, the grower records the nutrient input, applied quantity, unit, date and their person identity. The stock controller records the lot consumption against the task. The manager can then read the observation, task, nutrient application and stock use in their respective records.

Repeat with the nutrient reading attached to the wrong field. Correct the field link before using the record for a field history report. Reconcile the application quantity and the lot use in their matching units.

What your team sees

  • Field observations — Read scouting dates, measurements, units and notes by field.
  • Nutrient applications — Review input, quantity, date and applicator by field.
  • Active crop cycles — Find the planting context for the field’s history.

Follow the work through

Use field work for the approval path and input stock and usage for lot reconciliation.

What it keeps track of

Data model
Field observations
Field scouting observations with measured value, unit and notes
Nutrient readings
Recorded input applications to a field by a named applicator
Fields
Farm fields and plots with area, location and availability status
People
Farm staff, operators, reviewers and managers with their authenticated user account and role title
Field tasks
Planned and executed field work assigned to a person for a specific cycle
Input usage
Input quantities consumed against a field task

Who uses it

Permissions
Grower
Records field findings and applications, Greenhouse Manager reviews them, and Stock Controller reconciles lot use.
Admin
Maintains access.

Set up Greenhouse Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started