Wedding RSVPs Per Person, Per Event: A Multi-Day Guide
Track each guest across the welcome dinner, Mehndi, Sangeet, ceremony, and reception. Learn household invitation rules and accurate event headcounts.
By Mia · · Updated
For a multi-day wedding, collect one attendance answer from each person for each event they are invited to. A yes for the reception does not tell you whether that person is coming to the welcome dinner or Sangeet. A household response should preserve those individual answers, even when one relative submits the form for everyone.
Cordially Wed supports per-person, per-event RSVPs alongside household guest management. The workflow starts with the invitation list, then the attendance answers, then a separate confirmed headcount for every gathering.
Which wedding events need their own RSVP?
Any gathering with a separate attendance or capacity decision needs its own count. That might include a welcome dinner, Mehndi, Haldi, Sangeet, ceremony, reception, or next-day brunch. Write down the time, venue, invitation audience, and response deadline for each.
A single weekend total cannot tell your caterer how many meals to prepare on Friday or your transport provider how many people need a Saturday pickup. Ask about the gatherings you actually need to plan, rather than making guests answer for every minor schedule item.
Who is invited, and who has accepted?
Keep invitation eligibility separate from attendance. First decide which people may attend each event. Then collect their yes or no. A guest who was never invited to the rehearsal dinner should not be counted as a declined invitation.
In Cordially Wed, event audiences can use guest records, guest lists, or tags. An event without a targeted audience is open to all guests. Set a specific audience for private gatherings and check the invitation before sending.
How do households RSVP for multiple events?
One person can coordinate the household response while every named person answers separately for each invited event. For example, a parent may accept the ceremony and reception, while an adult child declines the ceremony because their flight arrives later.
In Cordially Wed, members added under a primary guest share that primary guest's event invitations. Their attendance answers can differ. If the adult child should only be invited to the reception, use a separate guest record with that audience instead. The household RSVP setup guide walks through this distinction and the guest profile steps.
What should an event headcount look like?
Use a small example to check your setup. Three people are invited to the welcome dinner, Sangeet, and reception:
- Asha: dinner yes, Sangeet yes, reception yes.
- Dev: dinner no, Sangeet yes, reception yes.
- Nila: dinner yes, Sangeet no, reception yes.
That means two confirmed for dinner, two for the Sangeet, and three for the reception. It is seven accepted person-event responses across the weekend, but only three distinct people. Neither number should be passed off as the headcount for every event.
Keep pending answers separate from no answers. A non-response is an unresolved planning decision, not a confirmed decline.
How should you record meals and dietary needs?
Record dietary needs against the individual, including named household members, so a note does not accidentally apply to the whole family. Before handing over a catering count, match those people to the yes-list for the relevant event. A vegetarian guest who is not attending the dinner should not increase that dinner's vegetarian count.
Cordially Wed supports dietary notes per person. A dietary note is different from an event-specific meal selection, so agree with your caterer on any additional menu choices you need to collect and verify them before the deadline.
How do you follow up without chasing the whole guest list?
Review unanswered RSVPs by event and contact the relevant household or guest. Include the event name and deadline in the reminder so a guest who has already answered for the reception understands what is still missing. See our wedding RSVP reminder guide for wording.
Cordially Wed supports SMS and WhatsApp communication in one inbox. Use the channel your contact prefers and send their RSVP link. If they reply conversationally instead, confirm exactly which people and events they mean, then make sure those answers are recorded. A message saying 'we are coming' is not automatically a completed set of event RSVPs.
How do you compare RSVP tools for a multi-day wedding?
Try a household whose members give different answers, a reception-only guest, and an invitation-only dinner. Check the guest experience and the final count for each event. Do not assume other providers lack multiple-event or party RSVPs: both our Zola comparison and Joy comparison document those capabilities.
Cordially Wed combines this planning workflow with guest records and SMS plus WhatsApp conversations. Guest management and RSVPs are free; texting guests is paid. Start with your wedding guest management setup, then test one household before sending the full list.
Frequently asked questions
Can wedding guests RSVP separately for each event?
Yes. Per-event RSVP tracking records an individual guest's answer for each invited gathering, so a reception acceptance does not imply attendance at the welcome dinner or ceremony.
Can one family submit different answers for different people?
Yes. A household response can contain different event answers for each named person. In Cordially Wed, added members share the primary guest's event invitations, but their yes or no answers are independent.
How do I invite some guests only to the reception?
Use an event audience that includes them for the reception and excludes them from other gatherings. In Cordially Wed, use separate guest records if people under one household contact need different invitation sets.
Should unanswered wedding RSVPs count as no?
No. Keep unanswered invitations pending until you resolve them. Track invited, accepted, declined, and pending people separately for each event.