The Indian Wedding Guest List: How to Build It, and How to Cut It

Every name is a multiplier, not a line item

Families think about the guest list as a social document. Caterers, hoteliers and planners think about it as a multiplier. Both are right, and the gap between those two views is where most Indian wedding budgets quietly break.

Here is the arithmetic that families rarely do out loud. A single uncle added to the list is not one plate. If your wedding runs a haldi, a sangeet, the muhurtham or pheras with a lunch, and a reception, and he attends all four, that is four covers. At an indicative 2026 range of Rs 1,600 to Rs 3,500 per plate for a good hotel or premium venue in a metro, one name has cost you roughly Rs 6,400 to Rs 14,000 before anyone has poured a drink. Add a spouse and it doubles. If they are outstation and you are hosting rooms, add two to three nights of accommodation on top. For the full cost model at each guest count, see wedding cost by guest count, and for how per-plate pricing actually works, wedding cost per plate in India.

This post is not about the money. It is about the process and the politics of producing the list itself, which is the harder problem. The cost pages will tell you what 400 guests costs. Nobody tells you how a family gets from an uncapped wish list of 900 names to a defensible 400 without three cousins refusing to speak to each other. That is what follows.

One framing worth adopting early: the guest list is not a popularity contest and it is not a measure of anyone’s love. It is a capacity allocation problem with an emotional overlay. Treat it structurally and the emotion becomes manageable. Treat it emotionally and it never ends.

Set quotas before anyone names a single person

The single biggest mistake is starting with names. Someone opens a spreadsheet, everyone begins adding, and within a fortnight there are 780 entries that nobody is willing to remove because every one of them now belongs to a specific person who will notice.

Do it the other way round. Agree the total first, then divide it, then let each list owner fill their own allocation. This is the three-list method.

The three lists

• Bride side list. Owned by the bride’s parents, covering their family, community, professional and social obligations.
• Groom side list. Same, owned by the groom’s parents.
• Couple list. Owned by the couple, covering friends, colleagues, college groups and chosen family.

A workable default split for an Indian wedding where both families are contributing is 40 percent bride side, 40 percent groom side, 20 percent couple. If one family is hosting and paying for a specific function, that family’s quota rises for that function. If the couple are older, self funding, or one family is much smaller, adjust openly rather than pretending the split is neutral.

Why quota first breaks the deadlock

Under quota first, the argument happens once, at the top, between four or five decision makers, over a single number. Under name first, the argument happens 200 times, at the bottom, between everyone, over specific human beings. The second version is the one that damages relationships.

Quotas also make cuts self policing. If the groom’s side has 160 seats and has listed 210 names, the groom’s parents cut 50. Nobody from the other side has to point at a name and say no. That is the whole trick: it moves the painful decision inside the family that owns it.

Set the quota against a real number, not a wish. Your total should come from a venue capacity you have actually confirmed, or from a budget ceiling you have actually agreed. Choosing the venue and the head count are the same decision, which is why choosing a wedding venue should happen alongside the first list draft, not after it.

Tier every name A, B or C

Once each side has filled its quota, tier every single name. Three tiers, no fourth, no half tiers.

• Tier A. The wedding is meaningless without them. Immediate family, grandparents, the aunts and uncles who raised you, closest friends, the people whose absence you would remember in twenty years. For most families this is 60 to 120 names in total across both sides.
• Tier B. Genuinely wanted, invite if capacity allows. Extended family you actually see, longer standing family friends, close colleagues, the wider college group.
• Tier C. Courtesy and reciprocity. Parents’ professional contacts, community and association members, families who invited you to their weddings, distant relatives who would be offended by omission but would not be devastated by it.

Using tiers against a capped venue

Tiers become operational the moment the venue caps you. Say the banquet holds 450 seated for the wedding lunch. You have 180 in tier A, 240 in tier B and 300 in tier C. Tier A plus tier B is 420. That is your wedding invite list, and 30 seats of tier C get in, chosen by a rule rather than by preference. Reciprocal invitations first is the fairest rule and the easiest to defend.

