Broadcast Rundown 101: What It Is, Why It Matters, and How to Build One
A clear, beginner-friendly guide to what rundowns are, how they keep live shows on time, and the exact steps to build one for broadcasts, esports, events, and livestreams.
A broadcast rundown is the single source of truth for a live show. It lists every segment in order, who’s on comms, which graphics and videos roll, and exactly when cues happen. This guide explains the essentials and gives you a practical framework to build a reliable rundown from scratch.
What is a broadcast rundown?
A rundown is an ordered table of segments (rows) with timing, roles, assets, and notes (columns). It keeps producers, directors, TDs, audio, graphics, talent, and clients aligned in real time so the show starts, flows, and ends on time.
Why rundowns matter
- Timing control: plan total duration, track over/under, and absorb drift with buffers.
- Operational clarity: each cue shows who acts and what rolls (Replay/Playback, GFX, stinger, SFX).
- Risk reduction: fewer missed cues, fewer last-minute scrambles, smoother talent delivery.
- Client confidence: visibility for stakeholders; easy approvals and changes.
Core components of a solid rundown
- Segment info: slug/title, description, objective.
- Timing: est. duration, planned start/end, live over/under.
- Roles: who calls/executes (Producer, Showcaller, TD, A1, GFX, Replay, Prompter, Talent).
- Assets & sources: graphic IDs, lower-third text, VT filenames, camera/source notes.
- Cues: stand by / roll / take / clear; tosses to talent or desks.
- Notes & contingencies: tech pause plan, backup fills, sponsor requirements.
Example rundown structure (highly condensed)
| # | Segment | Est. Dur. | Roles | Assets | Cues | Notes |
|---|---|---|---|---|---|---|
| 00 | Pre-Show Standby | 02:00 | Prod/TD/A1 | BG music, slate | STBY→ROLL BGM | Confirm comms |
| 01 | Cold Open | 00:30 | TD/GFX | Open stinger VT | ROLL (Name of tape source) →TAKE | Ready desk cam |
| 02 | Host Intro | 01:00 | Talent/Prompter | L3: host name | TAKE CAM 1→L3 (Lower third) | Hit beats |
| 03 | Segment A | 05:00 | Prod/TD/GFX | Pkg, GFX IDs | ROLL Tape→TAKE | Buffer 0:30 |
| 04 | Credits & Out | 00:30 | TD/A1 | End slate, music | TAKE→FADE OUT | Wrap comms |
How to build a rundown (step by step)
1) Define the show spine
Map the major blocks: open → host intro → segments/interviews/packages → sponsor obligations → finale/outro. Assign target durations and total running time (TRT).
2) Add timing & buffers
Estimate durations per segment and insert short buffers (10–30s) every few blocks. Mark where you’ll shave time if you run over.
3) Wire roles & assets
For each row, note who acts and which assets roll (lower-third text, VT filenames, stingers, camera/source). This prevents “what are we taking?” moments.
4) Plan cues & handoffs
Write clear cues: Standby/Ready/Roll/Take/Clear. Add tosses (Host → Desk → Field) so talent and TD know exact transitions.
5) Rehearse & refine
Run a full rehearsal to validate pacing. Adjust durations, confirm graphics text, and lock critical rows near air.
Best practices for live success
- One live source of truth: avoid multiple files; maintain a single shared rundown.
- Assign a Showcaller: one person owns over/under and final timing decisions.
- Use viewer links: let clients/talent follow along without managing licenses.
- Attach assets to rows: lower-third text and VT IDs live in the rundown.
- Define a change protocol: who can edit, who approves, who communicates.
Common mistakes to avoid
- Version chaos: PDFs/screenshots circulating after changes were made.
- Rigid plans: rundowns that can’t adapt to late changes or tech pauses.
- Asset gaps: missing lower-third text or VT filenames at go-time.
- No buffers: shows run long with nothing to trim safely.
Template starter columns
- # · Segment · Description
- Est. Dur. · Planned Start/End · Over/Under
- Roles (Prod/Showcaller/TD/A1/GFX/Replay/Prompter/Talent)
- Assets (L3R text, VT IDs, stingers, SFX)
- Source (CAM, Program, ISO, Game, Remote)
- Cues (Standby/Roll/Take/Clear/Toss)
- Notes · Status (Planned/Ready/Live/Done)
Quick pre-show checklist
- Single shared rundown link distributed to crew, talent, and client.
- Showcaller assigned; timing/over-under panel visible to control room.
- All lower-thirds and VT filenames verified in-row.
- Buffers placed and a shave plan agreed.
- Tech-pause fill segment ready (music bed + slate).
Ready to Streamline Your Production?
Get your first show organized in minutes. Create your free Cuer account today.