Multi-day wedding weekend timeline templates

The two-day American wedding weekend

A common US shape is a welcome gathering the night before and the wedding day itself, with a farewell the next morning. It keeps out-of-town guests busy without over-scheduling them.

• Friday evening — welcome dinner. 6:00 PM rehearsal (wedding party); 7:30 PM welcome dinner or drinks for out-of-town guests.
• Saturday afternoon — the wedding. 3:00 PM guests arrive; 3:30 ceremony; 4:00 cocktail hour; 5:30 reception; dinner, toasts, dancing to close.
• Sunday morning — farewell brunch. 10:00 AM–12:00 PM casual brunch before guests travel home.

The three-day Indian wedding

A compressed US Indian celebration often folds a week of tradition into a Friday-to-Sunday weekend. The pre-wedding functions build energy toward the wedding day, which stacks the baraat, ceremony, and reception.

• Friday — mehndi & sangeet. Afternoon mehndi (henna, close circle); evening sangeet — dinner, performances, and dancing for the wider guest list.
• Saturday — haldi, baraat, ceremony. Morning haldi at home (family); midday baraat (groom’s procession); afternoon ceremony with the pheras; evening reception.
• Sunday — farewell. A relaxed brunch or vidaai-day gathering as family and traveling guests depart.

The destination long weekend

A destination wedding stretches to three or four days because guests have traveled far — you want to give them an experience, not just a ceremony, while leaving room to actually enjoy the place.

• Thursday — arrivals & welcome. Guests arrive through the day; evening welcome reception once most have landed.
• Friday — a group activity. A hosted excursion or free day, then an optional casual dinner — keep it light so guests can rest.
• Saturday — the wedding. Ceremony in the late afternoon (better light, cooler temps); cocktails; reception into the night.
• Sunday — farewell brunch & departures. A morning brunch before checkouts; stagger nothing tightly against flights.

Build in buffer — the mistake everyone makes

The single most common timeline error is scheduling back-to-back with no slack. Hair and makeup runs long, photos take longer than planned, and a ceremony rarely starts exactly on time. Add 15–30 minutes of buffer between major blocks, and never schedule an event to begin the instant another ends — guests need time to travel, change, and breathe.

Be especially generous around anything involving travel between venues, and around the getting-ready window on the wedding morning, which is the block that most reliably overruns and pushes everything after it.

• Pad the transitions. Leave 15–30 minutes between major blocks so one overrun doesn’t cascade.
• Protect the morning. Getting-ready almost always runs long — start it earlier than feels necessary.
• Don’t stack against flights. On a destination or farewell day, leave wide margins before departures.

Transport and communicating the plan

When events are at different venues, transport is what makes or breaks the schedule. Arrange shuttles for the moves guests can’t easily make themselves (hotel to ceremony, ceremony to reception), publish the pickup times clearly, and build the shuttle timing into your buffer so a late departure doesn’t start the next event late.

And however good the plan, it only works if guests know it. Publish the full schedule where everyone can see it, and send day-of reminders — “shuttle leaves the lobby at 4:15” — to the guests attending that event. With a tool like Duva, each event has its own guest list, so the shuttle text goes only to the people who need it, by SMS or WhatsApp, and you’re not fielding the same “what time / where” question fifty times.