CTECritical Tracking Event

A Critical Tracking Event is a specific moment in the life of a food on the Food Traceability List where, under FSMA 204, you must capture and retain a defined set of Key Data Elements (KDEs). Each CTE is operationally familiar — receiving a delivery, packing a batch, shipping an order, transforming an ingredient — but FSMA 204 turns each of them into a regulated record-keeping moment with a 24-hour electronic-export expectation when FDA asks.

The rule is built around two artefacts: the Critical Tracking Event itself, and the Traceability Lot Code (TLC) that threads CTEs together. Once a TLC is assigned at one of three trigger points (initial packing of a raw agricultural commodity, first receipt from an exempt entity, or transformation), it is carried forward on every subsequent CTE for that food until the food is consumed, exported or destroyed.

The current FDA compliance date is January 20, 2026. After that, covered firms must be able to produce a sortable electronic spreadsheet of CTE / KDE data within 24 hours of an FDA request. Records must be retained for two years.

FSMA 204 applies to anyone who manufactures, processes, packs or holds a food on the Food Traceability List (FTL). The FTL includes cheeses (other than hard cheese), shell eggs, nut butters, cucumbers, fresh herbs, leafy greens, melons, peppers, sprouts, tropical tree fruits, tomatoes, finfish, smoked finfish, crustaceans, molluscan shellfish (bivalves), and ready-to-eat deli salads.

Exemptions exist but are narrower than people assume:

• Farms producing FTL foods sold direct to consumers, or whose annual food sales fall below the dollar threshold (currently $25k inflation-adjusted).
• Small retail food establishments (under $250k average annual food sales).
• Foods produced and packaged on a farm where the producer name and farm address are on the package.
• Foods that receive a "kill step" sufficient to eliminate the pathogens of concern (this exemption applies only to specific transformation contexts and does not extend back to the inputs).
• Restaurants, when serving directly to a consumer.

If you are unsure whether a specific product or process is in scope, default to assuming it is and document the exemption decision — FDA expects a written rationale, not a verbal assumption.

1. Harvesting — the act of removing the food from its growing area (covered crops only).
2. Cooling — the first temperature reduction of a raw agricultural commodity before initial packing.
3. Initial Packing — the first packing of a RAC (other than a food obtained from a fishing vessel).
4. First Land-Based Receiver — receipt of a food obtained from a fishing vessel onto land.
5. Shipping — moving a food from one location to another (within or between firms).
6. Receiving — receipt of a food at a location (after shipping).
7. Transformation — manufacturing, processing or significantly altering a food, or its packaging or labelling.

Internal moves within the same physical site, between locations under the same management, are not CTEs. Movement between different firms or different physical locations (regardless of common ownership) usually is a CTE.

Note that Shipping and Receiving mirror each other — the data leaving the sender must match the data entering the receiver. This bilateral check is what makes one-up / one-back traceability actually work across firms.

The TLC is the thread that connects all CTEs. It is assigned at exactly one of three trigger points and then carried through every subsequent CTE for that food:

• At initial packing of a RAC (other than from a fishing vessel).
• When first received from someone not subject to FSMA 204 (e.g. a small farm exempt from the rule).
• When transformed into a new food.

A transformation may assign a new TLC for the output and must record the TLCs of every input. The new-TLC + input-TLC link is what lets a regulator (or your own QA) trace from a contaminated finished product back to the specific harvest field, cooler load, fishing vessel landing, or upstream supplier batch in minutes rather than days.

FSMA 204 is data-format-agnostic — it requires records, not specifically GS1 records. In practice, GS1 standards are the path of least resistance because they are already on the case label, the ASN, and most retailer EDI flows.

• GTIN (AI 01) — identifies the product configuration, paired with the TLC at every Shipping / Receiving CTE.
• TLC (typically AI 10) — the batch / lot identifier itself, carried on every CTE for that food.
• SSCC (AI 00) — the pallet / container identifier, which lets a single scan at goods-in pull every TLC on that pallet into the Receiving CTE automatically.
• GS1-128 case labels — encode GTIN + lot + date + quantity, which means most of the inbound KDEs are already on the case before it lands at your dock.

Firms that align their TLC with their GS1 AI(10) batch/lot code can capture Shipping and Receiving CTEs with a single barcode scan instead of manual transcription — and that single decision is the difference between FSMA 204 being a low-overhead background process and a daily clerical burden.

• Missing a Transformation CTE because the change was treated as repackaging — relabelling and repackaging do count.
• Treating multi-site moves under common ownership as internal — they are still CTEs if the physical location changes.
• Capturing CTE data in separate systems (paper at receiving, ERP at shipping, spreadsheet at production) with no link between events — fails the 24-hour export.
• Missing the source-TLC reference on transformation outputs — breaks one-up / one-back trace.
• Recording the CTE date but not the time when the rule requires both (Cooling, Receiving for perishables).
• Assigning a fresh TLC at every internal step instead of preserving the upstream TLC, leaving FDA unable to trace.
• Treating an FDA mock-trace exercise as a tabletop conversation instead of producing the actual sortable spreadsheet.

