Every Indian wedding guest list follows the same arc. Week one: you and your partner sit down with a notebook and write down maybe 80 names. Feels manageable. Week two: both sets of parents have "a few additions." Week six: you're at 340 people and nobody can agree on which version of the spreadsheet is the real one.
The problem isn't the size of the list. It's that it lives in the wrong place — a flat file with no structure, no ownership, and no way to ask "who confirmed for the mehendi?" without manually counting rows. Here's a better way to do it.
Start with one list, not four
The biggest mistake is starting separate lists for each function — one for the wedding, one for the sangeet, one for the mehendi. You end up with four documents, all slightly different, and nobody knows which names are on which.
Start with one master list of every person you might invite. Don't filter yet. Don't assign events yet. Just get everyone's name, phone number, and a rough relationship category (immediate family, extended family, friends, colleagues) into one place.
One more thing: collect phone numbers upfront. You'll need them for WhatsApp invites later, and hunting for numbers after the list is "done" is its own separate nightmare.
Tag by event — don't duplicate
Once your master list exists, assign each person to the functions they're invited to. Not by copying them into a new sheet — by tagging them in place. One row per person, multiple event tags per row.
This changes everything downstream. When you need a headcount for the sangeet, you filter by that tag — instant answer. When you send WhatsApp invites for the mehendi, you send only to guests tagged for that event. No accidental messages. No "wait, are they coming to this one?"
A simple relationship tag (close family / extended family / friends / colleagues) is also worth adding. It makes seating and communication grouping much easier later.
One list. Every event. Zero confusion.
WedPlan keeps your full guest list in one place — tag by event, track RSVPs, send WhatsApp invites. Free to start.
Start free with Google
Pick a freeze date and actually use it
There is no Indian wedding where someone doesn't try to add names two weeks before the event. It will happen. The question is whether you have a system that handles it without unravelling everything else.
Set a freeze date — typically 3 weeks before the wedding — and communicate it clearly to both families. After that date, the caterer has confirmed numbers, the seating is being planned, and changes have real costs. Saying "the list is frozen" is much easier when you can point to a specific date you agreed on together.
"We froze the list at 380. Then my father-in-law added 12 people the week before. We ended up with 392 and an awkward call to the caterer." — Common story. Plan for it.
Build in a small buffer — if your venue holds 400 comfortably, freeze at 375. That buffer exists for exactly this situation.
Dealing with late additions gracefully
They're coming. Accept that now. The goal isn't to prevent late additions — it's to handle them without touching six different documents.
When someone gets added after the freeze date, add them to your system immediately with a clear "late addition" tag. This keeps your headcounts accurate and makes it easy to communicate the delta to your caterer — "we've had 8 additions since last week" is a much easier conversation than re-sending the entire list.
Also: send late additions their invite immediately, not in a batch later. Nothing makes a guest feel like an afterthought faster than receiving their invitation a week after everyone else.