How to make a wedding guest list for 5 functions

Four hundred people for the reception. Sixty for the haldi. Twenty five in the room for the pheras, and two of those twenty five are being argued about at this very moment.

Then there is one invitation, and it tells everyone about everything.

That last part is the whole problem, and it is the half most wedding guest list advice skips. Make tiers, everyone says, and then stops. Tiers are the easy part. Telling four hundred people about their tier without anybody feeling sorted into one is the part that takes judgement.

Stop keeping one wedding guest list

The default spreadsheet has a column called Invited with a tick in it. It works right up until the moment you need five different lists out of it, at which point you start filtering by hand at one in the morning and somebody who should have been at the sangeet is not.

Build it the other way round. Write down your functions first. Then, for every name, decide which functions that name belongs to. The unit of the decision is the circle, not the person, so you are making about six decisions rather than four hundred.

Guest list tiers, and who owns each one

Numbers vary wildly between families and there is no standard shape, so the useful part of this table is not the sizes. It is the last column. Almost every guest list argument is really an argument about who gets to decide, and it goes quieter once that is settled in advance.

Give each list owner a number rather than a veto. "Papa, your side of the reception is one hundred and forty" is a conversation about arithmetic. "Papa, we are not inviting the Guptas" is a conversation about the Guptas, and you will lose it.

Decide the smallest function first

The instinct is to start with the reception, because it is the biggest number and feels like the main event. Start at the other end instead.

The pheras list, or whichever ceremony has the smallest room, is the only list where an extra name has a real cost. Everywhere else an extra name is a plate. Here it is a chair that somebody else was going to sit on, and the person who does not get it will notice for a long time.

Settle that list while everyone is still calm and nobody has momentum. Every list after it gets easier, because the argument that actually binds has already been had.

When each list has to be locked is a question of dates rather than politics, and the wedding invitation timeline works those dates backwards from the wedding for you.

The politics, honestly

Your parents' list will be longer than yours and full of people you cannot place. This is not them missing the point of your wedding. It is them attending to a set of obligations that are real, that predate you, and that get settled at events like this one. Somebody came to your cousin's wedding, sat through a long evening, and gave a gift. That is now owed back.

Which is why the reception is the right place to be generous and the small functions are the right place to hold firm. The reception exists partly to discharge exactly this kind of obligation, and a hundred extra people at it cost money but cost nothing else. The haldi at your house cannot absorb a social debt without stopping being the haldi at your house.

Two specific fights worth pre-deciding, because they arrive in almost every wedding.

Colleagues. Invite the ones you would still speak to if you changed jobs tomorrow, and invite your boss only if that test passes. Inviting the whole team because it would be awkward not to is how twelve people you do not know end up at your reception. If the office needs acknowledging, acknowledge it at the office.

The cousin's new partner. Invite them. The relationship might not last, but the memory of being kept out will, and a cousin's partner is a household member the moment your family treats them as one. This is one of the few places where being wrong is nearly free in one direction and expensive in the other.

How to tell someone they are invited to two functions out of five

This is the part that goes wrong, and it goes wrong in one specific way.

Never send anybody a list of functions they are not coming to. Tell them what they are invited to, warmly and completely, and stop there.

An invitation showing six functions with two of them marked for you is a receipt. It reads as a ranking, because it is one. An invitation showing two functions is just an invitation, and the person receiving it has no reason to count what is missing.

The phrasing that works is short and has no apology in it. "We would love to have you with us for the sangeet on the 12th and the reception on the 14th." That is the whole message. Do not add "the other functions are family only", because you have now told them about the other functions, which is the thing you were trying not to do.

If they ask directly, answer honestly and briefly, and use a reason that is true. If the mehendi is family only, say it is family only. Do not say the venue is small when it is not, because at a wedding this size somebody will mention the actual venue in front of them within the week.

If a broadcast is how your family sends everything, read how to send a wedding invitation on WhatsApp before you point one at a tiered list.

One invitation, different links

You publish one invitation with every function in it. Your draft always holds all of them. What changes is the link you hand out.

The link you send the office shows only the reception. The one you send your cousins shows the sangeet and the pheras. The family link shows everything. Same website, same address, same photos and music and story, and each guest opens it to a page that looks like it was written for them, because from where they are sitting it was.

Nothing about who saw what is stored anywhere. The choice of functions lives in the link itself and nowhere else, so there is no hidden record of tiers sitting in your account waiting to be screenshotted. Rename an event later and the links you already sent keep working, because they point at the event, not its name.

In your dashboard you can save these groupings with names you choose, up to twelve of them, so in March you can send the office link again without trying to remember which boxes you ticked in January. You can also add a guest's name to a link, so the invitation opens with "To the Gupta Family" instead of a generic greeting.

What it does not do, and we would rather say so than let you find out: a link can be forwarded. Send your brother the everything link, he passes it to a friend, and that friend sees everything. Treat these links as discreet rather than secret. Discreet is what the situation calls for anyway, because what you are avoiding is a guest reading a list of functions they were left off, not a stranger learning your mehendi timing.

None of this depends on the design you pick. Every invitation in the catalogue carries the same per function links, so choose on how it looks and how it reads.

The spreadsheet is fine, if you fix one thing

You almost certainly do not need guest list software. Counting is the easy half of this problem and a spreadsheet already counts.

The fix is to make each row a household, not a person. Indian invitations go to households. A row per person gives you a list that is technically accurate and operationally useless, because you cannot ring a person-row and ask how many of them are coming.

Columns worth having: household name, the head of it you will actually contact, a phone number, the number of people you expect, which functions they are invited to, who in your family is chasing them, and what they said. The chasing column is the one people leave out and then regret, because without it two cousins ring the same aunt and nobody rings the other four.

Filling in the last column is a separate problem, and getting guests to actually reply is not solved by adding another column.

Keep the sheet for counting. Use the links for telling. A spreadsheet counts heads and counts them well, and it cannot stop you mentioning a function to the wrong person, which is the half of this job that costs something when it goes wrong. That half is what your invitation is for.

When someone turns up to a function they were not invited to

It will happen. Usually a relative who assumed, or someone an invited guest brought along.

Feed them. Seat them. Do it warmly and immediately, and never let it be handled at the gate by a cousin with a list and a sense of duty. A twenty year grudge costs more than a plate of food, and the person who turned up uninvited is almost never being rude. They thought they were included, which at an Indian wedding is a reasonable thing to think.

Prepare for it instead of policing it. Tell the caterer a buffer number for each function. Ask the venue what it would take to add ten chairs. Brief one person per function, ideally a family member with no other job that day, whose entire role is to say yes to everything and sort it out afterwards.

The one place you can legitimately hold a line is a function with a genuine hard limit: a temple with a capacity, a ceremony with fixed seating, a venue that needs names for gate passes. When that is true, say so in advance, in writing, to everybody. A limit announced three weeks out is a fact. A limit announced at the door is an insult.