How Should a Food Business Run a Mock Recall?

A mock food recall is a controlled exercise that tests whether a business can trace a product, identify affected stock and sites, communicate the right instruction, account for quantities and close any gaps. It is not a real consumer recall, and it should never be allowed to create a false public or regulatory alert.

TapTick can help teams schedule the exercise, send tasks to relevant sites, capture results and evidence, and track the corrective actions that follow. It does not decide whether a real withdrawal or recall is required or replace contact with the competent authority. See the TapTick features.

What should a mock recall test?

The exercise should test the complete response, not just whether someone can find an invoice. A useful mock recall asks the business to prove that it can:

• identify the exact product, pack size, batch, lot or date code in scope;
• trace the product one step back to its supplier;
• identify business customers, distribution points and sites that received it;
• find affected stock in sale, storage and preparation areas;
• identify whether it was used as an ingredient in another product;
• send a clear, consistent instruction to everyone who needs it;
• account for stock received, used, sold, transferred, held or otherwise unresolved;
• record decisions, times, exceptions and evidence; and
• assign and close corrective actions where the process did not work.

A traceability lookup alone is useful, but it is not the whole exercise. A recall plan can still fail because contact details are out of date, a duty manager does not see the alert, similar products are confused, secondary storage is missed or the final stock reconciliation is incomplete.

Is a mock recall required by law?

The legal duties and the exercise itself should be kept separate.

In Ireland, food businesses must maintain traceability and take the required withdrawal, recall and notification steps when unsafe food has been placed on the market. FSAI's Guidance Note 10 explains how to plan for those events and says it is best practice to test a recall or withdrawal plan periodically using a mock exercise.

In Great Britain, the relevant traceability and unsafe-food response duties sit within assimilated food law. FSA guidance says a business that believes it has supplied harmful, unfit or otherwise non-compliant food should immediately withdraw or recall it and tell its competent authority. The guidance provides practical templates for contacts, decisions, authority notifications, business communications and point-of-sale notices.

The FSA incident guidance also applies to Northern Ireland, while the underlying legal framework differs from Great Britain in important respects. Food businesses should follow the rules and regulator instructions that apply to their location.

The operational gap is real. Food Standards Scotland's Small and Micro FBO Survey, published on 19 August 2026, found that among 83 surveyed businesses with written recall or withdrawal procedures, 27% ran mock recall exercises at least every three years and 51% never did so. The survey describes practice; it does not set a legal testing interval.

How often should the exercise be run?

Use the regulator recommendations as the starting point: FSAI recommends testing the plan annually, while UK FSA/FSS guidance recommends reviewing the plan and procedures annually and says the review can include a mock exercise. These are guidance recommendations rather than a universal statutory mock-recall interval. Document the schedule and meet any stricter customer or certification requirement.

Factors that justify more frequent testing include:

• many sites, warehouses, franchisees or distribution routes;
• short shelf-life products or rapid stock movement;
• high-risk or ready-to-eat foods;
• frequent product, supplier or packaging changes;
• ingredients used across many finished products;
• local purchasing outside the central supply chain;
• recent traceability failures, recalls or audit findings; and
• new software, stock systems or organisational structures.

Do not wait for the next scheduled exercise after a major change exposes a new route through the supply chain. Test the changed part once it is operating, and retest any control that previously failed.

How should the exercise be prepared?

Appoint one coordinator to design and control the exercise. Other participants should receive enough information to act safely, but the coordinator does not need to give them every answer in advance. The test is more useful when staff must use the real procedure, contact list and records.

1. Select a product and scope. Use a real historical or current product with a defined batch, lot or date code. Avoid a vague instruction such as “all chicken products”.
2. Write a fictional trigger. For example, a supplier reports that one batch may contain an undeclared allergen. Mark every document and message clearly as an exercise.
3. Define the boundary. Decide whether the test covers traceability only, the full site response, consumer-notice drafting, out-of-hours contacts or all of these.
4. Set measures before starting. Decide what will be timed and what evidence participants must return. Regulators do not set one universal completion target, so the business must choose a realistic internal target.
5. Protect real operations. Do not contact consumers, suppliers, the media or regulators as though a real incident exists. Do not dispose of or unnecessarily disrupt safe stock.
6. Set a stop rule. If the exercise uncovers a genuine safety problem, stop treating it as a simulation and follow the real incident procedure.

How do you run the exercise?

1. Start the decision log

Record the start time, scenario, coordinator and people contacted. From that point, capture key decisions and the reason for each one.

2. Identify the affected product precisely

Confirm the product name, supplier, pack size, batch or lot, date code, quantity and hazard described in the scenario. Check whether similar products could be mistaken for it.

3. Trace backward and forward

Use the records the business would rely on during a real incident. Identify the supplier and receipt details, then identify every business customer, warehouse or site that received the affected product. For direct retail sales to final consumers, test how the business would identify stock, sales periods and the need for consumer communication.

