The Wedding Day Run-of-Show, Built at 90 Days: A Venue Coordinator's Template for Catching Surprises Before They Cost You

If your run-of-show lives in a Word doc that gets opened the Monday before the wedding, you are not running a venue — the wedding is running you. The smoothest operations we see start their day-of plan 90 days out, treat it like a living document, and use the planning conversations happening in the meantime to update it in real time. This is the template, the cadence, and the visibility loop that makes it actually work.

There is a quiet pattern in our data at Knotbook. Coordinators who win the day — clean transitions, on-time courses, no panicked group texts at 4:47pm — are not the ones with the prettiest binders. They are the ones who stop treating the run-of-show as a single artifact built in the final two weeks and start treating it as a 90-day document that absorbs every couple decision as it happens.

If you have ever discovered at the rehearsal that the couple "just assumed" their dog was walking down the aisle, that the groom's dad insisted on a toast you were not staffed for, or that catering was working off a guest count that has shifted by 22 people, you already know what we are talking about. The information existed. It just was not in your run-of-show.

What a venue run-of-show actually is (and what it is not)

Couples often confuse their guest-facing timeline ("ceremony at 4:30, cocktails at 5:15, dinner at 6:30") with the document the venue actually runs the day from. They are different artifacts.

• The guest-facing timeline is what gets printed on the program and sent in the welcome email. It has 6–10 lines.
• The vendor schedule is what the photographer, DJ, and florist work from. It has 25–40 lines and starts at load-in.
• The venue run-of-show is what your coordinator, your captain, your kitchen lead, and your house manager work from. It has 80–150 lines, starts the morning before, and ends with the lockup time the night of.

It is not a timeline. It is an operations script. It assumes someone could walk in cold and run the day from page one. That is the bar.

The 14-day myth (and why every veteran coordinator quietly hates it)

The standard wisdom in the industry is that the run-of-show gets locked at the final walkthrough — usually 10 to 14 days out. The problem is that by 14 days out, every meaningful decision has already been made. You are not planning a wedding at that point; you are transcribing decisions the couple made over the previous 9 months in fragmented Slack-like chaos across email, Pinterest, group chats, and three different Google Docs.

Most of the surprises that wreck a wedding day were technically decided 60–90 days earlier. They just were never communicated to the venue in a structured way. We wrote about this dynamic in detail in The Couples' Group Chat Problem — roughly 80% of wedding decisions happen in places venues cannot see. The 14-day handoff is where that visibility debt comes due, all at once, on the busiest week of the cycle.

A 90-day run-of-show is not "starting earlier for the sake of starting earlier." It is the document that absorbs decisions as they are made, instead of forcing you to reconstruct the last three months in a single 90-minute meeting.

Why 90 days is the right starting point

Three things converge around the 90-day mark in nearly every wedding:

1. Vendor team is locked. By T-90, photographer, florist, DJ/band, officiant, and rentals are all booked. You can finally write a vendor arrival ladder that will not change three more times.
2. Guest count starts firming. Save-the-dates have been out for months and most invitations have landed. Even before formal RSVPs close, your couple has a working number that is ±10% accurate. That is enough to plan service.
3. Couple decision fatigue starts setting in. Couples between T-120 and T-90 are the most decisive they will be all year. Two weeks before the wedding, they are running on caffeine and DM threads. Capture decisions while their judgment is sharp.

The venues that build the run-of-show at 90 days are not doing more work. They are doing the same work, distributed over 12 weeks instead of 12 days, with significantly fewer fires.

The 7 sections every run-of-show needs

If you take nothing else from this post, take this skeleton. Every wedding we coordinate at our partner venues runs a variant of these seven sections. Adapt the granularity, but do not skip any of them.

1. The vendor arrival ladder

Not "vendors arrive between 11am and 1pm." A row per vendor, ordered by arrival time, with point-of-contact, phone number, parking instructions, load-in door, and rough departure time. Photographers showing up at the same moment as a 14-foot floral arch is how you lose 25 minutes of getting-ready coverage.

2. Couple and family touchpoints

Where are the couple and key family members at every 30-minute interval from getting-ready through the last dance? This sounds like overkill until the bride's mother goes missing during family portraits. Knowing the planned touchpoint by 5:42pm tells you exactly where to send someone.

3. Service flow and course pacing

Doors open, first course fires, plates cleared, second course fires. Built backward from the speeches and forward from the ceremony close. Catering teams that get a venue-built service script (instead of just a guest count) move dinner along 8–12 minutes faster on average.

4. Special moments and cued events

First dance, parent dances, toasts, cake cutting, bouquet toss, surprise dance numbers, sparkler send-off. Each one gets a cue, an owner, and a backup plan if the moment slips by 10 minutes. This is the section that quietly collapses when the run-of-show is built two weeks out — there is no time to confirm with the DJ which song version is the edited one.

5. Coordinator handoffs

Who has the radio at 3pm? Who has it at 9pm? When does the lead coordinator hand off to the closing manager? If you run weddings with multiple staff, the handoff lines should be on the document explicitly. "Assumed" handoffs are how a couple ends up answering a vendor's question themselves at 10:15pm.

6. Risk register

One column. Three to seven rows. "What could go sideways, who decides, what is the fallback?" Rain plan, kitchen failure, late vendor, family conflict, drunk uncle, drone footage cancelled. Naming the risks shrinks them by half.

7. The "couple wishes" appendix

