Wedding run sheet template: a timeline that actually works

Your venue has asked for a wedding run sheet template. Your celebrant wants one too. Your photographer keeps asking about the timeline. And you have no idea where to start.

You’re not alone. A wedding run sheet template is the single most useful document you’ll create for your wedding day, and most couples have never built one before. The good news: it’s not complicated. The bad news: most of the templates floating around the internet were written by people who have never had to fix a timeline that went sideways at 4:30 on a Saturday afternoon.

I’ve spoken to coordinators who’ve rescued weddings where the run sheet was a single paragraph in an email. I’ve talked to photographers who’ve had couples hand them a timeline that allocated four minutes for family photos and expected 47 combinations. I’ve heard from DJs who’ve had the first dance scheduled for 8pm and the cake cutting for 8:02.

Here’s how to build one that actually works.

What a run sheet actually is (and what it isn’t)

A wedding run sheet is a minute-by-minute schedule of your entire wedding day. Each line has four things: a time, what’s happening, where it’s happening, and who needs to be there or doing something.

That’s it. It is not a checklist (that’s for the months before). It is not a seating chart. It is not an MC script, though your MC will use it to know when to grab the microphone.

A run sheet is the script for the day. Your vendors are the cast. Without it, everyone’s improvising. Sometimes that works. Usually it doesn’t.

Wedding Savvy has a built-in runsheet tool that handles the formatting, sharing, and versioning for you. You can browse the vendor directory and manage everything in one place. But even if you’re working in a spreadsheet, the structure is the same.

The four phases every wedding day breaks into

Every Australian wedding I’ve seen, regardless of style or size, breaks into the same four chunks.

Prep (morning to 30 minutes before ceremony). This is hair and makeup, getting dressed, detail shots with the photographer, and the quiet panic of realising you forgot to eat breakfast. Allow 2 to 3 hours for hair and makeup. Plan on about 30 minutes per service per bridesmaid, which lines up with what Easy Weddings recommends for timeline planning. If you have five bridesmaids getting both hair and makeup done, do the maths on that before you book a single artist.

Ceremony (processional to recessional). A civil ceremony runs about 20 to 40 minutes. Religious ceremonies can go over an hour. Build your timeline backwards from the ceremony start time: guests arrive 30 minutes before, the bridal party is hidden and assembled 15 minutes before that, and you arrive last.

Post-ceremony (recessional to reception entry). This is the danger zone. Congratulations, group photos, canapes, couple portraits, more congratulations. This block runs over more than any other because everyone underestimates how long it takes to move 100 people from one spot to another while they’re hugging you. Budget at least 90 minutes between ceremony end and reception start.

Reception (entry to exit). Most Australian receptions run 4 to 6 hours. This block has the most moving parts: entrances, meals, speeches, first dance, cake cutting, and the moment the dance floor opens and your uncle takes his shirt off.

Building your timeline: start from the ceremony and work backwards

Pick your ceremony time first. Everything else hangs off that.

If you’re getting married at 4pm on a Saturday in October, work backwards:

• 4:00pm: Ceremony starts
• 3:30pm: Guests begin arriving, music starts
• 3:15pm: Bridal party assembled and hidden
• 3:00pm: Bride arrives at venue (in the car, out of sight)
• 2:30pm: Bride leaves prep location
• 2:00pm: Bride gets into dress
• 12:30pm: Photographer arrives at bridal suite for getting-ready shots
• 10:00am: Hair and makeup begins (assuming three people, one artist each for hair and makeup)

Then work forward from the ceremony:

• 4:30pm: Ceremony ends, recessional
• 4:35pm: Confetti or petal toss if you’re doing one
• 4:40pm: Family photos (provide your photographer a shot list with names, not just “family photos”)
• 5:15pm: Bridal party photos
• 5:45pm: Couple portraits (this is your golden hour window if sunset is around 7:15pm)
• 6:00pm: Guests move to reception, canapes and drinks served
• 6:30pm: Reception doors open, guests seated
• 6:45pm: Bridal party entrance
• 6:50pm: Couple entrance
• 7:00pm: Entree served
• 7:30pm: Speeches round one (parents, or whoever you want going first)
• 7:50pm: Main course served
• 8:20pm: Speeches round two (best man, maid of honour, couple)
• 8:50pm: Cake cutting
• 8:55pm: First dance
• 9:00pm: Dance floor opens
• 11:00pm: Last song, farewell
• 11:30pm: Venue bump-out complete

Adjust the times for your season. A February wedding in Brisbane has a sunset around 6:30pm and the heat is still brutal at 4pm. A June wedding in Melbourne has a sunset closer to 5pm and you’ll want that ceremony happening by 2pm to catch the light. Check your sunset time and plan your couple portraits for the hour before it.

Who needs a copy (and what version they get)

Every key vendor should have the run sheet at least a week before the wedding. But not everyone needs the same version.

Your MC needs the full reception timeline with every announcement, speech introduction, and music cue. They’re running the room. Give them everything.

Your photographer and videographer need the full day timeline with exact locations for each photo session and a family shot list with names. They don’t need to know what time the cake is being cut unless they’re still there for it, but they do need to know they have 22 minutes for family photos, not 8.

Your venue coordinator needs the full timeline including vendor bump-in and bump-out times, meal service timing, and when the room needs to be ready for each transition. They do not need to know what song you’re walking down the aisle to.

Your celebrant needs the ceremony block plus who to coordinate with for music cues and the signing.