The other use of tiers is function allocation, covered below. Tier A gets everything. Tier B gets the big functions. Tier C often gets the reception only, which in Indian practice is a completely normal and non insulting invitation.

One discipline that saves arguments later: tier the name at the household level, not the individual level, and record the household size in the same row. A tier B entry reading ‘Rao family, 4’ is far more useful than four separate rows you later have to reconcile.

The politics, handled honestly

Here is the part most guest list advice skips, because it is written for a different culture. In India the wedding guest list is partly a public statement of a family’s standing in its community. That is not vanity. For a father who has attended 200 weddings in his trade association over thirty years, and been fed at every one of them, the invitations are an accumulated obligation. Telling him to cut 80 names is telling him to default on thirty years of reciprocity.

Reciprocal invitations

Reciprocity is the strongest single force on an Indian guest list and the least discussed. The practical approach is to make it explicit rather than let it operate invisibly. Ask each parent to mark every tier C name with a simple flag: did this family invite us to a wedding in the last ten years, yes or no. The yes list is close to non negotiable. The no list is where the real slack sits, and parents will usually cut it themselves once it is visible on a page.

Community and extended family expectations

In many communities there is an unspoken rule that if you invite one branch of an extended family you invite all of it. That rule is real and breaking it is expensive socially. The fix is to decide branch by branch, not person by person. Either the whole branch is in or the whole branch is out, and the decision is made once by the senior person in the family who understands the map. Half inviting a branch is the single most reliable way to cause lasting offence.

Practical language for saying no

Most of the difficulty is not the decision, it is the sentence. Some language that works, tested by planners on real families:

• Capacity, not preference. ‘The venue is capped at 400 and we are already over. We have had to keep the wedding to family and closest friends, and it has been painful on both sides.’
• Function, not exclusion. ‘The haldi is at home and only fits about 40 people. We would love to have you at the reception where we can actually sit and talk.’
• The couple as the reason. ‘They wanted something smaller than we would have done. We are respecting that.’ This is the most effective line available to parents and it is usually also true.
• Never explain by comparison. Do not say ‘we invited them because’. Any reason that ranks one guest above another will travel and will be repeated.

Deliver a cut personally where the relationship warrants it. A phone call from the parent, made before the invitations go out rather than after someone hears from a neighbour, defuses almost all of it. Timing matters more than wording. For how the wider etiquette works from the other side of the invitation, see Indian wedding guest etiquette.

Not everyone invited attends: the numbers that matter

Families make two opposite errors here, and both cost real money. The first is treating the invite list as the attendance number and catering for all 600 when 470 will walk in. The second, more common with destination weddings, is assuming the usual Indian drop off applies when the guests are travelling and have already booked flights, in which case attendance is far more certain than they expect and the food runs short.

Indicative attendance ratios that planners use as a starting point. Treat these as planning assumptions to be corrected by your own RSVP data, not as facts.

Two rules follow. First, a confirmed RSVP with a booked flight or a claimed hotel room is worth ten verbal yeses. Second, the drop off is concentrated in the smaller functions, not the wedding itself, so per function catering numbers should never be a flat percentage of the total.

The practical way to convert guesses into numbers is a save the date well ahead and a real RSVP mechanism, not a WhatsApp group. Read RSVPs and save the dates in India for how to run that, including how late the honest final count actually lands. Hand your caterer a confirmed number with a stated buffer, and put the buffer in writing so you are not arguing about it at 11 pm. What that buffer costs is covered in wedding catering cost in India.

Per function lists: most guests are not invited to everything

Outside a very small wedding, almost no Indian family invites the entire list to every event. Assuming otherwise is the fastest way to blow a budget, because it multiplies your largest number across your most expensive line.

A common structure for a three to four function wedding:

