How should a host collect RSVPs for a rehearsal dinner, ceremony, and brunch without three separate forms?

One list, several events, per-household invitations

A wedding weekend might include a welcome drinks gathering, a rehearsal dinner, the ceremony and reception, and a farewell brunch. Not everyone is invited to all of them. The rehearsal dinner is often close family and the wedding party; the brunch might be everyone staying at the hotel. Managing that with separate forms means a guest receives three links, replies to two, and you spend a week matching names across lists. Related: How should an event host handle plus ones and whole families when collecting RSVPs online?

The better structure is a single guest list where each household carries a flag for each event they are invited to. The RSVP form then shows that household only the events they can attend, with a yes or no and, where relevant, a meal choice for each. The guest experiences one link and one reply; you get one list with attendance and meals broken out by event.

Keep reading: What is the easiest way to collect RSVPs and meal choices from every wedding guest at once?, How do you give your caterer an accurate final headcount without recounting guests all week?, How should an event host handle plus ones and whole families when collecting RSVPs online?. See how RsvpMealr helps you event rsvp and meal choice collection.

Set up the form so guests never see an event they were not invited to

The awkward failure is a guest seeing a rehearsal dinner question when they were not invited to the rehearsal dinner. Any tool you use should let you invite households to events individually and hide the rest. A tool that supports this lets you tick each household into the events it belongs to, so the form a household opens is already tailored. If you build this in a spreadsheet and a general form, you will need separate links per invitation tier, which is manageable for two tiers and painful for four.

Label each event clearly with day, time, location, and dress note on the form, since guests replying to several events in one sitting will otherwise mix them up. A short line per event, such as Friday evening, casual, at the family home, is enough. Guests deciding about travel are also deciding about which events to attend, so this is the moment they need the practical details.

Meal choices where they matter, headcount where they do not

Not every event needs a meal choice. A plated rehearsal dinner does. A cocktail welcome party with passed appetizers needs only a headcount. A brunch buffet needs a headcount and dietary notes. Ask only what each event's caterer actually needs, so the form stays short and guests do not tire of it by the time they reach the main event's questions. Related: How do you give your caterer an accurate final headcount without recounting guests all week?

Carry dietary restrictions across events rather than asking three times. One dietary field per guest, applied to every event they attend, is easier for guests and gives each caterer the same note. If one event has a caterer who needs something specific, such as a choice between two brunch dishes, add that question to that event alone. Related: What is the best way to collect dietary restrictions from guests without a dozen follow up messages?

Reporting per event, chasing once

Once replies come in, each event needs its own headcount, meal breakdown, and dietary list for its vendor, and you should be able to pull those separately without touching the others. Build your exports by event from the start. The rehearsal dinner restaurant gets a count of attendees and entrees; the brunch caterer gets a count and dietary notes; the wedding caterer gets the full breakdown. Related: What is the easiest way to collect RSVPs and meal choices from every wedding guest at once?

Chasing, on the other hand, should happen once. A household that has not replied has not replied for all of their events, and a single reminder covering everything is far better received than three. Track reply status at the household level, and when you send reminders, mention the deadline and the fact that the reply covers the whole weekend. Guests appreciate not being asked three times, and you appreciate sending one message.