Ask any manager what they dread about an Environmental Health visit and the allergen folder is near the top of the list. Not because anyone disputes that it matters — hospitality has learned that lesson in the hardest possible way — but because the standard approach to compliance is a laminated matrix that was true the day it was printed and decays from that moment on.

The laminated sheet problem

The traditional allergen matrix is a spreadsheet printed on a Tuesday. By Friday the kitchen has changed the garnish on two dishes, swapped a supplier whose pesto now contains cashews, and added a special. The sheet doesn't know. The new starter isn't on it at all. And when a guest asks, a seventeen-year-old on their third shift is reading row 23 of a grid in 8-point type, under pressure, on a Saturday night.

That is not a compliance system. That's a compliance prop.

Where allergen systems actually fail

  • Drift — the dish changes but the paperwork doesn't, because they live in different places.
  • Coverage gaps — specials and substitutions never make it onto the printed matrix.
  • Translation errors — the chef knows the velouté has hazelnut; the document says 'nuts: no' because someone copied the wrong row.
  • Retrieval pressure — the information exists but can't be found quickly by the person being asked.

Tag the dish, not the document

The structural fix is to attach allergen data to the dish itself, at the moment the dish is created or changed — not to maintain a separate document that describes the menu from a distance. When the recipe changes, the tags are right there in the same edit screen, impossible to forget the way a separate spreadsheet is easy to forget.

Once the dish carries its own data, everything downstream stops being work: the printed matrix regenerates itself, the website lets guests filter by their own requirements before they even book, and the QR menu shows a coeliac diner only what they can eat. The answer to 'can I see your allergen information?' becomes 'of course' — instantly, in whatever format the guest or the inspector prefers.

A guest with an allergy doesn't want reassurance. They want evidence that your system can't forget them.

What good looks like

  • All 14 major allergens tracked per dish, set by the person who knows the recipe.
  • Dietary tags (vegan, vegetarian, gluten-free) handled in the same place, the same way.
  • A 'may contain' field for honest kitchen-reality notes — fryers, benches, suppliers.
  • A printable matrix generated from live data, so the EHO sees today's menu, not Tuesday's.
  • Guest-facing filters on the digital menu, so diners can check before they book.

Carte does all of this as a side effect of writing your menu. But even if you never use us: move your allergen data into the same place your menu is edited. The gap between those two places is where every failure lives.