Allergen chart for bars and restaurants: myth vs reality

Step one: a recipe spec for every dish before the matrix

An allergen chart starts in the standard recipe book, and the deliverable of the first step is a recipe spec for every dish, mother sauce, side and drink, with the exact ingredient, the supplier brand and the product spec sheet filed next to it.

You check it in a very simple way: pick five dishes from the menu at random, ask for their specs and confirm that behind each ingredient there is a supplier sheet, with no gaps like «house dressing» or «spice mix». If one is missing, the step is not closed.

This costs office hours and no investment, and it also puts your costing in order, because the same sheet that declares the mustard in the dressing is the one that tells you how much that dressing weighs on the plate against the 32 % food cost ceiling we use at Masterestaurant. One source of truth for two problems.

Step two: the matrix that crosses every dish with the official list

The matrix puts dishes and drinks in the rows and the mandatory-declaration allergens of your territory in the columns, and each cell allows four answers: contains, traces from shared processing, does not contain and not verified. That last one is the most honest answer on the sheet and the one most often erased out of embarrassment, when in fact it tells the floor that the dish is confirmed to no one until the kitchen checks the spec.

The deliverable is the complete matrix, with a version date and the head chef's signature, and it passes when no cell is empty and every «does not contain» traces back to a specific supplier sheet. Look hard at the shared fryer, which turns gluten-free fries into fries with traces, and at the batter flours, because that is where the spreadsheet LIES without anyone noticing.

Step three: the bar enters the recipe book with the same discipline

Every cocktail, syrup, cream and house beer needs its own recipe spec just like a dish, and the deliverable of this step is the bar section of the matrix, signed by the head bartender rather than the chef.

The almond syrup made on Mondays carries a dated label with its ingredient list stuck to the bottle, the egg white in the sour is logged as egg, and nut garnishes are noted separately because they are what the bartender improvises on a packed night. You check it by asking the bar shift, without looking at the menu, which allergens the best-selling cocktail contains; if they hesitate, the spec lives in a binder and not behind the bar.

And this matters for the business: the review by Stankovich et al. in Frontiers in Allergy (2023) counts 26 million adults with food allergy in the U.S., guests who choose where to drink based on the trust the bar gives them.

Step four: the ticket, pass and table protocol

The chart only protects guests when it travels with the ticket, so the fourth step puts in writing a protocol with three uneven checkpoints: the server who takes the declaration, the kitchen that validates it against the matrix and the pass that confirms the dish before it leaves.

The guest's declaration is marked on the ticket with a visible code, the kitchen uses a separate board and utensils for that dish, and the pass does not send it out until the named lead of the shift has checked it. The UK figure explains the urgency: Frontiers in Allergy (2023) attributes 59 % of food anaphylaxis hospitalisations in that country to food service establishments.

The deliverable is the protocol printed in the kitchen and at the bar, and you verify it with one drill per shift, in which someone declares a made-up allergy and you measure whether the whole chain responded without improvising.

What should you do when a supplier changes an ingredient?

You update the chart before the new ingredient reaches the line, never after. Think through the full sequence if you don't:

the case of sauce arrives from a different manufacturer, the new sheet declares sesame, nobody reads it because it came stapled to the invoice, the server confirms in good faith that the dish is safe and the kitchen sends it because the matrix still says what it always said. That mistake is not the server's, it belongs to the receiving process.

That is why the control lives at the storeroom door: whoever receives compares the product sheet with the previous one, and if anything changed, the item is set aside with a red tag until the head chef corrects the matrix and dates it again. The deliverable is a supplier change log with date, ingredient and signature, and you verify it by matching the month's invoices against that log.

The mistakes that repeat most when you run this guide

The number one mistake is treating the chart as a front-of-house document that gets printed once and laminated, when it is a living kitchen document that ages with every recipe or supplier change. I got this wrong for years, because I believed more information on the menu meant more safety, and the paradox is that the opposite happens: a menu full of icons convinces the server there is no longer any need to ask the kitchen.

The bridge between the two ideas is clear, the menu guides and the kitchen decides. Other frequent errors are leaving out daily preparations and specials, relying on the memory of the veteran cook and not dating versions. The cost of getting it wrong comes from the same review by Stankovich et al.: 25 % of anaphylactic reactions happen while the person is eating at a restaurant.

Closing checklist: how to know everything is right

The chart is right when it survives a ten-minute surprise audit, and Diego F. Parra frames it at Masterestaurant with these questions, in this order. Every dish and drink on the menu, specials and bar preparations included, has a recipe spec with supplier sheets on file. The matrix has no empty cells, carries a version date and a signature, and every «does not contain» traces back to a document.

The ticket, pass and table protocol is printed where the work happens, and the shift's last drill ran without improvising. The supplier change log matches the month's invoices. And the one most often forgotten: there is a lead with a NAME on every shift in the kitchen and at the bar, and the team knows who it is.

If any answer is no, today's action is to fix that single line before the next service, without waiting to rebuild the whole chart.

What separates a chart that protects from one that decorates?

The most repeated mistake, and Diego F. Parra flags it in every menu review he runs with Masterestaurant, is building the chart from the menu instead of the kitchen:

the menu says house salad, while the spec sheet says the dressing has mustard, the croutons have gluten and the grated cheese comes from a supplier that declares traces of tree nuts. Think about what happens if your sauce supplier quietly changes manufacturers on a Tuesday.

The new product sheet declares sesame, nobody reads it because it came stapled to the invoice, the chart still says does not contain and the server, in good faith, tells the guest the dish is safe. That is why receiving is part of the allergen system: a supplier change without a chart update is an incident even before anything happens.

What separates a chart that protects from one that decorates — in practice?

The business risk is not theoretical. The Frontiers in Allergy review (2023) attributes 59% of UK hospital admissions for food anaphylaxis to food service establishments, which moves the chart from paperwork to reputational risk control at board level.

Then there is the tension every chef-owner knows, safety against profitability. Gluten-free bread, plant milk or a nut-free sauce cost more, and the reflex is to refuse to adapt. I settle it in the spec sheet, not in the argument: cost the adapted version, check it stays within the 32% food cost ceiling (the maximum, never the recommendation) and, if it does not fit, that dish is not offered adapted and the chart says so. What you never do is improvise the swap at the pass.