Run a shoot day

A shoot day is won in the first thirty minutes and lost five minutes at a time. Running one means watching the clock so everyone else can watch the frame.

What this is about

On small crews nobody carries the title of assistant director, so running the day lands on whoever built the plan — usually the producer, sometimes the director against their own interest. The call sheet is the contract of the day: it fixes when trucks arrive, when the first take rolls and when the location closes behind you. Everything between those anchors is a chain of small trades. The person running the day makes those trades out loud, early and one at a time, instead of letting them pile up silently until wrap stops being possible.

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:

  • The first setup of the morning sets the tempo for every one after it — schedule something achievable there, not the hero shot
  • Lunch on time is schedule protection, not a courtesy: a crew that eats late works the afternoon at half speed
  • A schedule change announced by one person, once, to everyone, is a plan; anything else is a rumor
  • The final hour before a hard out is where quality quietly dies, so place your simplest material there

Step by step

This order gets you there fastest:

  1. Arrive before crew call, walk the location, and check that power, parking, access and the first setup match what the schedule assumes. Fix surprises before they start costing crewed minutes.
  2. Hold a two-minute briefing at call: name the first setup, the target for lunch, the hard out, and the one biggest risk of the day. Everyone hears the same plan exactly once.
  3. Post the setup order where the crew can see it and keep it current. When the order changes, tell everyone and update the sheet — a plan people cannot see is a rumor.
  4. Track each setup against its planned slot. The moment one runs long, decide out loud what gets simplified or dropped later, instead of hoping the lost time comes back on its own.
  5. Protect the meal break at the planned time. Push it only for a shot you are actually rolling on, never for one you are still lighting.
  6. Reconcile the remaining list in mid-afternoon: shots done, shots left, minutes left. If the math fails, cut coverage now while options still exist, not at the hard out.
  7. Call the last setup explicitly so nobody invents one more angle. Then wrap in order: media secured and verified, gear counted, location restored, tomorrow's call confirmed.
  8. Send a short end-of-day note the same evening: what was shot, what moved, and what that means for the next day. Memory does not survive the drive home.

Common pitfalls

What most often goes wrong in practice:

  • Solving creative debates at the monitor while forty crew-minutes tick away
  • Absorbing delays silently until the only options left are overtime or a missing scene
  • Treating the call sheet as the director's problem instead of the day's contract

With TillyGen

The call sheet you send from TillyGen is the same document the schedule was built in — every setup carries its scene, cast and time slot, and a change during the day is a marked edit everyone can trace, not a hallway rumor.

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

Who runs the day when there is no assistant director?

Whoever built the schedule — usually the producer. The director owns what happens inside the frame; someone else must own the clock, or both jobs get done badly at the same time.

How far behind is too far to recover quietly?

One slipped setup is normal friction. From the second one, the day needs a stated decision about what gets simplified or dropped — silent hope converts directly into overtime.

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.