Key takeaways
- Build the matrix from the bottom up: supplier specifications, then sub-recipes, then dishes. Never from memory or the menu description.
- Give the matrix a version number and date, keep old versions, and make one person responsible for every change.
- Supplier substitutions and specials are where matrices go wrong; build a check into goods-in and the specials board.
- Front-of-house staff should read from the matrix every time, because written information is what diners trust.
Why the matrix is the centre of your allergen system
Restaurants, pubs and takeaways serving loose food must supply allergen information for every item that contains any of the 14 allergens[1]. An allergen matrix, a grid of dishes against allergens, is the most common way to hold that information. Done well, it means any member of staff can answer an allergen question accurately at any time, and the kitchen has one source of truth instead of several half-remembered ones.
It also answers a trust problem. In 2025, 86% of people asked were confident in allergen information given in writing, a much higher level of trust than in verbal answers from staff[2]. A matrix gives your team something written to read from and show the guest.
The audience is large. In 2025, 23% of adults in England, Wales and Northern Ireland reported a food hypersensitivity[3]. Not all of them have one of the 14 regulated allergens, but they are all making choices based on what you tell them.
- Reported a food hypersensitivity 23%
Source: Food Standards Agency, 2025[3]
Show the data
| Item | Value |
|---|---|
| Reported a food hypersensitivity | 23% |
Start with ingredients, not dishes
The most common mistake is filling in the matrix from the menu: looking at ‘chicken Caesar salad’ and ticking egg, fish, milk and gluten from general knowledge. That misses the mustard in the dressing, the specific croutons your supplier sends and the Worcestershire sauce in the marinade. Build it in layers instead.
Collect supplier specifications
For every bought-in ingredient, get the product specification or label showing allergens. File them by supplier, with the date you received them.
Write sub-recipes
Dressings, sauces, stocks, spice mixes, batters and garnishes each get their own recipe card and their own row in the matrix. These are the building blocks.
Write dish recipes
Each dish lists its sub-recipes and ingredients, including garnishes, oils and anything added at the pass.
Roll up the allergens
A dish contains every allergen in every component. If a spreadsheet does this automatically, check the formulas once by hand.
Note shared equipment
Add a separate note for each dish where cross-contact is likely, such as a shared fryer or a grill used for bread. Keep this distinct from ‘contains’.
Sign and date
The person who built it signs; a second person checks a sample of dishes against the recipe cards.
Keeping supplier records is part of the wider duty to know where your food comes from: you must keep records of your suppliers and of any businesses you supply[4]. Your specification file doubles as that record for allergen purposes.
What a matrix row looks like
Example: three rows from a fictional bistro's matrix. Ticks mean the allergen is an ingredient; the cross-contact column records a known risk from equipment or the environment.
| Dish (v4, 03/11) | Gluten | Milk | Egg | Mustard | Fish | Sesame | Cross-contact note |
|---|---|---|---|---|---|---|---|
| Chicken Caesar salad | Yes (croutons) | Yes (parmesan) | Yes (dressing) | Yes (dressing) | Yes (anchovy) | No | Croutons toasted on shared tray |
| Fish and chips | Yes (batter) | No | No | No | Yes | No | Chips fried in shared fryer with battered fish |
| House burger | Yes (bun) | Yes (cheese) | Yes (sauce) | Yes (sauce) | No | Yes (bun) | Grill shared with toasted buns |
Show all 14 columns in the real thing, even where a column is empty across the whole menu. An empty column tells staff the allergen has been checked; a missing column leaves them guessing.
Version control: the step most kitchens skip
A matrix is accurate on the day it is checked. After that, every recipe tweak, new supplier and substitution can make it wrong. Version control is how you know which version was in use on a given date, and it is often the first thing asked for after a complaint.
- Give the matrix a version number and a date in the header, such as v4, 3 November.
- Keep every superseded version, on paper or as a saved file, for at least as long as you keep your other food safety records.
- Name one owner, usually the head chef, who approves every change. Others can propose changes but not make them.
- Print the current version for the pass and the floor, and remove the old copies the same day.
- Record each change in a short log: date, dish, what changed, who approved it.
Your food safety management system should keep records of your systems, checks and how you put things right[5]. The matrix and its change log are part of those records.
Handling substitutions and supplier changes
Substitutions are the most likely way a correct matrix becomes wrong. A wholesaler sends a different brand of mayonnaise, the usual bread is out of stock, or a supplier quietly changes a recipe. Build checks into the moments they happen.
- At goods-in, compare the product against the one on your specification file. Same brand and product code? If not, set it aside.
- Check the label of any substitute against the 14 allergens before it is used.
- If the allergens differ, update the matrix before the product is used, or do not use it.
- Tell the floor team at the pre-service briefing which dishes have changed.
- Ask suppliers to tell you when a product's recipe changes, and check labels on regular lines from time to time anyway.
If there is no time to update the matrix before service, take the dish off for allergy orders. A short-term gap is safer than an inaccurate answer.
Specials, events and set menus
Specials are often created on the day by a chef who knows the ingredients but has not written a recipe card. Make the allergen check part of putting a dish on the board: no allergen entry, no special. The same applies to set menus for functions, which tend to be written weeks ahead and changed on the day. Print a separate allergen sheet for each event menu and check it against the final version.
Example: a fictional gastropub in York adds a specials column to its matrix template. The chef fills it in before the board is written, and the duty manager checks it at the briefing. Specials without an entry are not offered to guests with allergies.
Getting staff to use it
A matrix in a drawer does nothing. Front-of-house staff need it within reach, need to know how to read it, and need permission to say ‘let me check’ every time. Build its use into training and service routines.
- Keep a copy at every service station and the pass, and a digital copy on the till or tablet if you use one.
- In training, ask staff to find the allergens in three dishes using only the matrix, and to spot the cross-contact notes.
- Make ‘I will check the allergen information for you’ the standard response, never an answer from memory.
- Have the kitchen confirm allergy orders at the pass against the matrix, not just the ticket.
For the full list and what each allergen covers, see the 14 allergens every venue must declare.
Paper, spreadsheet or recipe software
Any format works if it is accurate, current and easy to read during service. The choice depends on the size of the menu and how often it changes.
- Paper grid: fine for a small, stable menu. Easy to read at the pass, but every change means reprinting and collecting old copies.
- Spreadsheet: suits most independents. Sub-recipes can roll up into dishes automatically, and the version number and date can sit in the header. Lock the formulas and the allergen columns so only the owner can edit them.
- Recipe or stock software: worth it for groups and kitchens with frequent menu changes. Allergens flow from the ingredient record to every dish that uses it, which removes most manual errors, provided someone keeps the ingredient records current.
- Whatever the format, print a dated copy for the floor. Screens freeze, tablets run flat and wi-fi drops during the busiest service of the week.
Example: a fictional three-site café group moves from paper grids to a shared spreadsheet when it notices each site had a slightly different version. Head office owns the master; each site prints the current version every Monday and initials the change log.
A monthly matrix audit
Once a month, pick five dishes at random. For each, pull the recipe card, the supplier specifications and the matrix row, and check they agree. Check the product on the shelf against the specification on file. Ask one member of floor staff to answer an allergen question using the matrix. Record what you found and fixed. It takes under an hour and catches drift before a guest does.
Frequently asked questions
Is an allergen matrix a legal requirement?
The law requires accurate allergen information for every item containing any of the 14 allergens. A matrix is not named in law, but it is the most practical way to hold and share that information.
Should the matrix include ‘may contain’ risks?
Keep cross-contact notes separate from the allergens a dish contains as ingredients, so staff can explain both accurately. Do not mix them in a single tick.
How often should the matrix be updated?
Every time a recipe, ingredient, supplier or product changes, before the changed dish is served. Audit a sample of dishes each month even if nothing has obviously changed.
Can I use a digital matrix?
Yes, as long as staff can reach it during service, it is kept up to date, and you keep a record of earlier versions.
References
Food Standards Agency (2026). Allergen guidance for food businesses (opens in a new tab) ↑
Food Standards Agency (2025). Food and You 2 annual report: wave 11 (trends) (opens in a new tab) ↑
Food Standards Agency (2025). Food and You 2: wave 11 key findings (opens in a new tab) ↑
GOV.UK (2026). Food safety: your responsibilities (opens in a new tab) ↑
GOV.UK (2026). Food safety management systems (opens in a new tab) ↑