These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Farm Management System
- Features
- Observations and applications
Observations and applications
Capture field measurements and named input applications.
OverviewField Observations×
Farm Management System · Observations and applications
New
Field Observations
Field observations
| Observed at | Observation type | Value | Unit | Field | |
|---|---|---|---|---|---|
| 11 Oct | OT-785 | 260 | UNT-590 | FLD-7801 | |
| 03 Oct | OT-619 | 100 | UNT-782 | FLD-5577 | |
| 05 Oct | OT-408 | 380 | UNT-510 | FLD-4789 | |
| 09 Oct | OT-572 | 170 | UNT-314 | FLD-8399 | |
| 09 Oct | OT-441 | 710 | UNT-596 | FLD-5818 |
6 of 6 records
OT-785Field observations · FO-91447
Observed at11 Oct
Value260
UnitUNT-590
FieldFLD-7801
What you can do
Work from the field record
Field observations keep a date, observation type, measured value, unit and notes with the field. Input applications keep an application date, input name, quantity, unit and named applicator with the field. Both records help the team understand what happened at a plot.
How the work is organized
- Identify the work. Start from a field and a dated scouting observation.
- Record the event. Record its measured value and unit; record any input application separately.
- Review the result. Field Operator links the application to the field and named applicator.
Agree which measurements crews will record, the units to use and when an observation should be entered. Match the person named on an application to the work actually performed. Compare field application records with related task usage when both describe the same activity.
What to agree during setup
Agree which observation types and units crews will use. Decide when an application needs a separate task and usage record as well as the field entry. Keep the linked People and Users records current so the named operator or reviewer can be found during the rehearsal.
Check the handoff on an actual case
For a growing crop with a scouting concern, open the field history, compare prior measurements and notes, then create a new observation with its date and unit. If an input is applied, record the applicator and quantity against the same field. Follow the crop cycle and assigned task when planning the next inspection.
Ask Field Operator to record the new observation and a separate application with the correct field and applicator. Farm Manager compares these with the current crop cycle before planning inspection. Open the live record again after a deliberate change and agree who corrects it before the next step.
A field observation can explain why Farm Manager changes the next inspection task. Its measured value stays with the dated scouting record. An application names the input and applicator at the field; if stock was consumed through approved work, trace that quantity through the separate task-linked usage record.
What your team sees
- Field Observations — Shows dated scouting measurements and notes by field.
- Input Applications — Shows what was applied, when, and by whom on each field.
Follow the work through
See the field-to-harvest flow and the data model. The implementation guide gives a small rehearsal scope before a wider operating cycle.
What it keeps track of
Data model- Field observations
- Field scouting observations with measured value, unit and notes
- Input applications
- 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
Who uses it
Permissions- Field Operator
- , Farm Manager, Admin.
- Field Operator
- Records observations and applications; Farm Manager uses them to plan follow-up; Admin maintains user access.
Set up Farm Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.