TeamRally TeamRally
Join the waitlist
← All articles
TeamRally · 4 min read

How to Collect Dietary Preferences from Employees (Without Form Fatigue)

How to collect dietary preferences from employees efficiently — the one-ask pattern, severity handling, privacy basics, and why you should only ever ask once.

Collecting employee dietary preferences once, in one simple ask

How to collect dietary preferences from employees is really two questions: how to ask well, and how to stop asking repeatedly. Most teams fail the second one — the same people fill in the same allergy form before every single event, and response rates decay each time.

Ask once, with the RSVP

The single best practice: dietary collection rides along with the RSVP, never as a separate form. One ask, one click-path, one deadline. Every additional form costs you 20–30% of responses, and the people you lose are exactly the ones the caterer needed to know about.

The ask itself should offer structured options (vegetarian, vegan, gluten-free, dairy-free, nut allergy, halal, kosher) plus a free-text field — structured options make caterer counts trivial; free text catches the “anaphylactic, separate prep required” cases that matter most.

Treat severity as first-class data

A preference and a medical allergy are different categories. Your data should distinguish them, and your caterer briefing should lead with the medical ones. A useful heuristic for the free-text field prompt: “Anything our caterer must know to keep you safe?” — it invites severity information without interrogating anyone.

Privacy: counts out, names in

Caterers need counts per restriction, not names. Keep the name-level data internal and need-to-know; share the aggregated tab. The dietary restrictions spreadsheet is structured exactly this way — a name matrix internally, a caterer-ready count export.

Stop re-collecting

Dietary needs are stable. Asking before every event signals that you didn’t keep the answer — and after the third time, people stop answering carefully. The durable pattern:

  1. Collect once into a permanent store (a sheet, or a tool).
  2. At each event, confirm rather than re-ask: “We have you as vegetarian + nut allergy — still right?” One-click confirmation gets near-100% response.
  3. Re-verify anything older than a year.

This confirm-don’t-ask pattern is the core of TeamRally’s Preference Vault — dietary needs stored once and attached to every RSVP automatically, with a one-tap “still correct” check.

Part of the HR event logistics guide. Related: collecting t-shirt sizes in Slack.

Ask once, never again: TeamRally stores dietary preferences and attaches them to every event RSVP in Slack or Basecamp. Join the waitlist.