What is an allergen matrix, and who owns it?

A guest with a sesame allergy asks whether the chicken dish is safe. The server checks the allergen chart pinned in the kitchen: no sesame. The dish is served, and the guest reacts. The chart was right when it was printed, but the chef had changed the dressing two weeks earlier to one finished with sesame oil, and nobody updated the chart. The kitchen knew the recipe; the chart did not.

What is an allergen matrix? It is a grid that shows every dish on the menu against every allergen the venue must declare, with a mark wherever a dish contains that allergen. It is how servers, chefs and guests find out, quickly and reliably, which dishes are safe for someone with an allergy. It is only as good as its last update.

This guide covers what an allergen matrix is, what goes in it, the allergen rules that shape it, how it is built from allergen and recipe data, how to keep it current, who should own it and how the team should use it at the table. It describes general practice; the law where you trade decides exactly what you must declare. Every venue and figure in it is an example.

An allergen matrix is a table with the venue's dishes down one side and the allergens across the top. Each cell shows whether the dish contains that allergen. A server asked about sesame can run a finger down the sesame column and see every dish that contains it.

The matrix is a reference for the team and, in many venues, for guests. It turns the venue's knowledge of its recipes into a form anyone can read in seconds.

A food allergy can cause a reaction ranging from discomfort to a life-threatening emergency. A guest who tells the venue about an allergy is trusting the venue's answer completely. The matrix is what makes that answer reliable.

Without one, the answer depends on who is asked and what they remember. With an accurate one, every member of the team gives the same, correct answer.

Allergen rules differ between countries, but many follow a similar pattern. In the UK and the EU, food businesses must give information about fourteen major allergens, including cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, tree nuts, celery, mustard, sesame, sulphites, lupin and molluscs. Other places have their own lists.

Know the list that applies where you trade, and build the matrix around it. Many venues add other ingredients guests often ask about, such as garlic or onion, as extra columns.

The matrix should include every item a guest can order: every dish, every side, every sauce, every dessert, every drink that contains an allergen and every component that can be added or swapped. A dish that changes with its options, such as a burger with a choice of bun, needs the options covered too.

Include the specials and seasonal dishes. A matrix that covers the main menu but not the specials board is incomplete on exactly the dishes most likely to change.

Menu allergens are often shown on the menu itself, with symbols or a short note beside each dish. The matrix is the fuller record behind those symbols, used by the team when a guest asks about a specific allergen or a combination.

The menu and the matrix must agree. A menu that marks a dish as nut-free while the matrix says it contains nuts is a dangerous contradiction.

The matrix is built from allergen and recipe data: the ingredients of every dish, and the allergens in every ingredient. A sauce bought ready-made brings its own allergens, listed on its label or the supplier's specification; a dish made in-house carries the allergens of everything that goes into it.

Build each dish's allergens from its full recipe, including the components that are easy to forget: the oil it is cooked in, the dressing, the garnish, the stock in the sauce. Our guide to build an allergen matrix that stays correct covers the method step by step.

Many allergens enter the kitchen inside bought ingredients: a stock powder with celery, a bread with sesame, a sauce with mustard. The matrix depends on knowing what is in each product.

Keep the supplier's specification or label for every product used, and check them when a product changes. A supplier who changes a recipe, or substitutes a different brand, can change a dish's allergens without the kitchen noticing.

The matrix shows what each dish contains, but guests with serious allergies also need to know about cross-contact: the risk that an allergen gets into a dish through shared equipment, surfaces or oil. A dish with no nuts, fried in oil used for something containing nuts, may not be safe for a guest with a nut allergy.

Note cross-contact risks where they exist, and train the team to mention them. Honesty about the risk lets the guest decide; a confident "it is fine" that ignores the fryer does not.

The allergen matrix needs one owner: one person responsible for keeping it accurate. In most venues, that is the head chef, because they control the recipes, with a named deputy for when they are away.

Ownership matters because the matrix fails in the gaps between people. When the chef changes a recipe, the owner updates the matrix the same day; when a supplier changes a product, the owner checks it; when a special goes on the board, the owner adds it.

