Desi Wedding: Multi-Day, Multi-Family, One Platform

A desi wedding is not an event. It is a system. Over the course of three to seven days, two families host between four and twelve distinct functions, at anywhere from one to six different venues, for an overlapping set of 200 to 800 guests, many of whom are flying in from elsewhere. Each function has its own vendor list, its own timeline, its own dress code, its own dietary expectations, and its own cultural-familial negotiation attached. When people say a desi wedding takes eighteen months to plan, what they actually mean is that the logistics of one of these is closer to a small industry convention than to a single-day event.

This piece is for the couple, or the parent, or the planner in the middle of this system who is trying to figure out how to hold it together. I've planned two desi weddings in my family (one of them my own), attended thirty-one by the age of twenty-eight, and consulted on more than a dozen as an editor. The thing that makes or breaks them is not venue or decor or outfits. It is coordination.

Table of Contents

• What counts as a desi wedding?
• The three to seven day structure, in practice
• Multiple venues: the real coordination problem
• Multi-family politics: who hosts what, and how to talk about it
• Cultural factions inside the family
• The guest list problem at scale
• Where planning software actually earns its keep
• A realistic 18-month planning timeline
• Frequently Asked Questions
• Sources and Further Reading

What counts as a desi wedding?

"Desi" is a pan-South Asian self-descriptor, broadly covering weddings with roots in India, Pakistan, Bangladesh, Sri Lanka, and Nepal, plus their diasporas. In this piece I'm using it primarily to refer to Hindu, Sikh, Muslim, and Jain weddings that share the multi-day, multi-event structure most common in the North Indian and Punjabi traditions. The planning logic applies broadly, even when the specific ceremonies differ.

The unifying feature is that there is no single wedding day. There is a wedding week, with each day anchored by a distinct function that has its own guest list, venue, vendors, and ritual purpose.

The three to seven day structure, in practice

Here is a typical five-day desi wedding calendar for a North Indian Hindu wedding with both families in the diaspora:

Day 1, Wednesday: Arrival and Ganesh Puja. Out-of-town family arrives. A small puja is held at the bride's family home or the hotel, invoking Ganesh for an obstacle-free wedding. Small event, 30 to 50 people, mostly family.

Day 2, Thursday: Mehndi and Haldi. Late morning haldi at the bride's hotel suite or family home, 40 to 80 people. Evening mehndi-sangeet combined at a banquet hall, 200 to 400 people.

Day 3, Friday: Jaggo or rehearsal dinner. A Punjabi jaggo in the late evening, 40 to 80 people, for the bride's side. Groom's side may do a separate dinner.

Day 4, Saturday: The wedding. Morning baraat and pheras or Anand Karaj, 300 to 500 people. Lunch hosted by the bride's family. Evening reception, 400 to 600 people, hosted usually by the groom's family.

Day 5, Sunday: Brunch and farewell. Post-wedding brunch, 60 to 150 people, often at the couple's or groom's family's hotel. Vidaai and family departures.

Multiply by family complexity, regional tradition, and the number of events both sides want to host, and you get from five days to seven. Abbreviated weddings compress this to three days by combining events: haldi and mehndi into one afternoon-evening, sangeet and jaggo into one night, ceremony and reception on a single Saturday. A three-day desi wedding is still three long days, but it is achievable.

Multiple venues: the real coordination problem

In the simplest case, all events happen at one hotel: the mehndi in the ballroom Thursday night, the haldi in the poolside suite Friday morning, the ceremony in the garden Saturday morning, the reception back in the ballroom Saturday night. This is the dream setup, and it exists at a handful of Indian-wedding-specialist venues in places like Dallas, Toronto, New Jersey, and the Bay Area.

In the more common case, events are spread across:

• A home or smaller venue for the puja and haldi
• A banquet hall or hotel ballroom for the mehndi and sangeet
• A gurdwara or temple for the ceremony
• A different hotel for the reception
• Another venue for the post-wedding brunch

That's five venues in five days. Each venue has its own vendor list, its own setup and tear-down time, its own access rules, and its own point of contact. Your photographer needs to know exactly when and where to be at six different moments. Your caterer may or may not be the same across events; sometimes one caterer handles three events and a different one handles the gurdwara langar.

The logistical principle that keeps this from collapsing: one master schedule, visible to every vendor, updated once. Not a WhatsApp thread. Not a Google Doc that someone forgot to share with the DJ. A single source of truth with every event's venue, time, vendor arrivals, guest transport, and cultural-ritual specifics.

Multi-family politics: who hosts what, and how to talk about it

Historically in North Indian Hindu weddings, the bride's family hosts the mehndi, the ceremony, and the wedding lunch, while the groom's family hosts the sangeet (in some traditions), the baraat, and the reception. Punjabi and Sikh tradition typically has the groom's family more involved in hosting evening events. Gujarati tradition splits events by ritual specificity.

In the diaspora and in modern urban India, these lines have softened. Couples pay for some events themselves. Both families co-host certain events. Costs are sometimes split proportionally to guest list contribution.

The conversation that no one wants to have but everyone has to: who is paying for what, and who is deciding what. Have this conversation in the first eight weeks of planning, not the fifth month. It should cover:

• Which events are being held, and who is leading the planning for each
• Who is paying for each event, in full or split, and what the ceiling is
• Who makes decisions on vendor selection for each event (one decision-maker per event, ideally)
• Whether the two families will share any vendors (photographer, decor, DJ)
• How overage costs will be handled (they will happen)

