How to Audit Your Menu for Hidden Allergens

If nobody has done a dedicated allergen audit on your menu in the last year, it is worth assuming there is at least one gap sitting somewhere in a sauce or a garnish. This is not a criticism, it is just how menus work: they accumulate small changes faster than anyone tracks them, and allergen accuracy is usually the first thing to fall behind.

Start with the parts nobody thinks about

Skip the headline protein for a moment, you probably already know what is in the chicken. Go straight to the sauces, dressings, marinades, garnishes, and finishing oils, because that is where allergens hide in ingredients nobody reads as significant. A dish description rarely mentions the tahini in the dressing or the fish sauce in the marinade.

It also pays to check condiments that get treated as an afterthought, the little dish of chutney or the squeeze of aioli that arrives without ever being written into the menu description at all. These extras are added by habit, by whoever happens to be plating, and they are exactly the kind of detail that never makes it onto a formal allergen list.

A practical walk-through order

• Sauces and dressings: check for sesame, soy, dairy, and fish-based ingredients like fish sauce or anchovy
• Marinades and rubs: check for soy sauce, wheat-based thickeners, and nut oils
• Garnishes and toppings: check for seeds, nuts, and cheese finishes added at the last step
• Bread and starches served alongside the main dish, even when not listed as part of it
• Shared equipment: fryers, grills, and cutting boards used across multiple allergen categories
• Substitutions and specials: anything recently changed that has not been re-checked yet

Involve the person who actually cooks it

A recipe card is a good starting reference, but the person standing at the station often knows about small deviations the card does not capture, a pinch of something added by habit, a different brand of a condiment that changed the allergen profile without changing the recipe name. An audit that only reads paperwork misses this layer entirely.

It is worth walking the audit physically, station by station, rather than doing it entirely from a desk with recipe cards in hand. Standing next to the person cooking a dish surfaces details that never make it onto paper, because they were never written down as a formal step in the first place.

Make it a repeatable process, not a one-time event

An audit done once and never repeated has a shelf life measured in months, not years. Menus change too often for a single pass to stay accurate. Building the audit into a recurring quarterly habit, or tying it to any menu change, keeps the gap from reopening.

How long a real audit actually takes

Owners often overestimate how long a proper audit takes and underestimate how much it matters, which is a bad combination for actually getting it done. A focused walk-through of a menu with thirty to forty dishes, done by someone who already knows the kitchen, typically takes an afternoon, not a week. The barrier is rarely time. It is simply nobody having scheduled it.

Treating it as a scheduled task, blocked on a calendar the same way a deep clean or an inventory count would be, gets it done far more reliably than waiting for a natural gap in the week that never quite arrives on its own.

A useful side benefit of scheduling it regularly is that each subsequent audit gets faster than the last, since most of the menu will already be accurately tagged and only the changed items need real attention. The first audit is the expensive one. Every audit after that is mostly confirming what has changed since the last pass.

TasteGraph's menu setup walks through allergen tagging dish by dish when a menu first goes live, which functions as a built-in first audit, and any later recipe change can trigger the same review before it goes live to guests.