How to Build an FDA-Ready Harvest Log for FSMA Traceability

When an FDA investigator or state agricultural inspector reviews your farm or packing records, the important question is not which software you use. It is whether your records are complete, accurate, maintained as required, and—where the Food Traceability Rule applies—able to show the required relationships between traceability events.

For growers handling foods covered by the FDA Food Traceability Rule (21 CFR Part 1, Subpart S, often called FSMA 204), traceability is built around specific Critical Tracking Events (CTEs) and Key Data Elements (KDEs). A well-designed harvest log can provide the field-level information needed to connect harvesting with subsequent initial packing, lot identification, and case labeling.

You do not need a particular brand of software to build a useful traceability system. FDA does not prescribe a specific technology for maintaining these records. The practical goal is a consistent data structure that your team can maintain and that can be retrieved, sorted, and connected to the rest of your traceability records when needed.

1. Start With the Right Regulatory Scope

Before changing your field logs, determine which FDA requirements apply to your operation. The Food Traceability Rule in 21 CFR Part 1, Subpart S applies to foods on the FDA's Food Traceability List (FTL), subject to the rule's exemptions and exclusions. The FTL includes a number of produce categories, including leafy greens, fresh-cut produce, tomatoes, peppers, cucumbers, melons, fresh culinary herbs, and tropical tree fruits.

This is separate from the FDA Produce Safety Rule in 21 CFR Part 112, which has its own recordkeeping requirements. A harvest log may support both programs, but the requirements should not be treated as interchangeable. Check the current FDA guidance and your operation's specific circumstances—including applicable exemptions—before describing a particular field as legally required.

2. The Critical Tracking Events: Harvesting vs. Initial Packing

For operations covered by the Food Traceability Rule, traceability is organized around specific milestones called Critical Tracking Events. For growers and field packers, two important events are harvesting and initial packing:

• Harvesting: Defined as activities involved in cutting, gathering, or picking raw agricultural commodities from the field. Harvesting records establish the physical origin of the crop.
• Initial Packing: Defined as packing a raw agricultural commodity not previously packed. In most fresh produce supply chains, the initial packer is the entity legally responsible for assigning the Traceability Lot Code (TLC).

Do not assume that every activity between harvest and shipment creates a separate traceability event. Instead, map your actual workflow against the CTE definitions and KDE requirements in the rule. The practical objective is to preserve the link from the harvested food and its location through the applicable initial-packing and subsequent traceability records.

3. The Structure of an Inspector-Ready Harvest Log

For a covered harvesting event, the Food Traceability Rule specifies KDEs that should be captured in the applicable traceability records. The table below separates traceability information from common commercial labeling data. Exact obligations depend on the food, event, and exemptions that apply to your operation.

A harvest log that lists only "Monday – Romaine – 200 boxes" is difficult to use as a reliable traceability record. Your records should use consistent location identifiers and connect to the operation's written Traceability Plan. For covered entities, the plan should explain the procedures and records used to identify and link the required traceability events and KDEs.

4. Common Harvest Log Mistakes That Create Traceability Problems

During an inspection or traceability exercise, administrative disconnects can make it difficult to demonstrate how a harvested lot moves through the supply chain:

1. Inconsistent Location Identifiers: Using informal field names on daily sheets when the same production area has a different identifier in your Traceability Plan. Consistent identifiers make the harvest-to-lot relationship easier to demonstrate.
2. Ambiguous Date Formats: Using formats like "06/07/26," which can be interpreted differently by different readers. Use an unambiguous format such as YYYY-MM-DD or a clearly written calendar date.
3. Breaking the Lot-Code Link: The entity responsible for initial packing must assign the Traceability Lot Code at the applicable initial-packing event. Your harvest records should preserve the information needed to connect the harvested food to that lot code rather than relying on later manual reconstruction.
4. Records That Cannot Be Retrieved Efficiently: Paper records can be useful for day-to-day field work, but covered entities should plan how required traceability information will be assembled and provided in an electronically sortable format when FDA requests it. A system that requires extensive manual reconciliation increases the chance of errors.

5. The Operational Problem: The Gap Between Traceability Data and Labels

Many growers can maintain a useful harvest log in Google Sheets or Microsoft Excel but encounter an operational bottleneck when that data has to become physical carton labels.

Commercial supply chains may require case labels that follow GS1 and PTI specifications. Depending on the customer, that can include a GTIN, a lot number, a pack date, and a GS1-128 barcode. Other customer-specific elements may also be required. These are commercial labeling requirements, not universal FDA requirements, so confirm the specification for each buyer rather than treating every PTI element as a federal mandate.

Traditionally, packinghouse workers manually transcribe data from a field log into desktop label software like BarTender or ZebraDesigner. This manual step introduces transcription errors, delays packing line throughput, and frequently decouples the label lot code from the harvest log record.

6. The Bridge: From Harvest Record to Outbound Case Label

The practical solution is to keep the traceability data structured from the start and connect it to your labeling workflow. A spreadsheet can be a perfectly workable starting point; the important thing is that the same identifiers are carried consistently from harvest through the applicable packing and shipping records.

farmlabel.app provides a ready-to-use Harvest Log in Google Sheets format and connects that structured harvest data with its labeling workflow. The goal is not to claim that a template by itself makes an operation compliant. Instead, it gives growers a consistent way to capture field information and reduce manual re-entry when creating customer-specific case labels.

Instead of manual re-entry, the specific data fields in your harvest sheet serve as the direct input values:

• Harvest Date: Records the harvest event and can remain available as source data for downstream packing and labeling workflows.
• Field / Block ID: Preserves the harvest location identifier used in your traceability records and Traceability Plan.
• Commodity / Item Reference: Connects the harvested food to the product information used for the applicable customer label and, where applicable, its GTIN.
• Traceability Lot Code (TLC): Links the harvest record to the lot code assigned at the applicable traceability event, including initial packing where applicable. It should not be presented as a universal harvest-time field.

By structuring your daily log with these standardized fields, your field log ceases to be a dormant archive. It becomes the active instruction set that produces your physical, scan-ready shipping labels.