Multi-day Indian wedding planning checklist

Know the sequence before you build the plan

Everything downstream depends on getting the shape of the celebration right first. A common North Indian arc opens with a roka or engagement to formalize the match, sometimes a year ahead. The final week brings the intimate, joyful functions: a haldi where turmeric is applied at home, a mehndi where a henna artist works through the bride’s side, and a sangeet or garba — the big musical night of performances and dancing. The wedding day itself carries the baraat, the groom’s dancing procession, into the ceremony under the mandap, the pheras or saptapadi around the sacred fire, and finally the vidaai, the bride’s emotional farewell. A reception, often the largest and most formal event, follows.

Regional and religious variations reshape this. A Gujarati wedding leans on the garba and the pithi; a Punjabi Sikh wedding centers on the Anand Karaj at the gurdwara with its four laavan — see the Anand Karaj wedding website page for that sequence. A Muslim wedding is built around the nikah and walima, covered on the Muslim wedding website page. Name your own functions and plan around them; the checklist below adapts to whichever combination is yours.

• Roka / engagement. Formalizes the match, often a year out — the moment the real planning clock starts.
• Haldi, mehndi, sangeet. The pre-wedding functions in the final days — intimate at home, then the big musical night.
• Baraat, pheras, vidaai. The wedding day itself: the procession, the vows around the fire, and the farewell.

A sample three-day Indian wedding plan

This fictional Friday-to-Sunday plan illustrates how to separate functions, invitations, and logistics. It is not a required ceremony order or a recommended guest count. Confirm your own sequence with your families and officiant, and allow travel, rest, and venue setup time between functions.

• Friday: mehndi and sangeet. 2 pm mehndi at the family home for 30 invited guests; 7 pm sangeet at Example Hotel for 120. Keep two invitation lists and confirm who needs transport between venues.
• Saturday: wedding ceremony. 10 am ceremony at Example Garden for 150 invited guests. Confirm the arrival instructions with the officiant and venue, and share any earlier gathering time with the people who need it.
• Sunday: reception. 5 pm reception at Example Hall for 200 invited guests. Confirm checkout and luggage arrangements for travelers, plus the caterer’s final-count deadline.

Turn invitations into a headcount for each function

In the fictional plan above, 120 people are invited to the sangeet; that is not yet a catering count. If 90 accept, 10 decline, and 20 have not replied, the current confirmed count is 90 and the follow-up list is 20. Track invited, attending, declined, and pending separately for each event rather than treating the full guest list as confirmed.

Make a worksheet with one row per person and a column for every function. Add household, contact details, and any transport notes you need to coordinate. Assign a family member or planner to check missing responses before each vendor deadline, and agree with the vendor how children, vendor meals, and late replies affect the final order.

Set booking deadlines for your dates and venues

If you have about a year to plan, use the timeline below as a working schedule, not a promise of vendor availability. Start by checking dates with the venues and officiant your celebration needs. Ask about access and setup time for each function, catering requirements, parking, and any restrictions that affect the ceremony. Record actual booking and payment deadlines from each vendor.

The functions have their own specialists. Ask a mehndi artist how many guests they can serve in the available time and whether you need additional artists. A dhol player and a DJ or live band for the sangeet, a choreographer if the families are performing, decor and a mandap designer, and transport for the baraat all sit in the middle of the timeline. Ask each vendor about availability before setting a deadline in your plan.

• 10–12 months: venue & pandit. Check availability with your venue, officiant, caterer, and photo-video team.
• 6–9 months: the specialists. Set deadlines with the mehndi artist, musicians, choreographer, and decor team.
• 2–3 months: logistics. Review transport and hotel arrangements against booking cutoffs; reserve earlier when needed.

A month-by-month checklist to adapt

Roughly twelve months out, the foundations: confirm the dates for every function with both families, agree a budget and who is contributing, and book the venue and pandit before anything else. Nine to six months out, secure the vendors that fill up first — caterer, photographer and videographer, the mehndi artist, and music — and start the guest list, because its size drives every other number.

Six to three months out is the detail stretch: order or tailor outfits (more on the counts below), send save-the-dates so out-of-town and overseas family can plan flights, finalize decor and the sangeet program, and arrange hotel room blocks. In the final three months you send invitations, collect per-function RSVPs, confirm menus and headcounts with the caterer, and settle the day-of timeline with every vendor. The last two weeks are confirmations and the small things — welcome bags for out-of-town guests, cash for shagun and vendor tips, the baraat start time circulated to the groom’s side.

• 12 months. Lock dates with both families, set the budget, book venue and pandit.
• 9–3 months. Vendors, guest list, outfits, save-the-dates, hotel blocks, and the sangeet program.
• Final 3 months. Invitations, per-function RSVPs, menu counts, day-of timeline, welcome bags, tips.

Outfits, guests, and the numbers people forget

Two things blindside first-time planners of a big desi wedding. The first is outfits: the couple typically needs a distinct look for each function — a haldi outfit that can get stained, mehndi and sangeet looks, the wedding lehenga or sherwani, and a reception outfit — which means several orders, each with its own tailoring and delivery window. Family members often coordinate too. Ordering from India adds shipping and alteration time you have to plan backward from the first event, not the last.

The second is guest scale and how uneven it is. For example, a fictional 200-person reception might sit alongside a 150-person ceremony, a 120-person sangeet, and a 30-person mehndi at home. Planning a single flat headcount over-caters some events and under-seats others. Building the guest list per function from the start — who is invited to which day — is what keeps catering, seating, and outfits for the wedding party all sane.

• An outfit per function. Haldi, mehndi, sangeet, ceremony, and reception each need a look — order early, especially from India.
• Uneven guest counts. The sample reception has 200 invitees and the mehndi has 30; neither number is a confirmed attending count.
• Family across two countries. Guests split between the US and India shape save-the-date timing, hotel blocks, and RSVP channels.

How Duva holds the whole plan

A checklist this size needs somewhere to live. Duva keeps one master guest list and lets you tag each guest to the functions they are invited to, so the haldi list stays small while the reception list holds everyone — and every event carries its own headcount for the caterer. That same list powers your Indian wedding website and your RSVPs, so the people you plan around are the exact people who reply.

Because so much of the family is overseas, Duva sends RSVP links by SMS to supported +1 numbers and WhatsApp to supported numbers outside +1. Guests open the link and complete a browser form. The wedding-site interface supports English, Hindi, and Gujarati; provide your own translated event notes and preview the exact guest page. The standalone party RSVP link currently uses English. Invitations and automatic reminders never use credits (a one-time $10 unlock covers the messaging), and the checklist, budget, and vendor tracker are free to keep — so the plan you build on this page has a home that costs almost nothing to run.

• One list, tagged per function. Assign each guest to the events they are invited to; every function keeps its own count.
• RSVPs here and in India. Send browser RSVP links by SMS or WhatsApp to supported numbers; guests respond on the linked form.
• Free to keep. The checklist and guest list are free; RSVP invitations and reminders never use credits.