How to build an event production schedule that survives the week
A production schedule is the plan for the days around an event. When the trucks arrive, what gets built and in what order, who is on site, when rehearsals happen, when doors open, and how the room comes down.
It is not the run of show. The run of show covers the hours the audience is in the room, cue by cue. The production schedule covers everything either side of that, in activities rather than cues, usually across several days. Build the production schedule first. Its show day rows become the run of show later.
The schedule is also the single most-forwarded document on any job. Vendors quote from it, venues staff from it, clients read it to understand what they are paying for. It is worth building properly.
Start from the dock, not from the doors
Most people write a schedule forward from the first thing they will do. The schedule that holds up is written from the constraints.
Find out, before you write a line:
When you actually get the room. Not when the venue says the space is available. When you can put a truck at the dock and start moving. Those are different times and the gap is often two hours.
What the dock will physically take. One bay or four. A twenty-six foot box or a fifty-three foot trailer. Whether there is a lift, how big it is, and how long the run is from the lift to the room. A single small lift can add half a day to a build and nobody notices until it is happening.
Who else is in the building. The load in that goes wrong is rarely the one where you planned badly. It is the one where another event was striking in the same corridor and nobody told either producer.
The hard stops. Curfew, noise limits, union break rules, when the client wants to walk the room, when the room has to be clear.
Then build the days between those points.
Sequence by dependency, not by department
The instinct is to schedule department by department, because that is how the quotes arrived. It produces a schedule where six trades are in the room at the same time doing work that cannot happen simultaneously.
Sequence by what physically has to happen first. Rigging before anything under the rig. Floor before furniture. Power before anything that needs it. Scenic before the lighting that is focused on it. Catering last into a space that has to be clean.
Write the dependencies down as you go. When a truck is late, the useful question is not "what were we doing at two" but "what cannot start now", and a schedule built on dependencies answers that in a second.
Put a crew count on every line
This is the discipline most schedules skip, and it is the one that pays for itself.
A line that says "install soft goods, 9:00 to 12:00" tells you very little. A line that says "install soft goods, 9:00 to 12:00, four crew" tells you the day costs twelve crew hours, which is a number you can hold a labour quote against. Do that on every line and your day total is a real figure rather than an impression.
When the invoice comes in for more hours than that, you have an actual conversation to have rather than a feeling that it seems high.
Handle the days as separate clocks
A production schedule is not one long timeline. It is a set of days, each with its own start.
The practical version of this: a build day that runs to 11 PM does not mean the next day starts late. The next day starts when the crew is called. If your schedule treats the whole build as one continuous run of time, one overrun on Tuesday drags every remaining day and the document stops being true.
Show days that run past midnight are the other half of the same problem. A gala that ends at 12:40 AM ends on the following calendar day, and the strike crew called for 1:00 AM is being called for that day, not the one on the header of the page.
Build the buffer where you can spend it
Contingency time is not one block at the end. At the end it is worth nothing, because by then the thing that went wrong has already moved everything after it.
Put it in the places where overruns happen and where you can still recover: after the first load, after rigging, before rehearsal. Twenty minutes in four places will save a day that ninety minutes at the end will not.
Decide who owns each line, by name
Department names are not owners. "Lighting" does not answer a phone. The person who answers the phone is the owner, and their name goes on the line.
The status of every line matters too, and it only takes a word: not started, in progress, complete, blocked. Blocked is the important one. A schedule that cannot show you what is stuck is just a plan of what you hoped would happen.
Version it, and log who has it
Every serious production schedule goes out five or six times before show day, and the version people are arguing about on site is almost never the current one.
Two habits solve it. Put a version number and a time in the document itself, not just in the email. And keep a list of who has it, in what format, which version, and when they last got it. When the AV lead is working from something that does not match, you can see whether they were sent version 4 or version 6 rather than debating it.
The mistakes that cost the most
One document trying to be everything. A production schedule that also carries the show cues is too long to work from on the floor and too detailed to send a client.
No named owner on transitions. Lines get owners. The handovers between them often do not, and that is where hours disappear.
Crew counts left off. Without them there is no defensible labour number, and the invoice conversation becomes a matter of opinion.
A day with no start time. It sounds impossible. It happens on the fourth day every time, because it was added late.
Stale distribution. The schedule was right. The version in the vendor's hand was not.
A working template
The Event Production Schedule template in this shop was built around all of this. Durations drive each day and the clock resets on every date. Crew counts become crew hours per day automatically. A calculated dashboard names anything blocked, any line with no date, owner, duration or crew count, and any day whose hours are not being counted in your totals. There is a distribution log built into the file.
See the Event Production Schedule Template, or go straight to the listing on Etsy. It is $18 and it opens on a complete four day build so you can see how the pieces connect before you type over it.
For the show itself, read what a run of show is and how to build one.