How to manage dietary restrictions and food allergies at events

Manage dietary restrictions and food allergies at events by asking attendees what they need early, checking what your caterer can actually provide, and confirming how each agreed meal will reach the right person. Give someone ownership of that whole process, including ingredient changes, service questions and the route to medical help.

A question on a registration form doesn't finish the job. Someone has to read the answer, discuss it with the kitchen, get back to the attendee and check that the agreement survives a busy lunch service. That's where an event can look organised on paper and still let someone down.

If food is included in a paid ticket, buyers are making plans around your promise. A conference delegate shouldn't discover at lunch that their only option is a piece of fruit. A festival attendee shouldn't have to guess whether a vendor's answer came from the recipe or from memory. You need an honest offer and a service your team can deliver.

This guide walks you through collecting requests, choosing catering, planning meals, communicating clearly and handling service on the day. We'll also cover late changes, food stalls, emergency preparation and a worked example you can adapt to your next event.

Separate the meal choice from the food safety question

The first thing you want to do is stop treating every request as the same kind of request. Vegetarian, halal, a peanut allergy and coeliac disease can all change someone's meal, but they don't tell your caterer the same thing.

An attendee asking for a vegetarian meal is telling you about what they eat. An attendee reporting a food allergy is telling you about a food safety concern. Religious requirements may include sourcing or preparation conditions that a menu name doesn't explain. Ask about the practical requirement rather than assuming you know it.

Coeliac disease also needs care. The NHS describes it as a condition in which the immune system attacks the body's tissues when someone eats gluten. It's different from a food allergy, but it still needs a clear catering conversation. Don't file it under an optional preference because the attendee hasn't used the word allergy. NHS guidance on coeliac disease explains the distinction.

Give people room to describe the ingredient or requirement in their own words. A short list helps you count meal choices, but an "other" option and a private contact route help you catch what the list misses. Someone with several requirements should be able to state all of them.

Here's a common mistake. You see a milk allergy, notice a vegan option and assume the problem is solved. The Food Standards Agency warns that vegan food can still have unintended allergens from production or preparation. A dietary label and an allergen claim answer different questions. The FSA's explanation of vegan and free-from food makes that difference clear.

Keep that distinction in your records. "Vegan meal requested" is a meal choice. "Milk allergy reported, caterer reviewing" is an unresolved request. One doesn't automatically replace the other, and your team shouldn't quietly translate between them.

You also shouldn't ask attendees to rank their allergy as mild or serious so your team can decide whose request matters. Your job is to obtain the requirement and arrange an accurate response. The caterer and qualified medical team handle the matters within their expertise.

Ask early enough to act on the answers

Collect requests while there's still time to change procurement, preparation and service. That may be during registration or through a follow-up form. The right point depends on when the caterer needs the information and whether buyers have already chosen the people attending.

For a paid dinner, make the food arrangement visible before purchase. Tell buyers what's included, how to ask about dietary requirements and when they need to contact you. If the kitchen can't support certain requests, resolve that before somebody pays for a meal they're unable to use.

A group booking needs extra thought. The person buying a table may not know every guest's requirements. Give them a way to pass the request process to the actual attendees, and tell them who is responsible for returning the information. "The buyer didn't tell us" won't feel helpful at service.

Your form needs enough detail to support a catering decision without collecting an unnecessary medical history. A practical starting point is:

• The attendee's name and a booking or attendee reference.

• Which included meals or food sessions they will attend.

• Their requested meal choice, where choices are available.

• Any food allergy, intolerance, coeliac requirement or other food restriction they want you to consider.

• The specific ingredients or preparation requirements they need to discuss.

• A private contact route for clarification and changes.

Keep the meal question separate from the allergy question. "Choose your meal" followed by "Tell us about any food allergies or other requirements" is easier to understand than a single box labelled "special diet". It also gives the kitchen clearer records to review.

