When a food safety incident hits, there's no time to decide who speaks, what to say or how to reach customers. Those decisions need to be made beforehand. Companies that handle incidents well rarely do so by improvising. They do it because they had a plan, had practised it, and knew exactly who would do what in the first hour.
Our article oncommunicating during a recall or food safety crisis covers what good communication looks like in the moment. This one is about the groundwork: how to build a crisis communication plan before you need it.
During an incident, people are under pressure, information is incomplete and everyone wants answers at once. In those conditions, several things tend to go wrong without a plan:
Nobody is sure who has authority to speak
Messages are drafted from scratch under time pressure
Different people say different things to different audiences
Key audiences, like retailers or regulators, are told late or not at all
Approval loops delay responses while speculation fills the gap
A plan doesn't remove the pressure. It removes the avoidable confusion, so your energy goes into the actual problem.
Start by agreeing what triggers the plan. Not every complaint is a crisis, and treating everything as one leads to fatigue.
Examples of triggers might include:
A suspected or confirmed contamination or allergen issue
A recall or withdrawal, or a decision to consider one
An illness report linked to your product
A regulator inquiry or inspection finding with public impact
Media or social media attention about your product's safety
Set levels of severity, such as a watch level, an incident level and a full crisis level, with a clear description of each and who decides which level applies. This keeps the response proportionate.
Name the people, not just the roles, and name deputies in case someone is unavailable. A typical team includes:
A lead or decision maker with authority to act
Quality and food safety to provide technical facts
Regulatory affairs for notification duties and regulator contact
Legal to review statements and obligations
Communications to draft and coordinate messaging
Operations and supply chain for product tracing and logistics
Customer service and sales for customer and retailer contact
A scribe to keep a record of decisions and times
Write down who does what, and how to reach each person at any hour. Contact details go stale quickly, so check them regularly.
Different groups need different information, at different times. List who you'd need to reach:
Consumers and the public
Customers, retailers and distributors
Regulators and authorities
Employees
Suppliers and partners
Media
Investors, lenders or owners, where relevant
Insurers
For each, note what they most need to know, how you'd reach them and who owns that relationship. OurStrategic Communications 101 course covers how to think through audiences and messages.
Confusion about who speaks is one of the most damaging problems in an incident. Decide in advance:
Who the official spokesperson is, and who the backup is
Who may speak to media, and who may not
How statements are drafted, reviewed and approved
How quickly approvals must happen, since long approval chains slow everything down
Build in legal and regulatory review without letting it become a bottleneck. Agree in advance on a fast route for urgent statements.
You can't write the final message before you know the facts, but you can prepare the structure. Useful prepared items include:
A holding statement, a short initial message that acknowledges the situation, says you're investigating and promises further updates
Customer and retailer notification templates
Employee briefing notes
A set of anticipated questions and draft answers
A format for regular updates
Good messages are clear, factual and calm. They say what is known, what isn't yet known, what people should do and when the next update will come. Avoid guessing, and don't state anything as fact before it's confirmed. Explaining technical points in plain language is a skill in itself.
Decide in advance how you'll reach each audience and who controls each channel. That might include:
Direct contact for customers and retailers
Your website, with a ready place for an incident notice
Social media accounts and who monitors them
Press statements and media contact routes
Internal channels for staff
Formal channels for regulators
Keep messaging consistent across all channels. Contradictions between a press statement, a social post and a customer email do more harm than most people expect.
Communication depends on facts, and facts depend on your ability to trace products quickly. The plan should connect to your technical response: how you identify affected batches, how decisions on withdrawal or recall are made, and how information flows from technical teams to communicators.
Check this ahead of time. Ourproduct safety compliance checklist article includes a readiness section, and a regular compliance audit shows whether you really could trace and respond. Notification duties to authorities differ by country, so involve regulatory and legal advisers when documenting them.
During an incident, what people say about you matters as much as what you say. Decide who will monitor media and social channels, how often, and how misinformation will be addressed. Fast, factual correction is better than silence, and tone matters.
Employees are an audience, and often the first people asked about the incident by friends and family. Give them accurate information promptly and tell them who to refer questions to. The team handling the incident also needs support, because long hours and pressure affect judgment.
A plan that has never been tested is mostly a guess. Run a tabletop exercise at least once a year: present the team with a realistic scenario and have them work through it in real time. These exercises reveal missing contacts, slow approvals and unclear roles while the stakes are low.
Keep notes, fix what you found, and update the plan. Rotate the scenarios so the team practises different kinds of incidents.
After any real incident, hold a structured review. What worked, what didn't, what surprised you, what should change? Update the plan, and share lessons across the team. Reviewing near misses is valuable too.
A usable plan is short enough to be read in a hurry. At minimum, it should include:
Triggers and severity levels
Team roles, deputies and contact details
Audience list and ownership
Spokesperson and approval process
Holding statement and templates
Channels and who controls them
Links to recall and tracing procedures
Monitoring approach
Exercise schedule and review process
Keep it in a place everyone can reach, including when systems are down, and make sure the team knows where it is
Writing it once and forgetting it. Contacts and roles change, so the plan needs regular review.
Making it too long. Nobody reads a hundred pages in the first hour.
Leaving out key audiences. Retailers, regulators and employees are often forgotten.
Unclear authority. If nobody knows who can approve a statement, time is lost.
Waiting for complete information. A prompt, honest holding statement beats silence.
Never testing it. Exercises are where the weaknesses show up.
You don't need a perfect plan on day one. Begin with the team list, the spokesperson, a holding statement and a short audience map, then build from there. Shared understanding across quality, regulatory, communications and operations makes everything easier.
Build the skills behind your plan withCrisis Communications 101, which covers how to communicate clearly and calmly when an incident happens.
