Restaurant allergen matrix template: a practical working system.

A restaurant allergen matrix is only useful when the kitchen trusts it, the service team can read it quickly, and somebody knows what changed since the last review. A grid filled once and left in a folder is a snapshot, not a control system.

This toolkit includes that grid and the working process around it: an ingredient register, dish matrix, completed example, review log and printable handover. It covers the 14 allergen groups that must be declared for non-prepacked food under Irish and EU rules.

Download the allergen matrix template.

The files are intentionally blank where your team must make a judgement. They are not pre-filled compliance certificates, and completing them does not replace label checks, kitchen controls, staff training or professional advice.

What a restaurant allergen matrix should do.

A useful matrix answers five operational questions:

1. Which of the 14 regulated allergens are intentionally present in each dish?
2. Which ingredients and supplier documents support that answer?
3. Where has a cross-contact risk been identified and assessed?
4. Which allergen-containing part can the kitchen reliably remove or substitute?
5. Who reviewed the record, and what should trigger the next review?

It should not reduce a complex kitchen to unexplained ticks. A mark needs a traceable route back to the current product label, recipe and preparation method. That is why the workbook separates the ingredient register from the dish matrix.

Contains, may contain, and can be made without.

These three statements answer different questions and should never be merged into one vague allergen flag.

• Contains means the allergen is deliberately present in the recipe or an ingredient used in it. Record it from the current label and specification.
• May contain communicates a residual cross-contact risk supported by the supplier information or your own documented assessment. It is not a substitute for good controls and should not be applied to every dish by default.
• Can be made without is a service instruction, not a claim that the kitchen is allergen-free. Use it only when the allergen-containing element can be removed or substituted consistently, and still discuss cross-contact with the guest.

Build it from ingredients, not memory.

Start at goods-in. Give every bought-in product a stable ingredient ID, then record its supplier, product or specification code, the date its current label or specification was verified, intentional allergens and precautionary statements. Do not assume two brands of stock, bread or sauce have the same profile.

Next, list the supporting ingredient IDs on each dish row so another reviewer can trace the answer back to the ingredient register. This reference field does not infer allergen statuses or decide that a dish is safe. The reviewer must still reconcile every dish mark with its ingredients and method. Then walk the actual stations: fryer, grill, pastry, pass, boards, utensils and storage. The written recipe cannot reveal every cross-contact path.

The companion restaurant allergen audit gives you a station-by-station method for finding the gaps before you complete the matrix.

A worked restaurant example.

Take a plate of grilled hake, crushed potato, brown-butter caper sauce and dressed leaves. The recipe contains fish and milk. If the dressing contains mustard, mustard is also a contains status even when it is not named on the menu. If the supplier’s capers carry a sulphite declaration, that must be recorded too.

Suppose the kitchen can serve the fish with olive oil instead of brown butter. Milk may be marked “can be made without” only after the chef confirms the complete method: clean pan and utensils, no butter in the potato, and a separate finish. Fish cannot be removed without changing the dish. A shared grill does not justify an invented blanket statement; the team must assess the real cross-contact risk and controls.

The workbook’s worked-example sheet demonstrates this structure with clearly fictional dishes. Replace every example with your own verified ingredients and procedures.

Use a change-led review cycle.

A useful review date is not merely the first day of each quarter. The stronger trigger is a change: new supplier, substituted pack, reformulated product, revised recipe, new garnish, different fryer or grill practice, new menu, or a reported near miss.

When something changes, quarantine the affected answer until it is checked. Record what changed, the dishes affected, the evidence reviewed, the decision, reviewer and date. Then brief both kitchen and front of house. The included review log is deliberately short enough to use during service preparation.

Turn the matrix into a service tool.

Keep the full evidence record with the manager or kitchen lead, but give front of house a compact, current view. Staff should be able to distinguish an ingredient that is present, an assessed cross-contact warning and a possible modification without improvising.

When a guest reports an allergy, the matrix supports the conversation; it does not replace it. Confirm the exact allergen, check the current record and preparation method, involve the responsible kitchen person, and communicate uncertainty rather than guessing. If the record and the kitchen disagree, stop and verify before taking the order.

Crumb applies the same separation to live menus: ingredient-level records can feed guest allergen details, kitchen matrices and staff sheets, while “may contain” and “can be made without” remain distinct. Updating the approved source can then update every place that uses it, rather than leaving separate spreadsheets and menus to drift.

Official guidance and scope.

This toolkit is operational guidance, not legal advice. For restaurants in Ireland and the European Union, its structure follows Regulation (EU) No 1169/2011 and the official guidance for non-prepacked food. Great Britain applies its own food-information law and FSA technical guidance; Northern Ireland remains aligned with relevant EU food-information rules under the Windsor Framework. These sources are not interchangeable, so always use the current rules and enforcement guidance for the place where your restaurant operates.

• Food Safety Authority of Ireland: allergen information for non-prepacked food.
• Regulation (EU) No 1169/2011 on food information to consumers.
• Great Britain: Food Standards Agency technical guidance for non-prepacked food.

The best matrix is not the one with the most marks. It is the one your restaurant can explain, trace and update before the next guest relies on it.