A mock recall is a fire drill you run on purpose, before you need it. You pick a lot, trace it forward to every account it shipped to and backward to what it was made from, and time how long the answer takes.
For a small food brand it is the cheapest way to find the gap in your records — the missing lot code, the account you can’t reach — while the stakes are still zero. Here’s how to run one, and a template to start from.
What is a mock recall?
A mock recall is a practice run of your recall plan: you trace a chosen lot one-up and one-back, quantify what shipped where, and confirm you could retrieve or hold it, without any product actually being unsafe. It tests whether the plan works, on paper and on the clock.
It is distinct from a mock withdrawal, which is usually broader and less urgent: a withdrawal covers product pulled for quality or labeling reasons, not a safety hazard. The mock recall is the safety-grade version: it assumes a real health risk and measures whether you can move fast and completely. The value is entirely in what breaks during the drill, so run it like it’s real.
How often should a mock recall be done?
The FDA expects recall readiness and requires a written recall plan for many foods, but it doesn’t set a mock-recall frequency for most brands. In practice, food-safety audit schemes like SQF or BRCGS and retail buyers commonly require at least one a year, and many teams run one or two.
“Does the FDA require a mock recall?” is the common question. The rule you actually meet is that written recall plan, required where your hazard analysis calls for one; the mock recall is the standard way to prove it works. Even where no rule applies, a distributor or retail buyer questionnaire often asks when you last ran one, so treat annual as the floor, and run one after any change to your co-packers, product lines, or the system that holds your records.
Running the exercise, step by step
Pick a lot, trace it both directions, quantify it, and time the whole thing. A workable target for a small brand is a complete, documented trace within two to four hours. The number matters less than knowing yours and shrinking it.
- Pick a lot at random. Ideally one that went through a transformation or split, where genealogy is hardest.
- Trace one-up, one-back. What raw lots fed it, and every account it shipped to, with dates and quantities.
- Reconcile the numbers. How much you made, how much shipped, how much is still on hand should add up. Gaps are the finding.
- Run a contact test. Confirm you can actually reach every downstream account: a test message, not a real alarm.
- Time it. Start a clock at step one. The elapsed time is your headline metric to beat next quarter.
- Document as you go. Write the report while the gaps are fresh, not from memory next week.
Step three is where gaps surface. Here it is for one lot:
| Line | Units |
|---|---|
| Produced | 5,000 |
| Shipped (Acme 1,800 · Bly 1,400 · direct 900) | 4,100 |
| On hand | 700 |
| Unaccounted (the finding to chase) | 200 |
Produced minus shipped minus on-hand should be zero. Here it’s 200 units you can’t place: maybe a sample pull, maybe a mis-scan, maybe stock that shipped without a record. In a real recall those 200 are the ones you can’t reach, and finding them in a drill is the whole point.
How to write a mock recall report
A good report states the lot and scenario, the trace result both directions, the time taken, the quantity reconciliation, every gap you hit, and the fixes with owners and dates. It should be short enough to act on and specific enough to defend in an audit.
The point of the report isn’t the file. It’s the fix list. A buyer or auditor wants to see that you found problems and closed them: “the co-packer lot code wasn’t captured at receiving” becomes “capture it at the dock, owner J., done by the next run.” Keep the reports; the trend across them (time down, gaps closing) is the story you tell when someone asks whether you’re ready.
The recall plan template
A recall plan is the standing document a mock recall exercises. At minimum it names the team and roles, identifies the product and lots, holds the distribution and contact lists, and defines notifications, effectiveness checks, and where the records live.
| Section | What to fill in |
|---|---|
| Recall team & roles | Names and backups; who decides, who documents, who speaks to the FDA and to buyers |
| Product identification | Product, lot-code range, code-date format, quantity produced per lot |
| Distribution list | Where each lot shipped: accounts, dates, quantities |
| Reason & risk | What triggered the recall and the health-risk assessment |
| Contact list | Suppliers, co-packers, distributors, retail buyers, your FDA district |
| Notifications | Who you tell, in what order, with what message |
| Effectiveness checks | How you confirm product was held, returned, or destroyed |
| Reconciliation | Quantity produced vs. shipped vs. recovered |
| Records | Where the lot genealogy and this exercise log are kept |
What should you do next?
Run your first mock recall this quarter. Everything here costs a morning and a spreadsheet.
Prepare
- Write or update the recall plan using the template above: team, product, distribution, contacts, notifications, checks.
- Pick a lot to trace, ideally one that went through a transformation or split.
Run & improve
- Trace it both directions, reconcile the quantities, run a contact test, and time the whole exercise.
- Write the report as a fix list with owners and dates, and schedule the next drill, annual at a minimum.
Frequently asked questions
What is the difference between a mock recall and a mock withdrawal?
A mock recall practices for a safety hazard and is measured on speed and completeness; a mock withdrawal practices pulling product for a non-safety reason like a labeling or quality issue. The recall is the higher-urgency drill.
How long should a mock recall take?
There’s no fixed standard, but a small brand should aim to complete and document a full trace within two to four hours. Treat your current time as the baseline and work it down; the trend matters more than any single number.
Do retail buyers require a mock recall?
Often, yes. Distributor and retailer questionnaires and food-safety audit schemes commonly ask when you last ran one and what you fixed. Having a recent report with a closed fix list answers the question cleanly.