4. Check ingredient use and transfers

Determine whether the product was repacked, transferred between sites or used in prepared food. A recalled ingredient may create a wider set of affected finished products. See our guide to recalled ingredients used in multiple products.

5. Test the site response

Send a clearly marked exercise instruction to the participating sites. Ask each one to acknowledge it, search all relevant locations, identify the batch, report quantities and flag any discrepancy. If physical stock is used in the drill, prevent accidental disposal or customer confusion by marking the activity “SIMULATION ONLY”.

6. Test the communications pack

Prepare, but do not issue, the communications that a real event could require. That may include an authority notification, supplier or business-customer message, internal instruction and point-of-sale notice. Check that templates contain the information needed to identify the product and tell recipients what action to take.

7. Reconcile the product

Compare the amount received with the amounts still held, transferred, used, sold or otherwise accounted for. Record unexplained quantities instead of forcing the numbers to balance. The gap is one of the most valuable results of the exercise.

8. Close the exercise

Record the end time, results and unresolved points. Assign every improvement to an owner with a due date. A test is not complete when the meeting ends; it is complete when the important gaps have been corrected and, where necessary, retested.

What should be measured?

Useful measures include:

• time taken to identify the product and supplier;
• time taken to identify affected customers, sites and transfers;
• percentage of participating sites that acknowledged the instruction;
• percentage that returned complete information;
• time taken to locate and verify stock;
• quantity received compared with quantity accounted for;
• accuracy of contact and escalation details;
• number of products or locations initially missed;
• quality of the draft authority, business and consumer communications; and
• corrective actions completed by their agreed dates.

A fast result is not automatically a good result. Speed matters during a real incident, but accuracy, complete coverage and clear evidence matter too. Record both.

What records should be kept?

Keep a short exercise file containing:

• date, scope, scenario and participants;
• product, batch and distribution information used;
• timeline and decision log;
• site acknowledgements and returned evidence;
• traceability reports and quantity reconciliation;
• draft communications and contact checks;
• what worked and what failed;
• corrective actions, owners and due dates;
• approval of the final review; and
• retest result where a significant gap was found.

Retain the record under the business's document and record-control rules. The value is not a certificate saying a drill occurred; it is evidence that the system was challenged, weaknesses were identified and improvements were completed.

How should a multi-site test work?

A central coordinator should issue one controlled instruction, identify which locations are in scope and maintain a live view of completed, exception and no-response sites. Local teams should follow the same search, verification and evidence steps.

A practical scenario might use a fictional supplier notice for one batch of cooked chicken delivered to six sites and used in salads and wraps. The test should reveal whether head office can:

• identify all six recipient sites from purchasing and transfer records;
• find locally transferred stock;
• identify finished products that used the ingredient;
• obtain a named response from every duty manager;
• separate genuine zero-stock reports from missing information; and
• reconcile the overall quantity without relying on unstructured messages.

For the real-event workflow, read how to manage a food recall across multiple sites.

Common mock-recall mistakes

• Testing only head office. The exercise never checks whether a site can find the right product.
• Choosing an easy product. A single unopened case at one location does not challenge ingredient use, transfers or mixed supply routes.
• Giving staff all the answers. The test proves the coordinator's preparation, not the team's recall readiness.
• Confusing the exercise with a real alert. Messages are not clearly marked, creating unnecessary alarm.
• Stopping at traceability. No communication, site action, quantity reconciliation or decision log is tested.
• Accepting “done”. Responses do not identify the product, batch, quantity, person or time.
• Ignoring non-responses. The sites that do not reply are treated as an administrative issue instead of a control failure.
• Closing without corrective action. Gaps are discussed but not assigned, completed or retested.

Mock recall checklist

1. Appoint an exercise coordinator.
2. Select a real product and precise batch, lot or date code.
3. Create a fictional, clearly labelled scenario.
4. Define the sites, supply routes and response steps in scope.
5. Set timing, accuracy, acknowledgement and reconciliation measures.
6. Start the decision log.
7. Trace the product backward and forward using live records.
8. Check transfers and use as an ingredient.
9. Test site instructions, acknowledgement, stock search and evidence.
10. Prepare but do not issue external communications.
11. Reconcile quantities and record every gap.
12. Assign corrective actions with owners and due dates.
13. Retest important failures.
14. Review the exercise frequency after significant change.

Official sources

• Food Safety Authority of Ireland: Guidance Note 10 — Product Recall and Traceability
• Food Safety Authority of Ireland: Traceability
• Food Standards Agency: Food incidents, product withdrawals and recalls
• Food Standards Scotland: Withdrawals and recalls guidance
• Food Standards Scotland: Small and Micro FBO Survey 2025 — recall and withdrawal procedures

This article is general operational guidance, not legal advice. Follow the rules and competent-authority instructions that apply to your business and location.