Producer
The producer owns the gap between what was promised and what is achievable.
What this is about
Every other department can escalate a problem. The producer is where escalation stops — which means the plan has to be right before the crew is booked, not after.
Every department needs the same plan in a different view. That is exactly where document collections fail: they only ever serve one perspective well.
What runs differently here
Where this differs from the general case:
- A quote given before the shot list exists is a guess with a signature under it
- Contingency below 10 % turns the first weather day into an invoice conversation
- The schedule the client signs off and the schedule the crew shoots must be the same document
What the plan has to deliver
A production plan is useful to this role when it provides the following:
- A setup count before the quote goes out, not after
- Contingency stated as a number, not as an intention
- One schedule that client and crew both work from
- Cost consequences visible at the moment a scene moves
Common pitfalls
What most often goes wrong in practice:
- Quoting from a brief without breaking it into setups first
- Treating prep days as free because nobody is on camera
With TillyGen
TillyGen turns the brief into a setup count and a schedule before you quote, so the number you give is one you can hold.
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
How do I quote a job before the shot list exists?
Break the brief into an estimated setup count first, then apply your day rate. A setup estimate is defensible; a gut number is not.
What contingency should a commercial budget carry?
10 % is the industry floor. Below that, a single weather day turns into a conversation about the invoice rather than a line in the budget.
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.