Writing

18 September 2026 · 5 min read

How to Run a Mock Recall (and Why Traceability Alone Isn't Readiness)

How to Run a Mock Recall (and Why Traceability Alone Isn't Readiness)

Short answer: A mock recall is a scheduled test of your ability to identify, locate and account for an affected product as if a real recall were underway. Run it by picking a batch, tracing it forward and back within a set time, and reconciling the quantities. But if that is all you test, you are testing your traceability, not your readiness. A full mock recall also tests the response: who gets notified, how fast, who decides what, and whether the people involved actually know their roles.

Most brands pass the traceability half and quietly fail the response half, because they never test it. Here is how to run the whole thing.

The two things a mock recall should test

There are two separate questions inside every recall, and a good exercise tests both.

1. Can you find it? Given an affected batch, can you trace every unit forward to where it went and back to where it came from, and reconcile the numbers, within the time a retailer or regulator would expect?
2. Can you respond? Once you know what is affected, can your team coordinate the response. Notify the right people, assign actions, make containment decisions, and keep a defensible record, without it descending into a scramble?

Traceability software and a strong QMS help enormously with the first question. Neither answers the second. That is the gap a proper mock recall is for.

How to run a traceability mock recall

This is the baseline. Run it at least annually, and more often if your retailers require it.

1. Pick a target without warning the wider team. Choose a finished product batch, or trace back from a specific ingredient lot. Surprise is part of the test.
2. Set the clock. Give yourself a target time, commonly two to four hours, matching what your retailers expect. Note the start time.
3. Trace forward. Identify every customer, distributor and location the batch went to, and the quantity to each.
4. Trace back. Identify the ingredients, suppliers and lots that went into the batch.
5. Reconcile the quantities. Account for the full batch. Produced, shipped, in stock, sampled, wasted. The gap between what you made and what you can account for is your real exposure. A recovery rate below your target is the finding.
6. Record the time taken and the recovery percentage. These are your two headline numbers.

How to run a response mock recall

This is the half most brands skip. It does not need to be elaborate. It needs to be real.

1. Write a short scenario. For example: a consumer reports a foreign body, a retailer flags a mislabel, or a supplier notifies you of a contaminated ingredient. Keep it plausible for your operation.
2. Trigger it the way a real one would arrive. A phone call, an email, a complaint. Do not announce "this is a drill" to everyone at once. Start it with one person and see how far and how fast it travels.
3. Watch the first hour. Does the person who receives it know to notify the response team? Is a response team lead identified quickly? Does an actions log get started? Is severity assessed, or does everyone either panic or shrug?
4. Test the escalation matrix in anger. Try to reach the out-of-hours contacts you have on file. This is where brands discover the retailer technical contact left eighteen months ago and the insurer's number goes to a dead line.
5. Force a containment decision. Make the team decide whether to quarantine, prepare a withdrawal, or hold. Time how long the decision takes and how clearly it is owned.
6. Stop and debrief while it is fresh. Hold a review within a week. Capture what worked, what broke, and one owner and date for each fix.

What to measure

Do not let a mock recall end with "it went fine." Score it.

Why traceability alone is not readiness

A brand can have flawless traceability and still handle a recall badly. The batch was identified in ninety minutes, and then three hours were lost because nobody was sure who could authorise the quarantine, the comms lead was on annual leave with no cover, and the retailer contact on file had moved on. None of that shows up in a traceability exercise. All of it shows up in a real recall.

Readiness is traceability plus response. Test both, or you are only half-tested.

Frequently asked questions

How often should you run a mock recall? At least once a year as a baseline. Many retailer standards and certification schemes expect annual or more frequent exercises. Run an additional one after any significant change to your suppliers, sites or systems.

What is a good mock recall recovery rate? Aim to account for as close to 100 percent of the batch as possible within your target time. The exact threshold depends on your retailer and scheme requirements. The more useful output is understanding any gap and closing it.

What is the difference between a mock recall and a traceability exercise? A traceability exercise tests whether you can find and account for an affected product. A full mock recall tests that plus the response: notification, ownership, decisions and record-keeping under time pressure.

Who should be involved in a mock recall? Traceability and quality for the trace, and the full response team for the response half. Testing only the quality team means you never test the coordination that a real recall depends on.

Friday4:30 is the coordination layer that runs the response half of a recall, live and logged. Mock or real, the platform holds the escalation matrix, the actions log and the first-hour structure in one place. If you want to run your next mock recall on it, get in touch.