Table of six, Friday night, one guest with a tree nut allergy. The waiter taking the order is casual staff, three weeks in, and answers from memory when asked if the pesto has nuts in it. It doesn’t — this time. The process worked, but only because someone happened to remember correctly under pressure, on a table where it mattered. That’s not a system. That’s a coin flip you’ve been winning so far.
Why “brief the staff” isn’t a policy
Verbal allergen communication works exactly as well as the least experienced person on shift that night. Every dish, every modification, every substitution has to be re-explained correctly, from memory, in the middle of service — and it has to be re-explained every single time someone asks, because no record survives past that conversation. Add a specials board that changes daily, a kitchen that’s swapped an ingredient without telling the floor, and new casual staff who haven’t learned the full menu yet, and the odds of a clean run stop being good enough. One miss is the only one that matters, and it’s the one nobody sees coming.
What actually needs to happen
Put the dietary tag on the menu, not in someone’s head
A digital menu with allergen and dietary tags built into every item lets a guest filter for gluten-free, nut-free or vegan themselves, and staff end up confirming what’s already documented rather than recalling it live under pressure. The information doesn’t get less reliable the busier the shift gets, because it was never depending on anyone’s memory in the first place.
Make it survive the staff who haven’t been trained yet
Hospitality turnover means someone new is on the floor most weeks. Structured digital ordering cuts down how much a new starter has to know before their first solo table — they’re not expected to have the full allergen matrix memorised on day one, because the menu is doing that job for them.
Keep the note, not just the conversation
A CRM that attaches dietary notes to a guest’s profile means a regular’s allergy is already on file the next time they book or order. Nobody has to ask the same question from scratch, and nobody is relying on the same staff member remembering the same guest. For venues taking bookings, that note can sit against the reservation itself, so the kitchen knows before the table even sits down.
Don’t let the specials board break the system
Anything that changes daily — a special, a sauce swap, a seasonal ingredient — needs to go through the same digital tagging as the core menu, not get announced verbally at the pre-shift huddle and forgotten by the second seating. If it isn’t tagged, it isn’t tracked, no matter how good the briefing was.
Cover every outlet a guest actually orders from
A hotel guest who asks about dietary requirements at check-in shouldn’t have that answer disappear the moment they order room service or eat at the restaurant downstairs — it needs to be the same tag, visible on the same digital menu, wherever they place the order. The same logic holds for a cafe running a breakfast menu that switches to lunch mid-morning: if the dietary tags don’t carry across the switch automatically, the risk resets every time the menu does.
The risk was never the allergy
It’s the assumption that a conversation, repeated correctly by hand, at pace, by whoever’s rostered on, counts as a system. It doesn’t — it’s a habit that holds until the night it doesn’t. A filterable digital menu and a CRM note don’t take the risk to zero, but they take the outcome out of any one person’s memory on any one night, which is the only thing that actually protects a guest — and you. The staff member who got it right by memory tonight might not be rostered on next Friday, and the next person shouldn’t need to be just as lucky.