Running a Mock Recall to Test Traceability

A mock recall is a practice run that tests whether your business can trace an implicated product one step back to its supplier and one step forward to your customers, and account for all of it, before a real recall forces the issue. Set a target, start a stopwatch, follow the paper and digital trail, then measure how much product you accounted for and how long it took. Fix the gaps you find and keep the test record. Key takeaways: A mock recall tests your recall plan without a real incident: can you trace product back to a supplier and forward to customers, and account for it quickly?. Pick a real product and batch or use-by date, then trace one step back and one step forward from your records.. Time the exercise and calculate a reconciliation percentage: quantity accounted for divided by quantity received.. Aim high on accountability and speed, then treat every gap as a corrective action with an owner and a due date.. Keep the dated test record with your food safety documentation; many programs and auditors expect mock recalls at set intervals.. Mock recall scorecard: Measure, What to record, What good looks like. Reconciliation — Quantity accounted for / quantity received — Close to all product accounted for. Trace time — Elapsed time from trigger to full account — As fast as practical for your operation. Direction back — Supplier, batch, date, quantity found — Immediate supplier confirmed from records. Direction forward — Customers or destinations, dates, quantities — All direct customers or affected stock identified. Gaps — Issues found and corrective actions — Every gap has an owner and a due date. What a mock recall is and why you run one A mock recall is a simulated recall. You choose a product already in your records, then work backwards and forwards through your paperwork and systems to prove you can find where it came from and where it went. Nothing is actually recalled and no authority is notified, but you treat the exercise as though a genuine safety problem had been found. The point is to test the plan before you need it. A real recall is stressful, time-pressured and public. If your traceability has holes, you will discover them at the worst possible moment. A mock recall surfaces those holes safely so you can fix them in advance. It also proves the system to your team, your customers and your auditor. Many food safety programs, third-party certification schemes and customer supply agreements expect documented recall testing at set intervals, so confirm the exact frequency required for your business with your certifier, customer or the relevant food safety program. One step back and one step forward Australian traceability is built on the principle that each business must be able to trace one step back and one step forward. One step back means you can identify the immediate supplier of an ingredient or product, including what you received, when, how much and any batch or lot identifier. One step forward means you can identify who you supplied, when and how much, at least to your direct business customers. Retailers and food service businesses selling only to the final consumer generally cannot trace individual shoppers, so forward tracing for them focuses on identifying affected batches on the shelf or in the kitchen and removing them. A mock recall exercises both directions from a single chosen product so you can see whether the links actually connect. Back: supplier name, product, batch or lot code, delivery date, quantity received, and the invoice or delivery docket.. Forward: customers or destinations supplied, dates, quantities, and the batches or use-by dates involved.. Internal: how the incoming batch maps to what you produced, packed or served, if you transform the product.. Choose the scenario and the target Pick one real product that exists in your current or recent records. A high-volume ingredient used across several finished products makes a stronger test than a single simple item, because it forces your system to follow multiple threads. Decide the trigger you are simulating, for example a supplier notifying you that a specific batch may be contaminated with an allergen or a pathogen. Nominate the exact batch code, lot number or use-by date you are tracing, and note the quantity you originally received. That received quantity is your baseline for the reconciliation calculation later. Write the scenario down before you start so the exercise has a clear, fixed target and nobody moves the goalposts once the trace gets difficult. Time the trace and reconcile the quantity Start a stopwatch or note the start time, then work the trail using only the records you would genuinely have in a real event. Trace back to confirm the supplier and delivery, then trace forward to establish where every unit of that batch went: still in stock, used in production, sold or supplied on, wasted, or on hold. Add up what you can account for and compare it to what you received. The reconciliation percentage is the quantity accounted for divided by the quantity received, expressed as a percentage. A strong result accounts for close to all of the product; a low percentage means product is unaccounted for and, in a real recall, could still be in the market. Record the elapsed time as well, because speed matters when a genuine recall is underway. Quantity received (baseline) from the delivery record.. Quantity accounted for: in stock, in production, sold, wasted, on hold.. Reconciliation percentage = accounted for / received x 100.. Total time taken from trigger to full account of the batch.. Find and fix the gaps The value of a mock recall is in what it exposes. Common weaknesses include batch codes that were not captured on receipt, decanting or repacking that broke the link between an incoming lot and a finished product, missing or illegible delivery dockets, no clear record of who supplied what to which customer, and staff who did not know where the recall plan lives or who has authority to act. Treat each gap as a corrective action, not just a note. Give every gap an owner, a specific fix and a due date, then verify the fix. If the trace took too long, look at where time was lost, whether records are centralised, searchable and up to date, and whether the right people were available. A gap left unfixed will reappear in the next real event. Keep the test record Document the exercise while it is fresh. A good mock recall record shows what you tested, how you performed and what you changed as a result, which is exactly what an auditor or customer wants to see. Store it with your food safety documentation and diarise the next test. Keeping consistent records over time also lets you show improvement, for example a rising reconciliation percentage or a falling trace time across successive exercises. Date of the exercise and who took part.. The scenario, product, batch or use-by date and the received quantity.. Reconciliation percentage and total time taken.. Gaps identified, corrective actions, owners and due dates.. Sign-off and the scheduled date for the next test.. How a mock recall relates to a real one A mock recall tests your ability to trace and account for product; it is not a real recall and involves no public notification. In a genuine food recall in Australia, businesses coordinate with Food Standards Australia New Zealand (FSANZ) and the relevant state, territory or Commonwealth authority, and the recall process includes notifying authorities, communicating with customers and, for consumer-level recalls, the public. Because the legal and procedural requirements of an actual recall vary by product, jurisdiction and situation, follow the current FSANZ Food Industry Recall Protocol and confirm the specific steps with your state or territory regulator. Use the mock recall to make sure that, when a real one comes, the traceability part is already solved. Checklist: Real product and specific batch or use-by date chosen as the target.. Quantity received recorded as the reconciliation baseline.. Start time noted before tracing begins.. One step back completed: supplier, batch, date, quantity confirmed.. One step forward completed: destinations, dates, quantities identified.. Reconciliation percentage calculated.. Total trace time recorded.. Every gap logged with an owner, fix and due date.. Test record filed and next mock recall scheduled.. Common mistakes: Using a made-up product instead of one that exists in your real records, so the test proves nothing about your actual system.. Not timing the exercise, which hides how slow a real response would be.. Skipping the reconciliation maths and just declaring the trace successful.. Only tracing one direction instead of both back and forward.. Recording gaps but assigning no owner, fix or due date, so nothing changes before the next test.. Failing to keep a dated record, leaving nothing to show an auditor or customer..