What Is a Production Schedule? Definition and Example
A production schedule is the master timeline for producing an event, covering everything from load-in and rehearsal through show and strike, with times and owners for each phase. The run of show is the part that covers the show itself, minute by minute.
What a production schedule covers
A production schedule starts long before doors and ends after the last case rolls out. A typical one covers load-in, setup, soundcheck, rehearsal, doors, the show itself, and strike, each with a start time, a duration, and an owner. It is how the production manager knows the rigging call does not collide with the floor build, and how every vendor knows when the dock is theirs.
Production schedule vs run of show
The production schedule is the wide view of the whole production day. The run of show is the tight view of the show. Producers build both, and both stay far more useful as live documents the team can open than as printouts that go stale.
Keeping the schedule live
Production days shift. A truck runs late, soundcheck runs long, and the printed schedule is wrong by mid-morning. Build the schedule in NextShow instead: each phase is a segment, times cascade when something moves, locked segments hold the hard deadlines, and the whole crew follows one live link that is always current.
Build a live production schedule
Questions
What is a production schedule?
A production schedule is the master timeline for producing an event. It covers every phase from load-in and rehearsal through show and strike, with a time, a duration, and an owner for each phase.
What is the difference between a production schedule and a run of show?
The production schedule is the wide view of the whole production day, from load-in to strike. The run of show is the tight, minute by minute view of the show itself. Producers build both.
How do I share a production schedule with the crew?
Send one live link. A View link in NextShow opens on any device with nothing to install, so riggers, AV, catering, and venue staff all read the same current schedule instead of a printout that went stale at load-in.
