How to Manage Dietary Requirements at Corporate Events

Updated 20/07/2026

Dietary requirements are a normal part of planning international corporate events. They may relate to food allergies, coeliac disease, intolerances, medical needs, religion, ethical choices or personal preferences. Although these requirements are often collected in one registration field, they do not all create the same level or type of risk.

A safe and inclusive catering process depends on accurate information, clear responsibility and consistent communication from the participant to the organiser and from the organiser to the hotel, caterer, restaurant and service team. A list of dietary labels is not enough when recipes, preparation methods, cross-contact and service procedures remain unclear.

This guide explains how to collect, communicate and manage dietary requirements across meetings, conferences, incentive programmes, company retreats and gala dinners. It focuses on the planning process rather than duplicating the commercial event-management services described elsewhere on the Meridional Events website.

What Are Dietary Requirements at Corporate Events?

Dietary requirements are the food and drink conditions a participant needs or chooses to follow during an event.

They may arise from:

• food allergies;
• coeliac disease;
• food intolerances;
• other medical requirements;
• religious observance;
• vegetarian or vegan choices;
• ethical or cultural preferences;
• pregnancy-related guidance;
• personal food preferences.

These categories should not be treated as interchangeable. A severe allergy may require strict control of ingredients, preparation and service. A religious requirement may depend on certification, ingredients and preparation methods. A personal preference may be accommodated without the same food-safety implications.

The organiser does not need to diagnose or judge the requirement. The role is to collect enough practical information, transmit it accurately and confirm that the catering provider understands what it can safely deliver.

For international groups, terminology can create confusion. Words such as allergy, intolerance, gluten-free, halal and vegetarian may be interpreted differently by participants and suppliers. The registration and catering process should therefore move beyond one-word labels wherever clarification is required.

Food Allergies, Intolerances and Preferences Are Not the Same

A food allergy involves an immune-system reaction and can sometimes be severe. An intolerance has a different mechanism and may cause significant symptoms without being an allergy. A preference reflects what a person chooses to eat rather than a diagnosed medical need.

From an event-planning perspective, the distinction matters because the preparation and service controls may be different.

Food Allergies

Participants should identify the food or ingredient involved and any relevant risk information they have been advised to communicate.

The organiser should not make independent medical assumptions about the severity of an allergy or decide that a small quantity is acceptable.

Food Intolerances

Intolerances can still have a serious effect on the participant’s health and ability to attend the event. They should not be dismissed as preferences.

However, the participant may tolerate certain ingredients, quantities or preparation methods. Clarification should come from the participant, not from speculation by the event team.

Preferences and Lifestyle Choices

Vegetarian, vegan and other preferences should be recorded and respected, but they should not be presented to the kitchen as allergies unless the participant has specifically identified an allergy.

Incorrectly labelling every preference as a severe allergy can make kitchen communication less reliable and reduce attention to genuinely high-risk requirements.

Requirements Outside the Regulated Allergen List

European food-information rules identify 14 allergens that require declaration when used as ingredients. Participants can nevertheless be allergic or sensitive to other foods.

The registration form should therefore allow free-text information rather than offering only a fixed list of common allergens.

How Should Dietary Information Be Collected?

Dietary information should be collected early enough for menus, suppliers and service procedures to be reviewed before confirmation.

Use Structured Questions

A useful form can separate:

• food allergies;
• coeliac or other medical dietary requirements;
• religious requirements;
• vegetarian or vegan choices;
• other requirements requiring explanation.

Participants should be able to add details in their own words.

Ask Practical Follow-Up Questions

Depending on the answer, useful clarification may include:

• Which ingredient or food must be avoided?
• Is cross-contact a concern?
• Does the participant require certified food or preparation?
• Are there specific ingredients that are acceptable or unacceptable?
• Will the participant attend every meal?
• Is a companion or personal assistant included in the same requirement?

The organiser should not ask for a full medical history. Only information necessary to plan and serve the food should be collected.

Set a Deadline

Provide a clear deadline linked to menu confirmation and supplier briefing. Explain that late information will still be reviewed but may reduce the available options.

Confirm What Has Been Recorded

Allow participants to review or update their details. Spelling errors, incomplete entries and changes in attendance can otherwise remain unnoticed.

