Phoenix Journal · Food Safety & Compliance
What keeps an allergic customer safe is not the paperwork - it is whether a busy line can find the right answer and act on it without a mistake. Here is how to build that.
A ring binder of allergen information proves very little. What keeps an allergic customer safe is whether a busy line, mid-service, can find the right answer and act on it without a mistake. Allergen management that works is operational, not administrative - built into how the kitchen preps, stores, cooks and communicates, so the safe thing is also the easy thing.
Most kitchens have the paperwork. Far fewer have a system that survives contact with a Friday night. The difference shows up in the small moments: an agency chef who does not know which sauce carries mustard, a garnish added out of habit to a plate flagged nut-free, a matrix that was accurate until the recipe quietly changed. Good allergen management closes that gap by making the information usable at the exact points where decisions get made, rather than filed where nobody looks under pressure.
UK law recognises 14 allergens that must be declared: celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, tree nuts, peanuts, sesame, soya and sulphur dioxide. The obvious ones are rarely the problem; the risk lives in the hidden ones. Soya and sulphites turn up in sauces, marinades and dried fruit. Mustard hides in dressings and spice blends. Celery is common in stocks and soups. Gluten appears in things that are not obviously bread, from thickened gravies to soy sauce. A working system starts with an allergen matrix that maps every dish against all 14 - built from the actual recipes, not from memory - so that any member of staff can read the answer off a grid instead of guessing. The matrix is only trustworthy if it is updated the day a recipe or supplier changes, which is why one person should own it.
Declaring an allergen is only half the duty; the other half is stopping it reaching a dish that is supposed to be free of it. Cross-contact is a physical problem with physical answers: separate storage so allergens cannot drip or spill onto other foods, dedicated or thoroughly cleaned equipment and utensils, colour-coded boards used properly, and a prep order that handles allergen-free dishes before contamination is introduced rather than after. Between tasks, a genuine clean-down matters more than a wipe, because allergen residue does not have to be visible to cause a reaction - which is exactly the difference between a kitchen that looks clean versus one that scores clean. This is where cleaning and allergen safety become the same discipline: the surfaces, slicers, fryers and awkward corners that hold grease also hold protein residue, and controlling one controls the other.
In practice a few routines carry most of the load. Store allergens low and sealed so nothing can fall or leak onto ready-to-eat food below. Decant and label so an unmarked tub never becomes a guess. Prep the allergen-free version first, on a cleaned surface with clean equipment, before the allergen is anywhere near the bench. Keep a dedicated set of clearly marked utensils for high-risk work rather than trusting a quick rinse. And treat the deep clean between sessions as part of the allergen system, not separate from it, because the residue you cannot see is the residue that catches you out. None of these steps is difficult; the discipline is doing them every time, not only when someone declares an allergy.
Every system is really preparing for one moment: a customer says they have an allergy. What should happen is calm and quick - the order is flagged, the information is checked against the single source of truth rather than recalled from memory, the kitchen is told, cross-contact is controlled during prep, and the dish is confirmed to the customer. That only works if the whole team can do it, not one trained person who might be off that shift, and if it can be done at service speed. Handling allergen orders at speed without mistakes is a skill the whole brigade needs to share. Two habits underpin it: never guess, and be honest with "may contain" - use it only where a real cross-contact risk has been assessed, so it means something when it appears. Get this right and allergen management stops being a compliance chore and becomes what it should be, which is simply a kitchen that can be trusted with the people it feeds, every service and not just when someone remembers to ask.
Questions
Celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, tree nuts, peanuts, sesame, soya and sulphur dioxide (sulphites). Any of these must be declared wherever it appears, and emphasised on labels for prepacked-for-direct-sale food.
Flag the order, check the dish against your allergen matrix rather than from memory, tell the kitchen, control cross-contact during prep, then confirm to the customer. The whole team should be able to do this at service speed, not just one trained person.
It depends on the allergen and your menu. Shared oil carries cross-contact risk - for example frying battered fish and chips in the same oil. Where you cannot guarantee separation, you must say so honestly rather than imply a dish is free of an allergen it may contain.
Everyone who handles food or takes orders. Allergen management fails when it depends on a single person who might be on holiday or off sick. Every member of staff should know the 14 allergens, which are in which dishes, and the procedure when a customer asks.
Phoenix Duct Clean · by the numbers
Allergen residue does not have to be visible to cause harm. Ask us about a commercial kitchen deep clean that reaches the surfaces and equipment your allergen controls depend on.