How to collect dietary restrictions for a work party without a reply-all thread

The pattern is always the same. Somebody sends an email asking people to reply with any dietary restrictions. Thirty replies come back. Four of them are “none,” six are “I’ll eat anything!”, three are attached to a completely different conversation, and one says “same as last year” from a person whose last year you have no record of.

Then the caterer asks for a breakdown, and you spend an evening reading email.

There is a better way to do this, and it takes about ten minutes to set up.

Ask with the RSVP, not after it

The single most useful change: ask the dietary question at the same moment you ask people whether they are coming.

Two reasons. First, you get an answer from everybody, because they are already in the middle of answering you. A separate ask a week later reaches maybe half the room. Second, the answer arrives attached to the person’s name and their yes-or-no, so you never have to reconcile two lists.

If you only change one thing about how you run this, change this.

What to actually ask

Four questions cover almost everything a caterer needs:

1. Are you coming? Yes, no, or bringing a guest.
2. Do you have any dietary needs we should tell the caterer about? A short text box, not a dropdown.
3. Is any of that an allergy? Yes or no, with a box for details.
4. Anything else the venue should know? Mobility, accessibility, a quiet place to step out to.

Resist the urge to build a long checklist of every diet. A dropdown with twelve options misses the thirteenth, and someone will pick the closest wrong answer rather than typing what they actually need.

Wording that gets a useful answer

Small changes in wording make a real difference in what comes back.

Say who sees it. “This goes to the caterer” gets more honest answers than an unexplained question. People are reasonably cautious about telling their employer about a medical condition.

Separate cannot from would rather not. Both matter to a caterer, but they matter differently. “What can you not eat?” and “Anything you would prefer to avoid?” are two different questions, and asking them separately stops a preference from being treated as an allergy and an allergy from being treated as a preference.

Do not ask why. You do not need the reason, and asking for it makes people uncomfortable enough that some of them will not answer at all.

Give an example. “For example: vegetarian, vegan, gluten, dairy, shellfish, halal, kosher” prompts a specific answer rather than “nothing major.”

Allergies are not a preference, and should not be handled like one

Keep the allergy answers separate from the rest of the list, and give them to the venue as their own line rather than buried in a total.

A caterer who is told “four vegetarians, two gluten, one nut allergy” will treat those three things differently — the nut allergy is a kitchen procedure, not a menu choice. If you hand over a single blended list, that distinction gets lost at exactly the point where it matters.

If someone tells you about a severe allergy, tell the venue directly and ask them to confirm back to you what they are doing about it. Do not relay it once in an email and assume.

What the caterer needs, and when

Ask the venue two questions at the time you book: what do you need from us, and when do you need it by. The answers are usually:

• A final headcount
• A breakdown of dietary needs by count, not by name
• Any allergies, flagged separately
• All of it somewhere between three and fourteen days out

Set your own RSVP deadline at least a week before the venue’s deadline. That week is the buffer where you chase the six people who have not replied, and it is the difference between a calm Tuesday and a bad Friday.

Send the counts as counts. The caterer needs to know there are four vegetarians; they do not need to know which four. Which brings us to the next part.

Keep it private

Dietary information is health-adjacent, and some of it is genuinely medical. Handle it accordingly:

• Do not post a list of names and conditions anywhere the whole company can see.
• Send counts to the caterer, not the raw responses.
• Do not repeat what someone told you to anyone who does not need it to do their job that night.
• Keep it for this event. Do not build a permanent file of who eats what.

This is not a legal argument, it is a basic one: people told you something private because you asked them to.

On the night

Two things make the difference between a good plan and a good party.

Label the food. Small cards on each dish naming the main allergens do more than any amount of advance planning, because they let people check for themselves instead of finding a server and asking.

Tell one staff member. Somebody from your side should know which plates were made for whom and be findable. A vegetarian meal that arrives at the wrong table and never gets sorted out is the thing people remember about the night.

Turning answers into something you can send

If you collected the answers with the RSVP, this part takes about a minute. Sort by the dietary field, count the groups, list the allergies separately, and send the venue a short message:

62 attending. 7 vegetarian, 3 vegan, 4 gluten-free, 2 halal. One severe nut allergy — please confirm how you are handling it.

That is the whole deliverable. Everything before it exists to make that message accurate.

Doing it in one step instead of three

Staff Party asks the dietary question as part of the RSVP, keeps the answers attached to the person, and gives you the counts without a spreadsheet in between. The same list runs the door on the night.

It is the same principle as the rest of the party: ask once, in one place. The holiday party checklist walks through where this fits in the wider timeline, and what else Staff Party does covers the rest.