For a wedding weekend with several events, request a separate answer only when you need a separate attendance count. Match each person to the events they are invited to, keep restricted gatherings off general inserts, and test the guest-facing RSVP before printing. A single website link can collect several answers, but one wedding acceptance should not automatically count as a brunch acceptance.
One invitation does not always mean one attendance decision
A guest may attend the wedding on Saturday but leave before Sunday brunch. Another may miss Friday welcome drinks because of a flight. If your response form asks only whether they are coming to the wedding weekend, neither answer tells you how many breakfasts or welcome-party places to reserve.
The opposite problem is asking guests to answer the same question repeatedly. A ceremony, cocktail hour, dinner, and dancing can be four schedule entries without needing four separate yes-or-no questions. Start with the decisions your hosts and venues actually need, rather than turning every line of the itinerary into another RSVP.
This guide focuses on coordinating several guest lists and attendance counts. For a single event’s names, meals, and deadline, start with our wedding RSVP wording guide. The examples below are fictional planning examples, not rules that every wedding must follow.
Decide which events need their own response
| Situation | Response approach | Why it helps |
|---|---|---|
| Ceremony and reception have the same invitees and one overall attendance decision | One wedding response, with both locations and times clearly listed | A schedule can be detailed without duplicating questions |
| Welcome gathering needs a reservation count | A separate yes or no for each invited person | Friday attendance may differ from Saturday attendance |
| Farewell brunch is optional but catered | A separate brunch response | Optional attendance still affects food and seating |
| Informal drop-in gathering genuinely needs no count | State that no separate RSVP is required | Guests know they have not missed a response step |
| Rehearsal dinner includes only a smaller group | Restricted invitation and response route for that group | A general schedule must not accidentally extend the invitation |
Confirm the arrangement with each event’s host. A venue may require distinct counts even when two gatherings share the same attendees. If that applies, collect the information you need and explain the separate questions. Do not simplify the form by discarding an operational requirement.
Build a person-by-event list before designing the insert
Make one row per person, even if you will mail one envelope to a household. Use one column for each event’s invitation status and a separate column for its response. Keep “not invited,” “invited but unanswered,” “accepts,” and “declines” distinct. An empty cell is too easy to mistake for a no.
Consider this fictional household: Morgan and Taylor are both invited to the wedding and brunch; only Morgan is participating in the rehearsal dinner. Morgan accepts all three, while Taylor accepts the wedding and declines brunch. Their household has two wedding guests, one brunch guest, and one rehearsal-dinner guest. It does not have two attendees at every event simply because one person submitted the form.
Record names, the correct event permissions, each answer, and the latest confirmation date. A short note can explain a phone correction, but avoid storing unnecessary private reasons for someone’s absence. When a plus-one is allowed, confirm which gatherings that invitation includes rather than assuming it applies to the whole weekend.
Keep event visibility separate from RSVP permission
A page being visible and a person being able to respond are different things. A general itinerary might display a dinner that only a few guests can actually RSVP to. That can still sound like an invitation to a reader.
Zola’s official event-invitation guidance says guests can respond only to events assigned to them in the guest list, and explains the invited-status setting used for online responses. That is a permission control; review what appears on your public schedule separately.
The Knot’s private-event documentation describes a different presentation: private event details appear to invited guests during the RSVP process rather than on the general wedding website. It also notes limits on the information shown in that response box. Check the current guest view rather than assuming a long custom itinerary will fit there.
These platform details were checked on October 16, 2026, Türkiye time. Features can change. Neither a private-event setting nor a website password prevents an invited guest from sharing information. Use direct communication for details you do not want broadly circulated.
Choose the smallest printed set that communicates the right invitation
Keep the main invitation focused on the wedding. If everyone receiving a particular enclosure is invited to the same extra events, that enclosure can list them together with dates, locations, and response instructions. If invitations differ by household, make clearly labeled versions for assembly and check each against your mailing list.
For a limited rehearsal dinner, use a targeted insert or separate message. Do not put “rehearsal dinner by invitation only” on every household’s weekend card as a substitute for controlling who receives its details. Our rehearsal-dinner invitation guide covers that event’s individual wording.
A shared website address is useful because it stays short on paper. Print a readable address as well as any QR code, and use the exact event names found in the RSVP form. “Welcome gathering” on the card and “Friday dinner” online can sound like two different invitations.
Four original wording examples
1. Everyone receives the same three-event invitation
We hope you can join us throughout the weekend.
Welcome Dinner: Friday, August 6, at 6:30 p.m.
Wedding Celebration: Saturday, August 7, at 4:00 p.m.
Farewell Brunch: Sunday, August 8, at 10:00 a.m.
Please reply by July 9 at [your wedding website], with an answer for each event and each invited guest.
Add each venue’s name and address before printing. This layout is suitable only when every recipient is invited to all three events. The dates in this example fall on those weekdays in 2027.
2. Brunch is optional but needs a count
Staying through Sunday?
We would love to see you at our farewell brunch on August 8, from 10:00 to 11:30 a.m., at [venue and address]. Please let us know whether each invited guest will attend when you complete your wedding RSVP by July 9.
The question makes it comfortable to decline while still requesting a definite response. If the brunch host is different, include their name and coordinate the deadline with them.
3. One response covers the wedding, with a separate optional event
Please reply by July 9 at [your wedding website]. Your wedding response covers the ceremony and reception on August 7. You will also find a separate question about our optional welcome gathering on August 6.
Use this only after testing that the form actually behaves that way. Do not promise a separate question if it is hidden, disabled, or assigned to the wrong guests.
4. A phone alternative for several events
To reply by phone, please contact [host name and number] by July 9. Let us know which named guests will attend the wedding and which will join Sunday brunch. We are happy to record your answers for you.
The host should read the event-by-event answers back and enter them in the same master list. A phone reply should not create a second, disconnected attendance record.
Test five guest journeys before approving print
- Wedding-only guest: Can they respond without seeing a restricted dinner invitation?
- Guest invited to everything: Can they accept Saturday and decline Sunday?
- Mixed household: Can two people give different answers without one overwriting the other?
- Permitted plus-one: Does the additional person receive precisely the intended event options?
- Phone responder: Can the host record the answer and confirm it without asking the guest to submit again online?
Use a preview or test record where the platform supports it, and remove test responses before reporting totals. Test from a guest-facing session, not just the administrator view. Check the confirmation screen too: a general “thank you” message may leave guests unsure which events they accepted.
Turn responses into usable counts
Count accepted people within each event, not submitted forms or mailed envelopes. In the example household above, one submitted form produces different numbers for three hosts. Send each host the count and information relevant to their gathering, with the date of that version.
Follow up on a missing brunch answer as a missing brunch answer. Do not ask an already-confirmed wedding guest to RSVP to the entire wedding again. A useful message is: “We have your Saturday acceptance, thank you. Could you also confirm whether you will join Sunday brunch?”
If plans change after the deadline, update the affected event and contact its host before promising that space remains available. Keep the earlier answer traceable so two people coordinating the weekend do not work from conflicting totals.
Plan the invitation order around the finished response route
Choose your physical design from LunaInvites invitations, then finalize the printed link, deadline, and enclosure versions. The cover features our butterfly acrylic invitation with a green envelope as a design sample. Its product page lists a clear acrylic card with gold print, envelope, gold string, wax seal, and dried flower detail. Extra response or weekend cards should not be assumed to be included.
A digital proof is the design-approval stage of a physical invitation order. Check the wording against your tested guest response route before final approval. Under the current shipping policy, US shipping is free, with estimated total delivery of 7–8 days after final proof approval, including 2 days of production. This is an estimate, not a guaranteed arrival date; allow additional time for addressing and sending invitations to guests.
Cover: AI-assisted editorial layout using LunaInvites’ own product photograph. The pictured invitation is a product design sample, separate from the fictional wording examples above.