The version everybody plans for is the one that happens in the room. Someone reacts, you can see it, there are staff and a decision and an ambulance, and there is a process for that.
The version that actually turns up is a review on a Tuesday morning about a Friday night. "We told the server about my daughter's nut allergy. She was unwell that evening and we spent Saturday at the walk-in centre." Four stars, oddly enough, because the food was nice.
There is no incident report, because nothing visible happened. Nobody rang you. The Friday duty manager is off until Thursday. The server thinks she might remember a table with a child but isn't sure. And you have to reply to something in public within a few hours while knowing almost nothing.
This is the harder case, and it's the common one. Here's what to do with the first hour of it.
Not legal advice. Notification duties and record-keeping requirements vary by jurisdiction and change; get your own advice, and get it before you need it rather than at eleven o'clock at night.
Recover the perishable evidence first, not the story
Some records are already decaying. Deal with those before you think about wording, because the wording will still be available in an hour and the CCTV may not.
Check your CCTV retention today. Many systems keep seven days. If the meal was Friday and it's Tuesday, you have a small number of days to export and keep the relevant window, and if you spend two of them drafting a reply you will lose it. Export it now even if you never look at it.
Pull the ticket. Your till system will have the table, the time, the covers, the items and — if it was entered — the allergy modification. Whether that field is populated is itself the single most useful fact you will learn all day.
Print the rota for the shift. Who was on, on what section, and who was expediting. You will need this in an hour and it's easy to reconstruct now and hard to reconstruct in a month.
Check whether the batch is still traceable. If the dish involves a bought-in component, the lot may still be in the walk-in or the delivery note may still be in the folder. After a fortnight it's gone.
Twelve minutes, all of it, and it's the part people skip in favour of arguing about the public reply.
The public reply, and the sentence that ruins it
Post the short version quickly. Then take it private.
Thank you for telling us, and I'm sorry your daughter was unwell. Allergen handling is something we take extremely seriously and I'm looking into Friday evening now. I'm [Name], the manager here — could you email me at [address] so I can follow up with you properly?
That's it. Three things it deliberately does not do:
It doesn't say "we have no record of this." Even when true, this reads as a denial and as an accusation that the guest is lying — and if it later turns out the allergy was on the ticket, you have publicly said something wrong about a safety matter. It's the reply most likely to convert a four-star complaint into a formal one.
It doesn't explain the process. Nobody reading a public reply about a child being ill wants to hear about your allergen matrix, your training records or your colour-coded boards. It sounds like a defence, because it is one.
It doesn't apologise for a cause. "I'm sorry your daughter was unwell" is sympathy for a fact. "I'm sorry we served her nuts" is a conclusion you don't have. Sympathy first, findings later, and keep the two in separate sentences.
Asking staff about a shift they have half-forgotten
This is the part with the real technique in it, and getting it wrong destroys the only information you have.
If you ask a server "did you take an allergy order on Friday and did you pass it on?", you will get a defence. Not because anyone is dishonest, but because the question contains an accusation, and four days later memory is thin enough that it fills in from what should have happened. You will be told the correct procedure was followed, sincerely, and you will learn nothing.
Ask about the general case instead:
- "When someone tells you about an allergy at the table, what do you do next?" (You are looking for whether the answer includes the till, or only the kitchen.)
- "When the kitchen gets an allergy ticket, what's different about how it comes back?" (A flag, a separate plate, a verbal call — or nothing.)
- "How often does that happen on a Friday?"
- "Has there been a time recently where it nearly went wrong?"
Then, separately and last: "Do you remember a family with a child on Friday around eight?"
The general questions tell you whether your system works, which is the thing you can actually act on. The specific question tells you almost nothing four days later, and it's the only one that makes people frightened — so ask it once, at the end, and don't press it.
Escalate on the claim, not on the confirmation
Report it upward as an allergy claim now, while you know nothing. Owner, and your insurance or legal contact if your policy says so — most policies have a notification window and the window doesn't wait for you to establish the facts.
The instinct is to investigate first and escalate if it turns out to be real. That instinct produces late notifications and, occasionally, a voided policy. Escalating an unconfirmed claim costs a phone call.
Whether this needs reporting to environmental health depends on where you are and what happened. Ask your own adviser, and ask now.
Sometimes there is no answer, and you have to write that down
The likeliest ending: the ticket has no allergy note, the server believes she told the kitchen, the kitchen has no recollection, the CCTV shows a family eating dinner, and the guest is certain. Everyone is telling the truth as they hold it, and it cannot be resolved.
Write that down as the finding. "Unable to establish whether an allergy was communicated at the table or recorded on the ticket." Do not manufacture a conclusion, in either direction, and specifically do not conclude it was the guest's error because that's the version that leaves your process unchanged.
Then fix the thing the investigation actually revealed, which is almost never the dish. It's that the allergy left no trace. If the only place an allergy exists is in a conversation between a server and a chef, then every one of these becomes unresolvable four days later — and unresolvable is expensive.
Making the next one reconstructible
Two changes, both small:
Log every allergy order, including the ones that go fine. A line in the shift log — table, allergen, dish, who confirmed with the kitchen. Twenty seconds. On a normal Friday you'll write two of them and they'll look pointless, and then one Tuesday morning one of them will be the entire answer.
Make the till field mandatory rather than available. If the allergy note is an optional box, it's populated when service is calm, which is not when the mistakes happen.
Allergy mentions shouldn't sit in the ordinary reply queue waiting for someone's fifteen minutes — that's the one category worth interrupting a day for, and it should be unambiguous whose phone it reaches. OMMU flags allergen and illness language on arrival for that reason. The first hour above is the part that matters, though, and it works with a notebook.