Why schedules start to break in the second week of prep

August 31, 2026 · updated August 31, 2026

Ask any 1st AD which week of prep is worse, and the answer is rarely the first. The first week usually feels almost calm – the schedule goes up, the days look reasonable, nothing obviously wrong jumps out. It’s the second week where things start to genuinely go wrong: conflicts appear that weren’t there before, cast dates shift, locations that seemed settled turn out not to be. The schedule didn’t get worse. It got tested.

A first-week schedule is built on assumptions, not confirmations

The first schedule any production builds is necessarily provisional. Cast availability is what an agent said in an email three weeks ago, not a signed and confirmed date. A location is what a scout thought would work, not what a permit office has actually approved. None of this is careless – it’s simply the order things happen in. A schedule has to exist before anyone can confirm anything against it, which means the earliest version is, by necessity, built on a stack of reasonable guesses rather than settled facts.

That’s exactly why week one often looks calm. A schedule full of assumptions has nothing yet to disagree with. It’s internally consistent because nobody’s checked it against anything external yet.

Week two is when those assumptions get tested against reality

This is where the calm ends, and it’s not because the schedule got worse – it’s because the world it was guessing at started talking back. An agent confirms an actor is only available three of the five days the schedule assumed. A location scout comes back from a second visit with a permit restriction nobody knew about. A department head, seeing the schedule properly for the first time, points out a build time that was never realistic. Every one of these is a piece of the schedule’s original guesswork turning out to be wrong, arriving all roughly around the same point in prep – because that’s simply how long confirmations take to come back.

More eyes land on the schedule in week two than in week one

A first-draft schedule usually circulates narrowly – the AD, maybe the line producer, in a rough form. By the second week, it’s typically gone out wider: department heads reviewing it in earnest for the first time, a line producer scrutinising it against the actual budget rather than a placeholder one, sometimes a director looking at the shooting order seriously for the first time. More scrutiny finds more problems. This isn’t a sign the schedule got worse between week one and week two. It’s a sign it finally got read properly.

Contracts and confirmations tend to land on a similar timeline

Deal memos, location agreements, and crew confirmations often cluster around the same point in prep, simply because that’s how long the paperwork behind each of them takes to move. A schedule that looked settled in week one can find several of its foundational assumptions confirmed, denied, or changed within the same few days of week two – not because anyone was slow, but because that’s when this particular category of information naturally arrives.

A worked example

Picture a fairly ordinary case: a schedule built in week one assumes a supporting actor is available for three consecutive days, mid-shoot. In week two, their agent confirms availability for only two of those three, with the third now conflicting with a prior commitment. That single change doesn’t just move one actor’s row. The scene originally set for day three of that block needs a new day. Whatever was going to shoot on the day it moves to needs to shift somewhere else, or the day’s page count grows past what’s realistic. If a location was booked for a specific date range assuming the original block, that booking might now need renegotiating too. One three-word email from an agent – “only two days work” – and a chain reaction runs through the whole back half of the schedule. Multiply this by however many cast members, locations, and crew confirmations are still outstanding in week one, and it becomes clear why week two feels like everything breaking at once: it’s the same handful of pending confirmations, several of them, landing in the same several days.

The exact week varies with how long a production’s prep period runs – a four-week prep and an eight-week prep won’t hit this moment on the same calendar date. What doesn’t vary is the shape of it: a period of schedule-building on assumptions, followed by a period where those assumptions get checked against reality, arriving in a cluster rather than trickling in evenly. Calling it “the second week” is a useful shorthand for a shorter prep period. On a longer one, the same pattern often repeats more than once, each time a new wave of confirmations comes due.

Why a static schedule makes this worse than it needs to be

A schedule that lives in a document nobody re-checks until the next draft compounds this problem, because each newly confirmed piece of information sits unreconciled until somebody manually notices it doesn’t match anymore. A schedule connected to its own conflict checks re-evaluates the moment new information lands – an availability update, a location confirmation – rather than waiting for the next scheduled review to catch what’s already changed. That doesn’t make week two calmer. The same confirmations still arrive on the same rough timeline regardless of what tool is holding the schedule. It does mean the gap between a piece of information changing and someone noticing it changed things gets much shorter, which is most of what determines whether a second-week conflict gets caught with two weeks of runway left or two days.

What this means in practice

The mistake worth avoiding is treating a calm first week as evidence the schedule is solid. It isn’t evidence of anything except that nothing has challenged it yet. A schedule that hasn’t been checked against a confirmed cast date, an approved location, or a department head’s actual read isn’t validated – it’s just untested, which looks identical to validated right up until the moment it isn’t.

The practical response isn’t to expect fewer problems in week two. It’s to expect this specific one, and build the week accordingly: treat the second week as the point where the schedule needs active checking against everything that’s newly confirmed, rather than being surprised each time an assumption doesn’t hold. A conflict caught because someone was watching for it during the week it was always going to surface is a normal part of prep. The same conflict, caught by accident three days before the shoot, is the version that actually costs something.