How to Track RSVPs for a Multi-Event Indian Wedding Without a Spreadsheet

Tracking RSVPs for a multi-event Indian wedding without a spreadsheet: per-event RSVP links, a live headcount for Mehndi, Sangeet, Haldi and reception, plus dietary tracking.

By Mia · 2026-06-22

Here is the short answer: stop running one giant spreadsheet, and give each event its own RSVP. A desi wedding isn't one party with one guest list — it's Mehndi, Sangeet, Haldi, the Baraat, the ceremony, and the reception, each with a different crowd. The way to track all of it without losing your mind is a per-event RSVP link and a live headcount that updates the moment someone replies. No formulas, no color-coded tabs, no "wait, is Auntie coming to the Sangeet or just the reception?"

That's exactly what Cordially Wed does, and it's free. You build your guest list once, mark who's invited to which event, and each guest gets to say yes or no per event. You watch a real number for every function — 218 confirmed for the reception, 96 for the Haldi — instead of recounting rows. This guide walks through why the spreadsheet always breaks for a multi-day wedding, and how to set up something that actually holds 300 guests across five events.

We'll follow Priya & Raj, who are planning a three-day wedding with both sides of the family flying in. Their guest list is around 300 people. If you've ever tried to track that in Google Sheets, you already know where this is going.

Why one spreadsheet always breaks for a desi wedding

A spreadsheet assumes one event and one yes-or-no. A South Asian wedding is neither. Here's where it falls apart in practice:

• A different guest list per event. Priya's college friends are coming to the Sangeet and reception but not the Haldi. Raj's parents' work colleagues are reception-only. The elders and close family are at everything. In a single sheet, that becomes five columns of "Y/N/maybe" per person, and one wrong cell means someone shows up to a function with no chair or no plate.
• Aunties replying for the whole family. You text one invite and get back "Yes beta, all six of us coming" — but only to the Sangeet, and only four for the reception. A spreadsheet has no idea what to do with that. You end up doing mental math at midnight and guessing on the count.
• Replies arriving everywhere. Some say yes on WhatsApp, some over SMS, some catch you at chai. Without one place to record them, the real number lives in your head, and your head is full.
• Dietary needs get lost. Jain, Pure Veg, Halal, Kosher, a nut allergy, the cousin who's newly vegan — in a sheet these become a free-text column nobody filters, and the caterer gets a number with no breakdown.
• Two people editing at once. You update row 112, your fiancé updates it too, and now you genuinely don't know who's confirmed. Every couple has had the "wait, did you already count them?" conversation.

None of this is a discipline problem. It's that a flat grid was never built to track the same person across five different events, each with its own headcount and its own menu.

Set up one guest list, many events

The fix is to separate the two things a spreadsheet jams together: who your guests are, and which events they're invited to.

In Cordially Wed you build your guest list once — Priya & Raj's ~300 names go in a single time. Then you create your events: Mehndi, Sangeet, Haldi, Baraat, ceremony, reception, however many days you're celebrating. Now you tag each guest to the events they're actually invited to. The college friends get Sangeet + reception. The elders get everything. The reception-only colleagues get exactly one.

This is the part Zola and The Knot can't do. Those tools were built for a one-day Western wedding — one event, one RSVP, one headcount. They have no concept of "invited to the Sangeet but not the Haldi," which is the entire shape of a desi wedding. So instead of fighting a tool that assumes one party, you're using one that assumes many.

The payoff is that your guest list stops being a wall of Y/N columns and becomes what it actually is: a set of people, each with their own invitation. Add a guest later and you just tag their events. Family grows by six? You add six names, tag them, done — no reshuffling a grid.

Per-event RSVP links and a live headcount

Once events are set up, each guest can RSVP per event — yes to the Sangeet, no to the Haldi, yes to the reception, all in one tap-through. You're not asking them to fill a form five times; they see the functions they're invited to and answer for each.

And because aunties reply for the whole family, the RSVP handles a head of household responding for several people. "Six of us for the Sangeet, four for the reception" lands as real numbers on the right events, not a sentence you have to decode later.

Then the thing that actually saves you: a live headcount per event. Every event shows a real, current number — confirmed, declined, still waiting. The moment someone RSVPs, the count moves. Priya can open it the morning of and see 96 confirmed for the Haldi and 218 for the reception, without recounting a single row. That's the number you hand the caterer, the number you give the venue, the number you plan seating around.

You can also see who hasn't replied yet, per event — so a nudge goes only to the people who haven't answered for that specific function, instead of blasting all 300 again.

Track dietary needs the way a desi caterer actually needs them

For a South Asian wedding, the headcount is only half the story — the menu split is the other half. Cordially Wed tracks dietary needs right alongside the RSVP, so when someone confirms they can also tell you Jain, Halal, Pure Veg, Kosher, or flag an allergy.

Because it's tied to each guest and each event, you get a breakdown that's actually usable: not "some vegetarians somewhere," but a real split per function. Of the 218 confirmed for Priya & Raj's reception, you can see how many are Pure Veg, how many Jain, how many Halal, who has a nut allergy at table 9. That's the exact form a caterer wants it in — counts per category, per event — instead of a free-text column they'll quietly ignore.

It also means the Haldi lunch and the reception dinner can have different counts and different menu splits, which they will, because different people are coming to each. You're tracking the wedding as it really is: multi-day, multi-menu, multi-headcount.

How the replies and reminders stay in one place

The last thing a spreadsheet can't do is talk to your guests. Cordially Wed lets you message guests over WhatsApp and SMS — and your wedding website, RSVP links, and replies all live in the same place.

When guests write back, those replies land in one unified inbox instead of being scattered across your phone, your fiancé's phone, and three group chats. So when an auntie messages "can I bring my sister to the Sangeet," you see it next to her RSVP, not buried under 40 other texts.

A note on cost, because it matters: everything here is free — the guest list, per-event RSVPs, the multi-day timeline, budget, seating, Apple Wallet and Google Wallet passes, and your wedding website. The only thing you'd ever pay for is texting guests over SMS: your first 15 are free, and a one-time $49 unlocks unlimited SMS — no subscription. Sharing your RSVP link from your own phone, or over iMessage, stays free. So most couples track their whole wedding without paying anything.

You don't need an account to start. You can build your events, guest list, and per-event RSVPs in about a minute, then save it. If the spreadsheet has stopped making sense — and around 300 guests across five events, it will — build your wedding free at cordiallywed.com. About a minute, no account needed, and your headcount finally counts itself.