Do Not Rely on Memory or Informal Messages

Dietary requirements shared through calls, emails and messaging applications should be transferred into one controlled record.

The current version should show the participant, requirement, meals attended, agreed solution and any outstanding confirmation.

Manage Privacy and Data Sharing Carefully

Dietary information may reveal health, religious or personal information. It should be handled only by the people who need it for event delivery.

Explain the Purpose

Participants should understand that relevant information may be shared with the hotel, caterer, restaurant or another supplier so the requested meal can be prepared and served.

Share the Minimum Necessary Information

The kitchen generally needs to know the requirement and meal arrangement. It may not need the participant’s employer, job title or unrelated medical information.

Use Controlled Documents

Avoid leaving dietary lists on public registration desks, open banquet tables or shared screens.

Operational lists should be stored and circulated through an agreed process, with obsolete versions removed.

Do Not Publicly Identify Participants

A participant should not be asked to announce an allergy or religious requirement in front of the group.

Use discreet identification methods agreed with the supplier, such as named seating plans, coded place cards or direct confirmation by a trained server.

Agree What Happens After the Event

Dietary data should not be retained indefinitely without a reason. The organiser should follow the company’s data-management procedures and any applicable legal requirements.

How to Brief Hotels, Restaurants and Caterers

A catering provider needs more than a total such as “five gluten-free, three vegan and one nut allergy”.

Provide a Clear Dietary Matrix

The working document may include:

• participant identifier;
• exact requirement;
• meals and dates attended;
• cross-contact or certification concerns;
• agreed menu or alternative;
• service and identification method;
• status of supplier confirmation.

Ask the Supplier What It Can Safely Provide

Do not promise a participant that a requirement has been met before the kitchen has reviewed it.

The supplier should explain:

• which dishes and ingredients are suitable;
• how food will be prepared;
• how cross-contact will be managed;
• whether certified ingredients or facilities are available;
• how meals will be labelled and served;
• which limitations remain.

Check Every Catering Location

The hotel breakfast, meeting coffee break, restaurant dinner, activity lunch and gala venue may use different kitchens and procedures.

A requirement confirmed by one supplier is not automatically covered by another.

Communicate Changes to All Relevant Teams

Recipe changes, substitutions and guest-number updates should reach kitchen, banquet, front-of-house and event-management teams.

Request Written Confirmation for Complex Requirements

When a requirement involves severe allergy risk, coeliac preparation, religious certification or several excluded ingredients, obtain a clear written response rather than relying on a general verbal assurance.

Allergen Management and Cross-Contact

Allergen information identifies ingredients. It does not by itself confirm that a meal can be prepared without unintended contact with an allergen.

Cross-contact occurs when an allergen is unintentionally transferred to another food through equipment, surfaces, oil, utensils, hands, storage or service.

Ask About the Complete Process

The caterer may need to review:

• ingredient labels and supplier information;
• storage;
• preparation surfaces;
• utensils and equipment;
• shared fryers or cooking water;
• buffet utensils;
• plating and garnishes;
• service and delivery to the correct participant.

Do Not Treat an Allergen Matrix as a Complete Safety System

A matrix can show which regulated allergens are present in standard recipes. It may not account for substitutions, cross-contact or ingredients outside the regulated list.

Avoid Unsupported “Allergen-Free” Claims

Absolute language should be used only when the supplier can support it. It may be more accurate to state which ingredient is excluded and what preparation controls are in place.

Check Shared Equipment

Shared fryers, grills, toasters, serving utensils and preparation areas can affect suitability.

Brief Service Staff

The server should know which meal is intended for which guest and should not add an unverified garnish, sauce, bread or replacement item.

Managing Coeliac and Gluten-Free Catering

Coeliac disease requires a strict gluten-free diet. It should not be treated as a preference or managed only by removing visible bread or pasta from a standard plate.

Clarify the Requirement

A participant requesting gluten-free food may have coeliac disease, an allergy, another medical reason or a preference. Ask for the practical requirement without challenging the participant’s explanation.

Check Ingredients and Preparation

Gluten may appear in bread, pastries, pasta, sauces, stocks, marinades, processed meats, desserts and other prepared products.

