Separate guest lists for each wedding event, without four spreadsheets

Keep one master guest list, one row per guest, grouped by household. Before adding names to any event, write a one-line rule for who each event is for, with a cap, a plus-one policy and a kids policy. Then mark which events each household is invited to, let the host of each event sign off on its list, and send each household only its own events. Each event’s “separate list” is just a filter of the master list, so nothing drifts.

That’s also how Joy’s editors put it in their guide to Indian weddings with different guest lists: build one master list, then label every guest by event. The rest of this guide is the part that takes real work: the rules, the edge cases and the conversations.

Nobody plans to have four lists. It happens one reasonable step at a time:

• The mehndi is at the bride’s family home or a small hall, so her mom starts a short list for it.
• The sangeet needs a dance roster, so a cousin makes a sheet of performers and their families.
• The groom’s family sends their reception names as a forwarded message or a photo of a notebook.
• The wedding website collects RSVPs, but only some guests use it, and the rest reply to whoever invited them.

By the time the caterer asks for a final count, nobody trusts any of the numbers. That’s almost exactly the post that started a thread on r/weddingplanning:

“I’m manually updating multiple spreadsheets and chasing RSVPs from guests for each event. Is there a better way?”

One reply puts the whole fix in two sentences:

“I would avoid having four (or more) separate lists. Just keep one master list and give each person the access to see/RSVP to events as needed.”

On r/DesiWeddings, someone using a 36-tab Western wedding spreadsheet asked for one built for 3 to 4 events with different guest lists. A commenter who had kept a whole folder of sheets still landed in the same place:

“I would suggest you keep the guest list on one sheet with different columns for the events and a simple Y / N for inviting them.”

If you already have the columns sorted, our Indian wedding guest list template covers the layout and the headcount formulas. Here we’ll focus on filling those columns in.

Most guest list fights aren’t about a person. They’re about a rule nobody wrote down. If the sangeet is “family and anyone who’s dancing,” the question “why is Rohan’s colleague at the sangeet?” answers itself. So before anyone adds a name, agree on five things for every event:

1. Who it’s for, in one line. “Women from both families and the bride’s friends.” “Everyone who’s performing, plus family.” “Everyone we’re inviting to anything.”
2. The cap. The venue’s comfortable capacity or the number the budget can feed, whichever is lower. A home mehndi has a cap even if nobody says it out loud.
3. The host and list owner. The family paying for or hosting the event signs off on its list, even when both families contribute names.
4. The plus-one policy. Named partners only, partners of a certain length, or nobody extra.
5. The kids policy. All children, family children only, or adults only.

The usual shape, which Desi wedding guides from Anvaya to ShubhLink describe in much the same way, is a funnel: the smallest, most private events are for immediate family and the closest friends; the mehndi and sangeet add extended family and the couple’s friends; and the ceremony and reception are for everyone, including parents’ friends, colleagues and the community. Your families may draw the lines elsewhere, and that’s fine, as long as you draw them before the names go in. If you need a refresher on what each event involves, see Indian wedding events in order and the per-event guides to the mehndi, haldi and reception.

Here’s how the rules looked for Anaya and Rohan, the fictional couple in our showcase plan, hosting a mehndi, a sangeet, the wedding ceremony and a reception over one long weekend. All of it is example data, not a benchmark.

With the rules agreed, filling in the list is mostly mechanical. Each household gets a row (or a group of rows, one per person), a side (bride’s, groom’s or both) and a tick for each event. In practice, the ticks fall into a few patterns:

• All four events: both sets of grandparents, aunts and uncles, first cousins and their families, the couple’s closest friends.
• Sangeet, wedding and reception: second cousins, family friends who are practically family, the couple’s wider friend group, and the men of families where the mehndi is mostly women.
• Wedding and reception: parents’ friends, older community members who’d want to see the ceremony.
• Reception only: colleagues, neighbors, business contacts, the people the parents “have to” invite.

Then check each column against its cap. If the sangeet comes out at 260 against a cap of 220, the rule is too loose or the venue is too small, and you’d rather find that out now than in RSVP week. Remember that invited isn’t the same as coming: run each event’s invited count through the guest attendance calculator before you decide anything is over the cap.

Rules handle most of the list. These are the guests that send people back to the family group chat. Our suggestions follow the example rules above; yours may differ.

Is a sangeet-only invitation rude?

Desi wedding writers disagree, so here are both sides. The ShaadiShop blog’s advice on inviting everyone to everything is blunt: “DON’T invite guests to the sangeet-only. It’s tacky on your part and insulting to the guest.” Reception-only, on the other hand, is standard almost everywhere.

On r/DesiWeddings, a poster planning a US wedding asked whether they could invite newer local friends to the sangeet only, after more late declines than expected for the wedding itself. They described the sangeet as just as grand as the reception. Their update:

“The friends have taken it really well so far and seem super excited”

It comes down to expectations. A guest who wasn’t expecting a wedding invitation will read a sangeet invitation as a bonus. A relative who expected the wedding will read it as a snub.

With multiple events, the list has to answer “with whom” as well as “who”. Joy’s Indian wedding guide calls out the same trap: “A guest might bring a plus-one to the reception but not to the intimate haldi.” A few rules of thumb:

• Name the partner, per event. “Kabir Shah and guest” invites argument. “Kabir Shah and Meera Kapoor” for the sangeet, wedding and reception doesn’t.
• Decide kids per event, not per wedding. Kids at a daytime mehndi are part of the fun. A late reception with a bar is another matter. Whatever you choose, say it on that event’s invitation, not in a message afterward.
• Count people, invite households. Desi families usually reply as one household, but caterers and chairs count people. Every event needs a per-person count even if one person answers for the family.
• Ask the dietary question once. Vegetarian, Jain, halal, allergies: collect them once with the RSVP and reuse them for every event’s caterer.

