The article explores how crisis simulations can test traceability, decision-making, communication and response processes to help businesses identify weaknesses and improve recall readiness.
Food and product recalls are a critical part of protecting consumers, safeguarding brand reputation, and maintaining regulatory compliance when a product presents a safety, quality, or performance risk. While most organisations have recall procedures in place, crisis simulations provide an opportunity to test those plans in a realistic but controlled environment. This in turn allows teams to assess their readiness, decision-making, traceability, and communication processes before a real incident occurs. These exercises can deliver significant benefits across industries including food and drink, consumer products, automotive, pharmaceuticals, and retail by identifying weaknesses, improving response times, and building confidence in crisis management capabilities.
A successful traceability test does not, by itself, demonstrate that a business can manage a recall. Although a business may be able to locate the relevant information, it must also be able to turn that information into timely decisions and effective action.
A simulation allows a team to experience the challenges of a recall in a safe environment. It tests how the recall procedure works in practice and exposes assumptions that might otherwise remain unchallenged.
Why conduct a simulation?
A crisis simulation can assist with the following:
- Clarify roles and authority by confirming who can declare a recall.
- Determine who communicates with the media and regulators.
- The chain of command in a crisis and deputises when key people are unavailable.
Repetition can build confidence and speed, and in turn reduce panic, hesitation, and costly improvisation during a live incident.
The exercise also rehearses holding statements, customer notifications, and regulatory submissions under time pressure. It validates whether products can be traced one step forward and one step back within the target window of 2 – 4 hours, while testing mass-balance accuracy by reconciling quantities produced, shipped, returned and unaccounted for.
Simulations can expose broken decision trees, missing thresholds and unclear escalation triggers before a genuine event occurs. They also verify whether emergency contacts, customers, distributors, regulators and out-of-hours telephone numbers are current and reachable.
Documented exercises may provide evidence for BRCGS, FSSC 22000, IFS, retailer audits and regulators. They can also generate measurable indicators, including time to trace, percentage recovered and notification time, alongside a corrective action log that can be used to track improvement year on year. Faster, more tightly controlled recalls can mean less product is withdrawn, downtime is shorter and reputational damage is reduced.
Traceability should not depend on one person
A business may be able to trace its products while still depending on one person with the knowledge or system permissions required to extract and interpret the records. If that individual is unavailable, the identification of affected products can stall.
Shortened simulations may accept pre-prepared traceability records and therefore fail to test the complete trace or reveal this dependency. A more meaningful exercise should establish whether a deputy can access the system, extract the necessary records and interpret them without assistance from the usual specialist or the use of a pre-prepared trace.
The original batch may not represent the full recall scope
Teams may successfully trace an original batch but overlook rework, blended batches, repacked products or products sold under different brands. If related products are missed, affected stock may remain in circulation and the recall may later need to be expanded, potentially requiring a second public announcement.
Changes in ownership can add further complexity, particularly in agricultural supply chains, powdered commodities and third-party manufacturing arrangements. A demanding simulation should follow affected material through changes in ownership, processing and branding.
Recall authority must be clear
A recall procedure may name a response team without making it clear who can authorise the recall, who deputises or who makes decisions outside normal working hours. This can cause the response to stall while approval is sought.
There is also a risk that participants will take actions during a simulation that they would not have authority to take during a genuine incident. The exercise should use realistic availability. A decision-maker who would be ill, on holiday, or otherwise unavailable should not conveniently reappear. Delegated authority and out-of-hours arrangements need to be tested under realistic conditions.
A notification does not confirm that action has been taken
Customer contact details may lead to sales or accounts staff rather than someone with the authority to stop distribution or remove stock. Teams can also mistake sending a notification for confirmation that the required action has occurred.
Customers should not be contacted during a simulation unless everyone clearly understands that the contact is part of a test and, ideally, the arrangements have been agreed in advance. Unplanned calls can cause confusion and disruption.
Time-zone differences also need to be considered. If a manufacturer requires board-level input from suppliers overseas during the middle of the night; an otherwise appropriate contact may be unavailable when the UK-based team needs them.
Downstream responsibilities cannot be assumed
A manufacturer may expect its customer to contact distributors, retailers or consumers, even though the parties have never agreed or checked those responsibilities. As a result, affected products could continue moving through the supply chain while the business believes the recall is already underway.
The business should establish who is responsible for notifying each part of the supply chain and how those parties will confirm that action has been taken. This should reflect the actual allocation of legal responsibility and any retail own-brand contractual requirements, rather than assuming every customer operates in the same way.
Stock placed on hold may still be dispatched
Hold instructions and system controls may fail to cover third-party warehouses, goods already in transit or orders that employees have begun picking. Affected products could therefore leave the supply chain after the recall response has started, despite the business believing that dispatch has been blocked.
A simulation should check whether the hold instruction reaches every relevant location and order status. Systems such as SAP, which exchange information across companies, have improved control. However, system connectivity alone does not demonstrate that the hold process works.
The recall needs a defensible boundary
Production, cleaning and ingredient records may not establish a defensible boundary around the affected product. Without that boundary, the business could face a much wider recall or risk leaving affected stock outside the recall scope.
Teams may rely too heavily on small samples from paperwork, laboratory testing or audit findings without considering the wider risk picture. The simulation should examine the basis for the recall scope and the limits of the available evidence. It should also challenge assumptions, as unconscious bias or gaps in expertise can affect the risk assessment.
Communications must allow recipients to act
Recall communications may contain incomplete or confusing information about product names, pack sizes, batch codes or photographs. Slow approval can further delay the release of usable information.
If customers cannot confidently identify the affected stock, their enquiries can place additional pressure on an already stretched response team. The simulation should test whether the team can produce clear and accurate information and obtain approval in time. A lack of pre-prepared communications, materials and templates as a recurring area for improvement.
Product recovery must be practicable
A recall procedure may state that stock must be recovered without resolving how transport and returns will be managed. The business may not have established how returned products will be segregated and stored, whether sufficient capacity is available or how disposal will be handled.
A public recall announcement therefore risks committing the business to a major operational task that it is not ready to manage. Simulations often leave too little time to examine recovery, meaning that these discussions remain theoretical. Sufficient time should be allowed to explore the practical recovery arrangements and their limitations.
Recall plans must remain accessible during system disruption
Recall plans, contact information and traceability records may all be stored on the same network. If an IT outage or cyber incident makes that network unavailable, the team may have no accessible alternative.
The correct people may also be missing, while confusion can arise around the boundaries and overlap between crisis management, business continuity planning, and product recall. A simulation should challenge access to alternative information and test the triggers, handovers, and interactions between these arrangements.
From successful tracing to effective recall management
Traceability remains an important part of the recall process, but locating the relevant records is only one part of the challenge. An effective simulation tests whether the organisation can use that information to make decisions, communicate clearly, stop further distribution, recover affected products and coordinate its response when people or systems are unavailable.
By challenging the complete process rather than relying on a shortened traceability exercise, a crisis simulation can reveal practical weaknesses before the organisation faces a genuine recall.