An Indian wedding is really four main events, two smaller ones, and a handful of micro events, all packed into a few days. Each one carries its own cultural significance, own guest list, own food, and its own celebration.
The wedding is only as strong as its weakest event. Three events can run seamlessly, but if the guest count or one food item runs off at the fourth, then the entire wedding feels disorganised. The guests leave disheartened and the couple is left disappointed.
I have seen a wedding where the baraat arrived three hours late because baraatis could not stop dancing. The ceremony ran late, the food service ran late, and everything in between slid right along with it.
If you search for wedding day timeline" you will find a hundred articles about the same twelve-hour schedule, one day: hair and makeup at 8, ceremony at 4, send-off at 11.
That is no patch to a Desi wedding, where three or four days of wedding ceremonies. This guide covers how to actually build the timeline for one: the master schedule, the per-event schedules, the vendor coordination, and the visibility or vendor collaboration problem nobody warns you about.
A single-day wedding has one timeline with many activities. A multi-day Desi wedding has four problems that generic timeline advice never touches:
For what happens inside each event and why, our Indian wedding timeline guide walks through every tradition day by day. This piece is about how to schedule all of it.
Every family's lineup is different, but here is how the events typically stack up for a North Indian Hindu wedding, which this guide uses as its running example. South Indian, Sikh, and Muslim weddings each have their own structure (the anchor guide covers the variations), and the scheduling method below works the same for all of them.
The muhurat, venue load-up and end times with noise curfews. These are set before you plan anything. Put them on the calendar first and build everything else around them.
One timeline per event, plus a master schedule showing how the days connect. The master view is for you and your planner.
Outfit changes, venue turnarounds, and travel between locations take real time, so give them real entries with real durations.
Make sure you have their information with backup in contacts. Arrival time & individual production schedule.
Vendors, guests, and family each need a different view of the same day. Decide visibility activity by activity while you build, not by making separate documents afterward.
Send everyone their version at least a week out, then accept that something will move. The baraat leaves late because baraats always leave late; the real test is how fast everyone gets the updated version.
Here is a condensed version of a common three-day structure. Treat it as scaffolding:
Guests should see only the events they are invited to. A sangeet-only guest does not need the wedding day schedule, and out-of-town family needs all the days plus hotel and transport details.
Vendors are the opposite. They work together, not in isolation. The bartender needs the lighting team to throw the lights so the bar is actually visible. The DJ and the photographer work hand in hand, because nobody catches the grand entrance without knowing the DJ's cue. So vendors need to see most of everybody's activities: what is happening, where, and who is handling it. And when something changes, everyone needs to know instantly, not after three phone calls.
Run this off a single spreadsheet and you will spend the wedding week copy-pasting rows into separate documents, praying you did not send the wrong version to the wrong person. It is not a formatting problem. It is a data problem: one schedule, shown differently to every audience, updated for everyone the moment it changes.
Most wedding planning apps are built around one assumption: one day, one event, one guest list. They have no concept of a mehndi, no way to give the dhol player a different schedule than the caterer, and nowhere to put a muhurat.
AyeDu's free day-of coordination tool was built for exactly this structure. The workflow follows the same logic as this guide:
Most vendors receive a schedule a week or even a month before the wedding, and anything that changes after that reaches them secondhand, if it reaches them at all. When I talked to vendors at a WIPA conference about live schedule links, this was the part that got them excited: the schedule they open on the morning of the event is always the current one. No chasing the planner, no working off last Tuesday's PDF.
Every vendor you add also comes with a starter task checklist for their role, so nothing gets forgotten between booking them and the wedding day.
Most span three to five days: four main events (haldi, sangeet, wedding, and reception) plus the smaller and micro events around them. Some families compress everything into one packed weekend.
A common order is ganesh pooja, haldi, mehndi, sangeet, wedding ceremony, then reception. Names and order vary by region and family, and your pandit and elders have the final say.
A Hindu ceremony block, including the baraat, typically runs three to four hours. The muhurat sets the start time. Confirm the ritual list with your pandit, since inclusions and the number of pheras vary by family.
You are planning ten events, not one, and your timeline tool should know the difference. Set your events up once in AyeDu and share links that stay current no matter how many times the plan changes. Free for couples, built for weddings like yours.