Run-of-show software and broadcast rundown software solve a similar problem: they put every segment, cue and timing decision into one shared plan. The terms are often used interchangeably, but production teams may expect different features depending on whether they work in live events, television, streaming or news.
Understanding the overlap helps you choose software that fits the actual workflow instead of buying a tool based on terminology alone.
What is a run of show?
A run of show is the chronological plan for a live event or programme. It normally includes segment names, start times, durations, speakers, cues and responsibilities. Event producers may also call it a show flow, production schedule or cue sheet.
Typical run-of-show users include:
- Conference and corporate event teams
- Live-streaming crews
- Awards shows and stage productions
- Sports presentation teams
- Broadcast specials and studio programmes
What is a broadcast rundown?
A broadcast rundown is also a chronological show plan, but it is usually organised around stories. Each story can contain a presenter script, editorial ownership, production items, comments, notes and calculated timing. Television teams may call the same document a running order or run sheet.
A newsroom rundown often changes continuously. A story moves, a live interview becomes shorter, a video arrives late or a script changes after rehearsal. The software therefore needs to keep editorial and production details connected while the order changes.
If you need a starting structure, use this broadcast rundown template for live TV.
Run of show vs broadcast rundown
| Requirement | Run-of-show focus | Broadcast rundown focus |
|---|---|---|
| Core unit | Event cue or programme segment | Story or broadcast segment |
| Script | Speaker notes or event script | Presenter copy and editorial script |
| Timing | Scheduled clock and show calling | Forward timing, backtiming and on-air progress |
| Production cues | Stage, lighting, sound, video | Camera, graphic, video, sound, input, props |
| Collaboration | Production manager and department leads | Producers, journalists, directors, presenters and operators |
| Outputs | Crew views and cue sheets | Rundown, script, cuecards, prompter and print/PDF views |
| Integrations | Event clocks and show-control tools | MOS, graphics, video and broadcast automation |
The right choice is not decided by the label. A live-streamed conference may need broadcast-style scripts and graphics. A magazine show may need event-style show calling. The best system is the one that supports the detail and outputs your team really uses.
Features to look for in run-of-show software
1. One current plan for everyone
Every role should see the latest order without sending new files or asking which version is correct. Changes should be visible quickly and without destroying another person’s work.
2. Timing that remains useful during the show
Planned durations are only the beginning. During production, the team needs to know what is running, what comes next, how much time has been spent and whether the programme is over or under. A static sheet cannot provide that operational feedback by itself.
3. Structured production cues
Colour-coded and typed cues are easier to scan than free-text abbreviations. Camera, video, graphics, sound, lighting, props and instructions should remain attached to the correct line even after reordering.
4. Script and note separation
On-air words, producer comments and technical instructions serve different audiences. Keep them connected but visually distinct so a presenter does not read a control-room note on air.
5. Views for different roles
A director may need cues and timing. A presenter may need script or cuecards. A floor manager may need a concise now-and-next view. Role-specific views reduce noise while preserving one shared source.
6. Browser and mobile access
Productions rarely happen on one workstation. Browser-based access makes it easier for remote producers, gallery staff, presenters and mobile users to reach the same show plan without distributing local files.
When a spreadsheet is enough
A spreadsheet may be sufficient for a short, low-risk event with one editor, few cues and no live recalculation. It becomes fragile when several people need to edit, the order changes repeatedly, scripts are long, cue data must be structured or different departments need different outputs.
For more detail, see the hidden costs of spreadsheet rundowns.
When broadcast rundown software is the better fit
Choose a broadcast-oriented system when the show contains scripts, story ownership, production assets, live timing, cuecards or prompter output. It is also valuable when editorial and technical teams work on the same programme from different locations.
Falcon Rundown combines a shared running order with script editing, production items, sidenotes, comments, live timing, cuecards, prompter features, PDF/print outputs and integration options. It can therefore serve traditional broadcast workflows as well as many structured live productions.
Questions to ask before choosing a platform
- Can multiple users work without losing one another’s changes?
- Does the software support scripts as well as short cues?
- Can the team see live progress and over/under timing?
- Can production items be categorised rather than typed as plain text?
- Are cuecards, prompter and print outputs generated from the same source?
- Can permissions be adapted to producers, commenters and read-only users?
- Can it connect to the graphics, video or automation systems you already use?
Use our TV production planning software buyer’s guide for a more detailed evaluation, and read how to backtime a rundown before testing a live timing workflow.
Frequently asked questions
Is a run of show the same as a rundown?
In many productions, yes. Both describe the ordered plan for a live programme. The surrounding workflow determines whether teams expect event cues, editorial scripts, broadcast timing or automation integrations.
What is a run sheet?
A run sheet is another regional or industry term for the running order. It normally lists segments, timings, responsibilities and production notes.
Can one platform support both events and broadcast?
Often, provided it supports flexible fields, structured cues, collaborative editing, role-specific views and timing. Always test the platform with a real production rather than only a simplified demo.
Explore the Falcon Rundown workflow, review pricing or book a demo.