The question couples ask most often isn't "what functions do we need?" — it's "how do we fit all of them into the days we have without everyone running on empty by the pheras?" The functions are usually decided early. The schedule is where things quietly fall apart.
Multi-day Indian weddings fail at the transitions. The gap between the haldi ending and the evening sangeet beginning is almost always too short. The morning after a late-night sangeet is almost always underestimated. The time required to move 200 people from a hotel to a wedding venue and get them seated is almost always optimistic by 45 minutes.
What follows are three real working schedules — for three-day, five-day, and seven-day weddings — built around how these events actually run, not how they look on a mood board. Each schedule is a starting point, not a prescription.
Before You Build Any Schedule
Three things that will save you more time than any template. First: agree on the function list before you map dates. Adding a function mid-planning cascades into every vendor, guest communication, and timeline downstream. Second: identify your fixed anchors — the wedding ceremony time is typically set by the pandit and isn't negotiable. Build everything around it, not the other way around. Third: accept that every function runs 30–60 minutes late by default, and build that into your schedule rather than assuming you'll be the exception.
The other variable that matters: guest geography. A wedding where most guests are local has different morning-arrival logistics than one where 40% are flying in. Outstation guests need shuttle coordination, room key logistics, and more lead time on every schedule communication. Factor this in before you set any timing.
The 3-Day Wedding Schedule
The three-day format is the most common for city weddings and destination weddings with a tighter budget. It typically covers: a combined mehendi-sangeet evening, the wedding ceremony with haldi in the morning, and a reception. It's tight — but achievable when the run-of-show is planned explicitly.
The biggest risk in a three-day schedule is Day 2: haldi in the morning followed by the wedding ceremony the same evening. This works logistically only if the haldi ends by 1 PM and the wedding venue is a short distance from where guests are getting ready. If either condition isn't met, consider moving haldi to Day 1 as a standalone afternoon event.
The 5-Day Wedding Schedule
The five-day format gives you breathing room that the three-day doesn't. The extra days are typically used to separate the mehendi and sangeet into distinct events, add a dedicated haldi day, and give the couple a genuine morning before the wedding rather than a rushed one. It's also the format that most naturally accommodates outstation guests who arrive a day before the first function.
The risk in five-day weddings isn't timing — it's energy. By Day 4, guests who've travelled are running low. The wedding ceremony itself can feel like the sixth event in a row. Counter this by keeping Days 1 and 2 lower-key: arrival and roka/pre-wedding gathering rather than full production events.
Share the full schedule with every guest. Automatically.
WedPlan creates your wedding website with the full function schedule, venue details, and live RSVP tracking — one link for all your guests, across all your events.
Sign up freeThe 7-Day Wedding Schedule
Seven-day weddings are full productions. They typically include a tilak or engagement ceremony, separate mehendi and sangeet, dedicated haldi, the wedding ceremony, a day of rest or informal gathering, and a reception. At this scale, guest experience management — who's invited to which functions, how they receive schedule updates, how they navigate the venue — becomes as important as the events themselves.
The defining challenge of a seven-day wedding isn't the events — it's the sustained logistics. Catering orders change daily. Shuttle schedules shift. Some guests leave after Day 3 and need different accommodation checkouts. Others arrive on Day 5 for the reception only. Managing this without a centralised system is genuinely chaotic. Managing it well is what separates a seven-day wedding that people remember fondly from one they remember as exhausting.
What Goes Wrong — And How to Avoid It
Five patterns that come up across almost every multi-day wedding, regardless of format.
The optimistic transition. Every schedule assumes the previous function ends on time. It almost never does. The haldi that was supposed to wrap at 11 AM runs until 12:30 because the grandmother arrived late and the photographer wanted one more setup. Now the bride has 3.5 hours to get ready instead of 5. Build 45–60 minutes of buffer into every transition between functions, and treat that buffer as sacred rather than as slack to fill.
The schedule that lives only in the planner's head. Guests don't know when the baraat is arriving. Vendors don't know when dinner service should start. The DJ doesn't know when to fade the music. When there isn't a single shared document everyone can reference, these questions get answered differently by different people — and the inconsistency shows up on the day.
The underestimated guest movement. Moving 200 people from a hotel lobby onto shuttles, driving 15 minutes, and getting them seated at a venue takes 45–60 minutes from when the first shuttle departs to when the last guest is seated. This number doesn't appear in most schedules. It should.
Dinner opened too late. If dinner doesn't open until 9:30 PM on a night that started at 6:30 PM, guests with dietary needs, children, or early flights the next day are unhappy in ways that affect the rest of the evening. Open dinner service as early as the run-of-show allows — you can always eat and dance simultaneously.
No one in charge of the clock. On the day, someone needs to be the timekeeper — not the couple, not the parents, not the pandit. A coordinator, a trusted friend, or a senior vendor who has the full run-of-show and the authority to move things along. If this role isn't assigned explicitly before the day, it doesn't happen.
Communicating the Schedule to Guests
The schedule you've built is only useful if guests can find it. In a multi-day wedding, guests typically receive schedule information through three channels: the initial invitation, a WhatsApp broadcast before the event, and a physical schedule card at the venue. The problem is that these three sources often don't match — because the initial invitation was sent before the final timings were confirmed.
The cleanest solution is to share a single link — your wedding website — from the start, and update it as timings are confirmed. Guests bookmark the link once. You update the schedule once. Everyone is looking at the same information. The alternative — sending updated PDFs into WhatsApp groups — creates version confusion that you'll be resolving via individual messages until the morning of Day 1.