Dietary and allergen management for catering: the UK problems, and what solves them
Twenty years ago a catering team handled two vegetarians and a nut allergy. Today a 200 cover dinner arrives with 30 dietary requirements across a dozen categories, they land four days out, and half of them change. Most teams still manage that on a spreadsheet and a WhatsApp thread. This guide covers what dietary and allergen management actually involves in the UK, where it breaks, and what handling it properly looks like.
- UK law regulates 14 allergens, and allergen information has to be accurate, available and traceable to the ingredient.
- Dietary management is a bigger job than allergen labelling: somebody still has to find the guest a dish they can eat.
- Allergen data typed by hand goes stale the moment a recipe changes, and nobody can tell by looking.
- The useful output is a named replacement dish per guest, from recipes the chef already approved.
- The record of what was checked, by whom and when is what protects the business afterwards.
1. The problems catering teams hit with dietary requirements
- The numbers have grown. A 200 cover dinner now routinely carries 20 to 40 dietary requirements across vegan, vegetarian, gluten free, dairy free, halal, kosher, pescatarian and named allergies.
- They arrive late and they change. The list comes four days out, and it moves again on the morning.
- The list lives in three places. An email to the coordinator, a spreadsheet on a shared drive, and a WhatsApp message to the chef.
- "Vegetarian option available" is not a plan. Somebody still has to decide which dish, cost it, order for it and plate it.
- Allergen data is typed by hand. Then a recipe changes and the matrix quietly becomes wrong.
- Nothing is written down. When a guest asks who checked, or an environmental health officer asks, there is a memory and no record.
- Cross contact is managed by shouting. The plan for keeping the gluten free plate separate exists only in the head of whoever is on the pass.
2. What UK law actually asks for
Food businesses in the UK have to give accurate allergen information about the 14 allergens the Food Standards Agency regulates. For food that is not prepacked, which covers almost everything a caterer serves, the information has to be available to the guest and it has to be right.
Two further rules matter to caterers. Prepacked for direct sale food, the kind of item a team makes and wraps on site, has to carry a full ingredient list with allergens emphasised, which is the rule most people know as Natasha's Law. And Owen's Law is coming, which would require full written allergen information for diners rather than information on request.
Read the Natasha's Law guide and the Owen's Law guide for the detail on both.
Worth knowing: nothing in this guide is legal advice, and no system removes the duty. Software can check, suggest and record. The chef decides, and the business stays responsible.
3. Allergen management and dietary management are two different jobs
This distinction is the one most teams and most software blur, and it is worth being exact about.
Allergen management is information. Knowing what is in a dish, keeping that knowledge current, and putting it in front of the guest and the team. It answers "can this guest eat this dish?"
Dietary management is service. When the answer is no, somebody has to find the guest a different dish, cost it, order the ingredients, put it on the kitchen paperwork and plate it at the right seat. It answers "so what is this guest eating instead?"
Plenty of good systems do the first job. Far fewer do the second, and the second is where the hours go.
4. Build allergen data from ingredients, not from memory
A hand typed allergen matrix is right on the day somebody typed it. After that, every recipe edit is a chance for it to go wrong, and nothing about the document tells you it has.
Tag allergens once, at ingredient level. Then every recipe using that ingredient inherits the tag, every menu built on those recipes inherits it again, and a change to a recipe updates everything downstream on its own. Across 400 recipes this is the only approach that survives contact with a busy kitchen.
The same logic covers dietary categories. If the system knows an ingredient is dairy, it can work out that the dish is not vegan without anybody ticking a box.
5. The output that actually helps a kitchen
A warning is not an outcome. Telling a chef that guest 14 cannot eat the main is where most software stops, and it is the easy half.
The output a kitchen can use is a named replacement dish for that guest, drawn from recipes the chef already approved, costed, ordered for, and printed on the same sheet as everything else. Then the decision on the pass is a yes or a no, not a problem to solve during service.
6. Cross contact, and the part software cannot do
Handling, storage and separation happen with hands, not with data. A system can carry the plan and record that somebody followed it. A system cannot keep the gluten free plate away from the bread.
What good practice looks like is unglamorous: separate prep areas or separate times, colour coded boards, labelled and covered containers, a plated dish that is carried and marked so it reaches the right seat, and a briefing before service that names which seats are affected.
Write the plan on the same document as the food. A plan on a different page is a plan nobody reads.
7. The record is the point
After a difficult service, the question is always the same: what did you check, who checked it, and when.
A dietary process that produces a record answers that question. A process that lives in conversation does not. Keep the guest list with requirements, the dish assigned to each guest, the allergen data behind the dish, and the named sign off with a time on it.
8. What this means for your role
Head chef
You are the person who decides whether a guest gets served. What helps you is a shortlist of dishes from your own recipes that fit the guest, presented before service rather than during it. The system checks and suggests; you decide and sign it off.
Executive chef
You own the recipes, so you own the allergen data. Tagging allergens once at ingredient level, and letting every recipe and menu inherit it, is the only version of this that stays true across hundreds of dishes.
Head of catering
You carry the risk and the record. What matters is that every check is written down with a name and a time on it, so the business can show what it did and when.
Sales director
Dietary requirements are now a sales question. Clients ask what you do about them during the pitch, and a clear answer with a real document behind it wins work from a vague reassurance.
9. What to look for when you buy
- Allergens tagged at ingredient level and inherited by recipes
- All 14 UK regulated allergens, not a shorter list
- Dietary categories worked out from ingredients, not ticked by hand
- A suggested replacement dish per guest, from your own recipes
- Chef approval as a required step, not an optional one
- The dietary block printed on the kitchen paperwork itself
- A matrix that regenerates when a recipe changes
- A record with names and times on it
- Something that works on a phone in the kitchen
10. Questions people ask
What are the 14 allergens under UK law?
Celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, tree nuts, peanuts, sesame, soybeans and sulphur dioxide or sulphites above 10mg per kg or litre. The Food Standards Agency regulates all fourteen for food businesses in the UK.
What is the difference between allergen management and dietary management?
Allergen management is about information: knowing and declaring what is in a dish. Dietary management is about service: giving a guest who cannot eat the dish something else they can eat. Most software stops at the first one, and the second one is the work a kitchen actually has to do.
What is an allergen matrix?
An allergen matrix is a grid of dishes against the 14 regulated allergens, showing which allergens each dish contains. Built from recipe ingredients it stays true when a recipe changes. Typed by hand it only stays true until somebody edits a recipe and forgets.
Do allergen rules apply to catering and banqueting?
Yes. Catering, banqueting, hotel functions and private dining are all food businesses, and the same allergen information duties apply. Non-prepacked food served at a catering event has to have accurate allergen information available to the guest.
What is Owen’s Law?
Owen’s Law is a proposed change that would require restaurants to make full allergen information available in writing, usually on the menu. It is coming rather than in force, and teams that already build allergen data from recipes will have far less work to do when it arrives. See our Owen’s Law guide for the detail.
How far in advance should dietary requirements be collected?
Ask at booking, chase at the final numbers deadline, and expect changes right up to the day. The realistic goal is not to stop late changes but to make handling one take minutes rather than restarting the kitchen paperwork.
11. Where Havenue fits
Havenue tags allergens from ingredient data, checks every guest at a catering event against the menu, and suggests a replacement dish from the operator's own recipes for the chef to approve. The allergen matrix and the BEO are generated from the same booked catering event, and every check carries a name and a time.
See the Dietary and Catering Engine, the BEO and allergen matrix and reporting and compliance.
← Return to the Havenue home page