Explain what happens next. A useful form introduction would say, "Tell us what you need for the included lunch. Our catering team will review your request and we'll confirm the arrangement with you. Sending this form doesn't mean the meal has been confirmed."

Add a deadline agreed with the supplier, then give a contact route for requests after it. The deadline is a planning tool. It doesn't allow a server to ignore a food safety concern because the person arrived late or hadn't filled in the form.

Build the request reminder into your wider event confirmation email. Keep the message specific to the event and send it where the actual attendees can receive it. A receipt in the buyer's inbox doesn't prove their guests have seen the catering instructions.

Keep dietary information private and useful

An allergy record linked to a named attendee can reveal information about their health. Religious dietary information may reveal beliefs. The UK's Information Commissioner's Office lists health information and religious beliefs among the categories given extra protection under UK GDPR. The ICO's special category data guidance is the place to start when those rules apply.

Before collecting that information, establish the applicable legal basis, any additional condition required for sensitive information, and the privacy information you need to provide. Requirements differ by jurisdiction. A checkbox copied from another event isn't a privacy plan, and consent isn't automatically the right answer in every situation.

In practical terms, say why you need the information, who will receive it, how someone can correct it and how long you'll keep it. Collect enough for the event arrangement. Don't ask for test results, detailed treatment history or a doctor's letter just to organise lunch.

Limit access to the people doing the job. The catering lead may need the full requirement and a way to clarify it. A server may need a meal reference and the agreed handoff instruction. Your photographers, sponsors and general volunteer chat don't need a named allergy list.

Use an attendee reference in service records where that works, but remember that a reference can still identify someone when your team can link it back to their booking. Keep both versions under the same access discipline. Hiding a name isn't a reason to circulate the file widely.

Agree the sharing method with the caterer before the list grows. Use an access-controlled working record, remove obsolete copies and decide who handles updates. When you finish the event, apply the retention plan, while preserving any records you have a legitimate requirement to retain.

Make privacy part of delivery, too. A large badge saying "severe allergy" can announce personal information to everyone in the room. An agreed meal reference and a discreet conversation are usually a more considerate way to connect someone to their food.

Choose a caterer who can explain the process

Don't choose catering on the strength of a "we accommodate everyone" sentence. Ask the supplier to walk you through an actual request. Who reviews it? What records do they check? Who prepares the meal, who checks it and who answers questions at the event?

You want written answers before confirming the menu. Ask about ingredient specifications, preparation arrangements, storage, transport, service and substitutions. Also ask what they cannot support. A clear limitation is more useful than a broad promise that nobody can explain when you get into the details.

The FSA's allergen checklist for food businesses asks managers to identify overall responsibility and have a responsible person available during each shift. Use that as a starting point for your supplier discussion. It gives you a concrete question to ask about every meal service.

An event isn't always one kitchen. The venue may provide lunch, a sponsor may distribute snacks and a separate vendor may run coffee. Map every food and drink offer, including backstage catering and paid upgrades, then identify who controls each one.

Put the agreed responsibilities into the booking documents. Record the menu review date, request deadline, how attendee requirements will be shared, who confirms individual arrangements and what happens if an ingredient changes. Include the cost of any additional preparation or service in the quote.

Ask the venue about outside food and sealed alternatives before promising them. An attendee may need to bring their own food when the catering offer can't meet their requirement. Agree a practical arrangement, including storage or reheating only where the venue can actually provide it safely.

If a supplier won't give you a clear answer, don't fill in the gap yourself. Find a supplier who can, change the meal offer or tell the attendee the limitation. You control the event promise even when you don't control the kitchen.

Build the menu around confirmed requirements

Once requests arrive, review them together with the caterer. Don't turn every checkbox into an extra meal order. One person may have asked for a vegetarian meal and reported an allergy, so those two entries still refer to one attendee.

A meal matrix helps. Give each attendee one row for each meal they're attending, with their requirement, the supplier's response, the agreed meal, the service route and the confirmation status. Keep unanswered questions visible. "Awaiting caterer" and "confirmed" should look different at a glance.

