Recover a slipping schedule

Schedules do not collapse suddenly. They erode in ninety-second increments while everyone is busy, until someone finally does the math out loud — the recovery starts at that sentence.

What this is about

The instinctive reactions to a slipping day are all wrong. Hurrying makes crews sloppy and slower. Shaving five minutes evenly off every remaining setup punishes the good scenes for the sins of the bad ones. Skipping lunch converts one lost hour into a slow afternoon. The working method is surgical: quantify the gap, rank what remains by what the film actually needs, and remove whole pieces of coverage — a third angle, a nice-to-have insert — before touching any scene the story cannot live without. Then tell everyone the new plan, once, completely.

The order matters more than the tools. Skip a step and you usually notice two steps later — by which point the fix costs several times as much.

What runs differently here

Where this differs from the general case:

  • Measure in setups, not in feelings: shots remaining times realistic minutes per shot against minutes to hard out
  • Coverage is negotiable, scenes barely, story never — cut in that order and the film survives the day
  • Two setups merged into one repositioned shot recover more time than five setups rushed
  • A dropped shot that post never hears about becomes a hole in the edit six weeks later

Step by step

This order gets you there fastest:

  1. Do the arithmetic the moment your gut reports drift: list remaining shots, multiply by honest minutes each, compare with the clock. A number ends the debate about whether there is a problem.
  2. Take the director aside for three minutes — not at the monitor, not in front of the client — and rank the remaining material: must for the story, should for quality, could for love.
  3. Cut coverage first: drop the third angle, let a oner carry a transition, plan two shots to merge into one wider frame that does both jobs. Scenes fall only after coverage is exhausted.
  4. Merge setups that share light and camera position, even across scenes. Company moves and re-lights are where hours hide; frames are where minutes hide.
  5. Announce the recovered plan to the entire set in one statement: what falls, what merges, what the new order is. Ten quiet individual corrections create ten different days in ten heads.
  6. Hold the line on meals and safety margins. Both feel like reserves and are actually load-bearing walls — take them out and the afternoon collapses on top of the delay.
  7. Write down every dropped or simplified shot with a word on why, and give the list to post the same evening. What was cut consciously can be solved consciously.
  8. After the shoot, trace where the time actually went — the slow location, the underestimated setup class, the chronic late start — and feed that into the next schedule's assumptions.

Common pitfalls

What most often goes wrong in practice:

  • Rushing the crew, which trades quality away and gets no time back
  • Cutting the meal break and paying for it with a half-speed afternoon
  • Dropping shots silently so the edit discovers the holes weeks later

With TillyGen

Because every shot in TillyGen knows its scene and its slot, re-planning under pressure is moving marked pieces instead of rewriting a document — and the dropped-shots list post needs is already in the plan's change trail, exportable as PDF or CSV.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.

Frequently asked

At what point do I involve the client in schedule triage?

When their deliverables are affected, and with options rather than apologies: this falls, this merges, this survives — or we extend. Clients handle trade-offs far better than surprises.

How do I stop the same slip from recurring every shoot?

Keep the numbers. Actual minutes per setup class, per location type, per crew size — three shoots of records turn scheduling from optimism into arithmetic.

How long does it take to get started with TillyGen?

A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.

Can the results be exported?

Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.