Merging the bride’s and groom’s lists is where most duplicate rows and most hurt feelings come from. What works:

1. Same columns for everyone. Send both families the empty list first: name, household, phone with country code, side, and a column per event.
2. One list, not a bride tab and a groom tab. Mark each household bride’s side, groom’s side or both. Sort by last name and phone number to catch people both families added.
3. Each event has an owner. Both families can suggest names for any event; the host signs off on its final list. When the groom’s family hosts the reception, their call on its list is final.
4. Agree on a cut-off date. After it, a new name for any event needs both families to agree. Lists grow quietly otherwise, and late additions make earlier “no”s look personal.
5. Share costs by event, not by headcount guesses. If the families split costs, each event’s final yes count is what the split should use. Our guide on who pays for an Indian wedding covers the common splits.

ShubhLink’s guide to inviting guests to only some functions makes the most useful point we’ve read on this: “Hurt comes from how they find out, not from the fact itself.” Some options, all of which work if you’re consistent:

• One main card plus an insert per event. Each household gets the inserts for its events only. On a Knot community thread about Mehndi, Sangeet and Reception invitations, couples describe exactly this: inserts per event, with replies tracked per event.
• Separate invitations from each host. The same thread suggests the family hosting each event sends its own invitation. It fits the list-owner rule above.
• A digital invitation per tier, or a personal RSVP link. Make one version per group (“Full weekend”, “Sangeet onwards”, “Reception only”) and check which version you paste every time. Better still, give each household a link that only shows its own events.

What to say when someone asks

Someone will ask. Keep the answer about the event, not the person, and say it the same way to everyone in the same group. Lines that work:

• “The mehndi is at home, and it’s just immediate family. We’d love to see you at the reception.”
• “The hall only holds 220, so we kept the sangeet to family and the people performing.”
• “The couple wanted the smaller events to stay small, and we’re respecting that.”

And two habits that prevent most of the questions: don’t post the full schedule in a group where not everyone is invited to everything, and ask close family to hold off on posting photos of the smaller events in big groups until after the reception. If it was an honest oversight, fix it fast with a call.

For the reminder messages that follow, our RSVP reminder wording guide has ready-to-send texts and emails, and the RSVP deadline calculator works back from each caterer’s final-count date.

A shared wedding website is the easiest place to leak the schedule. One poster on r/weddingplanning described exactly what they wanted before choosing a site:

“Ideally, i would want a flow where the guests enter their names or emails and only see the events they are invited to on the schedule.”

The big wedding sites handle this differently, according to their own help pages:

• Joy: you tag guests, then set an event’s privacy to “Specific guests” and pick the tags. Guests unlock the schedule by entering their name and see only their events (Joy: private events, Joy: multiple events).
• Zola: you tick the events each guest is invited to under “Events Invited To”, guests can only RSVP to those, and you choose whether each event is public on the website (Zola: choosing who’s invited, Zola: RSVPs for multiple events).
• The Knot: you mark guests as invited to each event in the Guest List Manager, can limit RSVPs to invited guests, and must enable each new event in RSVP settings (The Knot: adding guests to an event, The Knot: collecting RSVPs).

Whichever you use, test it: add a fake “reception only” guest, look them up on your own site from a private browser window and check what they can see. For a side-by-side look at the tools, see how PlanMe compares with Zola, Joy and The Knot, or the head-to-head PlanMe vs Joy.

A spreadsheet is fine while you’re building the list. Our spreadsheet vs app guide covers when it stops being fine. If you’re choosing a wedding guest list app for several events, check these before you import anyone:

1. Can each guest be invited to some events and not others?
2. Does each household get one reply that covers only its own events, with a yes or no per event?
3. Can an uninvited guest see the private events anywhere: the schedule, the RSVP form or a reminder?
4. Does every event show its own invited, yes, no and pending count?
5. Can you set plus-ones and see dietary needs per guest, not just per household?
6. Can you tag guests by side and message a group, such as everyone who hasn’t replied?
7. Can both families and a planner edit the same list, without sharing one login?

Our roundup of the best wedding websites for multiple events runs six tools through tests like these, including where others do better than PlanMe.

PlanMe.Club is our product, built for weddings with several events and two families. In PlanMe, each event (mehndi, sangeet, wedding, reception and so on) is called a festivity. Here’s how the method above maps onto it:

• Each event added once. Add every event with its own date, venue and schedule. See festivities.
• One list, tagged by side. Import your sheet from CSV or Excel, group guests into households, tag them bride’s side, groom’s side or anything else, and choose exactly which events each guest is invited to. See guest management.
• A private RSVP link per household. Each household gets a link by email or text that shows only the events its guests are invited to, with no login, and everyone answers for each event. Guests can also look themselves up on your wedding website. See RSVP for multiple events.
• Counts per event. Every event keeps its own accepted, declined and pending count on the guest list.
• Plus-ones with approval. Add plus-ones and companions, with an approval step.
• Messages by tag or RSVP status. Send email or SMS broadcasts to a tag such as “groom’s side” or to everyone who hasn’t replied. If you want to message just one event’s guests, tag them for it. See guest email and SMS.
• Both families in one plan. Invite parents, siblings or a planner as collaborators and choose which parts of the plan each can use. See team and collaboration.

What PlanMe doesn’t do, so you can plan around it: it sends by email and SMS, not WhatsApp, and it doesn’t print invitations. Seating is manual, per event, from the guests who accepted, using the seating chart.