Ask the supplier to propose a manageable menu that covers the requirements they can meet. That may reduce unnecessary variation, but don't assume one alternative suits everybody. A plant-based main containing sesame doesn't solve a sesame allergy. A gluten-free option doesn't tell you whether it meets someone's other requirements.

For religious dietary requests, confirm the actual need with the attendee and supplier. Some attendees may accept a vegetarian alternative; others may require certified sourcing or particular preparation conditions. Respect the answer rather than substituting your own interpretation of the label.

Review the full meal. Check bread, sauces, dressings, garnishes, desserts and drinks as well as the main dish. A correctly planned plate can still go wrong when someone adds a finishing sauce from another recipe or replaces the dessert without reviewing the request.

Then review service. Will the meal be plated individually, held in a separate area or collected from a named person? Can the attendee get it within the lunch break? Is the collection point accessible? Coordinate that last question with your wider event accessibility checklist.

Confirm individual arrangements before you make general claims about the menu. Your ticket page can say that dietary requests are reviewed by the catering team. It should only make a specific free-from promise when the supplier has established that the promise is justified.

Check local allergen rules instead of copying a foreign template

An allergen list downloaded from another country can leave gaps. Use the rules for the place where the food is supplied and check the requirements for the actual service format. Packaged food, a staffed buffet and an independently operated stall may need different information arrangements.

In the US, the FDA identifies nine major food allergens under federal law, including sesame. Its packaged-food rules aren't a complete checklist for every event catering situation. Check the relevant state or local food authority for the restaurant, temporary food operation or service you are arranging. The FDA's food allergy guidance explains the federal scope.

For events under the FSA's guidance in England, Wales and Northern Ireland, food businesses must provide information about fourteen specified allergens used as ingredients. The guidance also distinguishes buffet items individually. Scotland has its own food authority, so check Food Standards Scotland for a Scottish event. Start with the FSA's allergen information guidance for the jurisdictions it covers.

In Australia and New Zealand, Food Standards Australia New Zealand sets out required allergen declarations under the Food Standards Code. For food without packaging or requiring no label, the information must be displayed with the food or available on request from the supplier. FSANZ's allergen labelling guidance explains the current requirements.

Check boxed lunches separately. The FSA has specific guidance for event caterers supplying food prepacked for direct sale. Ask your supplier which category its food falls into and what labelling that category requires.

Don't treat any statutory list as a list of every ingredient an attendee could react to. Record the actual request, including ingredients outside the local declaration list, and ask the supplier to assess it. A legally complete label may still not answer that person's question.

Check the finished information in the format attendees will use. A menu hidden behind a login isn't much help in a queue. A QR code can support access, but have a usable route for someone without a working phone or reliable signal.

Protect the plan through preparation and service

The caterer needs controls for unintended transfer of allergens between foods, often called cross-contact. As the event operator, your job is to confirm those controls with the supplier and make sure your event layout doesn't undermine them. You shouldn't improvise a kitchen procedure from a blog post.

Food Allergy Research & Education explains that cooking does not eliminate the risk of an allergic reaction from cross-contact. Removing a topping or heating the food again is not a substitute for the supplier's controls. Share FARE's cross-contact guidance with the team as a reference, alongside their catering training.

Ask about shared equipment, preparation areas, storage and the route to service. Then walk the serving area together. Can food move between stations? Can guests swap utensils? Can a runner collect a meal without knowing which order it belongs to? Those are event delivery questions you can help resolve.

Choose the service format with that discussion in mind. A self-service buffet gives guests more freedom to move utensils and food between dishes. Where the supplier's assessment requires a separate meal, arrange a controlled handoff and explain it to the attendee before they join the main queue.

Protect reserved meals from general demand. If the agreed meal is sitting beside the buffet with no collection control, another guest may take it because it looks good. Keep it with the responsible service team until the intended attendee arrives, following the supplier's holding instructions.

