Introducing Flow from Creventa: turn every enquiry into an event→

How to Write an Allergen SOP for Hospitality Events

In short: An allergen SOP for hospitality events is a written procedure that says who captures each guest’s dietary requirements, when the information is locked, how it reaches the kitchen and service team, and what happens when it changes. The safest venues capture allergies at the point of booking, set a firm cut-off, print every kitchen and service sheet from one source, and treat any late change as a controlled handover rather than a quick word in the pass.

What should an allergen SOP for events cover?

An event allergen SOP should cover five stages: capture, verification, kitchen handover, service and change control, with a named owner for each. Most venues already have an allergen policy for the restaurant. Events need their own procedure because the risk is different: the guest is often not the person who booked, information arrives weeks before the meal, and hundreds of plates leave the kitchen in a few minutes.

Write the SOP around the event lifecycle rather than around the allergens themselves. Staff training covers what the 14 allergens are. The SOP covers how a declaration made by a wedding guest in March reaches the right plate in June.

StageOwnerOutput
1. CaptureEvents coordinatorEvery guest’s choices, allergies and dietary preferences recorded against their name
2. Verify and lockEvents coordinator, head chefConfirmed list at the cut-off date, severe allergies reviewed by the chef
3. Kitchen handoverHead chefChef report with dish totals and allergy flags, custom dishes confirmed
4. ServiceBanqueting or restaurant managerFood pass, front of house report and place cards with allergy markers
5. Change controlDuty managerRecorded late changes, reissued sheets, briefed team

Stage 1: how to collect dietary requirements for weddings and functions

The safest way to collect dietary requirements for weddings and functions is to ask every guest directly, at the point of booking or invitation, through a structured form tied to the menu. Asking the organiser to gather allergies by email produces second-hand information, free-text notes such as “one veggie, a nut thing” and no record of who said what.

Your SOP should specify that the capture form:

  • Lists the 14 mandatory allergens as tick boxes, with a separate field for anything else, such as kiwi or mushroom
  • Separates medical allergies from preferences such as vegetarian, vegan, halal or no alcohol
  • Records the declaration against the individual guest, not the booking
  • Asks for the meal choice in the same step, so allergy and dish are linked from the start
  • Works from a personalised link or QR code, with no account or password for the guest to create

Removing the login matters more than it seems. Event guests are often older, on a phone, or reluctant to register for something they will use once. Every extra step lowers the response rate, and a missing response is the riskiest record of all because the kitchen cannot tell “no allergy” from “never answered”.

Hotels tracking allergies for large dinners and weddings should also set reminders into the procedure: at invitation, about a week before the cut-off and a couple of days before it. Chasing then becomes a scheduled step rather than something the coordinator remembers to do.

Stage 2: verify the data and set a cut-off

Every event SOP needs a cut-off date after which dietary information is locked and the kitchen orders against it. For most functions that is between 7 and 14 days before the event, and it should be written into the booking terms so the organiser knows it from the start.

At the cut-off, the events coordinator should run a check for three things: guests who have not responded, declarations with free-text notes that need clarifying, and severe or unusual allergies. The head chef reviews the last group and decides whether a custom dish is needed. That decision, and who made it, should be recorded against the guest so it appears on every downstream sheet.

Non-responders need a rule too. Many venues assume a non-responder has no allergy, which is the wrong default. A safer rule is that non-responders are flagged on the front of house report so a server asks at the table before the first course.

Stage 3: how to prevent allergen mix-ups between front and back of house

Allergen mix-ups at large catering events are prevented by printing every kitchen and service document from the same data, so the chef report, food pass, front of house sheet and place cards cannot disagree. Most mix-ups happen at handover points: a dietary list retyped into a function sheet, a seating plan changed after the place cards were printed, or a verbal update that never reached the server.

The SOP for the handover should set out these steps:

  1. Chef briefing. The head chef receives a report with dish totals by course and every allergy listed by guest name, table and seat.
  2. Dish allergen check. The chef confirms the allergens in every dish on the event menu, including sauces, garnishes and modifiers, and signs off the custom dishes.
  3. Cross-contact controls. Named chefs prepare allergen plates using separate equipment and a defined prep area, and those plates are plated and labelled first.
  4. Service briefing. Before doors open, the banqueting manager walks the team through every allergy by table and seat using the front of house report.
  5. Visual markers. Place cards and the food pass carry a clear allergy marker so a server can confirm the guest before setting down the plate.
  6. Plate-to-guest check. Allergen plates leave the pass with the guest’s name and seat, are delivered by a named server and are never auctioned at the table.

