South Asian weddings
How to Manage the Guest List for a 3-Day Indian Wedding
Keep one master guest list for the whole wedding, grouped by household, and tag each household
with the events it's invited to.
That single source of truth gives you per-event counts, address labels, and RSVPs without a separate spreadsheet for every day.
A 300-person, three-day wedding sounds like a logistics nightmare, and it can be if you let the list sprawl across five tabs and a group chat. It doesn't have to. Here's the way that actually stays calm.
1. Build one master list, not three
A three-day wedding tempts you into a list per event, which is exactly where the numbers start to drift. Instead, gather everyone into one list for the whole celebration. Import from a spreadsheet if you've got one, so you're not retyping names, and treat that single list as the truth every event draws from.
2. Group guests by household
Couples and families reply together, so group them into households rather than tracking loose individuals. A household like "Reena and Vikram Sharma, plus two kids" is one row to invite, one link to send, and one reply to track. That's what keeps a 300-person list manageable.
3. Decide the event tiers early
For most Indian weddings, close family and the wedding party get the full program, while wider circles are invited to specific events like the mehndi or the reception. Set these tiers before you send anything, because they drive your catering, your costs, and your invitation wording. A quick rule of thumb:
- Inner circle: every event, from the haldi to the reception.
- Extended family and friends: the mehndi or sangeet, plus the reception.
- Wider community and colleagues: the reception only.
4. Make plus-ones explicit
Decide plus-one rules per household, then set an allowed party size for each invite so guests confirm a partner or family by name rather than adding people you didn't plan for. Honestly, explicit plus-ones are the single biggest thing that keeps your final numbers from quietly creeping up.
5. Collect what each day actually needs
Different events need different details. The ceremony might need nothing beyond attendance, while a plated reception needs a meal choice and dietary notes. Capture addresses once, on the master list, so printed invitations and thank-you cards both pull from the same place.
6. Track RSVPs per event, live
Give each guest a private link that shows only their events and lets them reply to each one separately. Watch live per-event counts so you know exactly how many to cater for the mehndi, the ceremony, and the reception, and send gentle reminders to anyone who hasn't replied instead of chasing by hand.
A spreadsheet versus one connected list
A spreadsheet can hold names. It's the multi-day, multi-event part where it starts to strain.
| One connected list | Spreadsheet | |
|---|---|---|
| Per-event invitations from one record | Manual | |
| Live per-event headcounts | ||
| Guests reply themselves | ||
| Plus-ones capped by name | Hard | |
| Addresses and meals in one place | Scattered | |
| See who has not replied | Manual |
None of this means you need fancy software to get married. But once you're past about 40 guests across more than one day, a guest list manager that does per-event RSVPs earns its place fast, mostly by doing the counting and the chasing for you.
Common questions
Start with one master list for the whole celebration, then group guests by household and tag each household with the events they are invited to. The average Indian wedding hosts around 330 guests (WeddingWire India, 2024), so a single source of truth prevents duplicates and stops you maintaining a separate spreadsheet per day. That structure powers per-event counts, address labels, meal totals, and RSVPs without retyping names every time a cousin forwards a screenshot.
No. For a three-day Indian wedding, close family and the wedding party usually attend the full program, while wider circles join specific events such as the mehndi or the reception. Decide those tiers before invitations go out because they drive catering, seating, and wording. Marking event access per household early also stops last-minute guilt invites that blow your haldi headcount the week before turmeric paste is ordered.
Set plus-one rules per household before anything is sent, and encode an allowed party size on each invite so guests confirm a partner or family member by name rather than adding people you did not plan for. South Asian weddings often reply by household, which helps when elders respond for several relatives at once. Explicit party limits keep final numbers from drifting after you have already told the caterer a count.
Give each household a private link that shows only their events and lets them reply to each one separately, with meal choices where food is served. Live per-event counts then tell you exactly how many to prepare for the mehndi, the ceremony, and the reception without chasing replies across chats. OfficiallyTogether built this flow for multi-event South Asian weddings so the guest list and RSVP layers stay in one dashboard.
Lock tiers and household groupings before save-the-dates, then treat the list as living until your RSVP deadline. Ask for replies three to four weeks before the first event, or earlier if caterers need a plated count. Use one reminder a week before the deadline and a brief final nudge a few days out, each with the same private link, so the last ten percent reply without you calling every aunt individually.
Your wedding, in one calm place.
Build a free site, collect RSVPs, and keep every event and memory together. No credit card.
No credit card required.