Kitchen Training Culture: Why Inductions Fail


TL;DR: Inclusive menu design allergens means building safety into structure, not bolting it on. When menus and kitchen culture are designed with allergens in mind from the start, every guest eats with confidence and the food stays good.
Inclusive menu design for allergens is not about producing a separate, apologetic sheet of ‘safe options’ that reads like a hospital discharge form. It is about building a kitchen culture and a menu structure where every guest can eat with genuine confidence, and where the chef’s craft remains fully intact.
I remember a dinner service, probably fifteen years ago now, when a guest quietly mentioned a nut allergy at the table. The waiter came back to the pass looking mildly terrified. We had three dishes on the menu that week involving almonds in some form, one of them a garnish that had been added because it looked pretty (it did not look pretty, for what it is worth). We managed, but only just, and only because I happened to be on the pass that night. That is not good enough. That is luck dressed up as competence.
Since then I have thought quite carefully about how kitchens actually build allergen safety into their practices, rather than bolting it on at the end like a fire extinguisher nobody has checked in three years. The answer, it turns out, is mostly about design. Menu design, kitchen design, and the design of how your team communicates.
The fourteen legally recognised allergens in the UK are well documented. Celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soybeans, sulphur dioxide, and tree nuts. Most chefs could list them in their sleep. The problem is rarely ignorance of the list. It is the gap between knowing the list and designing a menu that accounts for it from the outset.
Allergen friendly menu planning begins at the writing stage, not at the point of a guest’s request. When you draft a new dish, you should be mapping its allergen profile at the same time as you cost it. If a sauce contains a hidden allergen, say a worcestershire sauce with anchovies in a dish you are not advertising as containing fish, that is a design failure. Not a guest relations problem. A design failure.
The practical shift here is small but significant. Build a simple allergen matrix for every dish on your menu, updated every time a recipe changes. One column per allergen, one row per dish. Cross it weekly. It takes twenty minutes and saves a great deal of anxiety on both sides of the pass.
There is a tendency, particularly in establishments that are slightly nervous about allergens, to respond to any dietary restriction with the phrase ‘we can probably do something’. That phrase is not reassuring. It is the culinary equivalent of ‘the train might be on time’. Guests with serious allergies are not looking for probably. They are looking for yes, with certainty behind it.
Dietary inclusivity in restaurants is built on specificity. When a guest mentions an allergy, your front of house team should be trained to ask precise questions: is this an intolerance or a diagnosed allergy? Does cross-contamination present a risk? Are there other restrictions alongside it? This is not interrogation. It is care, and guests with genuine allergies recognise the difference immediately.
A confident answer from a waiter, backed by genuine kitchen knowledge, does something quite particular for a guest. It relaxes them. And a relaxed guest eats better, orders more generously, and remembers the experience as a good one. That is the hospitality argument for getting this right, separate from the legal and ethical ones, which are not small.
The kitchen can be immaculate in its allergen practices and it still falls apart if the waiter does not pass the information correctly. Front of house staff need to understand which dishes contain which allergens, how modifications work in your specific kitchen, and when to escalate a query directly to the chef. This should be part of induction, not something mentioned once at a team briefing and then forgotten.
Run allergen scenario training during quiet service periods. Give staff a fictional guest with a specific allergy and ask them to walk through the conversation, the menu, and the kitchen communication. It sounds slightly corporate, but it works, and it surfaces gaps in knowledge you did not know you had.
Safe menu design in hospitality does not mean offering a stripped-down menu that is technically safe but thoroughly joyless. It means building dishes that are genuinely delicious and either free from common allergens by nature, or modifiable without compromising the dish’s character.
Some of the best food is naturally free from the most common allergens. A properly made roast chicken, a piece of grilled fish with seasonal vegetables, a good risotto. None of these require elaborate substitution. The problem tends to arise with sauces, stocks, dressings, and garnishes, the parts of a dish that are often made in larger batches and contain ingredients that do not make it onto the menu description.
Review your stocks first. A chicken stock made with celery is a celery-containing stock. If that stock goes into your ‘simple roast vegetable’ dish, the dish is not celery-free, regardless of what it says on the menu. This is a common one. Make allergen-specific stocks where your menu demands it, and label them clearly in the kitchen.
Cross-contamination is where good intentions go wrong. A kitchen that takes allergy friendly restaurant practices seriously has designated areas, boards, and utensils for allergen-free preparation. Not shared equipment washed between uses. Separate equipment, used only for that purpose, stored and labelled accordingly.
This does not require a complete kitchen redesign. In most kitchens, a clearly marked set of chopping boards, a dedicated pan or two, and a specific shelf in the fridge for allergen-safe components is enough to manage the majority of requests safely. The labelling matters as much as the separation. If it is not marked, it will be grabbed in a rush by a commis who means no harm but does not know the context.
Write allergen requests on a separate docket, printed or written in a different colour if your system allows it. Mark the plate going to the pass. Have the chef, not a runner, verify it before it leaves the kitchen. These are small steps. They matter enormously.
Going Further: Safe Plates
If you want to go further than an article can take you, Safe Plates: Mastering Dietary Compliance covers this properly. It works through the legal frameworks across the UK, EU, and US including Natasha’s Law and the FASTER Act alongside the operational side: how to build allergen systems that hold under pressure, how to train staff so the knowledge actually sticks, and how to create the kind of documentation that protects a kitchen when something goes wrong. There are checklists, supplier-verification templates, training logs, and case studies built for real service environments. It costs less than a round of drinks and takes a few hours to read. What it gives you is a structure you can actually use.
A menu communicates something about a restaurant before a single dish arrives. A menu that acknowledges dietary needs clearly, without reducing everything to a grid of ticks and crosses, tells a guest that they have been considered. That consideration is a form of hospitality in itself.
Marking dishes that are naturally free from the most common allergens, or that can be adapted on request, is a practical approach that most guests find genuinely useful. It does not need to dominate the menu. A small symbol system with a key, or a brief note at the bottom of the page, does the job without turning the menu into a compliance document.
Some restaurants now offer a brief allergen conversation at the start of the meal as standard, particularly in tasting menu formats where guests are committed to a set course. This works well. It removes the slightly awkward moment of guests raising allergies mid-service, and it gives the kitchen time to plan properly rather than improvise.
Yes. Under UK food information regulations, food businesses must be able to provide allergen information for the fourteen major allergens in any dish they serve. This can be provided in writing on the menu, verbally by trained staff, or via a written document available on request, but the information must be accurate and accessible.
In most kitchens, genuine ‘free from’ guarantees are very difficult to make because of the risk of cross-contamination during preparation. What a kitchen can guarantee is that it has followed specific protocols to minimise that risk. For guests with life-threatening allergies, honesty about the limits of what a kitchen can safely manage is more useful than a reassurance that may not be accurate.
The answer is preparation, not improvisation. If allergen information is mapped before service, the kitchen knows exactly which dishes can be modified and how. A clear docket system and a designated preparation process means allergen requests are handled as part of the normal flow rather than as interruptions to it.
In most cases, no. If an adaptation involves a significant additional ingredient or substantially more preparation time, a modest adjustment might be reasonable. Charging a guest for the fact that they have an allergy, however, is poor practice and damages the trust you are trying to build. If allergen adaptations are part of your menu design rather than an afterthought, the cost differential is usually negligible.
The kitchen that handles allergens well does not do so by removing ambition from the menu. It does so by knowing the menu properly, communicating it clearly, and treating every guest’s safety as part of the craft rather than an obstacle to it. That almond garnish I mentioned at the start? We removed it. The dish was better without it.
Take It Further
Everything in this article points in the same direction. If you want a complete system rather than a set of principles, Safe Plates: Mastering Dietary Compliance is the practical follow-through. Legal frameworks, operational tools, training records, supplier checks — it is all there, built for kitchens that take this seriously.
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