How to Track Wedding RSVPs for a Multi-Day Wedding

Tracking RSVPs across a Mehndi, Sangeet, and reception is harder than one yes-or-no. Here is a calm, per-event system that keeps every guest count straight.

By Mia · 2026-06-28

A single-day wedding has a simple question: are you coming? A multi-day wedding asks it five or six times over. Your aunt might make the Mehndi but skip the Sangeet, your college friends might fly in only for the reception, and the catering count for the Haldi looks nothing like the count for the Nikah. If you try to hold all of that in one spreadsheet column, the numbers slip, and you end up texting people the week before to ask what you already asked in the invite. The good news is that tracking RSVPs across many events is mostly a matter of structure. Set it up once, the right way, and the rest is just watching responses come in.

Treat every event as its own guest list, not one big yes or no

The single biggest mistake is asking guests to RSVP to the whole wedding at once. A grandparent who comes to all four days and a coworker who only attends the reception both count as one yes, which tells your caterer nothing. Instead, give each event its own attendance column: Mehndi, Haldi, Sangeet, Baraat, ceremony or Nikah, and reception. Each guest gets a yes, no, or pending for each one. Now a single screen tells you that 120 are confirmed for the Sangeet and 210 for the reception, which is exactly what every vendor will ask for. This also respects how desi guests actually attend. Family on both sides may join the religious events while colleagues come only to the party. Per-event tracking lets you honor those patterns instead of fighting them, and it stops you from over-ordering food for events most guests were never invited to.

Only invite each guest to the events that apply to them

Not everyone is invited to everything, and that is normal for a multi-day wedding. The Haldi might be close family only, the Mehndi might be the bride's side, and the reception might be everyone. Before you collect a single RSVP, decide which guests are invited to which events and tag them accordingly. This does two things. First, your RSVP requests go out clean, so a coworker is never asked whether they are coming to a 30-person family ritual. Second, your pending list stays meaningful. If someone has not replied, you know it is a real gap, not noise from an event they were never asked to. Sort your guest list into circles early: immediate family, extended family per side, family friends, and the couple's own friends and colleagues. Map each circle to events once, and every later count stays honest.

Collect a few extra details with the RSVP, not after

The RSVP is your one reliable moment of a guest's attention, so ask for everything you will need in the same step. Beyond which events they are attending, capture meal needs and a plus-one count. For a desi wedding, give real dietary options rather than a free-text box: Pure Veg, Jain, Halal, vegetarian, vegan, and a separate field for nut and other allergies. Free text turns into thirty different spellings of the same thing and someone has to clean it up by hand. Structured options give your caterer a clean tally per event, since the Mehndi lunch and the reception dinner may need very different vegetarian counts. Also ask how many seats each yes represents, because in many families one invitation quietly means four people. Collecting this with the RSVP saves you a second round of follow-up texts to every confirmed guest.

Send RSVP links by the channel your guests actually read

Paper cards and email RSVPs go unanswered for weeks, especially with elder relatives and guests living overseas. Most people, across generations, open a text within minutes. Send each guest a personal RSVP link by SMS or WhatsApp, with one tap to confirm per event. WhatsApp is often the better choice for family abroad, where it is the default way everyone already talks. The link should open to a page showing only the events that guest is invited to, so the experience feels personal and takes seconds. Keep your message warm and short, name the events, and include the dates. Then, instead of chasing individuals, you send one gentle reminder a couple of weeks later to only the people still marked pending. Because each link is tied to one guest, their reply updates your counts automatically, with no transcribing from a group chat.

Build one live dashboard you check, not many you reconcile

Once responses arrive, you need a single source of truth. Aim for one view that shows, per event, how many are confirmed, declined, and still pending, plus a dietary breakdown for each. This is the number you hand to caterers, the venue, and your seating plan, and it should update the moment a guest replies. Watch the pending column most closely. Two months out it is fine for it to be large; three weeks out, it should be your active to-do list. Set a soft internal deadline about a month before each event and treat anyone still pending after it as a phone call rather than another text. A multi-day wedding also has a long tail, so keep RSVP tracking, dietary needs, and seating in one place: when a guest switches the Sangeet from yes to no in the final week, that single change should flow to your headcount, dietary tally, and table chart without you re-keying anything. Lock final vendor numbers as late as each caterer allows.

Give guests their own schedule so they stop asking you

Tracking RSVPs is half the job. The other half is making sure confirmed guests actually show up to the right event, at the right place, at the right time. With three or four venues across several days, you will otherwise field a steady stream of where do I go and what time messages in the final week. Solve it by sending each guest a personalized version of the schedule that reflects only the events they said yes to, including venue, timing, and any dress code. A wallet pass is the calmest way to do this: the guest adds it once, and their schedule, table number, and dietary note sit on their phone's lock screen, updating if anything changes. That cuts day-of confusion and quietly confirms attendance, because a guest who saves a pass is a guest who is planning to come.

A free way to run all of this in one place

If juggling several spreadsheets sounds like a lot, that is because it is, and it is exactly the problem Cordially Wed was built to solve for couples planning their own multi-day weddings. You import your guest list, tag who is invited to the Mehndi versus the Sangeet versus the reception, and send each guest a personal RSVP link by SMS or WhatsApp. Replies flow into one dashboard with per-event counts and a dietary breakdown for Jain, Halal, Pure Veg, and allergies, and confirmed guests get an Apple or Google Wallet pass showing their schedule, table, and venue. The guest list, RSVPs, wallet passes, seating chart, and a free wedding website are all free; the only paid piece is unlimited guest texting, a one-time $49 after your first 15 texts, with no subscription. If you want to try it, you can add your first guests and send them at cordiallywed.com/invite whenever you are ready.