Mock Recall and Traceability Exercise: How to Run One and What to Record
Updated: Nov 10
Reviewed by Aaron Lyon, President of A.P. Lyon and former Director of Quality Assurance and International Regulatory, with more than 30 years in medical device quality. Last reviewed November 10, 2026.
Every food company has a recall procedure. Far fewer know how long it actually takes them to find every unit of an affected lot, contact every customer, and account for every kilogram of ingredient. A mock recall answers that question while the stakes are low.
Done properly, a mock recall tests the whole chain: records, systems, people and contact lists. Done as a desk exercise where the quality manager traces one lot through a spreadsheet already open on their screen, it tests almost nothing.
This guide explains what FDA rules and ISO 22000 and FSSC 22000 expect, then walks through planning, running and scoring an exercise that finds real weaknesses.
What the requirements say
FDA 21 CFR Part 117
Under 21 CFR 117.139, a facility whose hazard analysis identifies a hazard requiring a preventive control must have a written recall plan. It must include procedures that describe the steps to be taken, and assign responsibility for taking those steps, to:
Directly notify direct consignees of the food being recalled, including how to return or dispose of the affected food
Notify the public about any hazard presented by the food, when appropriate to protect public health
Conduct effectiveness checks to verify that the recall is carried out
Appropriately dispose of recalled food, through reprocessing, reworking, diverting to a use that does not present a safety concern, or destroying it
The rule also requires records that allow traceability one step back and one step forward under the Bioterrorism Act recordkeeping requirements in 21 CFR Part 1, Subpart J.
ISO 22000:2018
ISO 22000 requires a traceability system (clause 8.3) that can uniquely identify incoming material from immediate suppliers and the first stage of distribution of the end product. The system must be verified and tested.
Clause 8.9.5 requires a withdrawal and recall process, with nominated competent persons, notification of interested parties, handling of withdrawn product, and recording of the cause, extent and result. The organization must verify the effectiveness of withdrawal and recall through techniques such as mock withdrawal or practice withdrawal.
FSSC 22000 and customers
FSSC 22000 and most retail customers expect the traceability and recall process to be tested at least annually, with a target time to complete the trace. Many customers specify a time limit, commonly between two and four hours, and a mass balance. Check your scheme's current requirements and your customer codes of practice.
The FSMA 204 Food Traceability Rule
The FDA's Food Traceability Rule, 21 CFR Part 1, Subpart S, adds requirements for foods on the Food Traceability List, such as many fresh-cut fruits and vegetables, shell eggs, finfish, crustaceans and soft cheeses. Covered businesses must keep Key Data Elements for defined Critical Tracking Events, maintain a written traceability plan, and provide an electronic sortable spreadsheet to FDA within 24 hours of a request. FDA has extended the compliance date to July 20, 2028. Confirm the current date and whether your foods are on the list. If they are, design your mock recalls now to rehearse the 24-hour spreadsheet.
Mock recall vs traceability test
The terms are used loosely, but it helps to separate them:
A traceability test checks that records let you trace a lot backward to its raw materials and forward to its customers.
A mock recall goes further: it tests the decision-making, communication, product retrieval and effectiveness checks in the recall plan.
A good annual program runs both, often in the same exercise.
Step 1: Plan the exercise
Choose a realistic scenario
Pick a scenario that tests something you are unsure about. Examples:
A supplier notifies you that a lot of sesame paste may contain undeclared peanut. Trace backward: which of your finished lots used it?
A customer reports a foreign body in a finished product. Trace forward: where did the lot and the lots produced on the same line that shift go?
A positive Listeria monocytogenes result on a food-contact surface. Which lots are implicated since the last negative?
Rotate scenarios each year: backward one year, forward the next, and a raw material used across many products every few years. Include a rework or a multi-ingredient lot, because those are where traceability usually breaks.
Decide who knows
The most realistic exercise is unannounced to most participants. The coordinator and top management know; the recall team learns when the exercise starts. Run it at a realistic time, not just Tuesday at 10 a.m. Try a Friday afternoon or a second shift.
Set targets
Define in advance:
Time target: for example, all affected lots identified and quantities accounted for within two hours, and all direct customers identified within four hours
Mass balance target: for example, 100% of the finished product quantity accounted for, and at least 99% of the raw material quantity
Communication target: all customer contacts verified as current
Step 2: Run the trace
Start the clock when the scenario is issued. Record each step with a timestamp.
Backward trace (finished product to raw material):
Identify the finished product lot, its production date, line and shift.
Pull the production record and the batch sheet.
Identify every ingredient and packaging lot used, including rework.
Trace each lot back to the supplier and the receiving record.
Confirm quantities received, used, remaining in stock and scrapped.
Forward trace (raw material to customer):
Identify every finished lot that used the affected raw material lot.
For each finished lot, identify quantities produced, in stock, on hold, and shipped.
For shipped product, identify each direct customer, ship date, quantity and delivery location.
Include samples, retained samples, donations and employee sales.
Step 3: Do the mass balance
The mass balance proves that you have found everything. For the raw material:
Quantity received
Minus quantity used in production, by finished lot
Minus quantity remaining in stock
Minus quantity scrapped, returned or used in trials
Equals the unaccounted difference
Repeat for finished product: quantity produced, minus shipped, minus in stock, minus samples and scrap. Explain any difference. Unexplained differences above a small tolerance, such as normal process loss, mean the trace is not complete.
Step 4: Test the communication
A traceability test that stops at the spreadsheet leaves the riskiest part untested. As part of the exercise:
Confirm the recall team call list: names, roles, phone numbers, and backups for each role.
Call or email one or two real customers to verify their recall contact details, telling them it is a test. Many customers welcome this.
Confirm you could reach your regulatory contacts, certification body, insurer and any co-packers or warehouses.
Draft, but do not send, the customer notification letter and, where appropriate, a press statement.
Step 5: Score and report
Write a short report:
Scenario, date, start and end time, and participants
Lots identified, quantities and mass balance results
Time to complete each stage against target
Communication checks and results
What went well
Gaps found, such as missing records, an out-of-date contact, a rework lot that could not be traced, or a warehouse that did not answer
Corrective actions, with owners and dates
A mock recall that finds no gaps is either a very mature system or an exercise that was too easy. Most good exercises find two or three things to fix.
Step 6: Close the gaps
Enter the gaps into corrective action. Typical actions include adding lot capture for rework, linking warehouse management records to production lots, updating customer contacts, and training the backup recall coordinator. Retest the specific weakness rather than waiting a year.
Common weaknesses mock recalls find
Rework not traced. Rework added to a batch without its own lot number.
Bulk ingredients in silos or tanks without a clear rule for which lots were in use and when.
Outside warehouses that do not answer outside business hours or cannot report by lot.
Out-of-date contact lists, especially for customer quality contacts.
Paper and system records that disagree, such as a lot number transcribed incorrectly.
No backup coordinator. The exercise fails when the one person who knows the system is on vacation.
Records an auditor will ask for
The withdrawal and recall procedure and the written recall plan
The traceability procedure
Mock recall and traceability test reports, with timing and mass balance
Corrective actions arising from exercises
The current recall team and contact list
For FSMA 204 foods, the traceability plan and evidence that the 24-hour spreadsheet can be produced
Documents that help
A.P. Lyon's Mock Recall and Traceability Exercise ($49) gives you the scenario plan, timing log, mass balance worksheet and report. It works with the Traceability Procedure and the Product Withdrawal and Recall Procedure, which covers the elements of 21 CFR 117.139 and ISO 22000 clause 8.9.5.
All three are part of the Food Safety Management System, Complete ($1,295), and you can choose individual procedures in Build Your QMS with volume discounts.
Not sure where your quality system stands? Take the free QMS gap check: about 20 questions, an instant report of your gaps by clause, and the procedures that close each one.
Just getting started? The free Startup Quality Plan shows which procedures you need now, which can wait, and how long they take to put in place.
The documents need to be adapted to your products, systems and customers, and a PCQI or other qualified person should review your recall plan. They are documentation, not validation or certification.
Next steps
Read how recall plans fit into the FSMA food safety plan in HACCP Plan vs FSMA Food Safety Plan, see how allergen management ties into recall scenarios, browse the food safety documents, or contact A.P. Lyon about consulting.



Comments