Guest list politics: the aunt, the colleague, and the neighbour

Three days before my sister's roka, my mother handed me her phone with a face I recognise: the "we have a problem" face. Bua had called. Not to ask what time to reach, or what to wear. She had called to inform us that her husband's sister's family — four people I had never met, from a city I had never visited — would obviously be coming, "kyunki family hai."

At almost the same hour, a colleague messaged me: "Heard about the roka, congrats! Are we invited or is it family-only? No pressure haan." And that evening, our downstairs neighbour, the one who signs for my couriers, said with a smile that carried a full sentence inside it: "Beta, ghar mein function hai suna."

One list. Three completely different kinds of pressure. That week taught me that a guest list isn't really a counting problem — the counting is easy. It's a diplomacy problem, and almost all of the difficulty concentrates in three categories: the aunt, the colleague, and the neighbour. Get these three right and the rest of the list mostly sorts itself. This is the playbook I wish someone had handed me, with the decision rules and the exact messages I now use.

Why these three are where the fights happen

Most of your guest list is obvious. Parents, siblings, the friends you actually talk to, the cousins you grew up with — nobody argues about them. The friction lives at the edges, where an invitation stops being a personal wish and becomes a signal about relationships you don't fully control.

The aunt problem is about obligation you didn't choose — invites demanded on your behalf by the family's emotional map. The colleague problem is about where a boundary sits — how much of your work life crosses into your personal celebration. The neighbour problem is about proximity — people who will literally see the cars, hear the dhol, and smell the food whether you invite them or not.

They need different handling because the currency is different. With the aunt, the currency is family peace. With the colleague, it's professional comfort. With the neighbour, it's daily coexistence. Treat all three the same and you'll over-invite one and offend another.

The aunt problem: invitations you didn't ask to send

The classic version: an elder relative decides that their extended connections must be on your list. Bua's husband's sister. Tauji's daughter's in-laws. The family friend "jinke yahan hum har function mein jaate hain." From your side these are strangers; from the family's side, not inviting them is a slight that gets discussed for months.

