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
- Yield grading
Yield grading
Retain accepted and rejected weights for the exact harvest being graded.
OverviewYield Grade Detail×
Agriculture ERP · Yield grading
New
Yield Grade Detail
Yield grades
| Id | Harvest | Grade | Accepted weight | Rejected weight | Unit | |
|---|---|---|---|---|---|---|
| IDD-919 | HRV-6309 | GRD-105 | 160 | 80 | UNT-997 | |
| IDD-512 | HRV-3353 | GRD-340 | 100 | 230 | UNT-489 | |
| IDD-930 | HRV-6012 | GRD-789 | 70 | 100 | UNT-537 | |
| IDD-744 | HRV-3676 | GRD-274 | 180 | 200 | UNT-405 | |
| IDD-609 | HRV-1191 | GRD-103 | 200 | 70 | UNT-669 |
6 of 6 records
IDD-919Yield grades · YG-96449
HarvestHRV-6309
GradeGRD-105
Accepted weight160
Rejected weight80
UnitUNT-997
What you can do
Keep each grade attached to the harvested evidence
Yield grading records the grade, accepted weight, rejected weight and unit against the exact harvest. The reference lets Agronomy Reviewer follow the measured outcome to that harvest and its crop cycle. Field Operator captures evidence through the authorized grading command, while Agronomy Reviewer manages the recorded grade detail.
The command validates evidence before saving and refreshes the linked crop cycle’s harvest detail. A repeated harvest and grade returns the original record. Agree a separate correction procedure when a measurement changes. The team needs to distinguish recovery of a saved submission from a new decision about the measured output.
How the work is organized
- Harvest selection. Choose the exact harvest before recording a grade. Check its crop cycle, actual date, quantity and unit. Similar crop descriptions and repeated harvest dates need enough context for the operator to identify the intended source.
- Weight detail. Keep accepted and rejected weights in the declared unit. Agree grade labels before reviewing totals. Compare grading with the harvested quantity only when the measurement basis agrees, and leave unexplained differences visible for Agronomy Reviewer to investigate.
- Repeated submission. Use the same harvest and grade when recovering the original command result. Review the returned record before submitting anything else. Agree who handles a mistaken weight and how the original evidence remains understandable after a correction.
What to agree during setup
Name the person who records weights and agree what evidence Agronomy Reviewer expects. Define grade labels and permitted units with the farm’s own working examples. Keep those conventions consistent across harvest entry, grading and review. Decide how the team handles mixed units before they appear together in an output discussion.
Configure the grading command for the intended Field Operator account and rehearse it separately from general grade-record management. Agronomy Reviewer manages the recorded evidence. Test the command with valid and invalid weights, and agree how the reviewer investigates a difference against harvested quantity. Keep the actual result and source references available when the operator needs help recovering a submission.
Check the handoff on an actual case
For a rehearsal, choose a harvest recorded as 300 kilograms. Capture a grade with 270 kilograms accepted and 30 kilograms rejected. Submit through the authorized command, open the saved grade and follow its harvest reference back to the intended crop cycle. Agronomy Reviewer compares the combined weights with the harvest quantity in the same unit before drawing an output conclusion.
Repeat the same harvest and grade and confirm that the original record is returned. Test an unauthorized account and invalid grading evidence, then compare the grade and linked cycle detail before and after refusal. If the farm needs to correct the saved weight, rehearse that procedure separately with Agronomy Reviewer. Recovering a repeated submission should preserve the earlier result rather than quietly replace it.
What your team sees
- Yield Grade Detail — Grade evidence with its harvest, accepted weight, rejected weight and unit.
- Rejected Yield Weight — Grade records with positive rejected weight for reviewer follow-up.
Follow the work through
Use yield evidence to season review and confirm the preceding harvest acceptance decision with its reviewer.
What it keeps track of
Data model- Yield grades
- Accepted and rejected weights graded from a harvest
- Harvests
- Harvested quantities per crop cycle with grade and acceptance
- Crop cycles
- Crop cycles planted on a field from planning through closure
Who uses it
Permissions- Agronomy Reviewer
- Manages grading records and reviews their harvest context.
- Field Operator
- Captures evidence through the authorized grading command.
- Admin
- Configures the agreed command and reading access during setup.
Set up Agriculture ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.