Handling Allergies and Dietary Needs: Start at the Booking

Around 30% of restaurant patrons self-identify as having a food allergy or sensitivity. That is not a niche group. That is nearly one in three guests walking through your door.

Here is the statistic that should concern every restaurant operator: 53.9% of food allergy reactions at US restaurants occurred despite the restaurant staff being notified about the allergy in advance.

The problem is not awareness. It is the gap between when a guest communicates their allergy and when that information reaches the kitchen. Collecting dietary requirements at booking time -- before the guest arrives, before the kitchen starts prep, before the server meets the table -- closes that gap.

Why the booking is the right moment

The current default at most restaurants is discovery at the table. The guest sits down, mentions an allergy to the server, the server relays it to the kitchen, and the kitchen adapts on the fly. This works often enough to feel reliable. But the failure rate is unacceptable when the consequence is anaphylaxis.

Approximately 25% of anaphylactic food reactions occur while dining at restaurants. In the UK, 59% of food-related anaphylaxis hospitalisations are attributed to catering establishments.

Collecting dietary information at booking time changes the dynamic in three ways:

The kitchen prepares in advance

When the kitchen knows about a nut allergy before service starts, cross-contamination protocols activate during prep, not during the rush. Alternative ingredients are sourced. Specific utensils are set aside. There is no scrambling at 7:30 PM when the guest arrives and the kitchen is already working at full capacity.

The server leads the conversation

Instead of "Do you have any allergies?" at the table -- which puts the burden on the guest -- the server can open with: "I see we have a gluten-free requirement noted for your party. Our chef has prepared several options that are safe for you. Here is what I would recommend tonight."

That shift from accommodation to anticipation is the difference between adequate service and memorable service.

The guest relaxes

Guests with food allergies dread the restaurant conversation. They have had bad experiences. They have been made to feel like a burden. Some research indicates that more than 15% of food-allergy families avoid restaurants entirely.

When their needs are already known and prepared for, the anxiety dissolves. They feel cared for. That feeling creates loyalty that is difficult to replicate through any other means.

What to collect

The booking form should include a simple, open-ended field: "Any allergies or dietary requirements?"

Let guests type a free-text response. This is important. Do not force them into checkboxes that might not cover their specific need. Common responses include:

• Allergies: Nuts, shellfish, gluten, dairy, soy, sesame, eggs
• Intolerances: Lactose, gluten sensitivity, FODMAP
• Lifestyle choices: Vegetarian, vegan, pescatarian
• Religious requirements: Halal, kosher, no pork, no alcohol in cooking
• Medical diets: Low-sodium, diabetic-friendly

The free-text approach captures edge cases that checkboxes miss: "My daughter is allergic to kiwi and strawberries but can eat other fruits" or "Celiac disease -- even trace amounts of gluten will make me ill."

The distinction between severity levels matters enormously for the kitchen. "Gluten-free" might mean celiac disease -- where trace contamination causes serious illness -- or a lifestyle preference where the kitchen has more flexibility. When the stakes are high, the booking note gives the team time to clarify before the guest arrives.

The information flow that prevents failures

A study in the journal Frontiers in Allergy found that 74% of all allergy-related food reactions involve non-pre-packaged food -- the kind restaurants serve.

The failure point is rarely that nobody knew about the allergy. The failure point is that the information did not reach the right person at the right time. The flow should be automatic:

1. Guest enters dietary note during booking -- captured in the reservation record
2. Information attaches to the reservation -- visible on the dashboard, timeline, and reservation details
3. Kitchen sees it during prep -- in a pre-service briefing or prep sheet
4. Server reviews it before greeting the table -- ready to discuss menu options
5. Guest confirms upon arrival -- catching changes or errors

At no point should someone have to remember or manually transfer this information. Manual handoffs forget. Automated ones do not.

The confirmation check

Even with advance notice, always confirm dietary requirements at the table:

"I see we have a nut allergy noted for your party -- is that still correct? Is it for you specifically, or someone else in the group?"

This confirmation catches errors (maybe the allergic person is not dining tonight), updates changes (dietary needs evolve), and reassures the guest that you read their notes and take them seriously. It also clarifies severity: "Is this a preference or a medical allergy?" helps the kitchen calibrate their response.

Guest profiles that remember

The real power of digital reservation systems is persistent guest profiles. When a guest books for the second time, the system already has their dietary information on file.

The guest does not re-enter their allergies. The server greets them with "Welcome back -- we have your nut allergy noted, as always." The kitchen recognises a returning guest with specific needs. Over time, you build a comprehensive picture of each guest's requirements.

For guests with severe allergies, this continuity is deeply reassuring. They have found a safe place. They do not have to re-explain, re-justify, or re-worry. The restaurant knows them.

Where restaurants get it wrong

Untrained staff

Only 33% of restaurants report specific food allergy training, even though 90% report general food hygiene training.

Every staff member who touches food should understand allergy protocols. That includes seasonal staff, new hires, kitchen assistants, and bartenders. One uninformed person in the chain can undo all the preparation. Train on cross-contamination in practice, which dishes contain which allergens, how to communicate with the kitchen, when to escalate to a manager, and what to do during a reaction.

Dangerous misconceptions

Research has found that 38% of restaurant staff believe an individual experiencing an allergic reaction should drink water to dilute the allergen. 23% think consuming a small amount of an allergen is safe. 21% believe removing an allergen from a finished dish makes it safe to eat.

These are not minor misunderstandings. They are dangerous. Regular training that addresses these specific misconceptions is not optional -- it is a safety requirement.

Over-promising

If you cannot accommodate an allergy safely, say so at booking time. "We cannot guarantee a completely nut-free environment due to our kitchen setup" is honest and responsible. It is far better to decline a reservation than to accept one and put someone's health at risk.

The opportunity most restaurants miss

Some restaurants see dietary requirements as problems to manage. The ones that prosper see them as opportunities to build loyalty that competitors cannot match.

Disney's theme parks tracked their allergy-friendly meal service as it grew from 52,000 meals at Walt Disney World in 2005 to 625,000 across both parks by 2012. That growth did not come from reluctant accommodation. It came from making food-allergic families feel genuinely welcome.

A guest with a severe allergy who has a safe, enjoyable dining experience at your restaurant tells every person they know with a food allergy. Word-of-mouth within allergy communities is intense and specific. That kind of recommendation is more valuable than any advertising.

A genuinely excellent vegan menu attracts vegan diners and their non-vegan friends. Gluten-free bread that tastes good wins lifetime loyalty from celiac guests. Halal or kosher certification opens entire customer segments. Every well-handled dietary requirement is marketing through service.

How Nine Tables handles dietary information

Nine Tables includes a dedicated notes field in the booking widget where guests describe their dietary needs in their own words. That information attaches to the reservation and appears everywhere it needs to: the booking list, the visual timeline, the reservation details that servers pull up on their device, and the guest profile that persists across visits.

When a returning guest books, their dietary information is already on file. The system does not ask them to re-enter it. The information flows from booking to kitchen to server without anyone needing to remember, relay, or transcribe.

Start at the booking

The economics are clear: one in three guests has some form of dietary consideration. The safety stakes are high: allergic reactions happen at restaurants despite advance notice, and the failure point is almost always information that did not reach the right person.

Capturing dietary needs at the moment of booking -- not at the table, not by memory, not through verbal handoffs -- is the simplest change a restaurant can make to improve both safety and service. The guest tells you once, in their own words, before they arrive. From that point forward, everyone who needs to know does know.

That is how you handle dietary requirements. Not as an afterthought. As a starting point.