Not operational, but critical. The 5–10 lines from the couple about what would make the day feel like theirs — Dad's specific cocktail, the song that has to play, the photo at the corner of the property where they got engaged. This is the section that turns a competently-run wedding into a 5-star review. We dug into the texture of what couples actually praise in 5-Star Wedding Venue Reviews, Reverse-Engineered.

The visibility problem: how do you actually know what couples want?

Here is the part the template alone does not solve. The 7-section skeleton is useless if the data flowing into it is stale. And in most venues, the data flow looks like this:

• Couple sends a 9pm email with three new ideas.
• Coordinator reads it the next morning and replies to two of the three.
• The third gets lost in a thread.
• Couple assumes silence equals approval.
• It surfaces at the rehearsal.

This is the visibility gap we wrote about in The Wedding Venue Visibility Gap. The fix is not to demand more emails from couples. The fix is to give them a structured place to plan — one where their decisions automatically flow into the document your coordinator is operating from.

Knotbook was built for exactly this. When a couple updates their guest count, swaps a song, picks a getaway car, or asks "can my grandfather sit closer to the dance floor?" — your coordinator sees it in the same view that drives the run-of-show. No second email. No re-keying. No rediscovery at the rehearsal.

The 90 / 30 / 14 / 7 cadence

A run-of-show is not built once. It is refreshed in waves, with each pass triggered by a milestone event. Below is the cadence we recommend.

T-90: Skeleton draft

Build all seven sections with placeholders. Vendor arrival ladder uses booked vendors and rough times. Service flow uses the package's standard pacing. Couple wishes appendix is empty. The point of this draft is not to be right — it is to exist, so every conversation between now and the wedding has a place to land.

T-30: First major refresh

This is where most of the special-moment decisions get locked: ceremony processional order, first dance song, parent dances, speeches, surprise moments. Pair this refresh with a final menu confirmation. The timing also lines up with what we wrote about in The Final 30 Days — the communication cadence that catches every surprise before it hits your day-of.

T-14: Vendor sync

Send the vendor schedule (sections 1–4, redacted for what each vendor needs) to every vendor. Get acknowledgments in writing. This is where mismatched assumptions surface and get fixed.

T-7: Final lock

Walkthrough with the couple, final guest count from catering, family conflicts noted, weather plan committed. Print three copies. Put one in the manager binder, one at the captain's station, one on the kitchen pass.

T-2: Quiet review

You, alone, at your desk, reading the document like you are seeing it for the first time. Whatever makes you flinch is what you fix tomorrow.

The mistake that quietly kills the document

Most run-of-show templates we see fail for the same reason: they live somewhere the couple cannot touch. So updates depend on the couple emailing the coordinator, and the coordinator typing the update into a Word doc. There is friction at every step. The friction kills the loop.

The venues with the cleanest day-of operations have one thing in common — the couple's planning surface and the venue's operating document are connected at the data level. When the couple updates their seating chart at 11pm, it is reflected in the venue's run-of-show by 11:01pm. There is no re-typing, no version drift, no "I sent that to you, did you not get it?"

This is not a software pitch — it is a workflow point. Whether you build it in Knotbook or assemble it from a venue dashboard plus three integrations, the test is the same: can the couple update one source of truth, and can your coordinator operate from that same source of truth on the day? If the answer is no, you are managing two documents. And one of them will be wrong on the day.

Steal this skeleton

Here is the literal structure we recommend our partner venues use as a starting point. Copy it, paste it into your own template tool, and adapt to your service style.

WEDDING RUN-OF-SHOW — [Couple Name] — [Date]
Last updated: [auto-stamp]

1. Vendor Arrival Ladder
Time | Vendor | POC | Phone | Load-in door | Notes

2. Couple + Family Touchpoints
Time | Person | Location | Coordinator on point

3. Service Flow
Time | Cue | Owner | Backup

4. Special Moments
Time | Moment | Cue source | Music/sound | Backup if late

5. Coordinator Handoffs
Time | From | To | Radio/keys/binder

6. Risk Register
Risk | Trigger | Decision-maker | Fallback

7. Couple Wishes
[Free-form, ~500 words from the couple, written in their voice, never edited by venue staff.]

That is the document. It is not glamorous. It does not need to be. What makes it work is not the template — it is the 90 days of conversations that flow into it.

The compound effect: better days mean better reviews mean better booking rates

Here is the part that operators forget. A clean wedding day is not just about avoiding a bad review — it is the single biggest driver of future bookings. The couples whose weddings ran smoothly are the ones who become referrals, who tag your venue in 47 photos on Instagram, and whose vendors recommend you to the next 12 inquiries that come in.

The math compounds in the other direction too. A single bad day can cost you 6–10 inquiries the following season. The 90-day run-of-show is not a luxury — it is the cheapest insurance policy in your operation. If you are building a run-of-show two weeks before every wedding because you "have not had time," what you actually do not have time for is the bookings you will lose because of one unforced error.

Further reading for venue operators

• The Final 30 Days: A Pre-Wedding Communication Cadence — the touchpoint script that pairs cleanly with this run-of-show template.
• The Coordinator Inbox Audit — the 14 emails every venue sends twice, and how to automate 80% of them.
• The Wedding Venue Visibility Gap — why the planning you cannot see is costing you real money.
• The First 30 Days After a Couple Books — the playbook for setting up every upsell (and every clean day-of) that follows.
• From Booking to Big Day: Modern Venue Coordination Workflows in 2026.