Staff also need to know what is in every dish served that day, not just which guests have allergies. Build a five-minute menu briefing into every event, with the dish allergen matrix to hand at the pass.

Stage 4: change control on the day

Late allergen changes should go through one named person, be recorded, and trigger reprinted sheets rather than a handwritten note. A guest who mentions an allergy at the bar during the drinks reception is a normal event, and the SOP should treat it as one.

The duty manager takes the detail, informs the head chef, updates the guest record and reissues the affected food pass and front of house page. If the venue keeps versioned run sheets, the old version should be removed from the pass. This step is where an allergen record earns its value: if something goes wrong, the venue can show what was declared, when, and how it was acted on.

What does UK law require for allergens at banquets and hotel events?

UK food businesses, including hotels and event venues, must be able to tell guests if any of the 14 allergens is in the food they serve, under the Food Information Regulations 2014. For most banquet and plated event food, which is not prepacked, the information can be given in writing or verbally, and the Food Standards Agency encourages businesses to provide it in writing and back it up with a conversation.

Natasha’s Law applies to food that is prepacked for direct sale, meaning food packed on the premises before a customer orders it. For events, that typically covers items such as packed conference lunches, boxed sandwiches or grab-and-go snacks. Those need a full ingredient label with allergens emphasised. Plated dinners and buffets fall under the non-prepacked rules instead. Check current guidance from the Food Standards Agency and your local authority, as this article is general guidance, not legal advice.

Where software fits in an event allergen SOP

Allergen tracking software for events replaces the retyping between stages, which is where most errors enter. Creventa, an event management platform for hospitality venues, sends each guest a branded personalised link or QR code to choose their meal and declare allergies, with no account to create. It records all 14 allergens plus custom ones, keeps medical allergies separate from preferences, and blocks menu items a guest has declared an allergy to, with an explanation of why.

The kitchen and service documents are generated from those responses. The chef report, food pass, front of house report and place cards print with allergy flags, run sheets can list allergy orders first for the kitchen, and custom dishes for guests with severe allergies flow into every report. An unconfirmed orders report shows dietary detail for guests who have not completed their order, and buffet tent cards can carry allergen information. Creventa integrates with TenKites, so dish allergen data can come from the venue’s existing menu system.

Allergy declarations2.1% of guests

Festive guests who declared an allergy on Creventa, Christmas 2025

Response rate99.2%

Guests who responded to pre-order invitations, with three automatic reminders

Allergens tracked14 plus custom

All mandatory UK allergens and any non-standard allergy

Time saved4 to 6 hours per event

Reported by multiple Creventa customers

Allergen SOP sign-off checklist

Use this list to check your procedure before the next large event:

  • Every stage has a named owner and a deputy
  • Guests declare allergies individually, against the menu, without a login
  • Medical allergies and preferences are recorded separately
  • A cut-off date is in the booking terms and the reminder schedule is set
  • Non-responders are flagged for a check at the table
  • All kitchen and service sheets print from one source
  • Late changes go through the duty manager and trigger reissued sheets
  • Prepacked items for the event carry full ingredient labels

Frequently asked questions

How should venues collect dietary requirements for weddings and functions?

Ask every guest directly through a personalised link or QR code that lists the 14 allergens, separates allergies from preferences and links the declaration to the guest’s meal choice. Gathering allergies through the organiser by email produces second-hand, unstructured information.

Is there software for guest dietary requirements without a guest login?

Yes. Event platforms such as Creventa send each guest a personalised link by email, or a QR code, so they can choose their meal and declare allergies without creating an account or password.

Does Natasha’s Law apply to banquets and hotel events?

Natasha’s Law applies to food prepacked for direct sale, such as packed conference lunches or boxed sandwiches. Plated banquet and buffet food is non-prepacked, so venues must provide allergen information for the 14 allergens, ideally in writing backed up by a conversation.

How do you prevent allergen mix-ups at large catering events?

Print the chef report, food pass, front of house report and place cards from one data source, mark allergy guests on place cards and the food pass, brief the team by table and seat, and send allergen plates to the table with a named server.

What should happen if a guest declares an allergy on the day?

The duty manager records the detail, informs the head chef, updates the guest record and reissues the affected service sheets. The change should never rely on a verbal message alone.

About the author

Andrew Norton, Head of Product, Creventa. Andrew leads product at Creventa after years working with hospitality venues on the admin gap between a confirmed booking and event day.


Book a Demo