These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Agriculture ERP
- Features
- Harvest acceptance
Harvest acceptance
Review the actual harvest and close its crop cycle only when field work is resolved.
OverviewHarvest Review×
Agriculture ERP · Harvest acceptance
New
Harvest Review
Harvests
| Id | Cycle | Harvested at | Quantity | Unit | Grade | |
|---|---|---|---|---|---|---|
| IDD-276 | CC-7589 | 06 Oct | 640 | UNT-954 | GRD-573 | |
| IDD-761 | CC-4296 | 15 Oct | 960 | UNT-154 | GRD-681 | |
| IDD-130 | CC-8316 | 08 Oct | 30 | UNT-378 | GRD-455 | |
| IDD-590 | CC-3651 | 06 Oct | 400 | UNT-113 | GRD-851 | |
| IDD-658 | CC-4646 | 09 Oct | 290 | UNT-600 | GRD-889 |
6 of 6 records
IDD-276Harvests · HRV-58298
CycleCC-7589
Harvested at06 Oct
Quantity640
UnitUNT-954
GradeGRD-573
What you can do
Let harvest evidence determine the next crop stage
A harvest records its actual date, quantity, unit and grade against the crop cycle. It also references the person associated with acceptance. Field Operator records the harvest evidence. Agronomy Reviewer decides whether to accept it through the controlled command. Keep the expected harvest date distinguishable from the crop cycle’s recorded actual date.
Acceptance validates the evidence and resolves the reviewer’s account through the linked staff record. A successful request updates the actual harvest date on the crop cycle. With field tasks still open, the cycle becomes Harvesting. With none open, it becomes Closed. Rejection and repeated acceptance write nothing, preserving the operating evidence already recorded.
How the work is organized
- Recorded harvest. Field Operator selects the intended crop cycle and enters the actual date and quantity in the agreed unit. Agree the meaning of the grade with Agronomy Reviewer before using that label in a season review.
- Reviewer decision. Agronomy Reviewer accepts through the command using the reviewing account. Check the account-to-person mapping during setup. Review the saved outcome alongside the harvest evidence so the team can explain who made the acceptance decision.
- Cycle outcome. Acceptance checks remaining field work and selects Harvesting or Closed accordingly. Review the actual harvest date separately from the expected date. A physically finished harvest can still leave the crop cycle open because an operating task remains unresolved.
What to agree during setup
Rehearse harvest entry and acceptance together. Agree how the operator records the person reference during entry and how the reviewer checks it against the acceptance outcome. Keep the review decision visible to the team rather than asking an operator to infer it from a name on the record.
Define the harvest evidence Agronomy Reviewer expects and the units operators may enter. Review the treatment of unfinished and Cancelled tasks with Farm Manager. Agree how the team follows a crop cycle left Harvesting after acceptance, including the later closing action once remaining work is resolved. Test that path during the pilot before relying on it in routine season review.
Check the handoff on an actual case
Record a harvest against East Plot’s crop cycle using its actual date and measured quantity. Leave an Inspection task open. Agronomy Reviewer accepts valid evidence, then checks that the crop cycle carries the actual harvest date and remains Harvesting. Farm Manager identifies who owns the unfinished task and agrees its next action.
Use a separate eligible case with no open tasks and confirm that acceptance selects Closed. Repeat the accepted request and verify that no further changes occur. Attempt acceptance with an account lacking reviewer authority, then try invalid harvest evidence. Both refusals should preserve the records. Keep the original reviewer attribution and actual date available when explaining the result to the operator.
What your team sees
- Harvest Review — Dated harvest evidence with its crop cycle, quantity, unit, grade and acceptance person.
- Active Crop Cycles — Crop stages and recorded dates for following the field work that remains.
Follow the work through
Rehearse harvest evidence to acceptance, then continue with yield evidence to season review.
What it keeps track of
Data model- Harvests
- Harvested quantities per crop cycle with grade and acceptance
- Crop cycles
- Crop cycles planted on a field from planning through closure
- Field tasks
- Assigned field work with lifecycle status and completion date
- People
- Farm staff and operators referenced by operational records
- Users
- Users
Who uses it
Permissions- Agronomy Reviewer
- Manages harvest acceptance and the affected crop cycle.
- Field Operator
- Records harvest evidence.
- Farm Manager
- Manages tasks that can keep the cycle open.
- Admin
- Configures agreed access for the rehearsal.
Set up Agriculture ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.