List the decisions each gathering needs
Start your wedding weekend RSVP plan by listing each part: welcome drinks, rehearsal dinner, ceremony, reception and farewell brunch, for example. Note the location, guest group and supplier who needs a count. Some moments may belong together; others need a separate attendance decision because guests can join one without joining the other.
Do not assume every event needs the same questions. A casual welcome gathering may only need attendance. A seated dinner may need individual meal selections. A shuttle may require its own booking decision. Give each question a purpose so guests are not answering the same long form several times.
Decide who is invited to each part before sending
Build the guest list for each gathering deliberately. A rehearsal dinner might include a smaller group than the ceremony, and some travelling guests may only attend part of the weekend. Check companion and children’s arrangements separately rather than copying the main wedding list without reviewing it.
Keep a public or shared wedding website appropriate for its audience. Listing a limited dinner without explaining who is invited can make other guests think they should attend. Guest-specific invitations are a clearer place for personal details. Do not share another guest’s private link to demonstrate a schedule; use your own host preview.
- Guest group: the people included in that particular gathering.
- Attendance decision: whether each person can join that part.
- Planning answers: only the meal, travel or other details that gathering needs.
Make separate replies obvious to the guest
Label every gathering with a clear name, date, time and location. Explain that guests should reply to each part they are invited to. “Please let us know about the weekend” is vague; “Please reply separately for the welcome dinner and Sunday brunch” tells someone exactly what remains to be done.
HeyVite sub-events group several gatherings under one event, with a guest list and RSVP for each part. Set up the invitations around your real plan, then inspect a guest’s view before sending. Confirm that the person sees the appropriate gatherings and that a completed response is not being mistaken for an answer to the whole weekend.
Work back from the earliest supplier deadline
Ask every venue or supplier when they need final numbers, then allow time to clarify missing responses. You may be able to use one guest-facing deadline for the weekend, but only if it gives you enough time for every gathering. If a dinner closes earlier than brunch, explain that distinction next to the relevant reply.
Follow up about the unanswered event, not the guest’s attendance in general. A useful message is: “Thank you for replying for the wedding. Could you also let us know about [gathering] by [deadline]?” This avoids asking someone to repeat a response they have already submitted.
Reconcile counts by event and keep changes connected
Before sending final numbers, review each gathering on its own: attending, declined and unresolved, plus the planning answers you actually need. A total of unique people across the weekend cannot replace the number of meals for Saturday dinner or seats on a particular shuttle.
Choose one person to coordinate late changes across the weekend. If a guest changes travel plans, ask which gatherings are affected and update those records. Notify the relevant supplier and co-host, and make sure the guest has the current schedule. One central plan helps you avoid several individually accurate lists that no longer agree.
Frequently asked questions
Do I need separate RSVPs for wedding-weekend events?
Use separate replies when gatherings have different guest lists, attendance choices or supplier counts. A reply to the ceremony or reception does not tell you whether someone will attend a welcome dinner or farewell brunch.
Can different guests see different wedding events?
HeyVite sub-events support a guest list for each gathering. Review the intended guest’s view before sending, and share their private link only with that recipient so the plan is not confused by a forwarded invitation.
Should all weekend events have the same RSVP deadline?
They can if the deadline leaves enough time before every supplier’s cutoff. Otherwise, show each gathering’s deadline clearly and follow up only on the response that is missing.