The matrix must change every time a recipe, an ingredient or a supplier changes. Make the update part of the change itself: no new dish, no recipe change and no substitution goes live until the matrix has been updated.

Date every version, and keep the old ones for a while. If a question arises later about what a guest was told, the version in use on that date is the answer.

Check the matrix regularly against the real recipes: once a month, or whenever the menu changes, the owner walks through each dish with the cooks and confirms its ingredients. Recipes drift as cooks make small changes, and the check catches the drift.

A matrix that has not been checked for six months is a matrix that is probably wrong somewhere.

When a guest mentions an allergy, the server should check the matrix, not memory, and tell the kitchen on the order. If a dish contains the allergen, offer an alternative; if it might, because of cross-contact or uncertainty, say so honestly.

Our guide to allergen rules and the conversation at the table covers how the conversation should go. The matrix gives the server the facts; the conversation gives the guest confidence.

Sometimes a dish can be made without the allergen: the sauce left off, the garnish changed, a different bread. The matrix should show which dishes can be adapted, and the kitchen must confirm that the adaptation is safe before it is offered.

Record the adaptation on the order clearly, so the cook knows the change is for an allergy, not a preference. Our guide to what a modifier is on a restaurant order covers how changes should reach the kitchen.

The matrix helps the server choose; the ticket helps the cook deliver. Every order for a guest with an allergy should carry the allergy on the ticket, clearly, so the cook and the pass know to take care.

A matrix that is perfect but whose information never reaches the cook protects nobody. The allergy must travel from the guest to the plate.

Some venues keep the matrix on paper, printed and pinned in the kitchen and at the service station; others keep it in a system, on a screen or a tablet. Digital matrices can be updated once and seen everywhere; printed ones must be reprinted and replaced every time.

Whichever form, make sure every copy is the current one. An old printed copy left at the bar is as dangerous as no matrix at all.

Some guests want to see the matrix themselves. Offering it, or showing allergen information on a digital menu, lets guests check for themselves and choose with confidence.

Make the information readable: clear symbols, a key, plain names for the allergens. A matrix that only the kitchen can understand does not help a guest.

Train every member of the team on the matrix: where it is, how to read it, how to tell the kitchen about an allergy and what to do when unsure. Make "check, do not guess" the rule.

Train new staff before their first shift, not after. A new server who does not know where the matrix is will answer from memory, and their memory is the newest in the building.

If a guest reacts, act at once: call for medical help if needed, follow the venue's emergency procedure and look after the guest. Afterwards, find out what went wrong: the matrix, the recipe, the order or the kitchen.

Our guide to an allergy mistake: the next ten minutes covers what to do. The matrix is often where the investigation starts.

Drinks contain allergens too: milk in coffees and cocktails, eggs in some cocktails, sulphites in wine, gluten in beer, nuts in some liqueurs and syrups. Include the drinks in the matrix, or in a separate one for the bar.

A guest with a milk allergy who checks the food matrix and orders a coffee with milk is let down by a matrix that stopped at the kitchen door.

Specials change often, which makes them the dishes most likely to be missing from the matrix. Add each special to the matrix before it goes on the board, and remove it when it comes off.

Brief the team on each special's allergens at the pre-service briefing. A special that nobody can describe the allergens of should not be served to a guest with an allergy.

When a supplier substitutes a product, or the kitchen uses a different brand because the usual one is out of stock, the allergens may change. The substitution must be checked against the matrix before the product is used.

Make checking substitutions part of receiving. The person who accepts a different product should know to check its allergens, or to tell the owner of the matrix.

Cooks need the allergen information as much as servers. A cook who adds a garnish, swaps a sauce or improvises a dish for a guest with an allergy must know what each ingredient contains.

Keep the matrix, or the recipe sheets with their allergens, where the cooks can see them. A cook who has to guess what is in a sauce made by another section should ask, and the answer should be written down.

In a group with several venues, each venue's matrix must match its own recipes. A dish with the same name at two venues may be made differently, with different allergens.

Keep a matrix for each venue, owned by each head chef, and check them whenever dishes or suppliers are shared. A central matrix that assumes every venue makes every dish the same way can be wrong in several places at once.

