FDA kill-step exemption needs a dated application record

Classify the exemption path before changing the record set

The direct answer is to record which regulatory path is being used for the identified food and event before removing later traceability duties. FDA's FAQ and 21 CFR 1.1305 distinguish a person that receives an FTL food and applies a kill step, a person that receives food after a prior kill step, and a shipment made in reliance on a written promise that a receiver or later entity will apply the step. Those paths have different triggering facts and retained evidence. A recipe that normally cooks a product, a supplier's process description, or a food category marked pasteurized does not by itself establish which path applied to this lot. ^{[1] [2]}

The decision record should identify the regulated person and location, food and form, incoming traceability lot code and source, receiving event, claimed paragraph of the rule, responsible reviewer, process or agreement relied on, effective time, source documents, unresolved facts, and the traceability records that remain required before and after the boundary. Preserve the determination version used at the time. Later process, supplier, formulation, equipment, or authority changes should trigger review without rewriting the basis for an earlier shipment. ^[2]

Prove the kill step that actually occurred

For the own-process path, FDA says the person must keep receiving records for the covered food and a record of applying the kill step. FDA's FAQ says the rule allows flexibility in the form of that proof and notes that records kept under other requirements, including preventive-control monitoring or thermal-processing records where applicable, may be used. Reuse does not make a generic standard operating procedure sufficient. The retained record still needs to establish that the relevant process was applied to the identified food, lot, equipment, location, and time. ^{[1] [2]}

A defensible application record can connect the incoming lot and receiving evidence to the scheduled process, actual critical parameters and monitoring, equipment or line, start and completion times, operator and reviewer, deviations and corrective action, released output identity, and source record. Qualified owners must decide which values and approvals establish the applicable kill step; the traceability system should preserve their evidence and history rather than infer lethality from a product name or expected recipe. If execution evidence is missing or disputed, retain the uncertainty and the broader record obligations until an accountable determination is made.

Treat a future-process agreement as a governed dependency

Section 1.1305(d)(6) addresses food that will receive a kill step or will be changed so it is no longer on the Food Traceability List under a written supply-chain agreement. The agreement is not interchangeable with proof that a process already happened. The rule specifies agreement content and governance, including the substance of the commitment, effective date, printed names and signatures, maintenance while effective, and renewal at least every three years. Where the committed step sits farther downstream, the receiving party also needs the required chain of written commitments rather than an unsupported assumption about the ultimate processor. ^[2]

Manage the agreement by counterparty legal identity, facilities and roles, covered foods and forms, process commitment, effective and renewal dates, signatories, downstream conditions, linked contracts and supplier records, owner, notice of change, termination, and affected open lots. Test an acquisition, facility transfer, formulation change, alternate processor, expired agreement, rejected shipment, and lot diverted away from the named kill step. The system should show whether the agreement was effective for the actual transaction and whether receiving, shipping, or other records remain necessary; it should not convert an evergreen supplier flag into permanent exemption evidence.

Test the boundary with an adverse lot history

Run one representative history with two incoming FTL lots: one receives the documented process as planned, while the other is diverted before processing after a parameter deviation. Add a third lot received from a supplier that says a prior kill step occurred but cannot provide attributable evidence, and a fourth shipped under an agreement that expires before receipt. Reviewers should reconstruct which exemption path was claimed for each lot, the evidence available at that time, which records were still required, the correction history, and where an exception or escalation prevented a silent scope change. ^{[1] [2]}

The FDA sources establish regulatory text and agency guidance; they do not determine whether a real process is a qualifying kill step, whether a food or person is covered, whether an agreement satisfies the rule, or whether any record is adequate. Those conclusions require the current rule, complete food and process facts, applicable food-safety and preventive-control records, and qualified regulatory, food-safety, operations, quality, supply-chain, and legal judgment. This article proposes an evidence architecture for that governed decision; it does not classify a product, lot, process, facility, or company. ^{[1] [2]}

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.