Field work

A field task links the field, crop cycle and assigned staff member. Its type identifies Planting, Irrigation, Feeding, Inspection or Harvest work. The due date tells the operator when the work is expected. The completion date retains when it actually happened. A task can be planned, approved, in progress, completed or cancelled.

Farm Manager reviews planned work before Field Operator executes it. The execution command checks the task’s lifecycle state, field and cycle links and assigned operator identity before writing. Any input application stays attached to that task, so the manager can follow the completed work back to its instruction and the lot used.

• Task preparation. Farm Manager chooses the field and crop cycle together, sets the task type and due date, and assigns the intended staff member. Check that person’s linked account during setup so the operator can execute the correct assignment.
• Manager decision. Farm Manager moves planned work to Approved after checking its scope and assigned person. Where the farm delegates this decision to Manager, configure that authority explicitly. Review a changed assignment before the operator relies on the earlier decision.
• Execution result. Field Operator submits actual work through the guarded command. Successful execution posts input usage, reduces stock once per input lot and completes the task using the actual applied date. Repeating the request returns the original saved result.

Define when a task is ready for approval and who may change its assignment afterwards. Rehearse execution with the task states the farm intends to use. Keep the manager’s decision visible before work begins and agree who resolves a refused request when the state or assignment needs attention.

Set up My Field Work using the current account’s linked staff record. Test with distinct operator accounts, including people with similar names. Decide how Farm Manager follows unfinished work and handles Cancelled tasks. Review those outcomes with Agronomy Reviewer because unresolved work affects the crop cycle’s harvest-acceptance outcome.

Prepare a Feeding task for East Plot’s growing crop cycle and assign the intended Field Operator. Farm Manager reviews its due date and planned application, then marks the task Approved. The assigned operator executes it with a reviewed input lot and the actual applied date.

Confirm that saved usage points back to this task and lot. Compare the lot’s remaining quantity with the recorded application and check the completion date. Repeat the command and verify that it returns the saved result without another usage record or deduction. Attempt execution as another operator and confirm that refusal leaves the task and input records unchanged. Record who will resolve a genuine assignment error before routine work begins.

• Planned Field Work — Planned assignments for the manager’s scope and approval decision.
• My Field Work — Tasks assigned to the staff record linked to the current operator’s account.
• Overdue Field Work — Unfinished tasks due today or earlier for the team’s follow-up.

Rehearse approved field work. Follow completed harvesting work into harvest evidence to acceptance.