How do you track RSVPs and dietary restrictions for a family reunion with over 100 people in 2027?

The outcome you should expect

A well-run tracking system for a reunion of this size produces one authoritative guest list, not five competing ones. In practice, a 100–130 person family reunion settles at roughly 85–92% response within three weeks of a deadline reminder, with the last 8–15% arriving in the final 72 hours. You should expect a final confirmed headcount that lands within about 5–8% of the actual number who walk through the door, because a handful of people always bring an unannounced plus-one, a teenager, or a last-minute guest.

On the dietary side, expect somewhere between 15% and 30% of attendees to flag at least one restriction. For 120 guests that is roughly 18–36 people, and they will not cluster neatly. You will typically see a long tail: two or three serious allergens (peanut, tree nut, shellfish, gluten), a larger group of preference-based flags (vegetarian, vegan, no pork, no beef), and a stubborn set of "no red meat" or "low sodium" requests from older relatives. The deliverable you are aiming for is a caterer-ready summary: total plates, plus a count per dietary code, plus a short list of named individuals with severe allergies so the kitchen can plate those separately.

The outcome you should *not* expect is a clean, final number. Treat your tracker as a living document with a version date. The last version before the caterer call is the one that matters, and you should be able to produce it in under five minutes from a phone at the venue.

What drives that outcome

Three things determine whether your RSVP and dietary tracking succeeds or collapses: how you collect responses, how you structure the data, and how you chase non-responders. Get the collection mechanism wrong and you will be reconciling text messages at midnight. Get the data structure wrong and you cannot answer "how many vegan plates?" without counting by hand. Get the follow-up wrong and you will be guessing at 20% of your headcount.

Collection mechanism. For a family reunion in 2027, the realistic options are a shared spreadsheet (Google Sheets or Excel Online), a form tool (Google Forms, Microsoft Forms, Jotform), or an event platform with RSVP built in. A form is best for clean data capture because it forces structured answers. A spreadsheet is best for editing and reconciliation because you can fix a wrong entry in seconds. The strongest setup is a form that writes into a spreadsheet, so you get structured input and a flexible master list. Avoid pure group-chat RSVPs — a 100-person family thread will bury responses and you will lose track of who said what.

Data structure. One row per attendee, not one row per household, is the single most important decision. If you record "Aunt Rosa's family: 4," you cannot capture that one of those four is gluten-free and another is a toddler who needs a high chair. One row per person lets you filter, count, and sort. Columns you actually need: household or invite group, guest name, age band (adult, teen, child under 12, toddler), RSVP status (yes, no, maybe, no response), arrival and departure dates if it is a multi-day reunion, dietary code, allergy severity, and notes.

Follow-up cadence. Non-response is the enemy. A single deadline produces a partial list. A deadline plus two reminders produces a near-complete one. The cadence that works: announce the date and the RSVP link 10–12 weeks out, send the first reminder at the deadline, send a second reminder three days later, then switch to direct personal outreach for the remaining holdouts. Personal outreach converts far better than a group message because people respond to a name, not a broadcast.

The reason follow-up drives the outcome so hard is that the people who do not respond are not random. They are disproportionately the ones with complicated situations: elderly relatives who need to check with a caregiver, families with young children, and people with dietary needs who assume someone already knows. Chasing them is not busywork — it is where the accuracy of your dietary counts comes from.

Benchmarks and realistic ranges

Concrete numbers keep you from over- or under-planning. These ranges reflect how 100+ person family gatherings typically behave.

Response rates. Expect 80–90% response by two weeks before the event if you run a deadline plus two reminders. Without reminders, expect 55–70%. The gap is entirely follow-up. For a 120-person invite list, that is a difference of roughly 20–30 people you would otherwise be guessing about.

Attendance versus RSVP. Of those who RSVP yes, expect 90–95% to actually attend. Of those who RSVP no, expect essentially zero, though a small number will show up anyway. Plan food for your confirmed count plus a 5–10% buffer. For 120 confirmed, cook for 126–132.

Dietary flag rates. Across a general adult population, roughly 15–25% report avoiding some food or ingredient, and around 5–10% have a diagnosed food allergy. In a family group with shared genetics, allergy clustering is real — if one branch of the family has celiac disease or a nut allergy, expect more. Budget for 20–30% of guests having at least one flag.

Severe allergy prevalence. Serious, anaphylaxis-risk allergies typically run 2–5% of a group. For 120 people that is 2–6 individuals. This is the number that justifies separate plating and a labeled station, not just a "gluten-free option."

