Every other list in this course records something that happened. This one is different: it is a reference document that has to be correct before anybody asks, because the moment somebody asks is the moment it is too late to go and find out. Allergen information is the clearest case in the whole library of the difference between a restaurant knowing something and a restaurant being able to show it — and the gap between those two is measured in one person's day off.
🥜 The card, not the chef's head
Which allergens must be declared, how, and on what, is set by your jurisdiction, and the food safety course is where the handling rules live. What this course is about is the artefact: one card per dish, kept current, that anybody on shift can produce.
A workable card holds four things, and the fourth is the one everybody leaves out:
- The dish, exactly as it appears on the menu — including the version with the sauce on the side, if that is a different answer.
- Every component, down through the sub-recipes. The stock, the marinade, the dressing, the dusting of flour on the pan. Most missed allergens are hiding one level down.
- The declarable allergens present, per your rules.
- The date it was last verified, and by whom. Without this the card is an assertion; with it, it is a record.
The reason the card exists rather than the knowledge is simple and unsentimental: the chef who knows will not always be the person standing there when a guest asks. Saturday, someone new on the phone, the owner away — that is the shape of the situation, and it is the ordinary case, not the unlucky one.
🔄 The day a supplier changes
Allergen cards do not go wrong when they are written. They go wrong three months later, quietly, and the trigger is nearly always the same: something in the supply chain changed and nobody connected it to a piece of paper.
A different brand of the same product, a reformulation of something you have bought for years, a substitute sent because your usual line was out of stock, a new sauce base that the chef is trialling, a special that becomes permanent. Each of these is a normal Tuesday, and each can silently invalidate a card.
Which is why this topic belongs in a course about paper systems. The fix is not knowledge, it is a trigger — a written rule about when the cards get looked at:
- Any new or substituted product gets checked against the dishes it goes into, before it is served.
- Any recipe change, including "we've started adding a bit of…", updates the card the same day.
- A standing review on a fixed date, so that the drift nobody noticed gets caught anyway.
- One named owner, exactly as with every other list in this course.
The substitution case deserves its own line, because it is the one that arrives with no announcement: a delivery is short, the supplier sends something close, the kitchen accepts it under pressure at nine in the morning, and the specification sheet nobody read is in the box.
🗣️ What happens at the table
The card only pays off if there is a route from a guest's question to the card and back, and that route has to work with the staff you actually have on a Friday.
Three things make it work, and none of them are about memorising ingredients:
- Nobody guesses. Ever. The only acceptable answers are the one on the card and "let me check that for you". Front of house should be trained to the second answer more than to the first — it is the one that is always available and always correct.
- Everybody knows where the cards are and can reach them during service. A binder in the office is a binder that will be replaced by a guess.
- The kitchen is told before the order goes in, not after, and there is one agreed way of marking it so it survives the pass. Whatever your system is, it must be the same on every shift.
What gets written down is worth a sentence too. Recording that a guest declared an allergy and what was done about it costs a line and gives you a record of the conversation. It is also the only way you will ever know how often this happens, which most owners badly underestimate.
📄 Being able to show it
Everything in this topic converges on a single test, and it is the two-minute test from topic 3 pointed at a different folder: can somebody who is not you produce the allergen information for your best-selling dish, right now, without phoning anybody?
Run it on a shift you are not working, and run it on your most complicated dish rather than your simplest. The failure modes are predictable and worth naming: the cards exist but are eighteen months old; they exist and are current but live on the chef's phone; they exist, are current, are accessible, and stop one level short of the sub-recipes.
Fix whichever one you find, then put the standing review date in the same calendar that the next topic is about — because an allergen card with a verification date on it is exactly the kind of thing that expires, and expiry is what closes this course.