Schedule a multi-day shoot
Day one of a multi-day shoot is rarely the problem. Day three is — when accumulated fatigue meets the scenes that were postponed.
What this is about
Single days forgive improvisation; sequences of days do not. Every decision compounds: a late wrap tonight pushes tomorrow's call, a postponed scene lands on the fullest day, and a crew that never recovers shoots visibly worse by the end of the week. Multi-day scheduling is therefore less about filling days than about protecting the sequence — clustering locations so moves happen between days rather than during them, respecting rest periods like the eleven-hour turnaround, spending the heavy setups early, and deciding in prep which day absorbs the overflow that always comes.
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
In planning terms, that means:
- Rest is a scheduling constraint, not a courtesy: eleven hours between wrap and next call is the standard the plan must contain.
- Call time progression matters — drifting earlier and later on alternating days wrecks sleep faster than long days do.
- The heavy scenes belong early in the sequence, while attention and goodwill are at their peak.
- A float day or half-day is the difference between absorbing a problem and cascading it.
Step by step
This order gets you there fastest:
- Cluster the schedule by location so company moves fall between days, not inside them. A move overnight costs nothing; the same move at noon costs setups.
- Place the heaviest and most failure-prone scenes in the first half of the sequence, leaving the back half for material that survives a tired crew.
- Build call times as a stable progression and protect the eleven-hour turnaround: a night scene in the middle of the week reorganizes everything around it.
- Plan travel days as travel days. A four-hour drive before a full shooting day is a full shooting day less.
- Decide where the buffer lives — a float half-day, a light final day — and defend it when someone proposes to fill it in prep.
- Schedule dailies logistics and data backup into each evening, so a card problem surfaces the same night and not at the end of the week.
- Publish a day-by-day overview to all departments and clients, with the hard constraints visible: talent windows, access hours, sunset times.
- Hold a short review each wrap: what slipped, what moves, which version of tomorrow's plan is now true — and communicate it before people go home.
Common pitfalls
What most often goes wrong in practice:
- Front-loading nothing, so the postponed scenes pile onto the last day with no room left to fail.
- Treating rest periods as negotiable, then wondering why day four's footage needs reshoots.
- A schedule that only the producer has seen — departments discover the travel day when they are in the van.
With TillyGen
TillyGen drafts multi-day schedules with moves, clusters and constraints in one view, and when a scene slips, the following days re-balance instead of silently overloading.
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
Where should the buffer day sit in a shoot week?
Late enough to catch accumulated slippage, early enough to still matter — a light second-to-last day is a common compromise. A buffer on day one protects nothing.
How do I handle a night shoot inside a day sequence?
Isolate it: schedule the night block at the edge of the sequence with a recovery gap after, so the turnaround does not amputate the next day.
What belongs in the end-of-day review?
Three things: what did not get shot, where it moves, and which version of tomorrow's plan is now valid — communicated before wrap, not by message at midnight.
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.