Multi-Event RSVP: One Weekend, Three Events

A wedding weekend is not one event with a longer runtime. It is three events with three different guest lists, three different caterers and three different headcounts, and the moment you treat it as one, the numbers stop being trustworthy.

Eleni and Tom invited sixty people to the welcome dinner, a hundred and eighty to the ceremony and reception, and about ninety to the next-day brunch. One guest list, three overlapping subsets. Their first RSVP form asked a single yes or no.

By the week of the wedding they had a confident total and no idea how many of those people were coming to dinner on the Friday.

Why one yes or no does not work

A single RSVP answers the question "are you coming to the wedding". It cannot answer the three questions you actually have to pay for.

The consequences are specific:

• The welcome dinner is over-catered, because you assume everyone invited attends, and roughly a third of guests arrive too late on the Friday.
• The brunch is under-catered, because the people who said yes to the wedding were never asked separately and you guessed low.
• Nobody knows about dietary requirements per event, so the caterer gets one list for three sittings.
• Guests are confused about what they are invited to, which is the part that causes actual awkwardness.

That last one matters most. Not everybody is invited to everything, and there is no graceful way to communicate that in a single yes or no field.

Ask once, per event

The structure that works is one invitation, one link, and a separate answer per event that a guest can only see if they are invited to it.

Three answers, one form, one visit. The guest is asked once. You get three numbers.

This is where most free tools stop being useful, because they are shaped around a single event with a single date. Multi-event RSVP keeps one combined guest list and separate responses per event, which is the difference between one confident number and three.

Who sees what

The mechanism that avoids awkwardness is per-event visibility. A guest invited only to the ceremony should not see a question about the Friday dinner at all.

Handled that way, nobody has to be told they are not invited to something, because nothing they are not invited to is ever shown to them. Handled badly, with a single form listing all three, everybody sees everything and the omissions are conspicuous.

It is worth thinking about the tiering before you write a word of the invitation:

• Everyone: ceremony and reception.
• Travelling guests and close family: welcome dinner, because they are there anyway.
• Anyone staying over: brunch.

Those three rules will generate your three lists in about ten minutes and are much easier to explain to a relative than an ad hoc decision.

Save the date does the heavy lifting

For a multi-day weekend, the save the date matters more than for a single-day wedding, because guests are booking travel and accommodation around a shape they do not yet know.

Say the shape early, even before details exist. "Friday evening through Sunday lunch, on Naxos" is enough for someone to book the right flights. Without it, half your guests book to arrive Saturday morning and miss the Friday entirely, and you catered for them.

A save the date that collects contact details at the same time also solves the other multi-event problem, which is that you need a working email or phone number for each of three different reminder cycles.

Chasing, per event

Three events means three chase cycles, not one. They do not run to the same schedule either.

The welcome dinner needs a firm number earliest, because restaurants book smaller rooms and hold them for less time. The reception number is usually locked by the venue's own deadline. The brunch can be confirmed latest, and is the one most affected by people changing plans.

Practically, chase in that order and keep the three numbers separate in your own head. A guest who has answered for the wedding but not the brunch has not ignored you, they have answered the thing you asked.

Conclusion

The failure here is not a tracking failure, it is a question design failure. One yes or no cannot produce three headcounts, and no amount of chasing fixes that after the fact.

Decide the three tiers, ask each guest once with per-event visibility, and let the answers stay separate. You will end up with three numbers you can actually give to three suppliers, which is the only version of this that works.

If you are running a weekend rather than a day, start free with WhiteClover. One guest list, separate RSVPs per event, and each guest only sees the events they are invited to.

Frequently asked questions

How do I collect RSVPs for more than one wedding event? Use one invitation with a separate response per event, rather than a single yes or no. The guest answers once, in one visit, and you get a distinct headcount for each event to give each supplier. A single combined answer cannot produce more than one number.

How do I tell guests they are only invited to part of the weekend? You mostly do not have to. If your RSVP shows each guest only the events they are invited to, nothing they are excluded from ever appears. Listing every event on one form for everybody is what makes omissions conspicuous.

When should I send a save the date for a multi-day wedding? Earlier than for a single day, and it should state the shape even before details exist. Something like "Friday evening to Sunday lunch" lets guests book the correct flights. Without it, many will arrive on the Saturday morning and miss anything before it.

Do I need separate dietary requirements per event? Yes, if different caterers are involved. The same guest may attend two of three events, and each supplier needs its own list. Collecting dietary information once against the whole weekend leaves each caterer guessing which entries apply to them.

Which headcount should I confirm first? The smallest venue first, usually the welcome dinner, because restaurants hold small rooms for the shortest time. The main reception is normally fixed by the venue's own deadline, and the brunch can be confirmed last since it changes most.

Read next

• Multi-Event Save The Date For Weddings And Baptisms
• Wedding RSVP Guide: Timeline, Wording And Tracking
• Wedding RSVP
• Save the date