Lock the Cut: How to Stop Clients From Re-Opening Approved Scenes

Picture lock is supposed to mean something. Your client reviewed the scene, left their notes, and signed off. You moved on, built the sound mix around it, timed the graphics to it, and started polishing the rest of the video. Then a message arrives: actually, can we try the other take in scene three, and maybe move that section back before the testimonial? The work is never just the change itself. It is everything built on top of the approved scene that now has to be checked, adjusted, or redone. Locking the cut is the discipline that protects the schedule and the budget, and it only works when approval is a real event rather than a casual comment in a thread.

Why Approved Scenes Keep Getting Reopened

Scenes get reopened for predictable reasons. A stakeholder who never saw the earlier versions watches the near final cut and raises points that were settled weeks ago. The client approved quickly the first time, without really imagining the finished video, and only understood their own preferences once they saw everything together. Sometimes the approval was vague, a quick thumbs up in an email chain, and both sides left with different ideas of what was agreed. And sometimes the business itself changed: a price updated, a product name shifted, a claim had to come out. You cannot prevent every reopening, but you can make approval deliberate, make the record unambiguous, and make the cost of changing course visible before the work begins.

Decide What Locked Actually Means

Before the project starts, write down what approval locks. A workable definition covers four things:

• The order and structure of scenes in the approved version.
• The takes and performances selected for each section.
• On screen wording, including titles, lower thirds, and captions.
• Anything timed to the picture, such as music edits and graphic animations.

Share that definition in your kickoff notes and repeat it at each approval point. Clients are far more careful with their review when they know exactly what their sign off settles. It also reframes your role. You are not refusing changes, you are protecting decisions the client themselves made, which is a service any producer would recognize.

Make the Approval Moment Formal

Casual approvals create casual reopenings. Replace the quick email reply with a deliberate sign off step. Send the version with a short note naming what is being approved: this is the picture lock review, approving this version locks scene order and takes, and changes after this point are handled as change requests. Ask the client to confirm on the record, in the review thread, attached to the exact version they watched. When a client reviews through File Approved, that confirmation can generate a Certificate of Approval, a tamper-proof record of who approved which version and when. A certificate changes the psychology completely. Approval stops feeling like a draft opinion and starts feeling like what it is, a production decision.

Keep Versions Disciplined

Half of all reopening arguments are really version confusion. Someone comments on version six believing it is version eight, or asks to restore a scene that was cut two rounds ago and misremembers why. Protect yourself with strict habits. Every export gets a clear version number and date in the file name. Every review link points to one version only, and old links are retired when a new version ships. Keep your change notes tied to versions, so you can show any stakeholder the exact history: this scene changed in version four, at the client's request, and was approved in version five. When the history is that clear, most reopening requests quietly resolve themselves, because the client can see the decision they already made and the reasoning behind it.

Give Reopening a Path Instead of a Wall

A locked cut should not mean no changes ever. It should mean changes go through a simple, visible process. Set up a change request habit: the client describes the change and the reason, you reply with the cost and schedule impact in writing, and they approve the change before you touch the timeline. This does two things. It gives legitimate changes a fast, professional route through, and it makes casual changes pause, because the person requesting has to weigh the benefit against a real number. Keep the tone helpful throughout. A change request fee is not a punishment, it is the honest price of unpicking and rebuilding finished work, and most clients respect it when they see the reasoning laid out.

It also helps to keep a simple reopen log. Every time an approved scene is reopened, note the date, the scene, the reason, and what it cost in time. You are not building a case against the client, you are building a shared memory of the project. When the same stakeholder reopens a third scene, the log lets you have a calm, factual conversation about reviewing more carefully at the next approval point. Many editors share the log openly in the project thread, which has a quiet side benefit: people think twice before requesting a change when they know it will be recorded alongside its cost. Over a long project, that gentle visibility prevents more reopenings than any contract clause ever will.

When Reopening Is the Right Call

Some reopenings are genuinely necessary. A factual error, a legal problem, a product that was discontinued mid production, or a key message the business cannot ship without. Handle those gracefully and quickly, and charge fairly where the cause was outside your control. Your flexibility on the changes that matter buys you credibility for holding the line on the ones that do not. Over a few projects, clients learn the system: review carefully, approve deliberately, and save everyone's time. The cut stays locked, the schedule holds, and the final video is the one everyone agreed on.