How to Run a Mock Recall: A Step-by-Step Guide
October 2, 2026
A mock recall is a planned practice run of a real recall. You choose a lot, trace it through your operation, find every unit, and work out who you would need to call. Nothing actually leaves the building and no customer gets a real notice. The point is to find the gaps in your records while finding them is cheap.
This guide walks through a mock recall step by step: choosing the lot, assembling the team, running the trace, accounting for every unit, contacting customers in a simulated way, scoring the result, and fixing what you find. It is written for operations and quality leads at small and mid-size manufacturers, but the same steps work in a warehouse.
Why run a mock recall
Most plants believe they can trace a lot. A mock recall tests the belief. The first one often turns up something nobody expected: a partial pallet with no lot on it, a batch sheet with a transposed number, or a customer contact who left the company a year ago.
There are three good reasons to run one.
- It proves the records work. A trace that only exists in theory is not a trace. Running it shows whether receiving, production, and shipping records actually connect.
- It trains the team. In a real recall, people are under pressure. If they have already done the steps once, they know where to look and who does what.
- It answers outside questions. Customers, auditors, and some regulators ask whether you test your recall plan. A documented mock recall is a direct answer. Confirm what your own customers and regulator expect with your quality team.
If you want the background on what traceability covers and the records behind it, start with our lot traceability guide for FDA-regulated manufacturers. If you handle foods on FDA's Food Traceability List, our FSMA 204 explainer covers the 24-hour record request that a mock recall helps you prepare for.
Step 1: Choose the lot and the direction
Choose a lot that will actually test your system. A finished lot made yesterday from one ingredient is too easy. A better choice is an ingredient lot that was received a while ago, split across several pallets, used in more than one batch, and shipped to more than one customer.
Then choose a direction. A forward trace starts from an input, such as a supplier lot of an ingredient or packaging material, and asks where it went. A backward trace starts from a finished lot and asks what went into it. Alternate between the two over time, because each one tests different records.
Write the scenario down before you start. For example: “Our supplier has told us that lot 24-118 of sunflower lecithin may be contaminated. Find every batch, finished lot, and shipment that contains it.” A written scenario keeps the exercise honest and gives you something to score against.
Many teams and many customers set a target time for a mock recall. There is no single number that fits every business, so agree yours internally with your quality lead and write it down with the scenario. Then start the clock when you announce the scenario, not when the team is ready.
Step 2: Assemble the team
A recall touches every part of the operation, so the mock recall should too. Name one person as the coordinator. Their job is to run the clock, keep notes, and make sure each step gets done, not to do the trace alone.
- Quality: owns the scenario, the scoring, and the final report.
- Receiving or warehouse: finds the receiving records and every container of the lot still in the building.
- Production: finds the batches that used the lot and the finished lots they became.
- Shipping or customer service: finds the shipments and the customer contacts.
- A manager with authority: decides on holds and signs off on the result.
In a smaller plant, one person may cover two roles. That is fine, but write down who covers what. If the same person covers every role, the exercise is really testing that person, not the system.
Step 3: Run the trace forward and back
Start with receiving. Find when the lot arrived, from which supplier, in what quantity, and where it was put away. Pull the COA for that lot if you keep one. Our guide to managing certificates of analysis by lot covers how to keep those findable.
Next, follow the lot into production. Find every batch that consumed it and how much each batch used. Then find every finished lot those batches produced. Finally, find every shipment that contained those finished lots, with the customer, the date, and the quantity.
If you started with a forward trace, run one step backward at the end as a cross-check. Take one of the finished lots you found and confirm that its batch record lists the original ingredient lot. If the two directions disagree, you have found a gap.
In Swift WMS, this step uses the same screens a real event would. Lot Trace shows the plates a lot went into and where they shipped, with a CSV export. The batch record on each work order traces forward and backward, and Batch Genealogy exports the chain from receiving to shipment as a PDF. Recall Impact pulls together downstream lots, in-flight work, and shipped destinations for one lot. These are part of the Core plan.
Step 4: Account for every unit
Finding where the lot went is half the job. The other half is proving that the numbers add up. This is often called a mass balance or reconciliation.
Take the quantity you received and account for all of it. Every unit should land in one of a few buckets:
- Still on hand, with its location.
- Consumed into batches, with the batch and quantity.
- Scrapped or adjusted, with the reason.
- Returned to the supplier.
- Shipped, inside finished goods, with the customer and quantity.
Then do the same for the finished lots: produced, on hand, shipped, and anything scrapped or sampled. If the buckets do not add up to what you started with, write down the gap and the reason you found, or note that you could not find one. An unexplained gap is the most useful finding a mock recall can produce.
Walk the floor to confirm what is still on hand. A record that says three pallets are in a location is only a claim until someone looks. Good license plate labels make this much faster; our explainer on what a license plate number is covers why.
Decide in advance whether you will place real holds during the exercise. In a real recall you would hold every affected lot right away. In a mock recall, a real hold blocks real shipments. Swift WMS can bulk-hold every impacted lot from Recall Impact, so agree beforehand whether the team uses that step or only reviews the list.
Step 5: Contact customers, in simulation
You do not want to alarm a customer with a fake recall notice. You do want to know that you could reach every customer quickly if it were real.
- List every customer who received affected product, with the shipment date and quantity.
- Find a current contact for each one: a name, a phone number, and an email address for the person who handles recalls or quality.
- Check each contact against a recent invoice, email, or call. A contact that has not been confirmed recently counts as a gap.
- Draft the notice you would send, with the product, the lot, the quantity, and what you want the customer to do.
- If a customer agrees in advance to take part, send them a clearly marked test message and time the response.
Some customers ask suppliers to include them in a mock recall. If yours do, agree on the format and the marking of test messages before the day, so nobody mistakes the drill for a real event.
Step 6: Score the result and fix the gaps
Stop the clock when the team can show the full trace, the unit reconciliation, and the customer list. Then score the exercise against the scenario you wrote down.
- Time: did the team finish within the target you agreed?
- Completeness: was every batch, finished lot, and shipment found?
- Reconciliation: did the units add up, and was every gap explained?
- Contacts: was there a current contact for every affected customer?
- Records: did the forward and backward traces agree?
Write a short report: the scenario, the team, the times, the findings, and the score. Keep it with your other quality records. If Recall Impact was part of the exercise, Swift WMS saves a recall audit record you can keep alongside your report.
Each gap needs an owner and a fix. A lot number that was not captured at the dock is a receiving fix. A batch sheet with a copied number is a production fix. A stale contact is a customer service fix. Assign each one a date, then check it in the next mock recall.
How often to repeat, and the takeaway
How often you run a mock recall depends on your products, your customers, and your quality program. A yearly mock recall is a common starting point, with extra runs after a big change such as a new product line, a new building, or a new system. Some customers specify a frequency in their quality agreements. Confirm your specific requirements with your quality team or regulator.
Change the scenario each time. Alternate forward and backward traces, use different product lines, and run at least one exercise when key people are out. The goal is not a perfect score. The goal is a team that knows the steps and records that hold up.
- Choose a lot that tests the system, not one that makes it look good.
- Write the scenario and the target time down before you start.
- Trace both directions and make them agree.
- Account for every unit, and explain every gap.
- Fix the gaps, assign owners, and test them next time.
To see how lot trace, batch records, holds, and Recall Impact fit together, visit the lot traceability and recall impact page.