Plate counts by category. A realistic breakdown for 120 confirmed guests might look like: 90 standard plates, 12 vegetarian, 5 vegan, 6 gluten-free, 4 dairy-free, 3 nut-free (severe), and 8 "no pork" or "no red meat." These overlap, so the sum exceeds the number of people with flags. Always count by *code*, then deduplicate by *person*.

Timeline benchmarks. Lock the venue and caterer 6–12 months out. Send save-the-dates 6 months out. Open RSVPs 10–12 weeks out. Set the RSVP deadline 4–6 weeks out. Confirm final headcount with the caterer 10–14 days out. Send the dietary summary 7–10 days out. These are the windows that give a caterer enough time to order and enough flexibility to absorb a few late changes.

Cost implications. Caterers commonly price per person, so a headcount error of 10 people on a $35-per-plate dinner is a $350 swing. Many caterers also charge for the guaranteed minimum even if fewer attend, so over-counting is safer than under-counting. Dietary-specific plates sometimes carry a small surcharge; ask early so it does not surprise the family budget.

Multi-day reunions. If the reunion spans a weekend, track arrival and departure per person. A guest attending Saturday dinner only versus all three days changes your meal counts dramatically. For a three-day reunion with 120 people, you may serve 120 Friday, 140 Saturday (day guests), and 90 Sunday. Track each meal separately.

Risks, edge cases, and failure modes

Most reunion tracking failures are predictable. Here are the ones that bite hardest and how to defuse them.

The single point of failure. One person holds the spreadsheet on their laptop. They get sick, lose the file, or go offline at the venue. Fix: keep the master list in a cloud spreadsheet with at least two editors, and export a PDF or CSV snapshot before the event.

Household RSVPs that hide individuals. "The Garcias: 5" tells you nothing about dietary needs. Fix: require a name and dietary field for every person, even children. If a household refuses to list names, record "Garcia adult 1, adult 2, child" and capture dietary flags at the household level as a fallback.

Dietary flags collected but never transmitted. You have a beautiful sheet, and the caterer never sees it. Fix: produce a one-page dietary summary and email it to the caterer with a read receipt, then confirm verbally 3 days out.

The "I'll just eat salad" assumption. Vegetarians and people with mild preferences often under-report because they do not want to be a bother. Fix: phrase the question to normalize it — "We want everyone to eat well; please tell us anything you avoid."

Severe allergies treated as preferences. A peanut allergy is not a preference. Fix: separate severe allergies into their own column, flag them for the caterer, and consider a plated-and-labeled meal for those guests rather than a buffet where cross-contact is likely.

Cross-contact at buffets. Even with a gluten-free dish, shared tongs and adjacent trays create risk. Fix: ask the caterer to plate severe-allergy meals in the kitchen and label them by name.

Late additions. Someone's plus-one appears the day before. Fix: keep a 5–10% food buffer and a small reserve of extra plates, and set a clear "no additions after X date" policy communicated kindly.

Duplicate responses. A guest fills out the form twice with different answers. Fix: use a form that collects email or phone, deduplicate weekly, and keep the most recent response.

Unreliable self-reporting. People forget a child's allergy or misremember a diagnosis. Fix: ask about allergies in a way that prompts specifics ("list any food that causes a reaction, and what the reaction is") rather than a yes/no.

Privacy and consent. Dietary and allergy information is health-adjacent data. Fix: keep the sheet access-limited, do not post it in a group chat, and share only the aggregated counts plus the named severe-allergy list with the caterer.

The "maybe" pile. Maybes are the hardest to plan around. Fix: treat maybe as no for food planning until confirmed, then add them to the buffer, and send a final confirmation nudge 10 days out.

Cultural and religious restrictions. Halal, kosher, and fasting periods are real and often under-reported. Fix: include an open text field, not just checkboxes, so people can explain.

Language and literacy barriers. Older relatives may not use forms. Fix: offer a phone-in option where a designated family member fills the form on their behalf, and mark the source of the entry.

A practical rollout plan

Here is a step-by-step rollout you can hand to whoever is running logistics. It assumes a reunion in 2027 with 100–150 invited guests.

Phase 1 — Set up (12–14 weeks out). Confirm the date, venue, and caterer. Build the master spreadsheet with these columns: household, guest name, age band, RSVP status, days attending, dietary code, allergy severity, notes, response date. Build the RSVP form with matching fields and link it to the sheet. Assign two editors and one backup.

Phase 2 — Invite (10–12 weeks out). Send the invitation with the RSVP link and a clear deadline. State the deadline twice. Explain why you are asking about dietary needs: so everyone gets a meal they can eat. Include a phone number for people who cannot use the form.

Phase 3 — Collect (10 weeks to deadline). Monitor responses weekly. Deduplicate. Fix obvious errors. Do not chase yet — let the deadline do its work.

