Statement of Work

What this is about

Where the scope of work describes the project, the statement of work makes it enforceable: it attaches dates, acceptance criteria and payment triggers to each deliverable and gets signed by both sides. Corporate clients often issue an SOW under a framework agreement, one per project. For the production, the acceptance criteria are the part to read twice — they define when a film counts as delivered and when the invoice may go out.

A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.

What runs differently here

In planning terms, that means:

• Acceptance criteria decide when a deliverable is done — vague criteria delay every invoice
• Under a framework agreement, each project gets its own SOW with its own numbers
• Changes after signature run through change requests, not through goodwill

With TillyGen

TillyGen produces the countable project structure — films, setups, days — that a statement of work needs before anyone drafts contract language.

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.