Recording Harvest Data: Weights, Grades and Mortalities for Traceability

Harvest data is likely the single record most frequently referenced by outside parties — buyers confirming what they are purchasing, auditors reviewing traceability, and the farm's own future planning comparing this cycle's performance against history — which makes it worth structuring deliberately rather than treating as an informal tally sheet filled in quickly on a busy harvest day.

Core fields for every harvest record

• Batch or cohort identifier, tracing back through the farm's stocking records to the original stocking event and, ideally, back further to the hatchery batch ID covered in the hatchery record-keeping guide — this linkage is what makes full farm-to-fork traceability possible.
• Harvest date and system ID (pond, cage or tank harvested), matching the consistent identifiers used throughout the farm's other records.
• Total weight and count or estimated count, using the methodology covered in the companion counting and weighing guide, with the estimation method noted alongside the figure.
• Grade or size-category breakdown, where the harvest involves grading, feeding into both sales documentation and the farm's own size-distribution performance tracking.
• Mortality during harvest, logged separately from the successfully harvested total, since harvest-related mortality is its own useful data point distinct from pre-harvest standing mortality already captured in the farm's routine mortality records.
• Destination or disposition — which buyer, which sale, or internal transfer destination the harvested product is going to, closing the traceability loop from farm to the next point in the supply chain.

Linking harvest records to the full production history

A harvest record that stands alone, disconnected from the stocking, feeding and water-quality records that preceded it, loses much of its diagnostic value — linking the harvest outcome back to the full cycle's history (stocking density, feeding programme used, any notable health events, water-quality trends) is what lets the farm actually learn from each cycle's results rather than treating each harvest as an isolated event with no connection to the management decisions that produced it.

Using harvest data for performance comparison

Comparing harvest outcomes across cycles — yield per unit area, survival rate from stocking to harvest, grade distribution — against the farm's own historical baseline reveals trends an auditor's or buyer's single-cycle view would never show: a gradually improving or declining pattern, a seasonal effect, or the impact of a specific management change tested across successive cycles. This comparative use is often the most operationally valuable application of harvest data, beyond its compliance and sales-documentation functions.

Supporting buyer and certification requirements

Many buyers and virtually all serious certification standards expect harvest records to support full traceability — confirm the specific documentation format and retention requirement for the farm's actual buyers and target certifications, since requirements vary and a record structure adequate for one buyer or standard may fall short of a different one's specific expectations. Building the farm's standard harvest-record template to meet the most demanding current requirement, rather than the loosest, avoids needing to retrofit records later when a new buyer or certification imposes stricter expectations.

Digital versus paper harvest records

The same considerations covered in the farm's broader water-quality and cage-logbook record-keeping content apply here — either format can work provided the core discipline (consistent identifiers, complete fields, backup and tamper-evidence) is maintained, with digital systems generally easing the cross-referencing and trend-comparison work that makes harvest data genuinely useful beyond simple compliance documentation.

Worked example

A farm preparing for a new buyer's onboarding audit discovers its existing harvest records, adequate for its previous buyers, do not link harvest batches back far enough to satisfy the new buyer's full farm-to-fork traceability requirement — the records stop at the stocking event without a clear link back to the originating hatchery batch. The farm retrofits its template to carry the hatchery batch ID through stocking and harvest records going forward, and for the new buyer's immediate onboarding, manually reconstructs the missing linkage for recent harvests from its separate hatchery records, flagging the reconstruction explicitly rather than presenting it as originally captured. The new buyer accepts the reconstructed linkage given the transparency, and the farm's updated template now meets the stricter standard automatically for all future harvests without needing retrofit again.

Common mistakes

• Recording harvest totals without linking back to the originating batch or stocking record, breaking full traceability.
• Logging only successfully harvested totals without separately tracking harvest-related mortality.
• Treating each harvest's record as an isolated event rather than comparing against the farm's own historical performance trend.
• Building a harvest-record template to meet only the loosest current buyer or certification requirement rather than the most demanding one likely to apply.

Frequently asked questions

How long should harvest records be retained?

Follow the same retention standard as the farm's other core compliance and production records, generally multiple years depending on the specific certification or regulatory requirement — defaulting to a longer retention period than any stated minimum, where storage cost allows, protects against a future need to reference older records that a minimum-compliance retention policy would have already discarded.

What's the relationship between harvest records and the withdrawal-period compliance covered elsewhere in this cluster?

Harvest records should explicitly confirm and reference any applicable withdrawal-period clearance before the harvest date, linking the harvest event to the medication and withdrawal-tracking records covered in that companion guide — this linkage is specifically what an auditor or regulatory reviewer would check to confirm a harvested batch was genuinely cleared before sale.

Should harvest records capture quality observations beyond weight and grade?

Where relevant and practical, yes — notable quality observations (off-flavour testing results, any processing issues observed) add useful context, particularly for a harvest showing an atypical outcome that future review might need to understand the specific circumstances behind.

How should harvest data be shared with buyers who request traceability documentation?

Prepare a standard summary extract from the full internal record — batch linkage, harvest date, relevant quality and compliance confirmations — rather than sharing the farm's complete internal record system, which may contain more detail than a given buyer needs or than the farm wants to share broadly; maintain the fuller internal record for the farm's own and certification-audit purposes.

Does harvest record-keeping differ for a single large harvest versus multiple partial harvests from the same pond?

Each partial harvest event should be recorded individually with its own date, volume and grade data, all linking back to the same originating batch or stocking record — treating a series of partial harvests as a single combined record loses the event-level detail that both the farm's own trend analysis and full traceability documentation depend on.