• Haldi or pellikuthuru. Intimate, usually at home or a small venue. 30 to 80 people. Immediate family and the closest friends only. Nobody expects a general invitation to this and it is the easiest event to keep small. See the haldi ceremony guide.
• Sangeet or mehendi. Wider. 40 to 70 percent of the full list. Family, friends, the people who will actually dance. Costs scale hard here because of production and bar, so this is a genuine decision point rather than a formality. See sangeet night cost.
• The wedding. The largest or second largest. Tier A and B in full, plus whatever tier C the venue allows.
• Reception. Often the biggest and the most selective in character. This is where community, professional and courtesy invitations belong. A reception only invitation is completely standard in India and carries no insult, which makes it the most useful pressure valve you have. See wedding reception cost.

Communicating a partial invitation without offence

The mechanism is the invitation itself. Print or send only the cards for the functions a household is invited to, and make the framing about the nature of the event rather than about the guest. ‘The haldi is a small family ritual at home’ does work that ‘you are not invited to the haldi’ never can. Keep the wording consistent across every household in the same tier, because guests compare cards. For phrasing, see Indian wedding invitation wording, and for what multi card sets cost to print, wedding invitation cost.

Do not improvise upward on the day. Verbally adding people to the haldi because they are in town is how a 40 seat home function turns into 90 people, no food and a genuinely unhappy bride.

Plus ones and children: write the policy first

Decide both policies before a single invitation is designed, write them down, and apply them without exception. Exceptions are what generate the complaints, not the policy itself.

Plus ones

Workable policies, in ascending order of generosity:

• Married, engaged or long term partners only. The most common Indian default and the easiest to defend across generations.
• Named partners only. If you know the person’s name, they get a card in their name. No anonymous ‘and guest’. This is administratively clean and prevents surprises at the gate.
• Open plus one for guests travelling alone. Reasonable and humane for outstation guests who will not know anyone.

State it on the invitation by naming the invited people explicitly. ‘Mr and Mrs Menon’ is the whole policy, expressed correctly. Where a family may misread it, one call from the couple settles it.

Children

Child free Indian weddings are rare and often unrealistic, because extended families travel as units. The more practical options:

• Children welcome throughout, with a kids meal count given to the caterer and a supervised area at the sangeet and reception.
• Children at the wedding and reception, not at the late night sangeet. Framed as a timing issue, which it genuinely is.
• Family children only, meaning the cousins’ children, not friends’ children. Say it as ‘we are keeping it to family children’ and it lands without argument.

Whatever you choose, count children as real covers. Caterers charge a reduced rate for under 10s at many venues, but they still occupy a seat, a room and a car. A 400 adult wedding with 45 children is a 445 logistics problem.

The cut exercise: you are 40 percent over capacity

This is the situation almost every family reaches. Venue holds 400. List is 560. Here is the sequence that works, in order, without re opening the whole list.

1. Freeze the list. No additions from any side until the cut is done. Announce it. Every addition during a cut resets the exercise.
2. Deduplicate. Same household on two sides, same person under two spellings, colleagues listed by both a parent and the couple. On a 560 name list this routinely recovers 15 to 30 names for free.
3. Convert, do not delete. Move tier C households from the full wedding to reception only. This is the single biggest lever and it offends almost nobody. Moving 80 people off a Rs 2,400 lunch onto a Rs 1,400 reception cover changes the budget materially without changing the relationship.
4. Cut the non reciprocal tier C. Households that have not invited your family to anything in a decade. Parents should make this cut themselves within their own quota.
5. Apply the branch rule. Whole branches in or out. Never partial.
6. Cut lapsed contacts. No contact in five years and no ongoing relationship. Old colleagues from a job left a decade ago, neighbours from a previous city.
7. Trim couple side inflation last. Wide college and work groups where you would invite eight to avoid offending three. Cut to the three.
8. Re count and stop. If you are still over after all seven steps, the problem is the venue, not the list. Either the venue is wrong or the number is. Go back to the venue decision rather than cutting into tier A.

Two things not to do. Do not cut by seniority, which reads as disrespect. Do not cut the couple’s friends to protect parents’ courtesy invitations without a conversation, because that is the resentment that outlives the wedding.

The tracking sheet: fields a real guest list needs

