Allergen training for restaurant and foodservice staff

Twenty seconds at the counter

Almost everything written in English about allergen training assumes an American frame: nine allergens, a federal statute, a state health department. None of it applies in Antwerp or Rotterdam. The list is different, the legal basis is different, and the point where the obligation bites is different in a way that matters on the floor.

In the Benelux this is not really a labelling rule. It is about the twenty seconds in which somebody at a counter, often the newest person on the rota, gives an answer a guest will act on. That holds for a burger counter, a hotel breakfast, a staff canteen and a bakery alike.

The 14, and where the law says they appear

Regulation (EU) 1169/2011, Annex II, lists them: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame seeds, sulphur dioxide and sulphites above 10 mg/kg or 10 mg/l, lupin and molluscs. Each has its own short entry in the glossary.

Article 9(1)(c) makes their presence a mandatory particular, and article 21 requires them to stand out in the ingredient list, which is why a packaged product shows them in bold. That is worth staff understanding, because it explains why a supplier label is readable at a glance and a recipe card is not. Both articles concern prepacked food, and most of what a restaurant sells is not prepacked.

Article 44 is the one that reaches the counter

Article 44(1)(a) extends the allergen obligation to non-prepacked food and leaves the details to national law. The information is not printed on the item, so it has to come from somewhere else, and in most service formats that somewhere else is a person. Belgium and the Netherlands worded it differently and made it work almost identically.

Two things follow. The written file is not optional even where you answer orally: it is what the oral answer comes from and what an inspector asks to see. And the legal quality of the answer is a property of the person giving it: correct and complete in Belgium, immediate and correct in the Netherlands. That is a competence requirement written into a food information rule.

No article says "train them", and three things still do

Be accurate here, because overstating it is the fastest way to lose a room of operators who know the rules. Allergen training is not named anywhere as a standalone legal obligation, and no article says staff must be retrained every twelve months. It becomes mandatory through three routes.

1. The accuracy duty. If the oral answer is lawful only when the person can give it correctly, that ability is the condition your service model rests on. Training is how you produce it.
2. The hygiene training duty. Regulation (EC) 852/2004, Annex II, Chapter XII, requires food handlers to be supervised and instructed or trained in food hygiene in line with their work. No course, certificate or interval is prescribed, and "in line with their work" is your licence to train the counter differently from the kitchen.
3. The certification clause. BRCGS Food Safety Issue 9, clause 7.1.4, requires allergen awareness training and training in the site's allergen procedures for all staff, explicitly including technicians, agency staff and contractors. For a production site supplying a restaurant chain, that is usually the sharpest instrument in the room.

The competence the rule is describing

Read the Belgian decree and the Dutch article 3 side by side and you can work out what the person at the counter must be able to do.

The last one deserves its own scenario. The right behaviour when uncertain is never to guess and never to reassure. A network where staff know they are allowed to say "I cannot guarantee that" is safer than one where they have memorised more.

Train the answers, not the list

Most allergen courses teach the 14 and stop, producing staff who can recite a list and still get the question wrong. Build the course around the questions actually asked.

Take fifteen to twenty situations from your own menu and complaint log. A parent asks about milk in one item. Someone asks whether the fryer is shared. Someone asks about a bought-in sauce, where the answer depends on a supplier specification you did not write. Someone asks about an item changed last month, while the card at the till predates the change.

Each has a correct action, and it usually has the same shape: check the file, answer from it, or decline to guarantee. Teaching that shape through scenarios travels between sites better than teaching the list, and it gives you knowledge-check results you can read, because a wrong answer tells you which situation that site cannot handle yet.

Cross-contact is a different lesson

Keep the two apart when you design the rollout. The counter question is an information duty. Cross-contact is a handling duty, taught where the work happens: separate utensils, order of preparation, the shared fryer, cleaning between two products, the glove change nobody times.

Front of house needs to understand cross-contact well enough to answer honestly; the kitchen needs to prevent it. Different modules, different scenarios. The same logic applies to the greeting: where a brand standard tells staff how to welcome a guest, the person delivering the script is the person who answers the allergen question, so that part of the standard is a safety instruction, not a preference.

When the menu moves, the answer moves

The failure that produces incidents in multi-site foodservice is almost never ignorance of the 14. It is a site answering from a superseded version.

A supplier reformulates a sauce. A recipe is adjusted for cost. A seasonal item arrives with two new allergens. The specification is updated centrally, the card at site nineteen is not, and somebody gives an answer that was correct in March. The written file and the trained answer have to move on the same date, or the file becomes evidence against you rather than for you.

So allergens belong in your change process, not in an annual training slot. Every menu or supplier change is an allergen event until somebody has checked that it is not. How to run that across restaurants is covered in rolling out a menu change.

How Aristotl keeps the allergen answer current

The specification you already maintain, a matrix, a recipe database or a set of supplier sheets, is the source. Aristotl turns it into short scenario courses of 3-5 minutes rather than a list to memorise, so what staff practise is the answer they will have to give. Nothing goes live until your team has reviewed and published it.

Courses are assigned by site or team, so the counter version and the kitchen version can differ without running two programmes, and each person reads the course in their own language. When a specification changes, you update the course once and publish the new version. Completion is viewable per site and version in the platform, so you can see who was instructed on the current answer and which sites still run on the last one.

For the change itself, post it once as a must-acknowledge announcement: every crew member gets it on their phone, and you see by name who has confirmed it and who has not.

Take one item off next month's menu and test it: find the supplier sheet behind it, and ask whether every site that sells it could give the new answer on the first day.