Allergen Cross-Contact: Keeping It Off a Busy Line
Declaring the 14 is only half the job. The other half is stopping a trace of it reaching the wrong plate at 19:30 — and that half is a physical problem, not a paperwork one.
The allergen matrix on the wall tells a guest what's in a dish. It does nothing to stop a trace of peanut ending up in a dish that never listed peanut. That second problem — allergen cross contamination, or more precisely cross-contact — is where kitchens actually hurt people, and it's the part almost no allergen folder addresses beyond a line that says "avoid cross-contamination." Great. How?
I've run allergen orders through pass on nights when the printer never stopped. The dangerous thing about cross-contact is that it's invisible, it's tiny, and it happens during the exact ten minutes when everyone is moving fastest. This piece is the working version of cross contact kitchen control: what actually reaches the plate, and the handful of habits that keep it off.
Cross-contact is not cross-contamination
People use the words interchangeably. They shouldn't, because the fix is different.
Cross-contamination is the classic food-safety one: raw chicken juice dripping onto salad leaves, bacteria moving from a dirty board to a clean one. You beat it with temperature and, mostly, with cooking — heat kills the pathogen.
Cross-contact is allergen protein moving from a food that contains it to a food that doesn't. And here's the part that catches people: cooking does not fix it. Peanut protein is still peanut protein after 200°C in the oven. Frying a "clean" chip in oil that fried a battered, wheat-coated fish an hour ago transfers gluten straight into the chip. There is no kill step. The only control is keeping the protein away from the plate in the first place.
That single fact reorganises how you think. For pathogens, the cook is your safety net. For allergens, there is no net. Separation is the whole game.
The 14 and the Big 9 — know your list cold
In the EU and UK, food law names 14 allergens you must declare: celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, tree nuts, peanuts, sesame, soya, and sulphur dioxide/sulphites above 10 mg/kg. In the US, the FDA works from the Big 9 under FALCPA (plus the FASTER Act of 2021, which added sesame): milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame.
The lists differ, and if you cater across regions you carry both in your head. But the operational point is the same everywhere: you can only control what you can name. A cook who thinks "nuts" means walnuts and cashews and forgets that the satay is bound with peanut, or that the seeded loaf is coated in sesame, is a cook who will send the wrong plate eventually. Sesame and mustard hide in things — dressings, marinades, spice blends, "nature-identical" flavourings. Sulphites live in dried fruit and cheap wine. The invisible ones are the dangerous ones.
Separation: boards, utensils, fryers, air
Most kitchens already colour-code boards for raw/cooked — red, blue, green, brown. Very few extend that logic to allergens, and that's the gap. Cross-contact separation runs across four physical channels.
Surfaces and boards
A board that just chopped a bread roll has flour and crumb on it. Wipe it with the same cloth you use for everything and you've moved gluten around the section, not removed it. For a confirmed allergen order, you want a genuinely clean board — washed, not wiped — or a dedicated one. Some kitchens keep a purple board and purple-handled knife specifically for allergen-order plating. It costs $15 and removes an entire category of mistake.
Utensils and hands
The tasting spoon that touched the cream sauce and went back into the drawer. The tongs that plated the nut-crusted chicken and then grabbed a "safe" garnish. Hands that broke down feta and then assembled a dairy-free salad without a wash in between. Utensils and hands are the highest-frequency transfer route because they move constantly and nobody watches them. The rule is boring and non-negotiable: fresh utensil, washed hands, between the allergen task and the safe task.
The fryer — the worst offender
Shared oil is the single most common cross-contact failure in casual kitchens, and it's the one guests least expect. If your fryer cooks breaded (wheat) items, it is not gluten-free, full stop. If it cooks battered prawns, it is not shellfish-free. There is no "I'll just do it quick" — the protein is in the oil. Either you have a dedicated fryer for allergen orders, or you finish that item another way (oven, pan with clean oil), or you tell the guest the truth: we cannot make this safe in our fryer. Honesty beats a hospital.
Airborne and dry particulate
Flour clouds. Sifting flour, dusting a bench, opening a bag of ground almonds near an open plate — fine particulate settles on nearby food and surfaces. It's why a bakery section is a hard place to promise "nut-free." You can't wipe air. The control is spatial and temporal: do the dusty allergen work away from open safe food, and ideally at a different time.
Order of prep and cleaning between tasks
Sequence is a free control that costs nothing and prevents most bench-level cross-contact. The principle mirrors the low-to-high logic of general hygiene: do the allergen-free work first, the allergen-heavy work last.
If you're building mise for the day and you know a section will handle both a nut praline and a nut-free mousse, make the mousse first, clean down, then make the praline. Reverse that order and every particle of nut on the bench is a live threat to the mousse. Sequence turns a cleaning problem into a non-event.
Between tasks that cross an allergen boundary, "cleaning" means a real clean, not a wipe. There's a genuine difference — the same one that separates cleaning from sanitising in your daily routine:
| Action | Removes allergen protein? |
|---|---|
| Dry wipe with a cloth | No — spreads it around |
| Same cloth used all shift | No — the cloth is now a carrier |
| Hot water + detergent + rinse | Yes — physically lifts and washes protein away |
| Sanitiser spray alone | No — kills microbes, does not remove allergen protein |
That last row surprises people. Sanitiser is for pathogens. Allergen removal is a washing job — detergent and water lift the protein off the surface and rinse it down the drain. A dedicated allergen cloth (or single-use blue roll) that never touches a general surface stops the cloth itself becoming the transfer route.
Running an allergen order during service
Everything above is prep-time discipline. The real test is a confirmed allergen ticket landing at 19:30 with fourteen other checks on the rail. Here's the sequence that holds up under pressure.
- The ticket is flagged, loudly. Front of house must mark it and call it — "ALLERGY, table 12, no dairy" — not scribble it small. The whole section should hear it. A silent allergen ticket is an accident waiting.
- One person owns it. The dish gets made by a single cook, start to finish, so responsibility never fragments across the pass. No "someone garnished it, I don't know who."
- Clean station, clean hands, clean tools. Fresh board, washed hands, dedicated utensils. Ingredients pulled from original packaging where possible so the label is checked, not assumed.
- Cook it clean. Clean pan, clean oil, not the shared fryer. If a component can't be made safe, the dish is modified or refused — decided now, not improvised.
- It runs separately and it's identified. The plate is carried on its own or clearly marked so it can't be swapped with the table's other covers. A coloured pick or a verbal hand-off to the server closes the loop.
None of this is slow once it's a habit. The kitchens that struggle are the ones improvising it fresh every time. Build it into the section's muscle memory and an allergen order costs you maybe ninety extra seconds, not a panic.
The communication chain: kitchen → FOH → guest
The best-run line in the world fails if the information breaks at a handover. Cross-contact control is only as strong as the chain that carries the guest's need from the door to the plate and back.
The chain has three joints, and each one leaks:
- Guest → server: the guest says "I'm allergic to nuts." The server must capture it accurately and take it seriously — not "a lot of people say that." An allergy is not a preference.
- Server → kitchen: the note must reach the pass in a form the kitchen can act on. "No nuts" written on the ticket, confirmed verbally, acknowledged back.
- Kitchen → guest: if a dish can't be made safe, that has to travel back before the plate goes out — not after the guest has taken a bite and asked.
This is exactly the failure that drove Natasha's Law in the UK — the death of Natasha Ednan-Laperouse from sesame in a baguette that carried no ingredient warning. The law tightened labelling on prepacked-for-direct-sale food, but the deeper lesson for any kitchen is that the information chain is a safety-critical system, and a gap in it is fatal. The UK Food Standards Agency's allergen guidance for food businesses lays out both the labelling duty and the separation-and-cleaning controls that sit behind it — worth reading in full if you serve the public.
The kitchen's job in that chain is to have the answer ready before anyone asks. Which dishes contain what, which can be modified, which genuinely cannot — that has to be known, not worked out at the pass while a ticket waits. That's where your menu's allergen record earns its keep.
In ProChefDesk
When you build a menu, the allergens on each dish are pulled automatically from the recipe's ingredients and you can add manual ones for cross-contact risk (the satay bound with peanut, the shared-fryer note). That "contains" set follows the dish onto the printed menu and the line's Kitchen Cards, so the answer at the pass is the same answer the guest was given — no memory, no guessing.
What this doesn't cover, and what to do next
Cross-contact control has no single number to hit, which makes it harder to manage than food cost — there's no percentage to watch drop. It's a set of habits, and habits decay. Two things keep them alive.
First, write the allergen status down and keep it current. An allergen matrix that's six months stale — a supplier changed a recipe, you swapped an oil, a garnish crept in — is worse than none, because people trust it. Every time a recipe changes, the allergen record changes with it, or the whole system rots quietly.
Second, rehearse the allergen order when it's quiet. The section that has walked through the clean-board, one-owner, separate-run routine on a slow Tuesday is the section that executes it calmly on a full Saturday. You don't rise to the occasion; you fall to your level of training.
The honest summary is this: declaring what's in a dish protects you legally. Stopping cross-contact protects the guest. The first is a label. The second is boards, sequence, a clean fryer, washed hands, and a chain of people who all take "I'm allergic" as a hard line rather than a suggestion. Get the physical controls right and the paperwork describes a kitchen that's actually safe — not one that just looks safe on paper.
"The order came back — 'she's allergic to sesame.' We'd already plated it on the seeded bun. Caught it at the pass by ten seconds. Never again ran an allergy ticket without calling it out loud."
That ten seconds is the whole difference. Build the habits so you never need the luck.