Two dates get written on farm paperwork that look interchangeable and are not: the day a crop was harvested, and the day it was packed into the container it ships in. On a small operation picking and packing the same afternoon, the distinction barely shows up — both dates are the same, and nobody notices there were ever two questions being answered by one number. The distinction becomes consequential the moment those two events separate in time, which happens more often than people expect: cold storage before packing, a packing line that runs behind the harvest by a day or two, or a multi-day pick boxed together in one run.
An investigation that reaches your farm is not asking a generic question about “when.” It is asking one of two specific questions, and each has a correct date attached to it. Confusing the two does not just produce an imprecise answer — it can point the investigation at the wrong population of product entirely.
The confusion is understandable, because both dates genuinely describe the same physical carton, and in casual conversation “when was this picked” and “when was this packed” sound like variations on one question rather than two distinct ones. They are distinct because they trace back through entirely different chains of custody — one through the field and the crew that harvested it, the other through the wash line, the packing shift, and the equipment that touched it after harvest.
Harvest date answers a field question; pack date answers a process question
The harvest date locates a lot in the history of a field: what was planted, what was applied to it, and when it was removed from the ground or the tree. It is the date that matters for a spray or input record question — was this product harvested before or after a re-entry interval elapsed, which field did it come from, what season’s conditions produced it.
The pack date locates a lot in the history of a process: which wash water, which packing line, which shift, which equipment. It is the date that matters if a problem is traced to the packing operation itself rather than to the field — a sanitation issue in a wash tank, say, which would implicate every lot packed through that tank on a given day regardless of which field each one came from.
Neither date is more important in the abstract; they simply serve different investigators. A certifier auditing your organic practices cares almost entirely about the harvest date and what it connects to in the field. A food-safety inspector responding to an illness cluster traced to packing-line contamination cares almost entirely about the pack date and what it connects to on the line. A farm that can answer only one of the two questions will satisfy exactly half its visitors.
Build the lot code from the harvest date, not the pack date
This is where the distinction stops being academic. A lot code built from the pack date describes a packing run, not a planting — it tells you that several days’ picking went into cartons on a given afternoon, but it cannot tell you which field or which day’s harvest is inside any particular carton, because by pack time that information may already be mixed. A code built from the harvest date keeps the field link intact, because harvest is the moment the field information is still attached to the product.
Where packing genuinely combines multiple harvest days — which is common and not itself a problem — the honest response is not to rename the mixed batch with a single new harvest-style code. It is to treat the combination as a merge, the same way two lots combined in a bin get a merge record: note which harvest dates went into the pack run, and let the pack date describe the run while the harvest dates it references stay visible.
An investigation walks toward whichever date fits its question
When a complaint or a lab result arrives, the first useful move is to figure out which of the two questions it is actually asking, because that determines which date — and which set of records — to pull. A residue or contamination concern tied to a specific agronomic event walks toward the harvest date and the field records behind it. A concern tied to hygiene, equipment, or handling walks toward the pack date and the packing operation’s own records — water tests, sanitation logs, staffing on a given shift.
Farms that only record one date, and treat it as answering both questions, discover the gap exactly when it is least convenient: midway through a trace, when the date they wrote down turns out to answer the wrong one of the two questions the investigator is actually asking.
Recording both costs one extra field, not a new system
The fix is not a new record-keeping system. It is one additional field on the harvest sheet and the pack sheet, filled in separately even when the two dates happen to match. A form that only has room for “date” forces every user to silently choose which of the two meanings they intend, and that choice will not always be the same person making it the same way twice.
Where the two dates are genuinely identical — same-day harvest and pack, common on small diversified operations — write both anyway. The redundancy costs nothing, and it removes any ambiguity for a reader who was not there and cannot tell, from a single date, whether same-day packing was actually confirmed or simply assumed.
A simple habit enforces this without adding a step: make the harvest sheet and the pack sheet two different pieces of paper, or two different rows in a spreadsheet, even on days when they will hold identical dates. A single combined sheet with one date column invites exactly the shortcut this page argues against — one number silently doing two jobs, correctly until the one day it does not.
Where a linked record keeps both dates without extra entry
Farm40 records a harvest event and a pack or sale event as separate, linked entries rather than a single date field, so a lot carries both its harvest date and, where relevant, the date it was packed or shipped, without either overwriting the other. The limit is unremarkable but worth stating: the software distinguishes the two dates only because they were entered as two events. A farm that enters one date and calls it both has the same ambiguity on a screen that it would have on paper. For the wider discipline this detail supports, see the traceability guide.