Show Run Sheet Timing Calculator

Show Run Sheet Timing Calculator

Build a timed show flow from doors, anchors, segment blocks, cue density, changeovers, intermissions, holds, and final buffer.

🎬 Event Run Sheet Presets
Timing Inputs
All cue times are calculated from this anchor.

Run Sheet Timing Result

Segment Total
0 min
performance and host time
Cue Load
0 min
called cue allowance
Changeovers
0 min
resets plus format friction
Buffer Formula
00:00
max percent or format floor
Doors00:00 doors from selected lead time.
Critical BlockLongest timing driver appears here.
Run Sheet DensityCues per show hour appears here.
🎛 Timing Control Cards
Anchor
Show start, doors, intermission, hard out
Blocks
Performance, speech, reset, playback
Cues
LX, audio, video, deck, automation
Buffer
Hold margin separated from content time
📋 Segment Timing Table
Segment Type Typical Length Timing Formula Run Sheet Use
Opening walk-on 1 to 4 min intro cue + music bed + first line Locks the first minute after show start.
Band or act set 12 to 60 min song/set duration + applause tail Forms the main content block in concert formats.
Presenter block 2 to 8 min walk-on + remarks + exit cue Best listed as a timed block, not a cue note.
Awards or recognition 3 to 12 min names x pace + photo hold Needs margin when recipients cross stage.
Intermission 10 to 25 min audience break + restart warning Separate from reset time if crews work during it.
🔁 Changeover Timing Table
Changeover Clean Run Caution Run Timing Note
Solo mic or lectern reset 1 to 2 min 3 to 4 min Add time when stairs, awards, or handheld swaps stack up.
Band backline swap 8 to 12 min 15 to 25 min Line check and drum hardware are usual timing drivers.
Dance number reset 1 to 3 min 4 to 6 min Props and shoes can make small resets visible.
Corporate scenic change 3 to 6 min 7 to 12 min Coordinate video walk-ins with deck movement.
Festival act turn 15 to 25 min 30 to 45 min Patch discipline matters more than raw stage size.
📶 Cue Density Table
Cue Density Cues Per Hour Call Pace Operator Risk
Light 0 to 25 Mostly anchors Simple call sheet usually holds.
Moderate 26 to 55 Regular calls Mark standby groups and page breaks.
Dense 56 to 90 Frequent stacks Use cue numbers and clear departments.
Broadcast tight 90+ Near continuous Separate script timing from technical timing.
🧭 Buffer And Hold Table
Buffer Type Usual Range Formula Placement Best For
Show flow buffer 8% to 15% after segments, cues, and changes Live shows with normal audience response.
Festival recovery 15% to 25% after act turns and patch changes Multiple artists and moving backline.
VIP hold 5 to 15 min before opening or keynote Events with fixed arrivals or protocol.
Broadcast pad 3% to 8% inside each timed act Recordings where final runtime is strict.
🏟 Production Format Comparison

Concert

Segment timing is dominated by set length, applause, and encore decisions.

  • Use set blocks
  • Track backline turns
  • Keep encore separate

Corporate

Anchors, walk-ons, playback rolls, and presenter pacing drive the run sheet.

  • Protect show start
  • Mark all video rolls
  • Keep holds visible

Festival

Changeovers and patching are the schedule pressure points between acts.

  • Measure turn time
  • Separate line checks
  • Hold stage clears

Broadcast

Runtime discipline depends on scripted timing, cue count, and controlled reset pads.

  • Count standby cues
  • Time every insert
  • Watch hard out
Timing note: Put cue-call allowance in the calculator even when cues are instantaneous on stage. Standby, acknowledgement, and operator handoff still consume show-calling attention.
Run sheet note: Keep planned holds separate from percentage buffer. A hold is a known event condition; buffer protects the unknowns inside the show flow.

It’s panic time for a stage manager who realizes that he or she has multiple acts left in the show and they’re running behind. Panic begins small and escalates to frantic radio chatter and compressed intermissions.

Create a run sheet from intention instead of hope. Create it as if you knew how long each thing took and how much time are needed between things. Enter those numbers into the tool and it will do the math for you. How many cues need loading? Count the total number of segments. How much time do you have to changeover? What buffer time should there be? Answer all those questions first then look at the tool to see real picture of how long the entire event might take.

How to Make a Good Run Sheet

Planners typically go top-down: they choose a grand total show length and cram stuff into that. That normally won’t work, since it ignores difficulties of producing live TV shows. For example, a changeover will take four minutes, unless there is twisted cables or missed lighting cues. To reflect this reality, the calculator asks you to input normal technical cue density and average changeover times.

If you know roughly how many segments you have and their average run-time, feed those numbers in and the system crunches through raw content time. But it also considers the breaks that interrupt performances, such as presenters’ speeches and hosts’ blocks. Why? Because people pay less attention to a award presentation then a musical number. If you don’t know what’s reasonable timing for any activity, the interface has some helpful reference tables for that.

For example, in a clean run it may only take two minutes to reset a single mic; however, that can be doubled with hand-held swaps and/or stairs. Backline swaps are another matter. Festival acts can take up to 15-25 minutes to change out completely so the feeling of tightness on their schedule makes sense. Knowing this could of helped you give your crew realistic expectations. Underestimating a band’s instrument-patching time will throw off whole evening. That in turn clash with broadcast deadlines or the venue’s strict curfew.

Another frequently neglected metric is cue density. It may seem reasonable at the rehearsal table, but a light cue load multiplied by intricate audio and lighting triggers can lead to operator burnout faster than you think. Use the calculator to estimate your total cue count and average call time. Is the tech team being asked to do too much too fast? More isn’t always better. Higher density doesn’t necessarily lead to more buttons pushed; it leads to a higher chance of delays or response issues (missed cues). Leave wiggle room for handoffs between departments and standby acknowledgements.

When things go wrong (and they always will), buffer time acts like a safety net and prevents the show from unraveling. Adding a simple percentage at the end of your run sheet provides protection against cumulative delays. This can be a ten percent pad for a standard concert or a fifteen percent hold if it’s a festival stage. Either way, it covers the unexpected and allows for technical glitches, slower exits, or even longer applause without having to cut content abruptly. It’s smart to keep planned holds separate from percentage buffer, since one addresses known factors and the other covers unknowns.

In conclusion: A solid run sheet is a dynamic document; it leads the crew through the night with clarity and confidence. It trades structure for guesswork by having numbers figured out in advance. It gives your staff the breathing room they need to work well under pressure. The result? The result is a smoother show where the audience feels entertained, not rushed, and the staff feel prepared, not panicked.

Upfront planning takes time, but it will save you from scrambling later.

Show Run Sheet Timing Calculator

Leave a Comment