Field work

Field work connects a task type to a specific field and crop cycle. Farm Manager assigns a Team Member as owner and sets a due date. The task can be Planned, Approved, in progress, Completed or Cancelled. These states help operators distinguish proposed work from work they can execute and give managers a way to review completion.

The field and cycle references both matter. If a task points to a field that differs from the cycle’s field, the manager should resolve that mismatch before approval. An irrigation task for the wrong plot can make later input use and reporting misleading. The owner is a Team Member linked to a user account, so the assignment is more precise than a typed name.

• Plan. Select task type, field, cycle, owner and due date while work is still Planned.
• Approve. Farm Manager reviews the context before changing the task to Approved.
• Complete. Field Operator records completion date when the task is finished.

Agree who may approve a planned task and when a manager should cancel it instead. Define when operators change Approved work to in progress and what evidence is needed for Completed. A task can remain visible after its due date; the manager should review it rather than treating a calendar date as proof of execution.

For input bearing work, agree how stock lots and field applications are recorded alongside the task. The task is the link for consumed stock. A separate field application identifies what was applied to the field, by whom and in what unit. Match these records during review so a field activity and its stock effect tell the same story.

Create a Feeding task for a Growing crop cycle, assign an active operator and set a due date. Farm Manager reviews field and cycle and approves the task. The approval records input use against the task and reduces the eligible lot balance. The operator opens My field work, checks the recorded use and records completion. The manager checks the resulting status, use and completion date against the task’s field and owner.

Try a task whose cycle belongs to another field. Resolve the mismatch before approval. Also inspect an overdue Planned task and confirm that it remains a planning exception, not completed work. These cases help the team agree what an approved instruction actually authorizes.

• Planned field work awaiting approval — Review task context before work is approved.
• My field work — Let operators find their assigned tasks and due dates.
• Active field work board — Compare planned, approved and in-progress work by owner.

See field work and input use.