A crop account should help a packing lead answer a plain question: what happened to the fruit we picked? Start with one identified harvest group and follow its records through the review. The useful result is an account people can explain, with open questions visible, not a confident yield number assembled from unrelated totals.
Follow one harvest group to a clear review point
Imagine a hypothetical small tomato grower preparing a weekly operations review. The harvest sheet and packing report do not seem to agree. Before calling that a crop problem, the packing lead asks whether both reports describe the same fruit. Some of today's packs may contain yesterday's harvest, while some fruit picked today may still be awaiting inspection.
- Group
- One identified tomato cycle; fruit picked from Tuesday 00:00 inclusive to Wednesday 00:00 exclusive.
- Review point
- Thursday at 12:00, using the same recorded site time zone.
- Owner
- Packing lead, with the grower and record owners resolving their respective questions.
- Question
- Which records explain this group's current position, and what still needs checking?
These invented times define membership and a later review point, not a recommended harvest schedule. Record the actual site time zone. Follow that membership even if downstream work continues after picking ends. Do not substitute a calendar-day pack total simply because its date looks convenient. Fruit not picked is outside this harvested group; that says nothing about the amount left on the plants.
Keep the records that were actually used. A harvest ticket, a pack record and a later correction should remain identifiable, with their versions and review times. The worksheet is a proposed way to bring those references together; it does not replace the original evidence.
Fruit from another cycle stays outside this account unless the account is deliberately redefined. Where staff cannot separate mixed fruit, record that limitation rather than assigning a confident cycle identity to every kilogram.
Check what each weight includes
NIST's weighing FAQ distinguishes gross load, packaging tare and net product content. Check which value a ticket already reports before calculating another quantity.
- Gross
- Product plus packaging.
- Tare
- The packaging contribution.
- Net
- Product content, excluding that packaging.
- Already net?
- Do not subtract the same tare again.
Preserve units, ticket references and the material's weighing condition. Display rounding can affect apparent agreement. An unknown basis needs checking, not an assumed conversion. These definitions supply no scale approval, legal tolerance or proof of measurement accuracy.
Separate grade from the fruit's current state
NC State Extension's field-loss guidance notes that marketability depends on buyer specifications. The account therefore needs its actual local classification, not an assumed universal meaning for saleable.
| Recorded description | Interpretation |
|---|---|
| Local grade A, packed | Classification and current state are both recorded. |
| Local grade A, held | The same grade can still await a decision. |
| Grade not assigned | Classification remains unknown. |
A lower grade is not automatically a discard. A saleable label does not establish food-safety clearance, customer acceptance, dispatch or uncommitted stock.
Follow the work without creating another harvest
Return to HT19-01. Suppose staff replace an outer pack during handling. The new pack record describes a task performed on fruit already in the group. It does not describe another picking event. A dashboard that celebrates every completed pack task as new output can tell a very different story from the physical work.
- Identify the original fruit group and pack reference.
- Record the repacking task and receiving pack reference.
- Record any physically removed material separately.
- Identify the fruit's current state at the review cutoff.
Retain both pack references so a reviewer can see why two tasks refer to the same product. A replacement identifier is useful only when its relationship to the earlier one is clear. If that connection is missing, show an identity question instead of guessing from the operator, time or visual similarity.
The same caution applies to trim records. A description such as rejected may describe a classification decision, a proposed action or a completed removal. Ask which event the record actually confirms. Do not let a tidy status label answer a physical question it was never designed to answer.
Keep the arithmetic remainder open to investigation
The CEC food-loss measurement guide explains input/output accounting and its data limitations. For this proposed cohort worksheet, assume compatible product weights and non-overlapping states at one cutoff.
| Entry | kg |
|---|---|
| Harvest input | 100 |
| Packed local grade A | 70 |
| Packed local grade B | 12 |
| Held | 8 |
| Recorded trim/discard | 6 |
The remainder is 100 - (70 + 12 + 8 + 6) = 4 kg. That is unresolved, not verified waste or its cause. The packed figures include repacked fruit; do not add it again. Unknown required quantities make the balance uncomputable. Retain negative remainders too. Do not invent water-weight adjustments to force agreement. Trim already included in recorded discards is counted only once.
Show what was measured and what was assigned
Separate from that invented account, consider a practical exception: two crop cycles arrive together, and the only surviving ticket describes the combined load. A grower may still need a cycle-level report. That need does not create a separate measurement for each cycle.
- Measured pool
- The ticket describes the combined material within its stated scope.
- Calculated value
- Identified inputs and a stated calculation, not another independent weighing.
- Assigned share
- A recorded rule attributes part of that pool to a cycle.
- Unassigned
- No supported split is available.
- Outcome pending
- A quantity may be known while its later disposition remains undecided.
If a locally agreed assignment rule is used, identify the rule, who approved it and what evidence it uses. Label the resulting cycle quantity assigned, not measured. Do not use the presence of a precise decimal to imply that someone weighed that cycle separately.
There may be a sound business reason to keep a provisional allocation. Make that a visible reporting choice, not an invisible repair. A reviewer should be able to find the measured pool and distinguish it from the cycle shares without reconstructing a spreadsheet's hidden formulas.
Keep quantity evidence separate from outcome evidence. A held container can have a known weight and an unknown later outcome. A completed removal can have a known destination but an unrecorded quantity. One complete field does not fill in the other.
When the limitation matters to a decision, report the limitation. More attractive totals do not justify inventing the missing split, borrowing a nearby cycle's result or quietly treating an unobserved value as zero.
Finish with a review finding, not a convenient story
The packing lead needs a short list of questions they can resolve with the people who own the records. Give each question a reference and a next step. A blanket instruction to improve data quality is less useful than knowing which ticket or classification needs attention.
| Question | Next check |
|---|---|
| Ticket missing | Record owner checks the original evidence and marks what cannot be recovered. |
| Mixed cycle identity | Grower and packing lead review the group references. |
| Decision pending | Authorized owner records the assessment and its current status. |
| Correction proposed | Keep the original, reason, author and revised record linked. |
AI can extract stated values and references from readable tickets, summarize the open questions and draft a review note. Deterministic software should check the stated arithmetic, duplicate identifiers and required fields. Neither can manufacture a missing physical observation or decide that fruit is suitable for use.
A zero remainder would not prove that every underlying record was measured or every classification resolved. Keep those evidence limits visible even when arithmetic agrees.
Retain an accepted-with-limits or still-open finding when appropriate. The authorized people decide whether another observation, a corrected record or a documented reporting limitation is needed. Accounting acceptance is not product-release permission.
The practical gain is a better conversation about the actual work: which evidence is dependable, which process handoff is unclear and what the next review should check. Do not promise recovered yield or savings from the existence of the worksheet alone.