Event Run of Show
Manage stage, broadcast and event cues in order. A scheduled start and each cue's target length produce planned times; actual start, finish and pause intervals are recorded separately. Only queued cues may be reordered, with a change history. This runs in this tab's memory, so download the JSON yourself.
Key features
- Ordered event cues with title, owner and target length
- Actual start, pause, resume and finish timestamps with event history
- Cumulative planned times and live or completed end delay
- Queued-cue reordering with finished cues locked
- Printable run sheet and versioned JSON and CSV downloads
How to use
- Explore the example or create a new project and set the scheduled start.
- Add each cue's title, owner and target minutes, then put queued cues in the right order.
- At the event, start the next cue, pause and resume as needed, then finish it.
- Review planned and actual times, elapsed time, end delay and event history.
- Save JSON during and after the event; share a CSV or printed run sheet.
Use cases
- Run conference talks and transitions
- Track live delay in a stage rehearsal
- Record broadcast cue order and actual times
- Compare target and actual cue times after an event
Frequently asked questions
Does the timer stop when I hide the tab?
No. The browser may throttle display updates, but the page recalculates from actual timestamps and wall-clock time when visible again. Hidden time counts unless the operator explicitly pauses the cue.
Can I change a cue that already ran?
Completed and active cues cannot be edited or moved. Only queued cues can be reordered. Reordering is recorded in history and future planned times are recalculated in the new order.
How is delay calculated?
Planned end equals scheduled start plus cumulative target lengths. Live delay compares now with the current cue's planned end; completed delay compares actual finish with planned end. A negative value means early. Pauses reduce active elapsed time, but wall-clock delay includes pause time.
Is it autosaved or an audit-proof record?
No. It stays in this tab's memory and nothing is sent to a server. Download JSON during and after the event. JSON can be edited by the user, so it is not tamper-proof.
How is this different from the scoreboard, Gantt or teleprompter?
The scoreboard changes team scores. The Gantt planner computes pre-event dependency schedules. The teleprompter scrolls a script. This tool operates ordered event cues, records actual start/pause/finish times and shows planned-versus-actual delay.
Privacy
All entries and timestamps stay in this tab's browser memory. Nothing is autosaved or sent to a server. A system-clock change can affect displays and recorded times; this is not broadcast-grade timecode or a tamper-proof audit log.
Comments & questions