A wedding weekend is not one party with a long guest list. It is three or four parties whose guest lists overlap in ways that only you can see: everyone is at the ceremony, most come to the welcome drinks, and half the room has a flight and skips the brunch.
That makes the RSVP job different. You need a headcount for each event, a way for a guest to answer once instead of four times, and a clear view of who has said what. Here is how to set that up, and what to do when one reply has to cover several events.
Plan each event as its own count
Start by listing the events and who each is for. A typical weekend has a welcome drinks evening, the ceremony and reception, and a farewell brunch, but yours might add a rehearsal dinner for family or a day trip for the guests who travelled. The point is that each one has its own venue, its own caterer and its own number.
For every event, write down three things before you send anything:
- Who is invited. All guests, or a smaller group such as family and the wedding party.
- The limit. The room might hold fewer people than the guest list, and the brunch venue might hold fewer still.
- The date you need an answer. A caterer for the main meal wants numbers earlier than the cafe doing brunch. See choosing an RSVP deadline for working backwards from each supplier.
Why one reply for everything goes wrong
The lazy approach is a single question: “Will you attend?” It falls apart the moment someone is coming to part of the weekend. A guest who cannot make Friday still says yes, and you assume they will be at the drinks. A guest who is staying for the brunch has no way to tell you they are skipping the ceremony dinner.
The opposite is just as bad. Four separate forms, one per event, means every guest does the same work four times, and the ones who answer one and forget the rest become your chasing list. You end up with an accurate headcount for the event they remembered and a guess for the others.
The fix is one reply that asks about each event separately. The guest answers once, per person, and you still end up with a number for every event.
What a single weekend reply should ask
Keep the form short and let the structure do the work. For each person on the invitation, list each event by name and date, and offer a yes or no. A household of three might have three people going to the ceremony, two going to the welcome drinks and none at the brunch, and the form should let them say exactly that.
| Guest | Welcome drinks | Ceremony | Brunch |
|---|---|---|---|
| Guest A | Yes | Yes | No |
| Guest B | Yes | Yes | Yes |
| Guest C | No | Yes | No |
Put the questions that apply to everyone, like dietary needs, in one place rather than once per event, so a guest is not asked about allergies three times. Questions that apply to a single event, such as a meal choice at the ceremony dinner, belong on that event. For wording ideas, read how to word a wedding RSVP, and for dishes see collecting meal choices.
Be clear about who is invited to what. If the welcome drinks are for everyone but the rehearsal dinner is family only, a guest should only see the events meant for them, or they will ask why they were left out.
Counting the weekend without double-counting
Once replies arrive, resist the urge to make one grand total. The number that matters is per event. The caterer for the ceremony does not care how many people are at the brunch.
A tidy tracker has one column per event and a total at the foot of each:
- Going, maybe and not coming for every event, so you can see the gap between confirmed and hopeful.
- Children and plus-ones counted as people, not as parties. A party of four is four meals.
- A waitlist for any event with a hard limit, so a decline frees a place for someone who was turned away.
- Unanswered as its own line, never folded into “no”. Those are the guests to chase.
Reconcile the sheet against each supplier’s deadline, not just at the end. Two weeks out from the first event is no time to discover that the brunch count is a guess.
How JoinMe handles a weekend
On JoinMe each event of the weekend is its own invitation page, with its own guest limit, waitlist and reply-by date. You group them into a series, and guests then see which weekend each event belongs to, with the events listed by date.
The weekend reply lists the events in one form, with a choice for each person. Behind the scenes it saves a separate reply on each event, so one event being full or past its deadline does not undo the others. Each event’s own questions are asked in the same form. An event that sits behind a different invite code, or that requires a mailing address, is answered on that event’s own page instead.
On your side, a weekend overview on the manage page shows going, maybe and waitlisted counts for each event of the series, and lists the guests who replied for the whole weekend with what each said per event. Every event keeps its own list and capacity, so the per-event number your caterer needs is always just that event’s count. To see what is included for couples, see the wedding RSVP page.
Chasing the guests who only answered part
Weekend replies leave a new kind of gap: a guest who said yes to the ceremony and never touched the brunch line. Decide in advance what counts as a final answer. A good rule is that a person is only complete when every event they are invited to has a yes or a no.
- Send the first reminder a few days before the earliest reply-by date, not the latest.
- Name the events still open when you nudge, so the guest knows exactly what is missing.
- Treat silence on an event as unanswered, and decide before the deadline whether you will ask or assume.
- Check each supplier’s number against the final per-event count the same day you send it.
- Keep a short list of late changes and who approved them, so counts do not drift after the deadline.
For a gentler way to chase, read how to get people to actually RSVP. And once the counts are settled, the seating chart from a spreadsheet guide picks up where this one stops.
Questions people ask
Should I send one invitation or one per event?
One invitation that covers the weekend is easier for guests, as long as each event is asked about separately. Guests answer once, and you still get a number per event.
Do all guests need to be invited to every event?
No. A welcome party for everyone and a rehearsal dinner for family only is normal. Guests should see only the events meant for them.
How do I count people for a brunch if some guests skip it?
Count per event, per person. A household of four going to the ceremony and two to the brunch is four for one and two for the other.
Can events in a JoinMe weekend have different limits?
Yes. Each event keeps its own guest limit, waitlist and reply-by date, even though guests answer for the whole weekend in one reply.