Your DJ or band needs the reception timeline with every formal moment that requires music: processional, recessional, entrance songs, first dance, parent dances, cake cutting, last song.

Your bridal party needs the prep timeline plus wherever they need to be and when. They don’t need vendor arrival times.

Your parents or a trusted family member need a simplified version: where to be, when to be there, and any roles they have. This is also the person who fields “where do I park” questions so you don’t have to.

If you’re using Wedding Savvy’s runsheet tool, you can create one master runsheet and share different views with different people via permission-controlled links. If you’re using a spreadsheet, make one master tab and then create filtered tabs for each group. Either way, version control matters. Label your run sheet with a date and version number. When you send version 4 to your vendors on Wednesday and then make changes on Thursday, send version 5 and make sure everyone knows the old one is dead.

The stuff everyone forgets to include

These are the things that don’t appear in template run sheets but absolutely should.

Vendor bump-in and bump-out times. Your florist needs to know what time the ceremony space is available for setup. Your DJ needs to know what time they can access the reception room for sound check. Your cake maker needs to know when the kitchen can accept delivery. These are not your problem to coordinate individually, but the venue coordinator needs to see them all in one place.

Vendor meals. If your photographer, videographer, and DJ are working through dinner, they need to be fed. Note the meal time on the run sheet and confirm with the venue that vendor meals are ordered. Most venues charge $40 to $90 per vendor meal. Budget for it.

Emergency contacts. One phone number for the venue coordinator. One for your celebrant. One for a level-headed friend who isn’t in the bridal party. If the cake doesn’t arrive, nobody should be calling you.

Weather plan. If you’re doing an outdoor ceremony, the run sheet needs a Plan B column. What moves indoors if it rains? Who makes the call, and by what time? A wet-weather decision at 10am changes the entire setup for a 4pm ceremony. A wet-weather decision at 3:30pm is a disaster.

The gap. If your ceremony and reception are at different venues (or different locations on the same property), map the travel time. Google Maps says 18 minutes; with a wedding dress, a car full of flowers, and a stressed-out bridesmaid, it’s 30. Round up.

Sunset time. I mentioned this already but I’m saying it again because it’s the number one thing photographers complain about. Look up the sunset time for your date and location. Your couple portraits need to happen in the hour before it. Build the run sheet around that, not the other way around.

Buffer time: why it matters and where to put it

I asked a Sydney DJ with 30 years of weddings under his belt how many receptions he’s seen run exactly on schedule. His answer: none.

That’s not a failure. It’s a design requirement.

Build 10 to 15 minute buffers after every major transition point. After the ceremony (guests will mob you). After family photos (Uncle Steve will wander off and someone has to find him). After the bridal party entrance (someone will need the bathroom). After speeches (one will run long, probably the best man’s). After the first dance (applause, then someone starts a second song).

Buffers are not wasted time. They’re insurance. If everything runs on schedule, you use the buffer to breathe. If something runs over, the buffer absorbs it and the rest of the night doesn’t collapse like dominoes.

And for the love of a smooth reception, split your speeches. Five speakers at 8 to 10 minutes each is 50 minutes of guests sitting in the dark. Do two or three before the entree, serve food, do the rest before the main course. Your guests will thank you. Your photographer will thank you, because they can actually see people’s faces instead of the backs of heads turned toward a screen.

What happens when things go wrong on the day

Your run sheet will go off schedule. Accept this now. No point having a whinge about it on the day.

The point of a run sheet isn’t to follow it to the second. It’s so that when things shift, you know what comes next, who needs to know, and what can be cut without anyone noticing.

If photos run 25 minutes over, you don’t panic and skip the entrees. You look at the run sheet, see that speeches round one has a 15-minute buffer and round two could compress by five minutes, and you make the call. Or you shorten the cake cutting to 60 seconds (which is all it ever needed to be) and nobody notices.

If a speech runs long, the MC quietly signals the next speaker to keep it tight. If the dance floor is packed, you push the farewell back by 15 minutes and nobody cares because they’re having a good time.

The run sheet is the map. The actual day is the terrain. The map is never the terrain. That’s fine.

Why a wedding run sheet template that’s a PDF isn’t good enough

Most wedding run sheet templates are PDFs or Google Docs. They work fine when you’re the only person making changes, two weeks out, in front of your laptop.

They fall apart when:

• Your photographer emails you three days before the wedding asking if they can arrive 30 minutes earlier for the light
• Your venue coordinator calls on Thursday with a room-flip timing change
• It’s the morning of the wedding and your celebrant realises they’ve been working from version 3 and you’re on version 5

A PDF can’t adapt. A spreadsheet can, but only if everyone remembers to refresh it. A proper digital runsheet tool with share links and version tracking means everyone is always looking at the same document, and when you make a change at 10pm on Thursday night, everyone sees it.

Wedding Savvy’s runsheet builder handles the sharing and versioning automatically. You can create separate runsheets for the ceremony and reception, add items with timings and responsible parties, and share them with vendors and the bridal party via links you control. The platform is free for couples. It also connects to your guest list (so you know exactly how many chairs you’re planning around) and your task list (so the run sheet isn’t the only timeline you’re managing).

If you’re deep in planning mode, the Tasks system auto-generates a wedding checklist ordered by months before your date, so you’re not building a run sheet from scratch with no context. And if you want to give your vendors a look at the bigger picture, the Budget Tracker and Guest List live in the same place.

Start with your ceremony time. Build out from there. Add buffers. Send it to your vendors a week before. Expect it to change. That’s the whole system.