Make recipe changes a stop-and-check moment. If a delivery arrives with a different product, the kitchen reviews it before using it for an agreed meal. If that review changes the arrangement, update the attendee and service instructions. A familiar product name isn't proof that the ingredients are unchanged.

Tell front-of-house staff which questions they can answer from the current records and which go to the catering lead. Give them an easy way to get that person. The sentence "I need to check that with our catering lead" is useful when the next step actually happens.

Run a short practice before doors. Ask a staff member to act as an attendee collecting an agreed meal, then follow the request through. If the team has to search several chats or find someone who has already left the venue, fix the process before lunch.

Tell attendees exactly what has been agreed

People need an answer they can plan around. "We've noted your requirements" confirms that you received a message. It doesn't tell them whether they can eat the included lunch or what they need to do when they arrive.

Once the caterer has reviewed the request, send the agreed arrangement in plain words. Identify the event, meal, relevant requirement, collection location and contact person. Explain any limitation accurately. Ask the attendee to contact you if the summary doesn't match what they told you.

A practical confirmation could say, "Our caterer has reviewed your request to avoid egg for Saturday lunch. Your agreed meal will be held at the staffed collection desk beside the dining entrance. Ask for the catering lead and give your attendee reference. Please contact us before the event if your requirements change."

Only send that wording when it describes a real, reviewed arrangement. Add the caterer's specific preparation information or limitations where relevant. Don't insert a generic "safe for all allergies" line, and don't turn a caveat into a reassurance stronger than the supplier can support.

If the supplier can't meet the requirement, say so early. Explain what the event can offer and discuss alternatives, such as permission to bring food or a different meal arrangement. Where a paid inclusion can't be supplied, review your terms and applicable consumer obligations rather than expecting the buyer to absorb the problem.

Use general pre-event messages for shared instructions. Tell everyone where food will be served, how to ask a question and where confirmed meals will be collected. Send individual requirements privately. Nobody needs a public email listing which guests have which conditions.

Give attendees one contact route for changes and keep it monitored. An inbox nobody checks during build won't catch a corrected request. Tell the catering lead how they will receive late updates, and confirm receipt when a change affects a meal already in production.

Work through a paid conference example

Imagine you're organising a paid conference for 240 attendees with lunch included. These figures are a planning example, not survey data. The supplier can provide a standard lunch, a vegetarian choice and individually reviewed meals where its preparation arrangements support the request.

Your initial form returns 28 vegetarian choices and nine attendees reporting allergy-related requirements. Five of those nine also chose vegetarian meals. You therefore have 32 people needing a meal choice or individual review outside the standard-only group, not 37. Adding every response category would double-count five people.

That doesn't mean you can order 32 identical alternative meals. The caterer reviews the nine individual requests and checks the vegetarian recipe against the five overlapping requirements. Your final order comes from confirmed meal assignments, while any unresolved request stays open for a separate response.

Suppose the quote includes $960 for preparation and service arrangements beyond the standard lunch. That's an illustrative cost of $4 across the 240 tickets. You can plan for it in your event budget before setting the ticket offer, instead of treating it as a surprise during build.

Choose a request deadline that fits the supplier's procurement schedule. After the deadline, the catering lead confirms the reviewed meal list and flags outstanding questions. Your event lead checks that each attendee has received an answer and that the collection route appears in the service brief.

During setup, you discover that the planned collection desk shares a queue with general lunch. You move the collection point to an accessible staffed location and update the attendee instructions. The meal hasn't changed, but the delivery arrangement has. That's a change worth communicating.

On the day, a runner reports that a reserved meal has no identifying reference. The team holds it and checks with the catering lead rather than matching it by appearance. The process has given them a useful action at the point where a guess would be tempting.

Plan for walk-ups, transfers and independent food vendors

Late changes don't disappear because the spreadsheet is finished. Ticket transfers, substitutions in group bookings and walk-up buyers can all bring requirements you haven't reviewed. Give your support and door teams a route to the catering lead rather than leaving them to promise a meal.