Phase 4 — Chase (deadline to deadline +1 week). Send reminder one at the deadline. Send reminder two three days later. Then move to direct personal outreach per household for anyone still silent. Log every contact attempt in the notes column.

Phase 5 — Lock (4–6 weeks out). Freeze the headcount for planning purposes. Produce the caterer summary: total plates, count per dietary code, named severe-allergy list. Confirm the guaranteed minimum with the caterer.

Phase 6 — Final confirm (10–14 days out). Send a final "confirm or cancel" nudge. Update the sheet. Re-send the dietary summary if anything changed. Add the 5–10% buffer to the food order.

Phase 7 — Event day. Print the guest list with dietary flags. Print a separate severe-allergy list for the caterer and the server lead. Have one person own the check-in table and mark arrivals. Keep the sheet open on a phone.

Roles to assign. One data owner (owns the sheet), one chase captain (owns outreach), one caterer liaison (owns the summary and the call), and one day-of check-in lead. For a 120-person reunion, four people is enough. Do not let one person hold all four roles — that is the single point of failure again.

What "done" looks like. You are done when you can answer these five questions in under a minute: How many people are confirmed? How many plates does the caterer need? How many of each dietary code? Who has a severe allergy and what is it? Who is still unconfirmed? If you can answer all five from your phone, your tracking system works.

Related questions

How far in advance should I send the RSVP deadline for a 100+ person reunion?

Set the deadline 4–6 weeks before the event. That gives you 2–3 weeks to chase non-responders and 2 weeks to finalize with the caterer. Anything closer than 3 weeks out leaves no room for vendor changes.

Should I track RSVPs per household or per person?

Per person. Household-level tracking hides individual dietary needs, ages, and arrival dates. One row per attendee lets you count plates by dietary code and flag severe allergies by name.

What is the best tool for tracking dietary restrictions at scale?

A form that writes into a shared spreadsheet. Forms force structured answers; spreadsheets let you edit and filter. Google Forms plus Google Sheets, or Microsoft Forms plus Excel Online, covers 100–150 guests comfortably.

How do I handle guests who never respond?

Send two reminders, then switch to direct personal outreach by phone or text. Non-responders are often the ones with complicated dietary or caregiving situations, so chasing them is where your accuracy comes from.

How many extra plates should I order for a 120-person reunion?

Order for your confirmed count plus 5–10%. For 120 confirmed, plan 126–132 plates. Caterers usually charge for the guaranteed minimum regardless of attendance, so over-counting is the safer error.

FAQ

How do I collect dietary restrictions without making it awkward? Frame it as hospitality, not medical intake: "We want everyone to have a meal they can enjoy — please tell us anything you avoid or are allergic to." Give an open text field alongside checkboxes so people can explain, and reassure them that only the caterer sees the details.

What dietary categories should I include on the RSVP form?

Start with the big allergens (peanut, tree nut, shellfish, dairy, egg, soy, wheat/gluten), then add vegetarian, vegan, no pork, no beef, no alcohol, and an open "other" field. Include a severity question so you can separate a preference from an anaphylaxis risk.

How do I share dietary information with the caterer safely? Send an aggregated summary — total plates and counts per dietary code — plus a separate named list of severe allergies. Do not send the full guest sheet. Use email with a read receipt and confirm verbally three days before the event.

What if a guest's dietary needs change after I send the caterer summary? Update the sheet immediately and re-send the summary. Caterers can usually absorb small changes up to 72 hours out. For severe allergies, call rather than email so you know the message landed.

How do I handle a multi-day reunion with different attendance each day? Track arrival and departure per person and build a meal-by-meal headcount. A three-day reunion can swing from 120 to 140 to 90 across days, and each meal needs its own plate count and dietary breakdown.

Do I need a printed list if everything is digital? Yes. Print the guest list with dietary flags and a separate severe-allergy list for the caterer. Venues have unreliable Wi-Fi, phones die, and a printed list at the check-in table is the cheapest insurance you can buy.

Sources

• CDC — Food Allergies
• FDA — Food Allergies: What You Need to Know
• Food Allergy Research & Education (FARE)
• USDA — Food Safety and Inspection Service
• American Academy of Allergy, Asthma & Immunology
• Google Forms Help
• Microsoft Forms Help
• Celiac Disease Foundation

Related on PULSE

• How to build a guest list template for large family events
• Planning meals for a multi-day family reunion
• Managing vendor communication for private events
• Collecting allergy information safely and privately
• Budgeting per-plate costs for 100+ person gatherings
• Day-of check-in workflows for large private events