Wedding Weekend Itinerary: The Complete Checklist

A wedding weekend itinerary needs six things confirmed before it goes out to anyone: what each day is, who is invited to which day, a start and finish time for every event, where guests are travelling from, one point of contact, and a version every guest actually opens rather than skims once in a group chat. Most weddings do not need one at all - Zola's 2026 survey of more than 11,500 couples found 37% added a single extra event onto the wedding day, while a full two-to-three-day weekend stayed rarer, at 18%.¹ The gap between those two numbers is the reason this is its own checklist, separate from the day's run sheet.

What does a full wedding weekend itinerary actually need to cover?

Three blocks, each answering a different question for a different audience, not one long document trying to do all three jobs at once.

Saturday already has an owner - the run sheet - because a vendor and a guest need the same day answered two different ways. Friday and Sunday usually have no owner at all until someone notices the gap a week out.

Decide these three things before you build anything

Which days actually exist. Not every wedding needs a Friday or a Sunday block. If the only event is the wedding day itself, stop here and use the run sheet on its own - a weekend itinerary with nothing either side of Saturday is a cover page for one document.

Who is invited to what. A welcome night guest list and a wedding day guest list are rarely the same list. Write both down before building the itinerary, not while building it - the itinerary is where that split becomes visible to guests for the first time, and it is the wrong place to discover it is still undecided.

One point of contact per day. Not the couple. A parent, the maid of honor, or whoever is actually free that day, listed by name against each block so a guest with a question texts them instead of the wedding party mid-ceremony.

Friday: what the welcome night needs confirmed

Four things, and all four are things a guest cannot guess: start time, end time, dress code if there is one, and whether it is the whole guest list or a smaller one. A welcome night with no stated end time runs long by default, and a welcome night that runs long the evening before a wedding is the one scheduling mistake that costs the next day, not just the one it happens on.

The Australian coordinator behind the Managing Matrimony runsheet guide puts the general version of this plainly: "The biggest mistake couples make is under-padding transitions."⁴ On a Friday night, the transition that gets under-padded is the one into Saturday morning - build the end time around the earliest getting-ready call time the next day, not around when the party naturally winds down.

Saturday: what the wedding day needs, beyond the run sheet

Saturday's schedule is not built here - the PlannedBy run sheet generator derives the whole day from a single input, the ceremony time, rather than a blank page filled in by hand. What the weekend itinerary adds on top is smaller and easy to skip: confirmation that every guest, not just the wedding party, knows the venue address and the start time, and a note on what happens if someone can only make part of the day.

Sunday: what the morning after needs confirmed

Three things: a start time that is later than couples plan for, a finish time, and a pack-down buffer at the end. A recovery brunch from roughly 9am to noon covers most weekends - enough for the wedding party to surface, eat, and say goodbye to guests flying out that afternoon.

The same under-padding warning that governs Friday applies here in reverse: build in a pack-down window rather than assuming the room empties the moment brunch does.⁴ A 30-to-45-minute buffer before checkout is the difference between a calm final morning and a scramble to find someone's overnight bag while the venue resets the room for its next booking.

Who on the guest list actually needs the full itinerary?

Not everyone travelling to the wedding is travelling far. 89% of Australian couples marry in their home state or territory, 7% marry interstate, and 4% head overseas³ - which puts roughly 11% of a typical guest list in the group that actually needs Friday's and Sunday's timing, because they are the ones with flights, accommodation and a checkout to plan around.

Australian weddings also skew toward a Friday-anchored weekend more than couples assume: 53% land on a Saturday and 20% on a Friday, together 73% of the year's weddings.² Build two versions of the itinerary rather than one - a full three-day version for the wedding party, family, and anyone flying in, and a Saturday-only version for local guests who only need the one day answered.

Frequently asked questions

Do we need a wedding weekend itinerary if it is a one-day wedding?

No. If every guest is only invited to Saturday, the run sheet covers it on its own. Build the weekend itinerary once there is a second event on the calendar - a welcome night, a farewell brunch, or both.

Does every guest need the same version of the itinerary?

No, and sending one version to everyone is the most common way this document gets ignored. Local day-guests only need Saturday's details. Build the full three-day version for the people actually staying the weekend - the wedding party, family, and anyone who booked a flight.

Who should be listed as the point of contact?

Not the couple. List a different person against each day - often a parent for Friday and Sunday, and the maid of honor or a coordinator for Saturday - so a guest's question about check-in or a start time never reaches the couple mid-weekend.

Does the ceremony have to be on the Saturday of the weekend?

No. Australian law places no restriction on the day or time of a marriage ceremony.⁵ Couples put the ceremony on Saturday because that is when the most guests can attend, not because any other day is off-limits.

How far ahead should the itinerary go out to guests?

Two to four weeks ahead for anyone travelling, so flights and accommodation can be booked around Friday's start time and Sunday's finish time, not just the ceremony time.

What is the single thing most itineraries forget?

The pack-down buffer at the end of Sunday. Couples build in transitions for Friday night and Saturday's reception, then leave Sunday's finish time as a guess - which is exactly the gap that turns a calm brunch into a scramble at checkout.

The fastest way to get this out the door

Start with the three decisions, not the document: which days exist, who is invited to each one, and who the point of contact is per day. Those three answers turn a blank weekend itinerary into a five-minute fill-in, because everything else on this page - the times, the buffers, the two guest versions - is detail layered onto a structure that is already decided.