A broadcast rundown template turns a programme idea into an operational plan that the whole production team can follow. It should show what happens, when it happens, how long it lasts, who owns it and which production elements are required. A useful template is more than a list of story titles: it is the shared timing and communication layer between editorial, gallery, studio and presentation.
This guide gives you a practical structure for live TV, streaming, newsroom output and studio productions. If you are new to the terminology, start with what a broadcast rundown is, then use the field structure below to build your own working template.
What a broadcast rundown template must answer
Every line in the running order should answer six basic questions:
- What is happening? Use a clear story or segment title.
- When does it start? Show the calculated start time or planned time-on.
- How long will it run? Separate manual duration, script duration and total duration where needed.
- Who owns it? Assign the producer, journalist, presenter or operator.
- What does production need? Add camera, video, graphics, sound, lighting and prop cues.
- What must the team know? Keep editorial comments and operational notes visible without mixing them into the script.
If any of these answers live in a separate message thread, spreadsheet or printed sheet, the production team no longer has a single source of truth.
Recommended fields for a live TV rundown
| Field | Purpose | Example |
|---|---|---|
| Line number | Stable reference during production | 12 |
| Start time | Planned or calculated time-on | 18:42:30 |
| Story title | Short, unambiguous segment name | LIVE: Election headquarters |
| Manual duration | Planned duration set by the producer | 00:03:00 |
| Script duration | Estimated reading time | 00:00:35 |
| Total duration | Full expected duration of the line | 00:03:35 |
| Assigned | Responsible team member | Field producer |
| Production items | Camera, video, graphic, sound or props | CAM 2, VTR 4, L3 NAME |
| Script | Presenter copy and editorial text | Intro and interview questions |
| Sidenotes | Operational instructions outside the script | Guest joins on return feed |
| Status | Editorial or production readiness | Ready |
A simple 30-minute rundown example
| Start | Title | Duration | Key cues |
|---|---|---|---|
| 18:30:00 | Opening headlines | 00:01:30 | OPEN, CAM 1, headlines graphic |
| 18:31:30 | Top story | 00:04:00 | CAM 2, VTR, lower third |
| 18:35:30 | Live interview | 00:06:00 | Remote input, mix-minus, name graphics |
| 18:41:30 | Explainer | 00:03:30 | Presenter, full-screen graphics |
| 18:45:00 | Commercial break | 00:03:00 | Break sting, playout |
| 18:48:00 | Second block | 00:09:30 | Stories, live and VTR elements |
| 18:57:30 | Close and credits | 00:02:30 | Closing camera, credits, music |
The exact fields will change by format, but the logic should remain consistent. A current affairs show may need detailed source and approval fields. A sports production may need replay, score and commentary cues. A live event may use “run of show” or “run sheet” terminology instead. Our guide to run-of-show software versus broadcast rundown software explains those differences.
Build timing into the template from the beginning
Timing should not be added after the editorial plan is complete. Set an intended duration for every story, account for transitions and confirm that the cumulative end time matches the programme slot. If the show has a fixed end, work backwards from that time as well as forwards from the opening.
For a step-by-step method, see how to backtime a TV rundown. Backtiming exposes hidden gaps, unrealistic interviews and overfilled final blocks before they become on-air problems.
Keep script, cues and communication connected
A presenter script and a production cue describe the same moment from different perspectives. Keeping them together means a producer can change the words while a director still sees the correct camera, graphic or video instruction. It also avoids filenames and cue details becoming detached from the story they belong to.
For multi-user teams, the template should support controlled editing, comments and clear ownership. Read more about collaborative script writing for broadcast teams.
Spreadsheet template or dedicated rundown software?
A spreadsheet can be a useful first sketch, but it becomes harder to manage when timing changes, several people edit at once, scripts grow, cues need structure and the live team requires different views. A dedicated rundown system can calculate timing, keep scripts and production items on the same story, show role-specific information and provide a current version to everyone.
Falcon Rundown is browser-based rundown software with shared projects, story scripts, colour-coded production items, sidenotes, comments, live timing, cuecards, prompter tools, print/PDF options and MOS-related integrations. That makes the template operational rather than static.
Pre-production checklist
- Every line has a clear title and owner.
- Durations include transitions, not only spoken content.
- Scripts and production cues are attached to the correct story.
- Graphics, video and remote inputs use recognisable names.
- The final calculated end matches the transmission slot.
- Editorial comments are separated from on-air copy.
- Presenters, directors and floor teams have the view or output they need.
- Last-minute changes are made in one shared rundown.
Frequently asked questions
What is the difference between a rundown and a running order?
They usually describe the same core document: the ordered plan for a programme. “Rundown” is common in North American broadcast, while “running order” and “run sheet” are common in other regions and production sectors.
Should a rundown include the full script?
For script-led programmes, yes. Keeping the script on the story helps editorial and production work from the same context. Short unscripted segments may only need prompts, questions or operational notes.
How detailed should production cues be?
Detailed enough that the relevant operator can identify the source, asset and action without guessing. Use consistent names for cameras, remote inputs, video clips and graphics.
Ready to move from a static template to a shared live workflow? Explore Falcon Rundown or book a demo.