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
- Fields and boundaries
Fields and boundaries
Keep field identity, area, location and surveyed geometry together.
OverviewAvailable Fields×
Farm Management System · Fields and boundaries
New
Available Fields
Planted waits for the farm manager
| Field code | Name | Area hectares | Location | Status | |
|---|---|---|---|---|---|
| FC-670 | Field 563 | 920 | D-1 | Available | |
| FC-395 | Field 274 | 570 | T-2 | Available | |
| FC-373 | Field 805 | 20 | C-3 | Available | |
| FC-911 | Field 966 | 230 | Y-1 | Available | |
| FC-557 | Field 445 | 500 | X-3 | Available |
6 of 6 records
FC-670Fields · FLD-69788
AvailableNameField 563
Area hectares920
LocationD-1
What you can do
Work from the field record
Begin with the field name and code that crews recognize. The farm manager records its location and area, then chooses whether the plot is available, planted, fallow or restricted. A restricted field should stay visible in planning discussions so a crop cycle is not assigned there by habit.
How the work is organized
- Identify the work. Start with the field code, name and location so the crew can identify the plot.
- Record the event. Keep the survey date and area beside the geometry on the boundary record.
- Review the result. Farm Manager compares the area and availability on the field with the dated survey before assigning a cycle.
The surveyed outline carries its own survey date and measured area. Compare that figure with the area on the field record before relying on either number for planning. The field identity remains the link between boundaries, crop cycles, observations and tasks.
What to agree during setup
Agree who may change a field from Fallow to Available, and who checks a newer survey against the existing field area. 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 plot returning from fallow, open its field record, check the location and latest boundary, then decide whether its availability status should change. Follow the linked crop cycle before assigning planting work. A boundary update should preserve which field the survey describes.
Ask Field Operator to locate the plot by code and location. Compare the survey area with the field area before Farm Manager changes availability. Open the live record again after a deliberate change and agree who corrects it before the next step.
A field can keep its identity across later surveys. When the surveyed area changes, compare the new date and geometry with the field record before planning more work. Keep the boundary attached to the same plot so observations, applications and crop cycles remain traceable through that field.
What your team sees
- Available Fields — Lists plots ready for crop planning, including code, area and location.
- Restricted Fields — Flags plots that need a manager decision before new work.
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- Fields
- Farm fields and plots with area, location and availability status
- Field boundaries
- Surveyed field boundary geometry with survey date and area
Who uses it
Permissions- Farm Manager
- , Field Operator, Admin.
- Farm Manager
- Owns the field decision; Field Operator confirms the plot on the ground.
- Admin
- Maintains linked 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.