Natasha’s Law Explained: What Food Businesses Must Do


TL;DR: Kitchen crisis protocols are pre-agreed, practised responses to specific emergencies. Head chefs who build them before a crisis hits keep service running. Those who wait until something goes wrong find out too late.
Every kitchen crisis I have ever walked into had one thing in common: nobody had thought about it until it was already happening. That is not bad luck. That is a failure of preparation, and it is entirely avoidable.
I have been in kitchens where the cold room packed up on Christmas Eve, where a chef de partie sliced through a tendon twenty minutes before service, where a supplier delivered two hundred portions of the wrong fish and expected gratitude. Each time, the difference between a kitchen that kept moving and one that collapsed was whether the head chef had a plan. Not a vague idea. An actual, rehearsed, written-down plan.
Kitchen crisis protocols are not glamorous. Nobody puts them on their CV or posts about them on Instagram. But they are the reason some kitchens survive disasters and others fall apart in front of a full restaurant. If you run a kitchen, you need them. And you need them before anything goes wrong, not during.
A kitchen crisis protocol is a pre-agreed set of actions that the team knows to take when a specific problem occurs. It is not a laminated sheet nobody reads. It is a practised response, built into the culture of the kitchen, so that when someone’s brain goes blank under pressure, the training takes over.
There are two broad categories worth separating out. The first is operational crisis: equipment failure, a key team member not showing up, a supplier letting you down, a menu that suddenly cannot be executed. The second is safety crisis: fire, a serious injury, a food safety incident, a gas leak. Both need protocols. They require different kinds of thinking and different speeds of response.
Head chef emergency planning covers both, and the best chefs I have worked with treat the two as equally important. Safety first, always. But operational resilience is what keeps people in jobs and restaurants open.
Ask yourself, honestly, whether your kitchen has a clear answer to any of the following. If a larder chef calls in sick on a Saturday morning, who does what, and is that written down anywhere? If the dishwasher floods the kitchen forty minutes before service, what is the sequence of actions? If a guest has a severe allergic reaction, does every single person on your team know their role, not just the front of house manager?
Most kitchens can answer the last one, because allergen training is legally required. But the first two? Usually not. Operational crisis management in food service tends to live entirely inside one person’s head, and that person is usually the head chef. Which is fine, until the head chef is the one having the crisis.
I once broke two fingers on my left hand three hours before a function for ninety covers. I kept going, which was stupid, but the point is that no one else in that kitchen would have known what to do had I walked out. That was my fault, not theirs.
Good restaurant crisis management does not require a forty-page document. It requires honest thinking about what is most likely to go wrong, followed by a clear, simple response plan for each scenario. Start with the most probable failures, not the most dramatic ones.
Here is how to build a framework that actually gets used:
Chef leadership under pressure is not about being the calmest person in the room. It is about making good decisions quickly, and that is much easier when the decision has already been made in a calmer moment.
Some things really do belong on a laminated sheet. Kitchen emergency procedures for fire, gas leaks, and serious injury should be physically posted in the kitchen, not just discussed at induction and forgotten. Every new team member should be walked through them on their first shift, not handed a sheet to read in the break room.
At minimum, your posted procedures should cover:
None of this is novel. It is also, in my experience, consistently underdone. I have walked into kitchens in London with decades of reputation behind them where the fire extinguisher was behind a shelf nobody could reach and the first aid kit had plasters from 2019.
Writing protocols is the easy part. Restaurant staff crisis training is where most operations fall short. A document is not training. Training is rehearsal, repetition, and the occasional uncomfortable conversation about what someone did wrong.
You do not need to run full-scale drills every month. But you should be doing something more than hoping everyone has read the folder. A fifteen-minute briefing once a quarter, walking through one specific scenario, is more valuable than an annual training day nobody remembers. Pick a different scenario each time. Rotate who leads the discussion. Make it normal, not theatrical.
The other thing restaurant staff crisis training must include is permission. Junior staff need to know they are allowed to stop service, raise an alarm, or refuse an instruction if they believe there is a genuine safety issue. That sounds obvious. In a kitchen with a strong hierarchy, it is anything but. I have seen commis chefs carry on working next to a gas smell because they did not feel they could say anything. That is a failure of culture, and culture is set by the head chef.
Food service incident response covers the non-safety crises that nonetheless threaten the service. A key supplier failing to deliver. A menu item that turns out to be off or unavailable. A piece of equipment breaking mid-service. These happen in every kitchen, repeatedly, and yet many kitchens handle them through improvisation every single time.
A few practical habits that help:
None of this replaces good sourcing and reliable suppliers. But reliability is a target, not a guarantee, and the kitchens that manage well are the ones that have already thought through the contingencies.
Every six months is a sensible minimum, and any time there is a significant change to the team, the menu, or the equipment. A protocol built around a chef who has since left is not a functioning protocol.
Yes, for anything that involves a guest or requires a coordinated response between the two teams. Allergen reactions, fire evacuations, and serious injury protocols all need front and back of house to know their respective roles. Keeping protocols siloed inside the kitchen is a common mistake that creates confusion exactly when you can least afford it.
A clear allergen response procedure, because it is both legally required and the scenario with the most serious potential consequences. After that, a staffing contingency plan, because the absence of a key team member is far more likely to disrupt service than most equipment failures.
Keep it conversational and specific to your kitchen. Walk through a real scenario that has actually happened in your restaurant, or one that very nearly did. Ask the team what they would have done. People engage with problems they can picture. They glaze over at generic training slides.
The kitchens I respect most are not the ones that have never had a crisis. They are the ones where, when something went badly wrong, the team knew what to do and got on with it. That does not happen by accident.
Chef Ian McAndrew’s specialist eBooks and guides are available directly on ChefYesChef, including his technical titles and autobiography. If you want more practical, chef-led reading beyond this article, you’ll find the full collection here.
Chef Ian McAndrew works with chefs, businesses, and individuals on a wide range of culinary projects, from concept development to practical problem-solving.
If you’d like to talk through an idea or need informed guidance, you’re welcome to contact him.
Essential cookies required for the site to function. Cannot be disabled.
Cookies that help us understand how visitors use the site.
Cookies used to deliver relevant advertisements.
Privacy Policy Terms of Service