For a transferred ticket, ask the new attendee to submit their own requirement. Don't copy the previous holder's allergy record onto the new person. Check what happens to the reserved meal and whether the supplier can revise the arrangement before confirming anything.

For a last-minute buyer, describe what's available and what still needs review. If food is a paid extra, avoid selling a suitable-meal promise until the supplier confirms it. Staff should be able to explain the limitation without making the person discuss their health in front of the queue.

A festival with independent stalls needs a different setup from a plated conference lunch. Each vendor controls its ingredients and preparation, so direct food-specific questions to the responsible vendor. Your event team still controls vendor selection, site information, escalation contacts and the promises on the event page.

Require a named contact for each stall and check how attendees can obtain current ingredient and allergen information. Build that into vendor onboarding before the event. Then inspect the service arrangements on site, including whether staff know who can answer a question during a busy period.

Include sponsor samples, bars and coffee service in the same review. A free snack is still food. Don't let a sponsor introduce an unreviewed sample stand after you've briefed every other food supplier. Give them the same information and change requirements that apply to the rest of the event.

Have a practical response when no suitable option is available. Show the attendee the accurate options and agreed alternatives. Don't send them around the site asking every stall the same question while your own team repeats, "Someone should be able to help."

Prepare for an emergency before you need the plan

Food allergy management needs an emergency route even when the catering arrangements are well planned. The NHS describes anaphylaxis as a life-threatening allergic reaction that can develop quickly and needs emergency action. Its anaphylaxis guidance covers signs such as breathing difficulty, throat swelling and fainting, and explains the UK response.

Work with your qualified medical provider on the response for your location. Staff should know how to call local emergency services immediately for suspected anaphylaxis, summon the medical team and bring responders to the person. Don't wait to find the event medical lead before making the emergency call. In the UK, suspected anaphylaxis requires calling 999. Don't export that number to an event in another country.

Agree the clinical response, training and any medication arrangements with the medical provider and relevant local rules. Adrenaline auto-injectors are part of established anaphylaxis guidance, but purchase, storage and administration arrangements belong in a professionally prepared plan. A general event briefing shouldn't pretend to replace that training.

Make the route practical. The radio call needs an exact location, someone needs to meet arriving responders, and the access path needs to remain clear. Ask how the plan works during the busiest meal break, when your first aid point and dining area may be separated by crowds.

Connect these arrangements to your wider event risk assessment. Record the responsible people, communication route and access arrangements so the medical response isn't stranded in a separate catering document.

After immediate care has been arranged, preserve relevant food, packaging and service records through the supplier's incident procedure. Record what happened without guessing at the cause. Follow the appropriate reporting requirements and let qualified people investigate before you make public claims about the incident.

Review delivery before the next event

After the event, compare confirmed arrangements with what actually happened. Were meals ready when promised? Could attendees find the collection point? Did staff have current information? Which questions required several handoffs, and where did a change reach the wrong person?

Ask for private feedback on the arrangement rather than another medical questionnaire. "Did you receive the meal we confirmed, and was it easy to collect?" gives you something you can act on. If an attendee reports a safety concern, use the incident process rather than treating it as an ordinary satisfaction score.

Review cost and waste with the caterer. Separate unused meals, extra labour, late changes and service problems so you can see what to improve. Don't cut a necessary preparation control because the final bill is higher than expected. Change planning, supplier choice or the ticket offer instead.

Keep the useful learning for your next edition, then apply your retention rules to the personal records. A better service brief doesn't need an indefinite archive of named health information. Check with repeat attendees again rather than assuming their requirements are unchanged.

The job is complete when an attendee has an accurate answer and your team can deliver the agreed arrangement. Ask early, get the caterer to review the actual requirement, confirm the meal and rehearse the handoff. That's how you turn a form response into food people can make informed decisions about at your event.