Field plan to authorization

Prepare a spray or pest operation for a client farm and take one revision through an independent review decision.

Step by step

Draft the operation Operations Planner

Operations Planner records the subject, farm, crop or animal, planned date, planned quantity and unit. The operation starts as Draft and the planner is its owner.
- Operation created at Draft
- Updates Field operations, Farms
Add planning evidence Operations Planner

The planner adds evidence lines, such as trap counts or soil moisture, and attaches files such as the product label.
- Evidence lines and files added
- Updates Agronomy evidence, Record attachments
Plan or send to review Operations Planner

The planner moves the operation to Planned, or to Review when the work needs a professional's sign-off. The current revision number goes with it.
- Draft → Planned, or Draft → Review
- Updates Field operations
Decide on the revision Domain Reviewer

A Domain Reviewer in the same organization, who did not prepare the plan, records Approve, Reject or Return with a reason against that revision. Approve moves the operation to Authorized.
- Decision recorded; Review → Authorized on Approve
- Updates Review decisions, Field operations
ApprovalA person approves before the work moves on.
Revise after a return Operations Planner

A returned plan goes back to the planner. Any change raises the revision and the plan returns to Review for a new decision.
- Revision raised and resubmitted
- Updates Field operations, Operation receipts

And how to keep it from happening.

The planner changes the date after approval and the crew acts on the old decision.
The reviewer is the same person who drafted the plan.
A plan goes to Review without current trap counts, so it comes back as Return.
Work is planned for a farm whose eligibility note does not cover it.

Start free, then use Proto to change fields, steps and approvals before your team goes live.