Guests ordering for delivery cannot ask a server. The allergen information on the delivery listing, or with the order, must be as accurate as the matrix in the dining room.

Check the delivery listings whenever the matrix changes. A listing that still shows an old recipe's allergens misleads guests who rely on it completely.

Staff meals and tastings matter too: team members have allergies as well as guests. Label staff meals with their allergens, and make sure team members with allergies know what they are eating.

A kitchen that looks after its own team's allergies builds the habits that protect its guests.

In many places, the law requires allergen information to be available to guests, accurately, and the matrix is how most venues meet the requirement. Inspectors may ask to see it, and how it is kept current.

Keep the matrix, its dated versions and the supplier specifications behind it. They are the evidence that the venue knows what is in its food.

An allergen mistake can harm a guest seriously, and it can bring legal action, a damaged reputation and the loss of the venue's licence or rating. The cost of keeping the matrix current is small beside the cost of a single serious mistake.

Treat the matrix as one of the venue's most important documents, because it is.

A matrix with dozens of columns and tiny marks is hard to read in a hurry. Keep it as simple as the information allows: clear columns, clear marks and the dishes in the same order as the menu.

Test it on a new member of staff. If they cannot find whether a dish contains sesame within a few seconds, the matrix needs to be clearer.

Guests often ask about more than one allergen, or about an ingredient that is not one of the fourteen, such as garlic. The matrix should help the server answer both, and the server should know when to ask the kitchen.

If an ingredient guests ask about often is not in the matrix, add it as a column.

The owner of the matrix will not always be there. Name a deputy who can update it when the owner is away, and make sure both know the process.

A matrix that can only be updated by one person is a matrix that falls behind every time that person takes a holiday.

Note the date and the change each time the matrix is updated: "dressing on the chicken changed to include sesame, updated by the head chef". A simple log of changes makes it easy to see when a dish's allergens changed and why.

The log also helps the team trust the matrix. A matrix that shows it was checked last week is one people use.

When the menu changes for a new season, rebuild the matrix for every new dish before the first service, and remove the dishes that have gone. A seasonal change is the moment the matrix is most likely to fall behind, and the moment to check it most carefully.

An invented bistro keeps a printed allergen chart, updated when the chef remembers. After a near miss with a changed dressing, the head chef takes ownership of the matrix, rebuilds it from every recipe and every supplier specification, and makes a rule: no recipe change or new special goes on until the matrix is updated and reprinted, with the old copies removed.

The sous chef checks the matrix against the recipes on the first Monday of every month, and the team is trained to check it for every allergy question. The next three changes to the menu, including a new supplier for the bread, are all caught and updated before a single plate is served.

In servearound, each dish carries its own allergens, chosen from a catalogue of the statutory families and about eighteen more, where either a whole family, such as fish, or a specific source, such as salmon, can be tagged, together with its ingredients and dietary tags. Allergens are set on each dish by the team, not drawn from recipes, because servearound holds no recipes.

The guest menu shows each dish's allergens and dietary tags, with filters to show only or avoid them and the note that guests should always tell their server about allergies. On the kitchen screen, the guest's allergies sit at the head of the ticket, and a dish shows in red when it contains one of them. See the menus module.

A grid of every dish against every allergen, showing which dishes contain which.

Those the law requires where you trade, often fourteen, plus any guests often ask about.

One named person, usually the head chef, with a deputy.

From allergen and recipe data: every ingredient of every dish, including bought products.

Every time a recipe, ingredient or supplier changes, before the change goes live.

Note the risks and mention them honestly to guests with serious allergies.

Check it for every allergy question, and pass the allergy to the kitchen on the order.

Offering it, or showing allergens on the menu, helps guests choose with confidence.

What is an allergen matrix? It is the grid of every dish against every allergen the venue must declare, and it is how the team answers allergy questions reliably. Build the allergen matrix from allergen and recipe data, including every bought product, and follow the allergen rules where you trade.

Give it one owner, update it before any change goes live and check it against the real recipes every month. Keep the menu allergens and the matrix in agreement, mention cross-contact honestly, train the team to check rather than guess and make sure every allergy reaches the kitchen ticket.