Handling an allergy request without slowing service

A cafe handling an allergy request well does one thing consistently: the information travels intact from the customer to the person plating the dish.

Where it goes wrong is rarely the cooking. It is a handover, a busy pass and a plate that looks like every other plate.

One route, used every time

A request each person handles differently is a request somebody eventually misses. The route should be identical whoever takes it.

1. The order carries it, written on the docket rather than remembered.
2. The kitchen acknowledges it aloud, so two people share the knowledge.
3. The dish gets marked, by a flag, a different plate or a separate rail.
4. The runner names it at the table, which is the last chance to catch an error.

The final step matters most and gets dropped most. A customer hearing the dish named can stop it before it reaches them.

Know the ingredients before service, not during it

A cook asked mid service whether a dressing contains mustard will guess, and the guess will be confident.

An ingredient list per menu item, prepared once and kept current, answers that in seconds. It needs a review whenever a supplier or a recipe changes, which is the part most cafes forget.

A supplier change is a menu change

The same product from a different supplier can carry different allergens and a different manufacturing line. Nobody notices, because the dish looks identical.

Any substitution needs a check against the ingredient list before that item returns. That check is the single highest value habit in this whole area.

Say what the kitchen cannot promise

A small kitchen with shared equipment cannot guarantee the absence of a trace. Saying so plainly respects the customer more than a reassurance nobody can support.

A severely allergic customer would far rather hear an honest limit than a confident yes. They came to make their own decision.

Train it as a drill, not a policy

A written procedure read at induction is forgotten within a fortnight. A two minute run through at a pre service briefing survives.

New staff should walk the route once with a real docket before their first busy shift. Our guide to opening and closing checks makes the same argument about habits that only survive when practised.

Record the request, not just the meal

A cafe that notes allergy requests learns which ones recur and which dishes attract them. That informs the menu more usefully than any guesswork.

It also means a regular does not have to explain themselves every visit, which is worth a great deal to somebody who usually does.

Review a near miss the same day

A dish caught at the pass is the cheapest lesson the cafe will ever get. Treating it as a relief rather than as information wastes it.

One sentence about where the handover broke, discussed that day, usually fixes a step everybody had quietly stopped doing.

Suppliers change formulations without telling anybody

A product can change its recipe between deliveries, and the label is the only notice a cafe gets.

Checking labels on arrival, for the handful of items that matter most, catches that at the door rather than at a table.

One person owns the ingredient list

A list everybody can edit and nobody maintains goes out of date within a season.

One named owner, reviewing it whenever the menu or a supplier changes, keeps it trustworthy enough to rely on during service.

What to change first

• One route carries every request, from docket to table
• The runner names the dish at the table, every time
• An ingredient list per menu item exists before service, not during it
• Any supplier substitution triggers a check against that list
• The kitchen states plainly what it cannot promise
• A near miss gets one sentence of review the same day