What actually causes prep-week overtime

August 31, 2026 · updated August 31, 2026

The easy explanation for prep-week overtime is an overly ambitious schedule – too much to do, not enough time. Sometimes that’s true. More often, the actual cause is something less visible: not the total amount of work, but how much of it gets stuck waiting on something else before it can even start.

This isn’t a claim that an overloaded schedule is never the problem

Sometimes a schedule genuinely asks for more than a day or a week can hold, and that’s a real, separate issue worth its own honest look. But it’s worth distinguishing from the more common pattern, because the fix for each is different. An overloaded schedule needs fewer pages per day or more days in prep. A timing problem needs faster propagation of decisions that are already being made at a reasonable pace – and treating a timing problem as a workload problem, by adding more days without addressing why decisions arrive late, often doesn’t reduce the overtime at all.

Waiting is the biggest hidden cost in a prep week

A coordinator can’t finalise a call sheet until the schedule for that day is confirmed. A department head can’t lock their prep plan until the breakdown is complete for their scenes. An AD can’t confirm a location until the scout report comes back. None of this is idle time exactly – everyone’s doing other things while they wait – but it means the actual finishing work, once the blocking information finally arrives, gets compressed into whatever time is left before the deadline, regardless of when in the day that turns out to be.

Decisions made late land as overtime for whoever acts on them

A location confirmed at six in the evening doesn’t cost the person who confirmed it anything extra. It costs the coordinator who now has to update the schedule, the department heads who need the new information to finish their own prep, and everyone downstream of them, all working later than planned because a decision that could theoretically have landed at ten in the morning happened to land at six in the evening instead. The total number of decisions didn’t change. When they landed did.

Working from an outdated version creates work that has to be redone

Prep work done against a schedule that then changes isn’t just delayed – it’s often wasted and has to be redone against the new version. A department head who spent the afternoon prepping for a scene that then moved days isn’t simply behind; they’re now doing that prep twice, once for a version of the plan that no longer exists. Rework doesn’t show up as its own category on anyone’s timesheet, but it’s real hours, and it’s a direct consequence of how late in the process changes are still landing.

Most late nights aren’t about total workload

If you added up all the actual hours of necessary work in a typical overtime-heavy prep day, it usually doesn’t come close to filling the hours actually worked. What fills them is a pattern: hours of partial progress and waiting, followed by a compressed period once the blocking piece of information finally arrives, followed by everyone racing to finish what’s now urgent because the day is nearly over. The workload was real. The overtime is mostly a timing problem, not a volume problem.

A worked example

A costume department is ready to finalise fittings for three actors, pending final confirmation of which scenes they’re now in, following a schedule change still being worked out between the AD and a location scout. The confirmation doesn’t land until after six. Costume now has the information they needed at nine that morning, with the same amount of actual work to do, compressed into whatever’s left of the evening. Nobody in this chain did anything wrong. The location scout wasn’t slow, the AD wasn’t disorganised, costume wasn’t behind. The work simply couldn’t start until the last piece landed, and the last piece landed late, which is a structural timing problem, not a workload one.

What this suggests about actually reducing overtime

Padding the schedule with more calendar days doesn’t fix a timing problem – it just gives the same late-arriving decisions more room to still arrive late within a longer window. What actually helps is shortening the gap between a piece of information changing and everyone who needs it actually having it: a schedule change reaching the call sheet and the affected department heads automatically, rather than through a chain of separate messages that itself takes time to propagate. That doesn’t make decisions land earlier in the day. It does shrink how much downstream time gets lost between a decision landing and everyone who needs it actually knowing.