Wedding Weekend Itinerary Template for the Wedding Party

A wedding is one day. A wedding weekend is three, and the wedding party is expected at most of it.

That gap is where the questions come from. Guests need an invitation and a dress code. The wedding party needs a schedule: what time to be where, what to wear, what to bring, and who to call when the thing you were told about on Tuesday has changed by Friday. Without one, twelve people each ask the couple the same four questions separately, which is how a couple ends up answering texts at eleven at night in the week they should be enjoying.

Below is a template you can copy, fill in and send. It covers Thursday afternoon to Sunday lunch, which is the standard shape of a wedding weekend in 2026, and it is built so that each person can find their own line in it quickly.

The Template

Fill in the times, delete what does not apply, and send it as one document a fortnight out.

The times are a realistic default rather than a prescription. A morning ceremony or a destination wedding reshuffles everything, and that is fine. The structure is what carries over: one column for the time, one for the thing, one for who it applies to, one for where, one for what to wear.

What Belongs On It

The useful test for every line: does this prevent a question?

Call times, phrased as arrival times. "Hair at 8:00" is ambiguous. "Be in the suite by 7:50, hair starts at 8:00" is not. Give the time to be there, not the time the thing begins.

Who each line applies to. The most common failure in a weekend itinerary is a schedule everyone has to read in full to find out whether they are in it. Name the people or the group on every row.

Dress code per event, in two or three words. Including Friday and Sunday, which is where guests and party members genuinely do not know what is expected.

Full addresses, not venue names. A name is not navigable. Put the address, and for anywhere rural put a note about parking and signal, because somewhere on that weekend someone will be standing in a lane with one bar.

One phone number for the day. Not the couple's. A maid of honor, best man or day-of coordinator who has agreed to be the contact. This single line removes more wedding-morning stress than anything else on the page. Our role by role breakdown of the wedding day covers who should be holding it.

What to bring to each thing. Rings to the rehearsal. Speech card to the reception. Flat shoes to the ceremony if it is on grass.

What is optional and what is not. Mark the optional events clearly. "Optional" written on a Friday morning activity gives seven people permission to sleep, which they need and will not take without it.

The hard stops. The transport that leaves at 2:30 whether or not everyone is in it. The rehearsal that cannot start late because the venue has another booking. Say which lines are immovable and why, in a few words.

What to Leave Off

Vendor contact details and load-in times. That is the couple's or the coordinator's document, not the party's. A party itinerary with the florist's delivery window in it is a document people stop reading.

Minute by minute reception detail. Nobody in the party needs the cake cutting to the minute. The run of show for the reception belongs with the MC, and our MC guide covers how that gets built.

Anything confidential. Surprises, the first dance song if it is a surprise, any planning the couple is not meant to see.

Your own private notes. If you are the one building this, keep your worry list separate from the thing you send.

How to Send It

One document, one place, one version. The most common way an itinerary fails is not being wrong, it is existing in four versions: a screenshot in the group chat, a PDF in an email, a printout from three weeks ago, and someone's notes app. By the week of the wedding nobody is certain which is current.

Pick one home for it and say so plainly when you send it: "This link is the only version. I will update it here if anything changes." A shared document, a shared calendar, or a page in whatever the party is already using all work. A screenshot does not, because a screenshot cannot be updated.

Send it two weeks out, then once more three days out. Two weeks is enough notice to book travel around and recent enough to be accurate. The three day resend is the one people actually read.

Put the Saturday on one screen. Whatever the format, the wedding day itself should be readable without scrolling sideways on a phone. That is the day it will be opened on.

Add the whole weekend to a shared calendar too. Separate entries with locations attached, so each person gets an alert twenty minutes before their own call time rather than consulting a document.

If people are flying in, the itinerary is only half of it. Our destination wedding coordination guide covers arrival windows, time zones and the extra day you need either side.

The Four Lines People Forget

In rough order of how often they cause a problem:

1. When transport leaves, and that it leaves then. More weddings run late because of a late minibus than any other single cause.
2. Whether lunch exists on Saturday. Getting-ready mornings are long and routinely foodless, and a wedding party that has not eaten by two in the afternoon is a wedding party that struggles by eight.
3. Who is bringing the rings to the rehearsal and the ceremony. Usually the best man, and worth writing down anyway.
4. What time Friday night ends. Without a stated hard stop, a rehearsal dinner runs to one in the morning and Saturday's 7:30 breakfast becomes a tragedy.

If You Are the One Building It

You are probably the maid of honor, the best man or a day-of coordinator, and the couple will be grateful in a way they will not fully articulate.

Build it from the ceremony backwards. Fix the ceremony time, then work back through transport, photographs, getting into outfits, lunch, hair and makeup and call times, adding a cushion at each step. Our wedding day timeline template does exactly this for Saturday, and this document is that timeline with the other two days attached.

Then do two things that cost ten minutes and save the weekend. Read it as each person: is your own line findable in five seconds. And ask one party member who was not involved to tell you what they would be unsure about. They will find two gaps you cannot see, because you know what you meant.

Common Questions

What should be on a wedding weekend itinerary?

Each event with its arrival time, who it applies to, the full address, and a two or three word dress code. Add one contact number for the weekend who is not the couple, mark which events are optional, and state the hard stops: the transport time, the rehearsal start and the Friday night cut-off.

When should you send the wedding party their itinerary?

Two weeks before the wedding, then again three days out. Two weeks gives people time to arrange travel and childcare around it, and the three day resend is the version most people actually read. Add the events to a shared calendar as well so each person is alerted before their own call time.

How early should the wedding party arrive on the wedding day?

Hair and makeup usually begins seven to eight hours before the ceremony, and the suit side is typically called four to five hours before. Give everyone an arrival time ten minutes before their slot begins, and be specific about what to arrive wearing and whether hair should be clean and dry.

Does the whole wedding party have to come to the rehearsal dinner?

Usually yes, and it is normally the one Friday event that is not optional, along with the rehearsal itself. Close family, the officiant, readers and out of town guests are commonly invited too, so numbers vary. Mark the rehearsal and the dinner as required and everything else on Friday as optional.

Should the wedding party itinerary be the same as the guest one?

No. Guests need the ceremony time, the address, the dress code and any welcome events. The wedding party needs call times, transport, photograph slots and the contact number. Send two documents, and keep vendor details out of both of them.

The Short Version

Build one document, Thursday to Sunday, with five columns: time, event, who, where, what to wear. Give arrival times rather than start times, name the people on every row, use full addresses, mark the optional events as optional, and name the hard stops. Put one contact number on it who is not the couple.

Send it two weeks out and again three days out, keep exactly one version, and make sure Saturday fits on a phone screen. Then remember lunch.

A three day schedule, twelve people and four call times, living in one screenshot nobody can find? Nozari keeps the weekend's events and every person's tasks in one shared place that updates for everybody at once. See how it works.