Allergen safety that holds up under service
Most kitchens know their allergens. The failures happen between the document and the pass — a changed recipe, a shared fryer, a server who is guessing.
Control, not paperwork
Three layers that have to work together
A printed matrix is only useful if the kitchen controls the process and staff can reach the answer. MenuOps covers all three.
The matrix itself
Every dish mapped to the 14 major allergens from your actual recipe, with 'contains' and 'may contain' kept separate. Merging them into one asterisk is how a matrix becomes useless.
Change control
Upload a revised menu and the affected rows are regenerated and flagged. A supplier switch that introduces an allergen with no menu change is caught at review, not at service.
Point-of-service access
Allergen information sits with the dish on the till. A server answers in seconds without walking to an office or interrupting the kitchen.
Where kitchens lose control
The five failures we keep seeing
None of these are carelessness. They are all consequences of the information living somewhere other than where the decision is made.
The matrix is a spreadsheet nobody updates
It was accurate on the day it was made. Recipes moved on, and the gap grows silently from there.
Staff can list the 14, but not the dishes
Reciting the list is memorisation. Recognising celery in a stock cube is the actual skill, and it is the one that gets tested at the table.
'Contains' and 'may contain' are collapsed
One column cannot express two different decisions. The guest is refused a safe dish, or reassured about an unsafe one.
Cross-contact controls are documented but not physical
A dedicated fryer appears in the procedure and a shared one at 6pm. Nothing catches the gap until an incident does.
Written information has drifted from service
The menu board, the online listing and the printed menu each get updated independently, and the allergen lines are always the last thing anyone edits.
In practice
How the answer reaches the table
The last step is the one that determines whether any of this matters during a Saturday service.
-
1
Guest asks
A coeliac asks whether a dish is safe. This is a routine question, not an exception, and it should never require a manager.
-
2
Server checks the matrix
The answer is on the till, with the ingredient responsible named — not just a yes or no.
-
3
Kitchen applies the control
'May contain' means the kitchen applies the documented procedure before the plate leaves the pass.
-
4
Server answers honestly
If the dish cannot be made safe, staff are told what to say and what to offer instead. That script is trained, not improvised.
Put this into practice
Upload a menu you already use. Review the allergen matrix MenuOps generates from it — that is the fastest way to know whether it is worth your time.