RSVPs for a Destination or Multi-Day Wedding
Why a single yes-or-no does not work when there are three events, how to collect per-event replies, and the earlier timeline a destination wedding needs.
One question is not enough
Welcome drinks, the ceremony, the day-after brunch — a guest can be at two of the three, and a single yes gives you nothing to plan against.
Per-event replies
How to structure it, and the per-event head counts you get back.
Not every guest sees every event
Some are invited to the whole weekend, some to the wedding only. The list has to carry that, and the reply form has to respect it.
The timeline moves earlier
Flights and accommodation mean guests need to decide sooner, and you need to know sooner. Recalculate the count-back from the deadline post with travel added.
What else to collect
Arrival and departure dates, accommodation choice, whether they need the shuttle. Custom questions doing real work here.
Attrition is higher, and normal
Plan for it rather than being surprised by it.
Run Your Wedding Guest List by Talking to It
Add guests, change party sizes and check who has not replied by asking, from the same assistant you already have open — no spreadsheet, no forms.
Collecting Meal Choices and Dietary Requirements
How to ask for meal selections per guest rather than per household, which dietary questions to ask, and how to hand your caterer numbers they can actually use.
How to Chase Wedding RSVPs Without Being Annoying
A chasing schedule that works, message templates for each round, and how to automate the reminders so you are not the one sending them.