Here's the rule I've settled on: the person who insists on the invite owns the relationship, and ideally owns the invite. If bua wants her sasural side there, the warmest and cleanest move is for bua to invite them — from her phone, in her voice. You provide the details; she extends the welcome. This does two things at once. It keeps the invitation genuinely warm (it's coming from someone who actually knows them), and it quietly makes the headcount her responsibility, which tends to make the number honest.

What you must not do is fight the principle in public. The circles-method math still applies — every name has a cost, and we've written the full framework in guest list planning for family functions — but you deploy that math privately with the decision-makers, not as a debate with the aunt herself.

Script — handing the invite back, warmly (Hinglish):

Bua, bilkul, unhe zaroor bulaana chahiye — aap unse zyada close ho, toh aap hi invite kar do na, aapke through message zyada achha lagega. Main aapko saari details bhej deta hoon: date, time, venue, sab. Bas ek baar poochh lena kitne log aa rahe hain, caterer ko count dena hai.

Script — the diplomatic decline, when the venue genuinely can't hold more:

Bua, main sach bata raha hoon — venue mein sirf 90 log ki jagah hai aur woh already full ho gaya hai. Is function mein toh bahut close family hi aa paayegi. Agli baar jab hum bada function karenge, tab zaroor unhe bulaayenge, promise.

Notice the second script never says "no" to the person; it says no to the space. That distinction is what keeps affection intact. And "agli baar" is not a lie if you mean it — Indian families have a lot of "agli baar."

The colleague problem: where does the office end?

Colleagues are hard because the line is invisible and everyone draws it differently. Invite one teammate and skip another, and Monday morning gets awkward. Invite the whole team to an intimate family puja, and you've turned a ritual into a networking event. Invite your manager and it feels transactional; don't, and it might feel like a snub.

The decision rule I use has one question at its centre: would I be genuinely happy to see this person at my dining table on an ordinary Sunday? If yes, they're a real friend who happens to work with you — invite them personally. If the honest answer is "we're friendly at work but that's the whole relationship," they belong to a lighter tier: a warm announcement, not a summons.

To keep it consistent (and defensible), pick a boundary before you send anything, and apply it to everyone equally. A boundary that works well:

Work relationship	Invite?	How to invite
Close work friends you meet outside office	Yes	Personal message or call, like any friend
Your immediate team	All or none — never a partial invite	One group note if you invite them; skip cleanly if you don't
Manager / skip-level	Optional; only if the relationship is genuinely warm	Personal, low-pressure line; make "can't come" easy
Wider office / other teams	Announce, don't invite	A share-after or a general "we celebrated" note

The most useful trick for the office is separating an announcement from an invitation. An announcement says "this happy thing happened / is happening" and expects nothing. An invitation asks someone to show up. Most colleagues only ever needed the announcement — they wanted to be told, not hosted.

Script — inviting a close work friend (English):

Hey! We're doing a small function for [occasion] on [date] at [place]. Would genuinely love to have you there — no formality, come as you are. Totally understand if the day doesn't work, but the invite is real, not polite. 🙂

Script — the team, when you're inviting all of them:

Team, quick personal one — we're hosting [occasion] on [date], evening onwards at [venue]. You're all warmly invited. Zero pressure to come, but if you're around, would love to see you there. Details + RSVP: [link]

Script — the graceful announcement, no invite implied:

Sharing some happy news — we're celebrating [occasion] this weekend with close family. Wanted you all to know! Will bring mithai to office on Monday. 😄

That last message is doing real work: it tells people, it pre-empts the "how come I wasn't invited" feeling, and the box of sweets on Monday closes the loop far better than fifteen half-hearted invitations would have.

The neighbour problem: proximity is its own invitation

Neighbours are the only category on this list who will witness your event regardless of whether they're on it. They'll see the shamiana go up, hear the music, watch the guests arrive. That visibility changes the etiquette: with neighbours, the goal isn't managing a headcount so much as managing goodwill on the street you have to keep living on.

The rule: scale the neighbour invite to the disruption, not to your closeness. A quiet at-home puja with fifteen relatives? A courtesy heads-up is plenty. A function with valet chaos, a DJ till 11, and cars down the whole lane? Now the neighbours aren't just optional guests — they're stakeholders in your evening, and a warm invite (even to just chai, even for just an hour) turns potential complaints into shared celebration.

There's also the offence-radius to respect. Within a small society or a tight colony, inviting some flats and not others is noticed instantly. The clean approaches are the extremes: invite the whole immediate cluster (your floor, the adjacent flats, the true colony friends), or invite none of them and simply give everyone a friendly warning about the noise and parking. The messy middle — three flats out of eight — is what starts the cold wars.

Script — courtesy heads-up, small function (Hinglish):

Namaste! Hamare ghar Sunday subah ek chhoti si puja hai, thodi aawaaz aur do-teen extra gaadiyan ho sakti hain 9 baje tak. Pehle se bata rahe hain taaki koi pareshani na ho. Aap sabko bhi chai pe zaroor aana — bilkul informal hai. 🙏

Script — genuine invite, bigger function:

Dear neighbours, we're hosting [occasion] on [date], evening onwards. Aap sab ghar ke paas hi ho, toh formally bulaana banta hai — please do come by, even for a little while. Parking thodi tight rahegi us din, isliye pehle se heads-up de rahe hain. Warmly, Flat [x].

Script — no invite, but keeping the peace:

Namaste sabhi ko — Saturday shaam humare yahan ek function hai, thoda noise aur parking ki dikkat ho sakti hai raat 10 baje tak. Advance mein maafi aur dhanyavaad aapke sehyog ke liye. Koi problem ho toh bejhijhak batayein. 🙏

A one-look decision map

When you're stuck on a specific name, run it through this:

• Is the pressure coming from a family elder, not from you? → Aunt problem. Hand the invite (and the count) back to the person who owns the relationship. Fight the math privately, never publicly.
• Is this a work relationship you're unsure about? → Colleague problem. Ask "dining table on a normal Sunday?" Yes = personal invite. No = announcement, not invitation. Never do a partial-team invite.
• Will this person see, hear, or be blocked by your event? → Neighbour problem. Scale to disruption. Go all-or-none within a cluster. A heads-up about noise and parking is non-negotiable either way.

The pre-send diplomacy checklist

Before your invitations go out, walk this once:

• List every "obligation invite" a relative has pushed onto you. Next to each, write who owns that relationship — that's who should send it.
• Decide your office boundary in one sentence, and check it applies equally to everyone. No exceptions that you'd struggle to explain.
• Separate your list into inviting vs just announcing to. Draft the announcement message too — it's the one people forget.
• For neighbours, decide cluster-wide: all or none. Draft the noise-and-parking heads-up regardless.
• Confirm nobody is getting a partial-team or three-out-of-eight-flats invite. Fix any you find.
• For every "yes," make sure you're capturing a real headcount, not a vibe — ask "kitne log aa rahe hain?" explicitly.

That last point is where the diplomacy meets the caterer. Once you've navigated who to invite, you still have to track who's actually coming — and soft answers from these exact three groups ("dekhte hain," "try karenge," "aa jaayenge shayad") are the ones most likely to wreck your final count. If you want to get better at reading and converting those, the dekhte hain decoder breaks down what each soft reply really means. And if your list has crossed the point where a chat scroll can't keep up, a personal-link RSVP tool like Inyeet lets each family confirm their own number — though for a fifteen-person at-home puja, honestly, a notebook and two phone calls still beat any app.

FAQ

An elder is insisting I invite people I've never met. How do I refuse without a family fight?

Don't refuse the people — hand the invitation to the elder who wants them there. "Aap unke zyada close ho, aap hi invite kar do, main details bhej deta hoon." It keeps the warmth genuine and quietly transfers the headcount to the person who asked. Only invoke the venue's real limit if you actually have to cut, and frame it as the space saying no, not you.

Should I invite my whole office team or nobody?

For your immediate team, it really is all-or-none — a partial invite is what creates the Monday awkwardness. For everyone beyond the team, switch from inviting to announcing: tell them the happy news, bring sweets to office, and skip the guest-list pressure entirely. Most colleagues wanted to be told, not hosted.

Do I have to invite every neighbour?

No — but you do have to warn every neighbour about noise and parking, and you should invite in clusters, not fractions. Invite the whole floor or none of it; three flats out of eight is what starts resentment. Scale the actual invitation to how much your event will disrupt their evening.

---

The one thing to take away: your guest list is a diplomacy exercise disguised as a spreadsheet, and the difficulty lives almost entirely in three people — the aunt, the colleague, and the neighbour. Hand obligation invites back to whoever owns them, draw one honest line at work and hold it evenly, and treat neighbours by how loud your night will be. Do that, and you'll spend the function enjoying it instead of explaining it. When you're ready to make the counting part effortless too, early access is here — but the diplomacy, that part is always yours.