Stop Allergen Mix-ups at Events: Sync Menus, Labels and Run Sheets

Stop Allergen Mix-ups at Events: Sync Menus, Labels and Run Sheets

FSANZ’s Plain English Allergen Labelling (PEAL) is now live, and auditors and clients want proof—on the day—that your allergen calls match what’s prepared and served. Here’s how catering owners, event managers, and kitchen leads can turn compliance into calm, consistent service.

1) Situation: New rules meet event-day reality

This is a “new compliance obligations” moment with an operational risk edge. You must show, in plain terms, where allergens are called out across menus, platter labels, and briefings—and that those call-outs reflect the dish actually served. The win isn’t just passing audits; it’s protecting guests and your brand.

Why this matters now

• Auditors and clients will ask to see your allergen evidence at service, not after.
• Inconsistent paperwork equals inconsistent plates—a direct safety risk.
• Documentation is part of service quality, not an afterthought.

2) The document gap at service

The kitchen updates a recipe to almond-free. The run sheet still warns “contains nuts.” The floor team prints yesterday’s page. No one can show who acknowledged today’s hygiene step.

That’s the document gap—when what’s cooked, what’s printed, and what’s briefed don’t match. It triggers guest risk, rework, delays, and tougher audits. It often stems from scattered files, unclear version control, and last-minute changes without a formal cutover.

Common failure points

• Recipes updated but menus/labels not refreshed.
• FOH prints an old run sheet from email.
• No record of who read the latest hygiene procedure.
• Dietary serves promised at quote stage but not finalised in production notes.

3) Plain-English call-outs your guests and auditors can see

What “plain English” looks like in practice

• Allergen declarations use bold or a clear contrasting typeface to the rest of the text.
• Call out common allergens plainly (e.g., milk, egg, peanuts, tree nuts, sesame, soy, fish, shellfish, wheat). Gluten and sulphites must also be declared.
• Where required, include mandatory warnings and advisory statements in simple terms.
• Date marking: show prep date and use-by/best-before as relevant to your service model.
• Consumers have a legal right to written or verbal allergen information on request; your team must be able to answer from current documents.

On-the-day labelling

• Use hygienic, food-safe, smudge-resistant labels with clear fonts.
• State dish name and allergens in bold; avoid abbreviations staff can misread.
• Include batch/time where practical for trace-back.
• For buffets/platters, place labels where guests and auditors can easily see them.

4) Make every surface match: menu, label, briefing

A 5-step pre-service sync

1. Single source of truth: one live event pack holding menu, allergen sheet, run sheet, and hygiene procedures.
2. Cutover time: freeze changes by a set hour; anything after triggers a controlled update.
3. Version lock: stamp documents with version/time; FOH prints only the latest.
4. Read-back: a supervisor verifies that labels, menus, and run sheet allergen flags match, line by line.
5. Briefing: deliver a 90-second allergen summary in the pre-shift huddle; note acknowledgements.

Service surfaces to sync

• Printed/onsite: menus, platter cards, pass labels, run sheets.
• Spoken: FOH briefings, dietary handoff at pass.
• Digital: the live event pack your team references on mobile.

5) Evidence beats promises: build an audit trail

Compliance requires evidence you can show. That means a controlled document system, not just shared folders. Your audit trail should demonstrate what changed, when, by whom—and who read it.

Proof points auditors expect

• Staff acknowledgements tied to the current version of food safety and hygiene procedures.
• Allergen sheets linked to final menus and labels, with timestamps.
• Change log for recipes and dietary adjustments.
• Pre-service checklist and label sign-off captured before doors open.
• Incident/near-miss log with corrective action and retraining notes.

Operational payoff

Document control (with ownership, versioning, and read receipts) reduces repeated questions, speeds onboarding, and keeps remote or casual staff aligned.

6) Who does what: a lightweight RACI for events

• Head Chef (Owner): owns the allergen sheet; approves final declares for each dish.
• Event Manager (Accountable): owns the run sheet and guest dietary list; sets change cutover.
• Ops Lead (Controller): manages version control; ensures only the latest docs are printable/viewable.
• Prep Lead (Responsible): separates dietary serves, labels them distinctly, and stores separately.
• FOH Captain (Responsible): verifies platter labels match the pass and briefs the floor team.
• All Staff (Informed): acknowledge current hygiene and allergen procedures before service.

Timing that prevents chaos

• Dietary serves planned at quote stage; finalised at least 14 days before the event where possible.
• Morning-of change? Trigger a mini-change process: update allergen sheet → regenerate labels → re-brief → capture read receipts.

7) Strategic upside: consistency, trust, and fewer last-minute fires

When menus, labels, and run sheets come from a single source of truth, your service becomes predictably safe. You’ll reduce last-minute scrambles, protect guests, and show auditors a calm, controlled operation.

Metrics to watch

• Label reprints per event (trend down).
• Late dietary changes inside cutover (trend down).
• Time to onboard new casuals (trend down).
• Allergen near-misses (trend down) and audit findings (close out faster).

8) Keep the current procedure with the crew

TKO Policy Guides helps you keep the current food and allergen procedure with the team running the event. Put your food safety procedures, allergen sheets, event run sheets and staff hygiene procedures in one place, update them before service, and make sure the crew on the job can reference the current version and record they’ve read it.