How to Collect and Communicate Dietary Restrictions for 200 People Without Losing Your Mind

I almost poisoned someone at my third event. Not literally, but close enough that I changed everything about how I collect dietary restrictions. A guest had a tree-nut allergy. She had mentioned it in the registration form. The form had a single open-text field that said “any dietary needs?” She typed “nut allergy.” My caterer received a spreadsheet with 180 rows. Hers was row 147. The salad dressing had pecans.

She caught it herself. But I didn’t sleep well that week, and I rebuilt the entire intake system the next morning.

Here is what actually works for groups above 80 people.

The three-field method

One open-text field does not work. It produces entries like “trying to eat healthy,” “vegetarian but I eat fish sometimes,” and “no nuts (serious).” Your caterer cannot act on that without a phone call for every ambiguous row.

Replace the single field with three distinct inputs:

Field 1: Dietary category (dropdown, pick one)

• No restrictions
• Vegetarian
• Vegan
• Gluten-free
• Kosher
• Halal
• Other (triggers field 3)

Field 2: Severity / allergy (checkbox, optional)

• This is a medically serious allergy (anaphylactic risk)

Field 3: Specific avoidance (text, 50 characters max) Only shown when field 1 is not “No restrictions.” Forces specificity. “No pecans, walnuts, or almonds” is actionable. “Trying to avoid processed foods” is not, and the 50-character limit discourages it.

The severity checkbox is the most important addition. It lets your caterer flag the 8 guests who need a dedicated plate from a separate prep station versus the 40 who prefer vegetarian but can eat around chicken if needed. Those are completely different operational problems.

Collection timing and format

Send the dietary intake form as a standalone step, not buried inside a 12-field registration survey. If it’s question 9 of 12, completion rates drop below 60%. Sent on its own, with a subject line like “One question before the event,” completion rates run 85-92% in my experience.

Send it 10-14 days before the event. Not 6 weeks out (people forget) and not 3 days out (your caterer can’t adjust).

Set a hard deadline of 7 days before the event with a single reminder at day 5. After the deadline, late submissions go to a “best-effort” list. You tell latecomers: we’ll do our best, but we can’t guarantee a separate plate if you didn’t submit before Friday. That language is honest and it stops the flood of “I forgot to mention” requests on the morning of the event.

What to send your caterer

Caterers don’t want your raw registration spreadsheet. They want a structured summary they can hand to a prep cook.

Send two documents:

Document 1: Dietary summary table

Category	Count	Notes
No restrictions	143	Standard plate
Vegetarian	22	No meat, fish OK for 9 of 22
Vegan	8	No dairy or eggs
Gluten-free	11	3 marked as serious allergy
Kosher	4	Requires kosher-certified kitchen or sealed tray
Halal	6	No pork products in any course
Other/complex	6	See detail list

Document 2: Individual flag list

Only include guests with a serious allergy or a complex restriction. 6-15 rows for a 200-person event is typical. Each row: name, table assignment or badge number, exact restriction, severity (allergy vs preference), specific avoidance text.

Your caterer needs both. The summary table drives prep quantities. The individual flag list drives day-of plate tracking.

Day-of communication at the venue

Send the individual flag list to three people: the catering manager, the floor captain, and whoever is running your registration table. The registration person needs it because guests sometimes stop at check-in to confirm their meal accommodation. If the registration staff can’t answer confidently, that guest spends the next 20 minutes anxious.

Plates for guests with serious allergies should be marked before service. I use colored toothpicks: one color for tree-nut allergy, another for shellfish. I tell the catering manager what each color means before service starts. It’s low-tech and it works.

During plated service, have one person on your team responsible only for allergy plates. Their job is to stand near the kitchen pass and confirm the correct plates reach the correct seats. At a 200-person event, this is a 45-minute job. It is worth it.

What to do when someone submits after the deadline

It happens every time. Someone registers on day three, doesn’t submit a dietary restriction, then emails you at 8pm the night before to say they’re celiac.

My protocol: I add them to the caterer’s individual flag list immediately, even if it’s 10pm. I text the catering manager rather than email. I tell the guest I’ve flagged it but cannot guarantee a dedicated plate; they should plan to verify directly with the server. That’s honest. And I’ve never had a caterer refuse to accommodate a late-night flag when I’ve communicated it clearly and calmly.

What I don’t do is absorb the anxiety on their behalf. If they submitted after the deadline, the responsibility shifted. Be clear about that in the original deadline language.

The mistake I see planners make most often

Collecting restrictions and then sending a single spreadsheet dump to the caterer. The caterer opens a 200-row Excel file, sees column G says “vegan” for some guests, and tries to tally it manually. Errors happen.

Your caterer’s prep kitchen operates on count-and-label logic. Give them counts, not raw data. Their job is to produce 8 vegan plates and flag them correctly. Your job is to tell them it’s exactly 8, which 8, and which of those 8 are serious. Do that clearly and the kitchen can execute.

You can find conference centers and hotels and resorts that offer pre-formatted dietary intake forms as part of their booking documentation. Some banquet halls include a catering intake sheet in their BEO packet. Ask for it during the site visit. If they have it, it’s one less document to build from scratch.

What the caterer actually needs to know

Before every event, I get on a 15-minute call with the catering manager specifically to review dietary restrictions. Not during the general pre-event call. A separate call, just for this.

I walk through the summary table line by line. I confirm the separate prep station for serious allergies. I confirm which dishes contain common allergens. I confirm that servers will announce the dish components during service, not just set down the plate.

That 15-minute call has prevented more problems than anything else in this system. Read more about how to run a pre-event vendor briefing and how to brief a caterer for a corporate event before you build yours.

How many attendees are you collecting for, and what’s your current intake method? If you’re still using a single text field above 80 people, the three-field system is worth the 20 minutes it takes to rebuild the form.