If you have read the FSMA Section 204 final rule or any of FDA's accompanying guidance documents, you have encountered the term "Critical Tracking Event." CTEs are the backbone of the FSMA 204 recordkeeping system. They define the specific points in the supply chain where food entities must create and retain traceability records, and they determine which Key Data Elements need to be captured at each point. Understanding what CTEs are and which ones apply to your operation is the starting point for any FSMA 204 compliance program.
This post explains each of the six CTEs defined in the rule, with examples drawn from fresh produce supply chains. It is written for operations and food safety teams who are coming to this regulation for the first time and need a clear picture of what events trigger a recordkeeping obligation under the rule.
The Six Critical Tracking Events
The FSMA 204 final rule defines six Critical Tracking Events, each representing a distinct type of activity in the supply chain for covered foods. Not every food entity will trigger all six CTEs. Which CTEs apply to your operation depends on what you do with covered foods: do you grow them, receive them, transform them, create new products from them, ship them, or cool them? Each activity type maps to a specific CTE.
Growing
The Growing CTE applies to persons who grow and harvest covered produce, specifically fruits and vegetables that are on the Food Traceability List and are intended to be consumed raw. The Growing CTE is triggered at the point of harvest. For growers, the required KDEs include a description of the food, the commodity and variety, the date of harvest, the quantity and unit of measure, the location where the food was grown (the farm), and the name of the grower.
It is worth noting that the Growing CTE applies specifically to the farm-level entity at the point of first harvest. If an entity purchases unharvested crops on the vine and arranges for their own harvest, that entity triggers the Growing CTE. If a grower contracts with a packing shed that takes ownership at harvest, the grower still triggers the Growing CTE at the time of harvest even if the packing shed takes over the records at the subsequent Shipping CTE.
Receiving
The Receiving CTE is triggered whenever a food entity receives a shipment of a covered food from an immediate previous source. This is the most broadly applicable CTE because virtually every entity in the supply chain below the grower level must record receiving events for every covered food they take in.
The KDEs for the Receiving CTE include the traceability lot code for the food received (as assigned by the immediate previous source), the quantity and unit of measure, the location where the food is received, the date of receipt, and the reference document number (such as a bill of lading or delivery record) that identifies the shipment. The receiving entity also records the name of the entity from which the food was received.
For a fresh produce distributor receiving from multiple farms and packing sheds each week, the Receiving CTE is the highest-volume recordkeeping obligation in the operation. Every inbound shipment of a covered food generates a Receiving CTE record. This is the CTE where supplier certificates become particularly important, because the traceability lot code that appears on the supplier's shipping document or COA is the identifier that links your receiving record back to the upstream supply chain.
Transforming
The Transforming CTE applies when a food entity converts one covered food into a new food, creating a new traceability lot code for the resulting product. Examples include a fresh-cut processor that converts whole heads of romaine into bagged salad mixes, a juicer that converts whole tomatoes into tomato juice, or a facility that combines multiple ingredient lots to produce a prepared entree.
The KDEs for the Transforming CTE include the new traceability lot code assigned to the output food, a description of the new food, the date of the transformation activity, the location where the transformation occurred, and the lot codes of all the input ingredients that were used in the transformation. That last requirement is important. If you combine five different supplier lots of spinach into a single bagged mix production run, your Transformation CTE record must reference all five input lot codes, not just the dominant ingredient or the most recently received lot.
Creating
The Creating CTE applies when a food entity creates a new covered food by combining or processing covered foods at a retail food establishment. This CTE is specifically targeted at retail-level operations such as grocery delis, salad bars, and food service preparers that take covered foods and assemble them into new ready-to-eat products. The Creating CTE is distinct from the Transforming CTE in that it applies to the retail preparation context specifically.
For most producers and distributors, the Creating CTE does not apply to their operations. It becomes relevant for grocery chains and food service operators who are building covered food products on-site from covered ingredients. Those entities need to maintain records linking their assembled product lots to the lot codes of the covered ingredients they drew from.
Shipping
The Shipping CTE is triggered whenever a food entity ships a covered food to another entity in the supply chain. It is the mirror of the Receiving CTE: for every Receiving CTE at a downstream buyer, there is a corresponding Shipping CTE at the upstream seller.
The KDEs for the Shipping CTE include the traceability lot code of the food being shipped, a description of the food, the quantity and unit of measure, the location where the food is shipped from, the date of shipment, the reference document number, and the name of the entity to which the food is shipped. The shipping reference document (a bill of lading, a shipping confirmation, or a delivery record) becomes the link between the seller's Shipping CTE record and the buyer's Receiving CTE record.
This reference document link is one of the critical points where traceability breaks down in practice. If your buyer's receiving record does not reference the same document identifier that appears in your shipping record, the two records cannot be efficiently joined in a recall query. Establishing a consistent reference document numbering convention between trading partners is one of the operational steps that makes multi-tier traceability work.
Cooling
The Cooling CTE applies when a food entity performs initial cooling of a covered food that requires temperature control for safety. This CTE is specific to foods that have a refrigeration or freezing requirement as part of their safe handling. For fresh produce, the Cooling CTE is typically triggered at the packing shed or distribution center when produce first enters a cold storage environment after harvest.
The required KDEs for the Cooling CTE include the traceability lot code of the food being cooled, the location where cooling occurred, the date of the initial cooling activity, and the reference document identifier. The Cooling CTE is the one most commonly overlooked by produce operations that have cooling as a normal part of their handling workflow but have not historically recorded it as a formal CTE record with a lot code.
Which CTEs Apply to Your Operation
To identify which CTEs apply to your specific operation, work through each type of activity you perform with covered foods. If you grow and harvest covered produce, the Growing CTE applies. If you receive covered foods from an upstream source, the Receiving CTE applies. If you cut, process, or combine covered foods into new products, the Transforming CTE applies. If you ship covered foods to downstream buyers, the Shipping CTE applies. If you perform initial cooling of covered foods, the Cooling CTE applies.
Most operations in the middle of the supply chain will find that at least three of the six CTEs apply to them: Receiving, Shipping, and possibly Transforming or Cooling depending on their activities. The key compliance question for each applicable CTE is whether your current records capture all the required KDEs for every event, consistently and in a form that can be retrieved within 24 hours on FDA request.
CTEs are not designed to be an exhaustive log of every activity that touches food. They are the specific handoff and transformation points where FDA's research indicated that record availability would most accelerate outbreak investigation. If you understand the six CTEs and can answer the KDE requirements for each one that applies to your operation, you have the foundation of an FSMA 204 compliance program.