The kitchen should also assess preparation surfaces, utensils, toaster use, shared frying oil and buffet service.

Do Not Remove Ingredients from a Finished Dish

Taking croutons from a salad or removing bread from a plate does not make the dish suitable when contact has already occurred.

Provide a Complete Equivalent Meal

A gluten-free participant should not repeatedly receive a plain plate with missing courses while other guests receive the full menu.

Review Breakfast and Coffee Breaks

Hotel buffets can create particular cross-contact risks through shared toasters, serving utensils, bread displays and unlabelled pastries.

Individually arranged items or direct service may provide clearer control.

Confirm Before Using “Gluten-Free”

The supplier should understand the applicable standards and be able to explain how the meal is prepared and served.

Managing Religious Dietary Requirements

Religious dietary practices vary between individuals and communities. The organiser should avoid assuming that one standard interpretation applies to everyone.

Halal Requirements

Some participants may require certified halal meat and control of ingredients, preparation and alcohol. Others may accept vegetarian or fish options when certified meat is unavailable.

Ask the participant what is required and ask the supplier what certification or documented process it can provide. Do not describe a menu as halal solely because it contains no pork.

Kosher Requirements

Kosher requirements may involve ingredients, certification, preparation, equipment and separation of meat and dairy.

A conventional hotel kitchen cannot necessarily provide certified kosher catering. Depending on the participant’s requirements, sealed meals from an approved provider may be necessary.

Jain Requirements

Jain dietary practice can exclude meat, fish and eggs and may also exclude root vegetables or other ingredients. Requirements differ, so obtain a clear list from the participant.

Fasting and Meal Times

Religious observance may affect when participants eat as well as what they eat.

The organiser may need to consider early breakfast, meals after sunset, takeaway arrangements or access to suitable food outside the standard programme.

Alcohol in Food and Hospitality

Alcohol may appear in sauces, desserts, extracts or drinks served during receptions. Provide appropriate alternatives and clarify whether the concern applies only to beverages or also to ingredients and preparation.

Vegan, Vegetarian and Other Dietary Choices

Vegetarian and vegan meals should be planned as complete dishes rather than created by removing the principal ingredient from a standard menu.

Define the Terms

A vegetarian diet normally excludes meat and fish. A vegan diet excludes animal-derived ingredients, which may include dairy, eggs, honey, gelatine and some processing ingredients.

Individual interpretations can vary, so the caterer should work from an agreed definition and recipe.

Provide Nutritionally and Visually Comparable Meals

A plate of side vegetables is not a suitable replacement for a complete main course.

The menu should include adequate protein, substance and variety across consecutive meals.

Check Hidden Ingredients

Stocks, sauces, pastries, desserts, cheese, gelatine, dressings and garnishes may contain ingredients that are not obvious from the dish name.

Avoid Repetition

Participants attending a multi-day programme should not receive the same basic option at every hotel, restaurant and venue.

Consider Other Requirements

Low-sodium, low-sugar, texture-modified and other medical diets may require specialist review. The event organiser should transmit the requirement accurately and obtain a response from the catering provider rather than designing a medical diet independently.

Buffets, Receptions and Gala Dinners

Different service formats create different dietary risks and communication needs.

Buffets

Buffets allow choice but can create uncertainty through shared utensils, guest movement, unlabelled dishes and cross-contact.

Useful controls may include:

• clear written labels;
• separate sections;
• dedicated utensils;
• trained staff at stations;
• individually prepared meals for higher-risk requirements;
• replacement procedures when utensils are moved.

Walking Dinners and Receptions

Small dishes circulated by servers can be difficult to identify. Staff should be able to describe ingredients accurately, and participants with specific requirements may need a separate agreed selection.

Seated Gala Dinners

Assigned seating makes it easier to connect a named participant with a confirmed meal, but place cards, table plans and service lists must remain consistent.

The detailed guide to organising a corporate gala dinner explains the wider catering and service sequence.

Coffee Breaks

Biscuits, pastries, milk alternatives and savoury snacks should be labelled and protected from utensil sharing.

Off-Site Activities

Picnics, packed lunches and activity catering require the same level of review as hotel meals. Packaging should identify the intended participant and relevant ingredients.

How to Ensure the Correct Meal Reaches the Correct Participant

