The two-family planning problem

South Asian weddings are rarely planned by a couple alone. They are negotiated by two kinship systems that may not share a language of money, hospitality, or what 'simple' means. Love is not the hard part. The hard part is a shared source of truth.

The real problem

Each side often believes it is already compromising. One family hosted a cousin's 700-person walima last year; the other flew in from overseas for a backyard mehndi. Without a neutral ledger of guests, deposits, and decisions, every suggestion sounds like criticism.

WhatsApp multiplies this: parallel threads, screenshots, and aunts appointing themselves project managers. The non-obvious insight: you do not need fewer opinions. You need one artefact both sides treat as current — timeline, guest counts, and budget owners.

Money without mythology

Payment norms vary by tradition and by family modernity. Some Muslim weddings treat walima hospitality as the groom side's honour; some Hindu families still speak in 'bride side / groom side' event ownership; many Sikh diaspora couples pool costs and ignore the scripts. Mythology from a generation ago can be a poor fit for Toronto incomes and Toronto venue prices.

A diplomatic approach: list events, estimate each, then propose ownership or split percentages in writing. Avoid vague 'we'll help.' Help is not a number. [PLACEHOLDER — note community-specific norms you want referenced after review.]

• Name a budget owner per event (person, not 'the family')
• Separate 'hosting at home' costs from venue deposits
• Agree what happens if guest count rises 20% after invitations
• Keep mahr and ceremonial gifts conceptually separate from party budgets where relevant

Merging guest lists without war

Equal headcount splits feel fair and often fail — one side may be locally rooted with 200 must-invites, the other smaller and overseas. Fairness can mean equal priority tiers instead of equal totals: parents' must-haves, couple's must-haves, then soft invites for reception only.

Ceremony caps are sacred when the space is small (gurdwara, home Nikah). Reception lists flex. Put both in a tool that shows event-level invites so nobody 'accidentally' brings twelve additional cousins to the morning.

Decision rights

Decide who has final call on: date, venues, ceremony officiant, alcohol policy, and open-versus-limited guest additions. Everything else can be collaborative. Couples who skip this conversation discover it during a deposit deadline.

What actually helps

Shared guest lists with event tags. Budgets with event tags. A timeline both mothers can open without downloading an app they hate. That is the product gap Ghoonghat is built around — not another Pinterest board.

Diplomacy is not silence. Diplomacy is making the plan visible enough that love does not have to compete with logistics in every conversation.