Skip to wedding guide

Wedding planning guide

Wedding Reception Run of Show: Cues, Owners, and Handoffs

A wedding reception run of show is the working cue sheet for the reception itself: it names each trigger, the person who owns it, what must be ready first, the spoken cue, the next handoff, and a fallback if timing changes. It complements—not replaces—the whole-day Wedding Timeline and the Host Script.

  • Private by default
  • Facts stay reviewable
  • Earlier versions stay recoverable

Start with the right source material

Who this guide serves and what to prepare.

Designed for

  • Couples who want a calm, reviewable reception plan without handing private details to every vendor.
  • A first-time MC or host who needs to know when to speak, when to wait, and who receives the handoff.
  • A planner or trusted family coordinator aligning meal service, photography, speeches, and entertainment around real event constraints.

Inputs to approve

Reception anchors
Confirmed room access, guest arrival, meal service, speeches, dancing, cake, and closing constraints.
Named owners
The person accountable for each moment, plus a reachable backup where the venue permits one.
Dependencies
What has to be ready before a cue: seats cleared, photographer placed, music loaded, cake staged, or catering released.
Spoken-copy boundaries
Approved names, pronunciations, sensitive-story limits, and the exact moments where the host should speak.

A bounded, review-first workflow

How to build a reviewable reception run of show

  1. 01

    Set reception anchors

    Start from the confirmed whole-day timeline, then isolate only reception moments that need an active cue or handoff.

  2. 02

    Assign one owner per trigger

    Name the person who decides the moment can proceed. List dependencies instead of assuming a DJ, venue, or caterer shares the same information.

  3. 03

    Write the spoken cue separately

    Keep the host's actual line brief and factual. The run of show records the trigger and handoff; the Host Script keeps the full spoken copy reviewable.

  4. 04

    Agree a fallback before doors open

    For each time-sensitive moment, choose a delay, shorten, skip, or reorder decision and the person authorized to make it.

01

A run of show is narrower than the Wedding Timeline

The Wedding Timeline holds the day-wide constraints: travel, ceremony, photos, venue access, and buffers. A reception run of show begins once the room is operating and turns only the active reception moments into cues people can execute.

That boundary prevents a useful cue sheet from becoming a second, conflicting master schedule. If an anchor changes, update the Timeline first, then review the dependent reception cues.

  • Use the Timeline for fixed time, location, dependency, buffer, and change authority.
  • Use the Host Script for full spoken wording and pronunciation notes.
  • Use this run of show for reception triggers, accountable owners, handoffs, and fallback decisions.
02

Make every cue executable by a real person

A time alone is not a cue. “7:40 speeches” leaves open who checks that the speaker is present, whether catering has paused service, whether the photographer is in position, and what the host says to start the moment.

The worksheet below makes those questions visible. It is deliberately a coordination aid, not a claim that AI Wedding Studio provides DJ, venue, or vendor collaboration software.

  • One owner is accountable even when several people help.
  • Dependencies are checked before the spoken cue begins.
  • A handoff states who receives responsibility next.
03

Protect people, culture, and the room

Wedding customs, family roles, and the order of toasts vary. Treat this guide as a planning framework, not a universal etiquette rule; confirm any cultural, religious, venue, or catering requirement with the people responsible for it.

Keep private family history, accessibility needs, names, and contact details in the private Wedding Project. Share a minimum necessary export and obtain permission before using personal stories, music, photos, or recordings.

  • Mark examples as illustrative, not real client events.
  • Use approved names and pronunciations rather than guessing.
  • Have the couple or their designated reviewer approve sensitive introductions and fallback choices.

Original worksheet

Reception cue sheet: moment to fallback

Illustrative example only. Confirm real owners, dependencies, and wording before use.
MomentTriggerOwnerSpoken cueNext handoffFallback
Grand entranceCouple and entrances are staged; photographer signals readyPlannerPlease welcome our newlyweds.MC opens the room; photographer captures entranceIllustrative: begin introductions with the wedding party already seated.
ToastsSpeakers are present and catering has paused servicePlannerWe will begin the toasts. Please join us in giving your attention to our speakers.MC introduces the first approved speakerIllustrative: move one unready toast after dessert rather than filling time with private stories.
First danceFloor cleared and music cue confirmedEntertainment leadPlease join us around the floor for the couple's first dance.MC steps away; music beginsIllustrative: use the agreed shortened track if the reception is running late.
Cake momentCake staged and photographer positionedPlannerWe invite you to gather nearby for the cake-cutting moment.Catering begins service after the photo cueIllustrative: skip the announcement if guests are already gathered and the couple prefers a quieter moment.

Quality gate

How to judge the draft before it leaves the workspace.

Ready when

  • Every reception moment has one accountable owner and a visible next handoff.
  • Spoken cues use approved names and match the reviewed Host Script.
  • Dependencies and delay authority have been confirmed with the people responsible.
  • The sheet is dated, versioned, and shared only with the minimum necessary people.

Revise when

  • A cue names a time but not the person who can start or stop it.
  • The room, catering, photography, or entertainment dependency is assumed rather than confirmed.
  • The host must improvise a sensitive introduction or private story.
  • A day-wide change has not been reflected in the reception sheet.

Privacy and rights

Share a usable cue sheet without oversharing the Wedding Project.

A reception cue sheet can be useful to an MC or planner without disclosing private notes, contact details, or family context. Keep the richer source facts and version history in the owner-scoped Wedding Project.

Confirm permission for photos, music, recordings, readings, and personal references. Cultural and family etiquette should be checked with the people involved rather than treated as a generic rule.

  • Remove personal contacts and sensitive notes from any working export.
  • Confirm names, pronunciations, and introductions with the people concerned.
  • Use only media and stories that are authorized for the reception setting.

Questions couples ask before drafting

Frequently asked questions

What is the difference between a reception run of show and a wedding timeline?

A Wedding Timeline covers the whole day and its fixed constraints. A reception run of show narrows to reception triggers, owners, handoffs, spoken cues, and fallbacks.

Is a run of show the same as a host script?

No. The Host Script is the reviewable spoken copy. The run of show tells the team when that copy is used, what must be ready, and who takes over next.

Who should own a reception cue?

Assign the person who can actually confirm that the moment may proceed. Other contributors can be dependencies, but an accountable owner keeps the handoff clear.

What should happen when the reception runs late?

Use a pre-approved fallback: delay, shorten, reorder, or skip a moment, with a named decision owner. Do not improvise sensitive wording or promises to guests.

Your facts stay together

Move this guide into a private Wedding Project.

Keep the profile, ordered timeline, source materials, review notes, and approved versions in one owner-scoped workspace.
Start your private Wedding Project