Picture Lock Documentation: How Editors Prove a Cut Was Approved
Picture lock documentation approval proof matters when disputes arise or deliveries are questioned. Here is how editors can create an airtight record that protects everyone.
Picture lock is one of the most important events in a film's post-production life. It is the moment when the edit stops changing. Everything that comes after: sound design, color grade, VFX delivery, music licensing, mix, and eventual delivery, all depends on the picture being genuinely locked.
Picture lock documentation and approval proof are what allow an editor to say, with evidence, that a specific version was approved by the right people on a specific date. Without that documentation, picture lock is a gentlemen's agreement, and gentlemen's agreements do not hold up when a producer wants to make changes after the colorist has started, or when a broadcaster questions which version was delivered.
Why Editors Need This Documentation
Editors are often in a peculiar position. They are the ones who hold the cut. They are the ones who receive notes, make changes, and manage versions. But the decision about when a cut is locked belongs to the director, the producer, and often to other stakeholders.
When a dispute arises, the editor is often the person who gets asked: "Was the cut actually locked? Who approved it?" If the answer is "I think so, the director said it looked great in an email," that is a very weak position to be in.
Good picture lock documentation protects the editor as much as it protects the production.
Not just that the cut was locked, but which cut, who approved it, when, and under what conditions. That is the record that matters.
What Picture Lock Documentation Should Include
At minimum, a complete picture lock record contains:
Version identification. The specific export: file name, resolution, duration, and frame rate. If there are multiple deliverables (a broadcast cut, a theatrical cut, an international version), each one gets its own lock record.
Approver names and roles. Who signed off, and in what capacity. "The director" is not enough. You want the person's name, their role, and confirmation that they had the authority to give final sign-off.
Date and time of approval. When the sign-off was given. Not when the version was exported. When the approval was received.
Version history. The previous versions that led to this lock: what changed between the last candidate and the locked version, who requested those changes, and when they were made.
Conditions or open items. If the lock was conditional ("approved pending one small fix to the title sequence"), those conditions should be recorded along with their resolution.
| Documentation element | Why it matters |
|---|---|
| Version file name and specs | Identifies exactly which file was approved |
| Named approver and role | Confirms who had authority to approve |
| Date and timestamp | Establishes when the lock happened |
| Version history | Shows the path to the locked version |
| Conditional items | Captures any open threads at the time of lock |
How to Collect Approval So the Record Creates Itself
The cleanest approach is to collect sign-off in the same system where the review happened. When the director and producer watch the final candidate cut and confirm it is locked, their confirmation should live in a thread attached to that specific version, timestamped automatically.
This is what PlayPause does. The editor uploads the candidate version, the director and producer review it, and they confirm approval in the review thread. The confirmation includes their name, the version they watched, and a timestamp. The editor does not have to reconstruct this from email chains later.
For productions using a more manual process, the minimum is an email from the director and producer explicitly stating that the specific version (referenced by file name or version number) is approved as picture lock. File that email in a dedicated folder alongside the locked file. Do not rely on implied approval from silence.
Managing Multiple Approvers
Some productions require picture lock sign-off from multiple stakeholders: director, producer, executive producer, distributor, broadcaster. Getting explicit sign-off from all of them creates a coordination problem, especially when they are in different time zones.
The staggered approach works: start with the director's approval, then send to the producer, then to the executive producer or distributor. Each round of sign-off is documented. If someone reviews and has notes, those notes are addressed and a new candidate is presented. The process repeats until all required approvers have confirmed.
For productions with formal broadcast approval requirements, see our guide on how broadcast editors deliver QC-ready cuts with timestamped note trails for how to structure the record to meet broadcaster standards.
What to Do When Someone Tries to Change the Cut After Lock
Post-lock change requests are one of the most common sources of production conflict. A producer sees the graded color and suddenly has a note about a cut that was locked two weeks ago. An executive watches the mix and wants a scene restructured.
The picture lock documentation is what allows the editor to respond professionally: "The cut was locked on [date] with sign-off from [names]. Any changes to picture at this stage require formal approval from all parties and will affect the sound design and color grade timelines."
This is not a negotiating position. It is a statement of fact backed by a documented record. The decision about whether to proceed with a post-lock change belongs to the production, not the editor, but the editor's job is to make the cost and process of that decision clear.
For a look at how formal approval gates prevent this problem from arising in the first place, see our guide on structured approval gates for each post-production stage on an indie feature.
"I think the director approved it" leads to disputed changes and unclear responsibility
Timestamped sign-off record means any post-lock request must explicitly override a documented decision
The Downstream Value of Good Lock Documentation
The sound designer needs to know they are working from the locked cut. The colorist needs to know their grade is going on the final version. The VFX team needs to know the shot timings will not change. For each of these departments, the picture lock documentation is what gives them confidence to proceed.
For the sound design handoff specifically, see our piece on how to prevent a sound designer from working off an outdated cut for how to structure the handoff around the documented lock.
- Collect explicit sign-off from all required approvers before declaring lock
- Record version details, approver names, and timestamp
- Note any conditions or open items at time of lock
- Archive locked file alongside sign-off record
- Brief all downstream departments from locked version only
- Document any post-lock change requests and their approval separately
Using the Lock Record at Delivery
At delivery, the picture lock record is part of the production documentation package. Broadcasters and distributors may ask for evidence of when the cut was locked and who approved it. Having a clear, timestamped record makes that question easy to answer.
For productions delivering to multiple outlets (festival cut, broadcast cut, streaming cut), each version has its own lock record. The broadcaster gets documentation for the broadcast version. The festival gets documentation for the theatrical version. There is no ambiguity about which version was approved for which purpose.
For a broader look at how to manage multiple cut versions for different delivery contexts, see our guide on managing multiple cut versions for a broadcaster, festival, and streaming delivery.
If your current picture lock process is a phone call and an email, you are one disputed change request away from a problem. PlayPause makes the formal sign-off step lightweight enough that it adds about five minutes to the process and eliminates the ambiguity entirely. The approval workflow tools are designed for exactly this: collecting, recording, and archiving explicit sign-off against specific versions. Start free at PlayPause and have your first formal picture lock record before the end of the week.
Abhijeet D. writes about media technology and collaboration for PlayPause. He covers the tools and workflows that connect editors, producers, and clients, from Camera-to-Cloud to secure review links.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free