FDA expects three things at any covered firm:

1. A written Traceability Plan describing how CTEs are captured, how the TLC is assigned, who is responsible, and how records are retained.
2. Records held for at least two years, accessible to FDA on request.
3. The demonstrated ability to produce an FDA-format spreadsheet of CTE data within 24 hours of request. The export must let FDA sort and trace forward and back.

Firms unable to demonstrate the 24-hour export during a mock trace exercise will be the first targets when FDA enforces post-compliance-date. The expectation is not just "have the records" but "hand them over in a usable format within 24 hours" — paper, scanned PDFs of paper, or unsortable PDF exports will not satisfy.

FDA has published a sortable-spreadsheet template that defines the columns expected. Each row is one CTE event, with columns for TLC, CTE type, KDE values, reference documents, source / destination locations, dates and times. The export must be:

• Electronic — paper or scanned-PDF does not count.
• Sortable — true CSV / XLSX, not PDF export of a printed table.
• Filterable on TLC — so FDA can isolate one lot and follow it.
• Inclusive of all upstream and downstream CTEs your records cover for the requested period.
• Delivered within 24 hours of the FDA request, with extensions only by FDA discretion.

External CTE capture (Receiving, Shipping, Transformation across firms) is the visible half of FSMA 204. The invisible half — and the one that determines whether your 24-hour export actually works — is the internal traceability programme that links every internal movement of a TLC from dock to dock. The rule does not require capture of every internal move as a CTE, but it does require that on FDA request you can reconstruct the chain from any TLC at any point in your facility.

• Every storage location has a unique identifier (rack, bin, cold room, staging lane). License-plate or pallet-ID-based location tracking is the cleanest pattern.
• Every move event captures: from-location, to-location, quantity moved, TLC, operator, timestamp. Scanner-driven moves with no manual entry are the only way this stays accurate at volume.
• Splits and combines (decanting, blending, repackaging) capture the input TLC(s), input quantity, output TLC, output quantity. A split that produces two new TLCs from one input creates two new chain links.
• Hold and release events capture the held quantity, the reason, the release authorisation, and the disposition of any quarantined fraction.
• Destruction and waste events capture the TLC, quantity destroyed, reason, witness signature, and disposal route.
• Every event is a single immutable row with the full context — never a state change to a previous row.

Sites that try to build internal traceability on top of spreadsheets or ERP item-master flags end up with a 24-hour export that is partial, late or inconsistent. The pattern that works: every operator action on a covered food creates a structured event in the same database, indexed by TLC, with reference to the upstream CTE and the operational context. The 24-hour export is then a query, not a reconstruction project.

FDA's enforcement pattern after the January 20, 2026 compliance date is well-telegraphed: announced and unannounced mock-trace exercises, scored against the 24-hour export expectation. A firm that produces the spreadsheet inside 24 hours with traceable, consistent data demonstrates a working programme. A firm that misses the window, produces partial data, or asks for an extension on the first request becomes an early enforcement target.

The discipline that works — borrowed from the recall-mock-up pattern long established under FDA's recall guidance — is the quarterly internal mock trace, run cold (no warning to the operations team), against a randomly selected TLC from the last 90 days. The exercise measures four things:

1. Time-to-spreadsheet — clock starts when the mock request is issued, stops when the FDA-format spreadsheet is in the exercise reviewer's hands. Target: under 4 hours for a routine TLC, under 12 hours for a complex transformation chain.
2. Completeness — every CTE in the chain present, every KDE populated, every reference document linked. Missing KDEs are scored and the gap fed back to the data-capture point.
3. Sortability — open the spreadsheet in Excel, filter on TLC, sort by date. The filter must isolate one chain cleanly without manual cleanup.
4. Bilateral consistency — for at least one Receiving CTE in the chain, contact the upstream supplier and request their Shipping CTE record for the same TLC. The two records must match (TLC, quantity, date, ship-to / ship-from). Discrepancies indicate a data-capture or sync problem at one end.

Quarterly cadence produces a meaningful trend: the time-to-spreadsheet should drop and the completeness should approach 100% within the first year. Firms that run mock traces only annually do not get the muscle memory or the feedback loop. Firms that never run them discover the problem only when FDA arrives.

FSMA 204 forces a conversation with every supplier and every customer of a covered food about the data each side will capture, transmit and retain. The 18 months before the compliance date were the right window to have that conversation; after it, every new supplier onboarding includes the CTE data exchange as part of the qualification package.

Onboarding new suppliers without this conversation is the single biggest forward-looking risk. A new supplier ships a covered food, no TLC is captured at Receiving, the upstream chain is broken, and the next FDA request exposes the gap. The supplier-qualification questionnaire needs an FSMA 204 section as a hard gate, not a footnote.