A guest list that is only names and phone numbers will fail you at the exact moment it matters, which is the week the caterer, the hotel and the transport desk all want different numbers from the same file. Build one sheet, one row per household, with these fields.

Keep one master file with one editor. Multiple versions circulating on WhatsApp is the most common cause of a wrong final count. Everyone else sends additions to the editor.

The rooms and arrival columns are what turn a guest list into a hospitality plan. They feed straight into the hotel room block and the wider outstation guest plan. What that hospitality costs sits in wedding hospitality cost, and the seating layout it eventually produces is covered in seating arrangement ideas.

When the list has to be locked

The list is not a document you finish once. It has three states and three deadlines, and missing the middle one is what costs money.

• Draft head count, 8 to 12 months out. Needed before you can shortlist venues at all, because capacity filters your options. This is the quota number, not names.
• Invite list locked, 3 to 4 months out. Needed to print invitations, size the room block, and confirm the venue and caterer minimums. After this point additions are individually approved, not open.
• Attending count locked, 7 to 14 days out. The number the kitchen actually cooks for. Your contract will specify the notice period for the final guarantee. Read it, because the difference between 10 days and 3 days of notice is real money.

These dates sit inside the wider schedule in the Indian wedding planning timeline and checklist. Venue and hotel availability is the constraint that decides how early the first two happen, and in peak season it is tighter than most families expect. See wedding booking lead time in India before you assume you have room to decide slowly.

Finally, hand the locked list to whoever runs the day. The gate, the welcome desk, the seating chart and the departure gifting all read from it. Which household gets a welcome hamper, which car meets which flight, who sits where: all of it is the guest list wearing different clothes. Feed it into the wedding day timeline and it does its last job properly.

Security and parking scale

• wedding security and bouncer cost
• valet and parking cost

Frequently Asked Questions

How many guests is normal for an Indian wedding?

There is no single normal. A tight family wedding runs 100 to 200 across functions, a mainstream urban wedding 300 to 600, and a large community or business family wedding 800 to 2,000 at the reception with far fewer at the ceremony. What matters is not the norm but the match between your number, your venue capacity and your per head budget. Work out the number you can host properly rather than the number your community expects.

How do you split the guest list between the two families?

A 40 percent bride side, 40 percent groom side, 20 percent couple split is a fair default when both families contribute. Adjust when one family is paying for a specific function, when one family is significantly smaller, or when the couple are self funding and want more of the allocation. Agree the split as numbers before anyone lists names, and let each side manage cuts inside its own quota.

Is it rude to invite someone only to the reception?

No. In India a reception only invitation is standard practice, not a slight, particularly for professional contacts, community members and wider family networks. It is one of the most useful tools you have for staying within venue capacity. Send only the reception card, keep the wording consistent for everyone in that tier, and do not explain it as a downgrade.

What percentage of invited guests actually attend?

For local guests, expect roughly 70 to 90 percent depending on how close they are. For outstation domestic guests, 40 to 60 percent of those invited. For international guests, often 25 to 45 percent accept, but nearly all who confirm and book flights do attend every function. Never cater off the invited number. Cater off confirmed RSVPs plus an agreed buffer, and see the RSVP guide for how to get reliable confirmations.

How do you tell a relative they are not invited?

Make it a phone call from the parent who has the relationship, made before invitations circulate rather than after someone hears it elsewhere. Frame it as venue capacity, not preference, and never compare one guest to another. Where possible convert rather than exclude: offer the reception instead of the wedding, or the wedding instead of every function. Timing and tone do more work here than the exact words.

When should the guest list be final?

Three points. A draft head count 8 to 12 months out, because it decides which venues you can even consider. The invite list locked 3 to 4 months out, so invitations can print and the hotel room block can be sized. The attending count locked 7 to 14 days out, per your caterer’s contractual notice period for the final guarantee. Check that notice period in writing early, because a short one costs more.

Sources and further reading

• Weddings in India (Wikipedia)
• RSVP (Wikipedia)
• Wedding invitation (Wikipedia)
• Haldi ceremony (Wikipedia)