Pasture work

Pasture Manager creates a task for a named pasture and cycle, chooses the work type, assigns a team member and sets a due date. The task can cover planting, irrigation, feeding, inspection or harvest. Its status distinguishes a plan from approved work, activity in progress, completion and cancellation. Field Operator should be able to find the current assignment without relying on a verbal handoff.

Approval is the manager’s decision about an actual planned task. The manager checks the pasture, cycle and assignee before marking it Approved. The task record then gives the operator a shared reference for field evidence. Completion uses the actual completion date; a due date alone cannot certify that the work happened.

• Prepare. Link the task to the pasture and cycle it serves, then assign the responsible team member.
• Decide. Pasture Manager reviews planned work and records approval before execution.
• Complete. Field Operator records progress and completion, including the actual completion time.

The status board supports a daily discussion between manager and operator. A task left Planned belongs in the approval queue. Approved work can be scheduled by its due date. In progress work remains open until someone records completion or a manager decides to cancel it. A completed task remains part of the cycle’s history even if the next plan changes.

Set the rule for who may assign work and who may change an approved task. Agree how much detail the five work types carry, especially when a feeding task consumes a stock lot. Decide whether the same person may both approve and perform a task under local policy. Configure permission checks on the actual user link through Team Members, rather than trusting a name typed into the task.

The manager should decide what happens when a pasture becomes Restricted after tasks were planned. Work may require a new review before proceeding. A cancelled task should remain visible in history, while a replacement task gets its own assignee and due date. These choices make the queue useful during busy weeks.

Start with a planned feeding task for an active cycle. Give it a due date and assign a Field Operator. Pasture Manager checks the location and cycle, then approves it. The operator records the task as in progress, links the feed used and records completion. Review the task board and the usage record together. The date on the task must describe when the work finished; the use date describes when the feed was consumed.

Repeat with a planned inspection for a Restricted pasture. Have the manager review its availability before approving anything. The exercise makes the decision point explicit and tests whether the team can still see cancelled or delayed work.

• Work Approval Queue — Planned tasks awaiting a manager’s decision.
• Approved Work — Assignments ready for operators to perform.
• Work Board — Approved, active and completed tasks grouped by status.

Use task execution for the daily handoff and feed accounting when the task consumes a lot.