Fields and Boundaries

Farm Manager gives each field a name and code that the crew can recognize. The register keeps its area and location beside its availability state. Available, Planted, Fallow and Restricted give the manager a way to distinguish land ready for consideration from land already in use or requiring a separate decision.

Field Surveyor records boundary geometry against that field, together with the survey date and area in hectares. The capture should resolve the correct field before it is saved. A familiar plot name helps the operator find the location, while the field reference keeps the survey connected to the same record used by crop cycles and work tasks.

• Field identity. Use the field code, name and location consistently when planning work. Review the recorded area before relying on it in an operating discussion, especially where neighboring plots have similar names.
• Availability review. Farm Manager records the state that describes how the field is being used. A Restricted field needs its situation resolved before the team treats it as available for work. Fallow and Available should have agreed meanings for the farm.
• Survey evidence. Keep the geometry, survey date and surveyed area together. Review a new capture against the intended field and confirm that the person submitting it is signed in under the correct team identity.

Agree the field naming convention before importing crop or task records. Decide who maintains the register and who captures surveyed geometry. Establish how the team compares the register’s area with a new survey and who decides whether an area should be updated.

Use hectares consistently for the recorded field and boundary areas. Agree how survey material arrives and what needs review before it is saved. If geometry comes from a separate survey tool, set up that handoff and confirm which person checks the resulting field reference. Keep access to field changes limited to the people responsible for maintaining the farm plan.

Use a pair of adjacent plots with similar local names. Farm Manager selects the intended field by its code and location. Field Surveyor prepares a boundary capture with its survey date and area, then confirms the linked field before saving it.

During rehearsal, choose the neighboring field deliberately and check that the reviewer can identify the mistake. Correct the reference before the capture becomes part of the planning discussion. Then compare the surveyed area with the field register and agree how any difference will be resolved.

Finally, put the correct field into a crop plan and a work task. The team should be able to follow both records back to the same field without relying on a typed plot name. Review its availability again before approving the planned work.

• Field Register — Field codes, areas and availability states support the manager’s plot selection.
• Boundary Survey History — Survey dates and geometry remain attached to the field they describe.

Start with field and cycle preparation, then follow approved field work.