Sign-off
A sign-off is the documented moment a version or phase is finally approved and later changes become billable.
What this is about
"Looks good" in a call is not an approval; it is a mood. A sign-off turns approval into an event: a named person confirms a named version in writing, and from that point the version is locked. This protects both sides — the client knows what was agreed, the production can build on a stable state. The classic failure is shooting or grading against a version that was never formally locked, then absorbing the rework as goodwill.
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:
- A sign-off names a person, a version and a date — anything less is a mood
- After sign-off, changes run as change requests with a price
- Written confirmation can be one sentence in an email; it just has to exist
With TillyGen
TillyGen records sign-offs against concrete plan states, so everyone can see which version was approved and what changed afterwards.
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
What if the client keeps changing things after sign-off?
That is what the sign-off is for: changes are welcome, priced and scheduled as change requests. The conversation stays friendly because the rule was agreed before it was needed.
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.