Farm Manager decides which assigned work may proceed. Field Operator records the actual work through a command that checks the whole request before posting usage or changing stock. Keep the field, crop cycle and assigned person together throughout the handoff.
Farm Manager selects the field and crop cycle, chooses the task type and sets its due date. Assign the staff member whose linked account will execute the work. Confirm the intended plot before preparing an application.
Farm Manager approves the task's scope and assigned operator, moving it from Planned to Approved. Manager may decide where the farm has configured delegated task approval. Confirm the decision before execution begins.
Field Operator submits the assigned task with the actual applied date and input usage. The command checks lifecycle eligibility, linked field and cycle, operator identity and every lot's existence, unit, expiry and remaining quantity before writing.
Field Operator's valid request records usage against the task and input lot, deducts stock once per lot and marks the task Completed. The completion date reflects the actual applied date. Review the saved usage against the physical application.
Field Operator repeats the request to obtain its original saved result after an uncertain response. Check the task and lot quantities before continuing. A repeated request must preserve the earlier usage and deduction.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.