A note on tone. These conversations are easier when both sets of parents feel they are being consulted as equals. In traditional frames the bride's family has been positioned as a more deferential host, and this has not aged well. If you are planning a wedding in 2026, the families should be at the table as peers.

Cultural factions inside the family

Even within a single wedding, there are usually two or more cultural lineages in play, each with different rituals, expectations, and sensitivities. A few common scenarios:

• A Punjabi bride marrying a Tamil groom. Baraat energy versus Carnatic morning ceremonies. Usually resolved by letting each side anchor one day.
• A Gujarati bride marrying a Bengali groom. Pithi versus gaye holud. Different garland and sindoor traditions. Resolved by performing both, sequenced.
• A Sikh bride marrying a Hindu groom. Anand Karaj versus pheras. Most couples do both, one per day, with legal registration happening once.
• An observant Hindu groom marrying into a non-observant Hindu family. Pandit selection, length of ceremony, diet at events all become discussions.
• A desi couple with a non-desi partner. Integration of Western rehearsal dinner, first dance, and vows into a traditional multi-day format.

The principle that works: everyone gets their ritual. Everyone does not necessarily get it at the same moment or in the same event. Split the days or split the hours. A 45-minute Anand Karaj on Saturday morning and a 30-minute Hindu symbolic ceremony on Sunday morning is a legitimate and increasingly common solution.

The guest list problem at scale

A 400-person wedding with four events is not a 400-name list. It is more like 1,200 to 1,600 guest-event combinations. Some guests attend every function. Some attend only the reception. Some fly in Friday and leave Sunday. Some are immediate family and come to everything including the intimate puja.

To manage this well, every guest should have:

• Name, relationship to couple, and family side
• Which events they are invited to
• Which events they have RSVP'd yes to
• Contact info
• Dietary restrictions
• Hotel and transportation needs (if applicable)
• Plus-one and children details
• VIP or seating priority notes

For a 400-person wedding with four events, manually tracking this in a spreadsheet is possible but painful. Every change (a cousin adds a plus-one, a great-aunt can no longer make the ceremony but still wants the reception) cascades across multiple event headcounts and catering orders. RSVP'd's cultural wedding profile is built to hold this kind of multi-event, multi-family guest data in a single place, so that when you update Auntie Rukmini's status, every downstream headcount updates automatically, and your caterer gets the updated number without you having to re-email them.

Where planning software actually earns its keep

Desi wedding planning has three recurring failure points, and software solves them in different ways.

Vendor coordination. Ten to twenty vendors per wedding, each with a contract, a deposit schedule, a scope of work, and a day-of schedule. A CRM with automated reminders for deposit due dates, contract reviews, and timeline confirmations prevents the most common failure (a missed deposit leading to a cancelled booking). Our vendor CRM includes contract parsing that pulls key dates and deliverables out of vendor PDFs, which is useful when your mother has a filing cabinet with 18 contracts and nobody is sure when the next dhol deposit is due.

Guest management. As discussed above, a 400-person multi-event guest list is the kind of thing that breaks a spreadsheet within three months of planning. Dedicated guest management with per-event RSVP tracking, automated reminders, and dietary filters saves dozens of hours.

Day-of coordination. Every desi wedding has a moment where the wrong vendor is at the wrong venue. Our day-of coordination agent, which pulls together vendor arrival times, event setups, and cultural ritual cues into a single timeline accessible from any phone, addresses this. The alternative is a planner with a binder and a radio, which is what my mother had in 2011, and she spent the wedding lunch shouting into a hotel phone.

For self-planning couples with smaller weddings, spreadsheets plus WhatsApp plus a shared Google Drive will work, barely. For weddings over 250 guests or five events, dedicated software is the difference between a stressful weekend and a disaster.

A realistic 18-month planning timeline

Month 18 to 14: Family alignment, budget, date. Both sets of parents, the couple, and any close decision-makers (elder aunties, older siblings) agree on total budget, host structure, and dates. Book the main ceremony venue and reception venue. Book the priest or granthi. If using a planner, book them now.

Month 14 to 10: Big vendors. Photographer, videographer, caterer, decorator, DJ. These are the vendors who book out 10 to 14 months in advance for peak desi wedding season.

Month 10 to 6: Supporting vendors and events. Mehndi artist, dhol players, bhangra troupe, horse, florist, outfits (especially bridal lehenga, which can require 4 to 6 months of custom tailoring), jewellery, guest invitations.

Month 6 to 3: Logistics. Guest list finalization, invitation sends, hotel blocks, transportation planning, permits (for baraat route, outdoor events), dietary and VIP tracking, rehearsal scheduling.

Month 3 to 1: Tightening. Final vendor timelines, day-of schedules, seating arrangements, final catering headcounts, cultural ritual specifics confirmed with priest or granthi, welcome bags, emergency contacts.

Week of the wedding: Hand over to planner or day-of coordinator. You, the couple, should be doing as little day-of operations as possible. Your job for the week is to show up and be present.

Frequently Asked Questions

Sources and Further Reading

• The Knot, Multi-Day Wedding Planning Guide
• WeddingWire, South Asian Wedding Planning Resources
• Carolyn Henning Brown, "The Hindu Wedding: Tradition and Adaptation," Journal of Ritual Studies
• Shalini Shankar, Desi Land: Teen Culture, Class, and Success in Silicon Valley (Duke University Press)
• Vogue India, Big Fat Indian Weddings
• Martha Lagace, "Managing the Big Indian Wedding," Harvard Business School Working Knowledge