A safely prepared meal can still fail if it is served to the wrong person or altered after leaving the kitchen.

Agree an Identification Method

Depending on the event, this may use:

• named seating plans;
• coded place cards;
• a discreet symbol;
• direct confirmation by a designated server;
• individually labelled packaged meals.

The method should protect privacy while remaining clear to trained staff.

Use One Authoritative List

The event manager, banquet captain and kitchen should work from the same current information.

Confirm the Participant Before Service

Staff should not identify someone by appearance or assume that the person sitting in a particular seat is the intended guest without confirmation.

Protect the Meal After Preparation

Special meals may need separate covering, labelling or holding arrangements so they are not mixed with standard plates.

Do Not Add Unverified Items

Bread, sauces, garnishes, chocolates and late substitutions should not be added without checking their suitability.

Give the Participant a Contact Point

Participants should know whom to approach discreetly if the meal appears incorrect or has not arrived.

Last-Minute Changes and Food-Allergy Emergencies

Late registrations, changed menus and participant movement between tables can affect the dietary plan.

Control Last-Minute Updates

Changes should be recorded in the master list and communicated to the kitchen, service lead and event manager.

Do Not Improvise Without Confirmation

When a suitable meal is unavailable, the supplier should review ingredients and preparation before offering an alternative. A server should not assemble an unverified replacement from the buffet.

Prepare for a Suspected Reaction

The venue and event team should know how to contact emergency services and where the participant is located.

Staff should follow emergency procedures and the participant’s own instructions where appropriate. They should not diagnose the reaction or delay professional assistance while trying to investigate the ingredient.

Preserve Relevant Information

Menus, ingredient records, packaging and supplier information may be needed after a suspected reaction. They should not be discarded or altered.

Record and Review the Incident

The organiser and caterer should document what happened, which actions were taken and what should change before the next service.

An incident should not be discussed publicly with the wider group unless there is a legitimate safety reason.

Common Dietary-Requirement Mistakes to Avoid

Using One Free-Text Field Without Follow-Up

Terms such as “gluten-free” or “halal” may require clarification before a suitable meal can be confirmed.

Treating Every Requirement as a Preference

Allergies, coeliac disease and medical diets can require specific safety controls.

Treating Every Preference as a Severe Allergy

Record the information accurately so the kitchen can prioritise risks appropriately.

Promising Before the Caterer Confirms

The organiser should not guarantee a certified or allergen-controlled meal without supplier verification.

Assuming One Confirmation Covers the Whole Event

Every hotel, restaurant, venue and activity caterer needs the relevant information.

Relying Only on Allergen Icons

Icons do not explain cross-contact, substitutions or ingredients outside the regulated list.

Serving an Inferior Meal

Participants should not repeatedly receive incomplete dishes or the same basic option throughout a multi-day event.

Publicly Identifying the Participant

Use discreet service procedures and limit personal information to staff who need it.

Failing to Brief Front-of-House Staff

A correct kitchen plan can be undermined by incorrect service, garnishes or substitutions.

Ignoring Drinks and Snacks

Allergens and religious restrictions can also affect coffee breaks, minibar products, cocktails, desserts and late-night food.

Managing Dietary Requirements at Corporate Events in Spain

Food businesses in the European Union must provide information about the 14 regulated allergens when they are used as ingredients, including for non-prepacked food served in restaurants and catering environments. Event organisers should still verify how each provider supplies that information and manages preparation and service.

For international events in Spain, dietary planning may involve several independent suppliers:

• hotel breakfast and meeting catering;
• restaurants;
• gala-dinner caterers;
• activity lunches;
• packed meals;
• reception and bar service.

Meridional Events creates, books and manages complete corporate programmes for international companies and agencies in Spain. Dietary information can be coordinated across the contracted hotels, venues, caterers and restaurants, but each supplier must confirm what it can safely and accurately provide.

Dietary requirements also form part of wider inclusive planning. The guide to accessible corporate events covers registration, venues, communication and participant access in more detail.

For information about Meridional Events’ wider operational service, visit the page on corporate event management in Spain.

Tell us about the event, participant number, dates, destination and known dietary requirements. Early, precise and confidential information gives each catering provider more time to verify ingredients, preparation and service arrangements.