The Wedding Day Run Sheet: How Planners Keep 12 Hours on Track
A working guide to the wedding day run sheet planners use to choreograph vendors, build in buffers, and keep a 12-hour day from unraveling.

A run sheet is the minute-by-minute operations document you build for yourself and every vendor, not the pretty timeline the couple hands to guests. It lists who arrives when, who does what, and where the slack is hidden. Build it backward from the ceremony and photos, then defend your buffers like your reputation depends on it. It does.
The couples you serve see a smooth, effortless day. What actually holds that day together is a document most of them never read.
This guide is for wedding planners and coordinators creating a vendor-facing operational run sheet, not couples planning the months before the ceremony. For a couple-friendly event schedule, use the wedding day timeline tool; for the longer planning process, see our 12-month checklist.
Run sheet vs couple timeline
The couple's timeline and your run sheet share a wedding date and almost nothing else. The couple's version is aspirational and public: "4:00 Ceremony, 5:00 Cocktails, 6:00 Dinner." Your run sheet is granular and private, tracking load-in, vendor meals, transitions, and the exact person responsible for each move.
Blur these two and you'll suffer for it. If guests see your operational times, they'll arrive against your setup schedule and treat soft targets as hard ones. If your vendors get the guest-facing version, they'll show up when the ceremony starts instead of two hours before to set up. Keep them separate on purpose.
Your run sheet answers three questions the couple's never does: Who is doing this? When exactly, to the ten-minute mark? And what happens if it slips? That third question is why planners exist. The couple's wedding day timeline is the story of the day; the run sheet is the machinery underneath it.
Building backward from the ceremony
Anchor everything to two fixed points and work outward: ceremony start and sunset. Ceremony time is usually locked by the venue or officiant. Sunset is locked by physics. Almost every photo you care about, portraits, golden hour, first look, hangs off those two anchors.
Start at ceremony time and subtract. Portraits before the ceremony? Count back through the first look, hair and makeup finish, and getting-ready coverage until you hit a realistic wake-up. Then subtract again for the things that always take longer than couples expect: buttoning a dress, wrangling a family formal, a delayed hair artist.
Anchor points to build from:
- Ceremony start: the immovable center of the day.
- Sunset: dictates when portraits and golden-hour shots must happen.
- Reception hard-out: the venue's contracted end time, often with steep overage fees.
- Vendor meal window: photographers and DJs need to eat during dinner, not during dancing.
Working backward from fixed points instead of forward from breakfast is the single habit that separates a run sheet that holds from one that collapses by 2pm.
Vendor arrival choreography
Vendors don't arrive when the party starts, they arrive in a staged sequence, and sequencing them is half your job. Get the order wrong and you'll have a florist trying to dress an arch while rental staff are still carrying in the chairs it's supposed to stand behind.
Stagger arrivals so each vendor walks into a space that's ready for them. Rentals and structural setup first. Then florals and decor onto the built furniture. Then lighting and AV. The couple's hair and makeup team runs on its own parallel track entirely, keyed to photo time, not venue setup.
| Window before ceremony | Who arrives | What happens |
|---|---|---|
| 5-6 hours | Rentals, venue setup | Tables, chairs, structural pieces |
| 3-4 hours | Florist, decor | Arrangements onto set furniture |
| 2-3 hours | Photographer, DJ, lighting | Coverage begins, sound check |
| 1-2 hours | Caterer final prep, officiant | Kitchen ready, ceremony brief |
Confirm every arrival window in writing the week before, and put a name and cell number next to each vendor on the sheet. When something slips, you're calling a person, not a company.
Buffer rules that save the day
Buffers are not padding you can cut when the schedule feels tight, they are the schedule. A run sheet with zero slack doesn't run early; it runs late from the first delay and never recovers, because delays compound. One late hair appointment cascades through portraits, first look, and ceremony.
Build in slack deliberately and hide it in the right places. A useful rule of thumb: add roughly 15 minutes of buffer for every major transition, and a larger 30-minute cushion before the ceremony itself, the one thing that truly cannot start late. Getting-ready and portraits are where delays are born, so weight your buffers early in the day.
Where to bank your buffer:
- Before the ceremony: the biggest cushion, because this is the immovable anchor.
- Between getting-ready and portraits: hair and makeup almost always run over.
- Family formals: the classic time sink, budget more than you think you need.
- Transitions between spaces: moving 130 people from ceremony to cocktails takes real minutes.
Guard these fiercely. The temptation to "borrow" buffer time to add one more shot is how days fall apart. Protected slack is what lets you absorb the inevitable surprise and still land dinner on time.
The communication tree
On the day, you cannot personally relay every update to every vendor, so you build a communication tree: a clear map of who tells whom. You are the hub, but you delegate spokes to an assistant, the venue coordinator, and the lead of each vendor team.
Define it before the day starts. The couple talks only to you, never to vendors directly, that's the whole value they're paying for. Vendors report to you or your assistant, not to the couple. The venue coordinator handles anything building-related. When the run sheet shifts, one message from you cascades down the tree instead of you making fifteen calls.
A workable tree:
- Couple to you only. They ask you; you handle it. Protect them from logistics.
- You and your assistant split the vendor teams to cover more ground.
- Each vendor lead relays to their own crew.
- Venue coordinator owns anything about the building itself.
Print the tree on the run sheet with every phone number. When the timeline moves 20 minutes, everyone learns it the same way, fast, and no vendor is left working off the old plan.
A run sheet template walkthrough
A strong run sheet fits on a few pages and reads at a glance under pressure. Each row is a time block with four columns: the time, what's happening, who's responsible, and any note or dependency. No prose, no paragraphs, just scannable rows you can read while walking.
Here's the shape of a single stretch of the day:
| Time | Event | Owner | Notes |
|---|---|---|---|
| 2:30 | First look | Photographer | Buffer 15 min after |
| 3:00 | Wedding party portraits | Photographer, assistant | Corral group early |
| 3:45 | Hide couple, guests arrive | You | Ushers in position |
| 4:00 | Ceremony | Officiant | Do not start late |
Distribute the right version to the right people: vendors get their arrival and load-in rows highlighted, the couple gets the clean guest-facing timeline, and you carry the master with every buffer and phone number. Pair it with your standard day-of coordination checklist so nothing structural gets missed, and lean on your broader wedding planning process to build the sheet the same reliable way every time.
Common questions about wedding day run sheets
What is a wedding day run sheet?
A run sheet is the detailed operational schedule a planner or coordinator builds to run the wedding day, distinct from the simplified timeline guests see. It lists exact times, the person responsible for each action, vendor arrival windows, and built-in buffers. It's the working document that keeps a 12-hour day on track, tracking logistics the couple never has to think about.
How is a run sheet different from a wedding timeline?
A wedding timeline is the guest-facing outline of major moments, ceremony, dinner, dancing. A run sheet is the private, minute-by-minute operations document behind it, covering vendor load-in, transitions, meal windows, buffers, and who owns each task. The timeline tells the story of the day; the run sheet is the machinery that makes the story happen smoothly.
How much buffer time should a run sheet include?
Roughly 15 minutes of buffer around each major transition, plus a larger cushion of about 30 minutes before the ceremony, the one moment that cannot start late. Weight your buffers toward the morning, since getting-ready and portraits generate the most delays, and those delays compound through the rest of the day if you haven't left room to absorb them.
When should vendors arrive on the wedding day?
Stagger arrivals in sequence rather than all at once. Rentals and structural setup come first, roughly five to six hours out, followed by florals and decor, then photography, DJ, and lighting two to three hours before the ceremony, with catering and the officiant close to the start. Each vendor should walk into a space that's already prepared for their part.
Written by the Bride Loom editorial team · Updated October 24, 2026. Read our editorial policy and corrections process.