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.
- Agriculture ERP
- Features
- Field register
Field register
Keep each field's area, readiness and observations connected to the work planned there.
OverviewField Observation Log×
Agriculture ERP · Field register
New
Field Observation Log
Field observations
| Id | Field | Observed at | Observation type | Value | Unit | |
|---|---|---|---|---|---|---|
| IDD-754 | FLD-3901 | 07 Oct | OT-457 | 600 | UNT-692 | |
| IDD-852 | FLD-4278 | 09 Oct | OT-150 | 610 | UNT-995 | |
| IDD-845 | FLD-5267 | 13 Oct | OT-563 | 270 | UNT-464 | |
| IDD-774 | FLD-9197 | 04 Oct | OT-650 | 140 | UNT-918 | |
| IDD-932 | FLD-7542 | 11 Oct | OT-323 | 800 | UNT-707 |
6 of 6 records
IDD-754Field observations · FO-75011
FieldFLD-3901
Observed at07 Oct
Observation typeOT-457
Value600
UnitUNT-692
What you can do
Start with the field people actually work
A planting plan needs a field that everyone can identify. The field register keeps its code, name, area in hectares and location together with its operating status. Farm Manager uses Available, Planted, Fallow and Restricted to describe the plot. Agree what each value means before it guides an assignment. A Restricted field needs a manager’s decision about the work being considered there.
Field Operator records dated observations against the same field. The observation type, measured value and unit explain what was collected. Notes carry the context, such as where a sample came from or why a reading needs another look. Farm Manager can review that evidence alongside the planting intention and work attached to the plot.
How the work is organized
- Field identity. Agree the code used in the field and the name staff recognize. Keep the plot’s total area separate from the area intended for a particular planting. Check similarly named plots before importing plans or assigning work.
- Readiness. Farm Manager maintains the field’s status from its actual operating situation. Review the crop cycles and tasks attached to it before changing readiness. The person planning the work needs to understand why the plot was marked Fallow or Restricted.
- Observation evidence. Field Operator records the observation date, measurement type and unit with a useful note. Compare readings collected on the same basis. A changed measurement label needs review before earlier values are included in the same trend.
What to agree during setup
Choose the field naming convention and resolve duplicate names before importing plans. Decide who checks area and location information, and when Farm Manager reviews readiness. Use location descriptions the team can recognize during work, such as an entrance, an adjoining road or the farm’s own plot reference.
Agree a vocabulary for observation types and units. Decide how an operator distinguishes soil measurements from other observations and what a reviewer needs in the note. Keep the original measurement basis when bringing older observations into the register. Identify the person who resolves an unclear field reference before the reading is used in a planting discussion.
Check the handoff on an actual case
Use East Plot as a rehearsal case. Farm Manager checks its code and recorded area, then reviews why it is marked Restricted. Field Operator records a dated soil observation in the agreed unit and notes where the sample came from. Review that entry with the crop plan and task attached to East Plot before deciding what can proceed.
Open a similarly named field and confirm that the observation belongs to East Plot. Ask the operator to explain the measurement from the note. Farm Manager then checks the readiness decision against the planned work. Updating the field’s status and completing the linked task remain separate actions with their own responsible person.
What your team sees
- Field Readiness — Field codes, recorded areas and readiness values for the manager’s planting discussion.
- Field Observation Log — Dated measurements with their type, unit and notes for review against the field.
Follow the work through
Continue with field to crop cycle, then rehearse approved field work against the same field.
What it keeps track of
Data model- Fields
- Farm fields and plots with area and operational status
- Field observations
- Field measurements and notes captured during the season
- Crop plans
- Planned crop variety, planting and expected harvest per field
- Crop cycles
- Crop cycles planted on a field from planning through closure
- Field tasks
- Assigned field work with lifecycle status and completion date
Who uses it
Permissions- Farm Manager
- Maintains the field register and coordinates linked plans and work.
- Field Operator
- Records observations.
- Admin
- Handles the agreed access setup and rehearses the team's record access before invitations are widened.
Set up Agriculture ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.