FSMA 204 · Definitions
What is a CTE?
Critical tracking events, key data elements, and traceability lot codes — in plain language.
A Critical Tracking Event is a moment in a food’s journey where the rule requires you to write something down.
The seven events, and the one requirement behind them
The critical tracking events are harvesting, cooling before initial packing, initial packing, first land-based receiver, shipping, receiving, and transformation. Alongside them sits the traceability plan — not an event at all, but a standing requirement for every covered business whether or not you ever perform a single CTE on the list.
It is not one straight line
This is the part most summaries get wrong. Harvesting, cooling, and initial packing apply to raw agricultural commodities that did not come off a fishing vessel. First land-based receiver applies to food that did. They are alternative starting points, not consecutive steps — a lot of romaine never passes through a first land-based receiver, and a lot of cod never passes through initial packing. Shipping, receiving, and transformation then apply to everyone downstream of whichever start applied.
CTE, KDE, TLC
- CTE — the event. What happened to the food, and when.
- KDE — the key data elements. The specific fields you record at that event: quantities, dates, locations, product descriptions, and reference documents.
- TLC — the traceability lot code. Created at only three points: initial packing, first land-based receiver, or transformation. Nothing else creates one.
- TLC source — the location that assigned the code. It travels in the shipping and receiving records so anyone downstream can trace back to where the lot began.
The 24-hour test
On request, you have 24 hours to give FDA an electronic, sortable file of your traceability records. The rule does not mandate any particular technology, but that requirement is what makes paper binders impractical for most covered operations. This is the clause that turns a recordkeeping exercise into a data project.
Where operations actually fail
Rarely at harvesting. Almost always at two places: receiving, where your record has to connect an incoming lot code to the source that shipped it, and transformation, where a new lot code has to stay linked to every input code that went into it. Break either link and the chain is unusable in a recall, which is the only moment any of it counts.
Educational summary. See FDA’s Critical Tracking Events and Key Data Elements for the full data elements, and note that exemptions and partial exemptions apply.