Field work

A field task carries the work type, due date, field, crop cycle and assigned person. That combination gives the grower a clear job and gives the manager a way to review whether the work belongs to an active cycle. Planting, irrigation, feeding, inspection and harvest are the task types available to the team. Keep separate tasks when the type, due date or assignee changes rather than letting a broad task stand for several distinct activities.

A planned task waits for manager review. Approval is the point where the team checks the field and cycle and confirms that the assigned person can carry out the work. Execution can then move through active work to completion. A cancelled task remains visible as a cancelled assignment; it should not be counted as completed work.

• Assign. Choose the work type, field, linked cycle, due date and person responsible.
• Approve. The manager checks the current field and cycle before releasing the task.
• Complete. The grower records completion and the manager checks the result against the cycle.

The assignee link resolves through the people record, which also connects to the user’s account. Teams should keep those links accurate before assigning field work. A typed person name in a note is no substitute for an assigned person on the task.

Agree what evidence is enough to mark each kind of task complete. A planting task may call for its completed date and a cycle stage update; an inspection may call for a separate dated observation. For irrigation or feeding, decide when a stock use record is required and which stock lot is used. The stock unit and recorded use unit must match in the operating procedure before the balance is adjusted.

The manager should define who can approve tasks and who can amend a due date after approval. If a field becomes restricted or a cycle closes, review outstanding tasks before letting them continue. Keep the task’s field and cycle aligned so a grower does not receive work on the wrong planting.

A manager plans a feeding task for a growing basil cycle and assigns it to a named grower. The grower checks the assigned task and due date on the field work board. The manager checks that the field and cycle are active and approves it. The grower completes the application, records the completion date and links the consumed input to the task. The stock controller compares that use with the selected lot balance and expiry. The manager can then review the completed work alongside the cycle’s observations.

Repeat the case after changing the field to Restricted. The manager should review the task before approval and keep the affected work in a clear state. This rehearsal establishes who resolves a conflict between a planned assignment and the current field record.

• Field work board — Find assigned work and its current status.
• Tasks awaiting manager approval — Review planned assignments before execution.
• Approved and active field work — Follow work released for execution.

Use field work for the approval and completion path. Review the linked input records before expanding the pilot.