Test whether food traceability records can answer a mock recall

A useful mock recall asks whether traceability records can identify the affected food, its movement and the unresolved gaps within a controlled exercise. Measure completeness and reconciliation, not only elapsed time.

FDA's Food Traceability Rule creates additional recordkeeping requirements for certain foods on the Food Traceability List. It connects Key Data Elements to Critical Tracking Events such as shipping, receiving and transformation, and requires a traceability plan for entities subject to the rule. FDA says the original compliance date was 20 January 2026, that it proposed a 30-month extension to 20 July 2028, and that Congress directed FDA not to enforce before that date. Treat the extension as proposed unless and until the legal text is amended, while recognising the stated non-enforcement direction. FDA Food Traceability Rule overview

A mock recall is an original readiness test in this guide, not a universal FDA requirement. Other food-safety rules, customer standards or contractual programmes may impose their own exercises.

Choose a real, non-incident lot and a clear exercise boundary. Trace one step back and forward where applicable, including transformation. Reconcile quantities and explain variance. Keep the exercise unmistakably separate from a real recall communication.

Define the food, traceability lot code or equivalent identifier, site and time window. State whether the test covers receiving, transformation, shipping, customers, suppliers or all of them. Do not quietly exclude difficult channels after the clock starts.

Confirm the rule's applicability separately. Check whether the food appears on the Food Traceability List, what activities the business performs and whether an exemption or modified requirement applies. FDA's February 2026 Q&A is draft guidance and says it is not for implementation; it can support understanding but does not replace the regulation. FDA draft Q&A guidance

Label every message and file “EXERCISE — NOT A RECALL”. Name the exercise controller and the person authorised to stop the test if a genuine safety issue appears.

Start with the lot identity and source. Retrieve the relevant receiving record, date, quantity and supplier reference. If the food was transformed, show how input lots relate to output lots. Avoid relying on a product description without the lot relationship.

Then trace output movement: shipment date, quantity, recipient and destination. Test whether records held by different systems use consistent identifiers. A warehouse code, enterprise-resource-planning number and supplier lot may all refer to the same food, but the link must be demonstrable.

Do not manufacture missing data during the exercise. Record the gap, who owns it and the potential consequence. A manual cross-reference created during the test may be a useful corrective action, but it is not evidence that the record existed beforehand.

Set the accounting boundary first. For one defined stock stage, beginning quantity plus eligible additions, less transfers out, shipments or documented loss at that stage, equals expected on-hand quantity. Reconcile transformation inputs and outputs separately from later finished-stock shipments, so the same material is not deducted twice. Compare results with records and, where safe and proportionate, actual stock.

Explain yield, waste, samples, rework, returns and unit conversions. A reconciliation percentage without the calculation can hide double counting. Record both the known quantity and the unresolved variance.

Assess location completeness separately from quantity completeness. The totals may reconcile while one recipient address is missing. Conversely, every customer may be listed while duplicated shipment lines overstate the affected quantity.

Assume a fictional processor selects an input lot of fresh produce used in two finished-product lots. Records identify both outputs, but one shipment uses cases while the transformation record uses kilograms. The first calculation appears to show more finished product than available input.

The team finds an undocumented conversion assumption and a duplicated transfer. It records the variance, corrects the controlled mapping only after approval and repeats the reconciliation. The exercise report distinguishes the original failure from the successful retest.

This example is invented and does not represent a food-safety event, client result or compliant calculation.

Fictional arithmetic example only; no recall test was performed. One input lot contains 1,000 kg. Invented transformation records allocate 600 kg to finished lot A, 350 kg to finished lot B and 50 kg to documented process loss. The input balance is 1,000 − 600 − 350 − 50 = 0 kg unexplained.

Now reconcile the finished lots separately:

The finished-stock balance has an unresolved 10 kg even though the transformation balance reconciles. Do not count both transformation and subsequent shipment as deductions from the original input in one equation: that would count the same material movement twice.

Suppose the 250 kg B shipment has a recipient name but no usable destination record. Its quantity is known, yet its destination remains unresolved. Report the two gaps separately. Do not invent a waste entry to force the 10 kg balance or infer a destination from a similar customer name.

These simplified figures exclude returns, rework, changing moisture and conversions. A real exercise needs the applicable process and unit basis. Numerical reconciliation does not establish food safety, legal compliance or the correct scope of an actual recall.

Record the requested data, source systems, retrieval time, exceptions, quantity reconciliation and people involved. Evaluate whether the result would support decision-makers, not merely whether a file was produced.

Assign actions for gaps and verify them through a focused retest. Use corrective actions that require evidence of effectiveness before closure when a recurring failure needs root-cause work. Preserve the exercise record under the authorised retention programme.

No. Speed is useful only when identity, completeness, quantities and destinations are reliable. A fast incomplete list can misdirect a response.

Only through an authorised exercise method that prevents confusion. Do not send language that could be mistaken for a real recall or public warning.

The enforcement direction does not remove operational risk, customer requirements or other legal duties. Decide preparation priorities from actual applicability and risk, and monitor FDA's final rulemaking status.

This article is general information. Verify current requirements and seek qualified advice for your specific circumstances.

Spotted an issue? Contact our editorial desk.