How to Build an Allergen Matrix That Survives an Inspection

An allergen matrix is the document that turns a good intention into a defensible process. It is also, in most kitchens, a piece of A4 in a drawer that was accurate eighteen months ago.

Here is what a useful one looks like and how to keep it true.

What it must contain

For every menu item:

• The dish name, exactly as it appears on the menu.
• Every allergen present as an ingredient, from all 14.
• Every plausible cross-contact risk, from shared equipment, oil, stock or prep surfaces.
• The controls applied for that item — dedicated fryer, separate prep, colour-coded utensils.
• A prepared-by name and a date, per row or per batch.

Why paper versions fail

The failure is not carelessness. It is that a paper matrix has no lifecycle. It has no owner, no change trigger and no way to know it is stale. A menu item is changed on a Tuesday by someone who does not know a matrix exists, and the matrix is wrong from Wednesday onward with no signal to anyone.

This is the specific problem digital extraction solves: when a new menu version is uploaded, the matrix is regenerated and the changed rows are flagged for review, rather than waiting for someone to remember.

Separate 'contains' from 'may contain'

The single most useful structural improvement is separating two different things that usually get merged into one ambiguous column:

Contains — deliberate

The allergen is in the recipe. Action: the guest must be told, and if they have the allergy they cannot eat the dish.

Cross-contact risk — accidental

The allergen is not in the recipe but may be present through the process. Action: the guest must be told, and the kitchen applies controls before serving. Not a refusal — a conversation.

Collapsing these two into a single yes/no is how restaurants end up either refusing service for a dish that is perfectly safe with care, or reassuring a guest about a dish that genuinely cannot be made safe.

Make it findable

A matrix in the office is a compliance document. A matrix on the floor is a control. It needs to be reachable in under five seconds by the person taking the order — which in practice means the point of sale, not a folder.

Review cadence

• On every menu change — the rows for changed items are re-verified before the new menu goes live.
• On every supplier change — reformulated stock or oil can introduce an allergen with no menu change at all. This is the one most often missed.
• Annually — a full re-verification, plus a re-check of every photograph and marketing asset that names a dish.
• After any incident — and the incident log should feed back into the matrix rather than living in a separate system.

What an inspector actually asks for

Expect four questions. Can you show me your current allergen information? How do you manage cross-contact? How are staff trained, and can I see the record? What happens when a guest reports a reaction? Each has a document behind it. If any of the four is answered from memory, that is the finding.

The practical takeaway

Treat the matrix as a live system rather than an artefact. Extract it from the menu automatically, keep it versioned, put it where staff are standing, and give it an owner. Everything else is detail.