Lead a set as producer

On set, the producer owns the conditions and the director owns the content. The days that go wrong are usually the ones where somebody confused the two.

What this is about

Everyone else on a set has a machine, a light or a frame to look after. The producer's instrument is the day itself: the burn rate, the client's mood, the next location, the question nobody has asked yet. That work is invisible when it succeeds, which is why inexperienced producers drift toward the monitor, where results are visible. Resist that pull. A producer standing next to the client, answering questions before they become interruptions, buys the director more creative freedom than any note over the shoulder ever could.

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:

  • Client questions route to the producer first — a client who briefs the camera operator directly has already cost the day twenty minutes
  • The producer's standing spot is near the client and the exit, not behind the director's shoulder at the monitor
  • Every wish uttered on set has a price in minutes; the producer is the only person expected to say it out loud
  • A producer who disappears to scout lunch during the hardest setup teaches the set to stop asking

Step by step

This order gets you there fastest:

  1. Align with the director before the day: which shots are non-negotiable, where coverage can shrink under pressure, and who calls the trade when time runs out. Decide this in calm, not in crisis.
  2. Welcome the client personally, set viewing rules early — where to stand, when to speak, who collects wishes — and give them a schedule so they can see the day working.
  3. Check actual progress against the plan at fixed points, not continuously. Morning, before lunch, mid-afternoon: three honest readings beat sixty nervous glances at the monitor.
  4. When a change request lands, answer with consequences instead of yes or no: what it costs in minutes, what it displaces, what you recommend. Then let the named decider decide.
  5. Keep the logistics train running while the set shoots: next location confirmed, transport timed, weather watched, overtime risk flagged to the client before it materializes.
  6. Note every deviation from the plan as it happens — added shots, dropped scenes, extra hours — so the wrap report and the invoice tell the same story without archaeology.
  7. Debrief the director in two minutes at wrap: what the day means for the remaining schedule, and what has to change in tomorrow's call sheet before it goes out.

Common pitfalls

What most often goes wrong in practice:

  • Giving creative notes over the director's shoulder because standing around feels unproductive
  • Hiding the cost of client wishes until the invoice makes them visible
  • Being unreachable during the hardest hour because something trivial needed organizing

With TillyGen

When the client asks for one more shot, you open the TillyGen schedule and show what it displaces — the trade becomes a marked change in the plan both sides can see, instead of a promise that surfaces on the invoice.

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

Should the client be on set at all?

Usually yes — approvals happen faster and surprises die early. The condition is a briefed client: fixed contact person, agreed moments for feedback, and no direct requests to crew.

What do I answer when the client wants one more version of a shot?

Never a bare yes. Name the price in minutes, name what it displaces, offer a trade. Most one-more-wishes evaporate when their cost becomes visible; the ones that survive were worth shooting.

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.