The sauce changed, the sheet did not
Your head chef reworks the dressing on a popular salad because the old one was splitting on long events. It is better. It also now has a different mustard in it. The allergen matrix for your summer menus was built in March, lives in a spreadsheet, and was exported to PDF for the client pack.
A month later your usual supplier is out of a stock item and sends a substitute from a different brand. The kitchen uses it, because that is what arrived. Nobody thinks to open the matrix, because nobody connects the delivery note to the document. The event packs going out next week still carry the March version.
A document cannot know what changed
Allergen information is usually produced as a finished document. That works on the day it is made. After that, it depends on people remembering to update it every time something upstream moves.
- Recipes live in a chef's notebook, a costing spreadsheet or a recipe system, separately from the allergen sheet.
- Supplier substitutions happen at delivery, and the person receiving goods is not the person who maintains records.
- The same dish appears on several menus and event proposals, each with its own copy of the information.
- Contract sites and event kitchens may make the same dish slightly differently.
No one is being careless. The structure makes the right update depend on a chain of people all noticing, and that chain breaks under normal pressure.
Why this is worth fixing
The most serious consequence is the one every caterer worries about, and it is the reason your own procedures exist. Beyond that, there is a steady operational cost: chefs are nervous about improving dishes because of the paperwork, the office spends hours rebuilding matrices each season, and client-facing packs can show different information from what the kitchen is working to.
There is also the question of evidence. If a client or an inspector asks what information you held about a dish on a given date, a folder of PDFs does not answer that well.
Dish records that know their ingredients
- Each ingredient you buy has a record, with the allergen information your team has taken from the product specification, and the supplier and product it came from.
- Each dish is built from ingredient records, so its allergen summary is derived from them rather than typed separately.
- When a chef edits a recipe, the change is logged and the dish is marked for review by whoever your procedures say must approve it.
- Goods-in can record a substitution against the product it replaced. That marks every dish using it for review, and lists the upcoming events where those dishes are booked.
- Menus, event proposals and client packs pull the approved information from the dish record, so there is one source rather than many copies.
- Every approval is dated and named, so you can show what information applied on any past date.
| Event | What the system does | Who acts |
|---|---|---|
| Recipe edited | Marks dish and linked menus for review | Approver named in your procedures |
| Supplier substitution logged | Lists dishes and upcoming events using it | Head chef and events team |
| New product specification received | Prompts an update of the ingredient record | Whoever maintains product data |
| Event pack generated | Uses approved dish information only | Events coordinator |
If you already use a recipe and allergen system that does most of this, such as Nutritics, we connect to it and handle the parts it does not reach, like substitutions at goods-in and event proposals.
What changes in the kitchen and the office
Chefs can improve a dish knowing the change will be picked up rather than forgotten. The office stops rebuilding matrices every season, because they are generated. When a substitution arrives, the events team sees the three weddings next weekend that use the affected dish and can check them before the packs go out.
It does not replace your judgement or your food safety management. It makes sure the right people are asked to look at the right thing, at the time the change happens.
Is this where you are now?
- Your allergen matrix is a spreadsheet or document updated at menu launch.
- Supplier substitutions are not recorded anywhere that links to dishes.
- The same dish information is copied into several menus and packs.
- Chefs hold back small recipe changes because of the paperwork.