What to Do When a Client Approves a Cut, Then Changes Their Mind a Week Later

A client emails "approved, this is great, go ahead and deliver final" on a Tuesday, you spend the next two days rendering, exporting, and archiving the project, and then the following Monday the same client writes back saying the team looked at it again over the weekend and actually they want to revisit the opening thirty seconds. If you've been editing professionally for more than a few years, you've lived through some version of this exact week, and it raises a question that a lot of editors never quite resolve for themselves: what does "approved" actually mean, and what happens when a client treats it as reversible anyway.

Why "Approved" Often Isn't as Final as It Sounds

The uncomfortable truth is that a lot of approvals happen casually, a quick email, a thumbs-up in a group chat, a verbal "looks good" on a call, and casual approvals invite casual reversals, because nothing about the moment felt like a formal decision to either party. When approval isn't a defined event with a specific action attached to it, a client's "sounds good" from last Tuesday doesn't carry the same psychological weight as a video that's already gone out the door, so they don't feel like they're breaking a promise by asking for one more change, they feel like they're just continuing a conversation that never really closed.

Building a Formal Sign-Off Step Into Every Project

The fix starts before the reversal ever happens, with a sign-off process that makes approval feel like a real event rather than a passing comment. That usually means a dedicated approve action, not a reply-all email, tied to the specific version being approved, with a timestamp attached automatically so there's no ambiguity later about which cut, and which date, the client actually signed off on. This is the exact reason we built a real Approvals mechanism into PlayPause rather than leaving sign-off to happen in whatever channel a client happened to be using that day, because a genuine approve button, clicked on a specific version, creates a record that a casual "looks great!" email never will. It's the same basic logic behind why a contractor has a homeowner initial each change order instead of just nodding along on a walkthrough, the click itself is what converts a feeling into a fact, and facts are what hold up three weeks later when someone tries to remember what was actually agreed to.

What to Put in Writing Before Final Delivery

Beyond the tool itself, your contract needs language that treats post-approval changes as a distinct, billable category of work, separate from the revision rounds we've covered elsewhere. This is the piece that protects you financially when a "final" quietly unravels, and it's worth having in every contract regardless of project size.

Notice that second point specifically says "for the approved version and scope," because sometimes what a client actually wants after reversing isn't a genuinely new idea, it's the previous cut back, which is its own kind of headache if you've already deleted project files assuming the job was closed. Which is exactly why keeping every prior version archived, even after delivery, isn't optional busywork, it's the thing that saves you when a client asks for round two of a video you thought was finished three weeks ago.

What About Approvals That Happen on a Call?

A lot of approvals still happen verbally, on a client call, in a Zoom review session, someone says "yeah, that's it, ship it" out loud and the meeting moves on to the next agenda item, and that's honestly fine as long as it doesn't stop there. The fix isn't to insist every client formally click a button live on the call, which can feel stilted and slows down a conversation that's otherwise going well, it's to follow up within the hour with a short message that says plainly "confirming we're locking version 4 as approved based on today's call, I'll send the formal sign-off link now so it's on record" and then actually send that link. That single follow-up habit closes the exact gap where a verbal yes quietly turns into a week later "wait, did we actually agree to that," because the recorded approval still happens, it just happens a few minutes after the conversation instead of interrupting it.

Pricing the Change Order Without Souring the Relationship

When a client does come back after formal approval, the conversation is actually easier than the pre-approval "no more revisions" conversation, because you have a much stronger position, they already said yes to something specific and dated. We tell editors to treat it plainly: "Happy to make that change. Since we're past the approved final, this falls under a change order at my standard rate, here's a quick estimate." There's no need for tension here, this is a normal, expected part of professional service work, the same way a contractor charges for changes requested after a homeowner signs off on a renovation plan. If your standard hourly rate is somewhere around 75 to 150 dollars depending on your market and the complexity of the work, quoting a small post-approval change as a flat 150 to 300 dollars rather than itemizing every minute tends to land better with clients too, it reads as a fair, simple number rather than a nitpicky invoice that makes them second-guess ever asking for anything again. If the phrasing itself feels tricky to land, our companion piece on how to tell a client no more revisions covers the tone and structure that keeps this kind of conversation firm without damaging the relationship.

Why This Happens More Often With Committees Than Individuals

Reversed approvals show up disproportionately on projects where the person who said "approved" wasn't actually the last word, a marketing manager greenlights a cut and then their VP sees it over the weekend and has notes, and suddenly what felt final on Tuesday is reopened by Monday through no fault of the person who approved it. This is really an extension of the same structural gap we cover in our piece on conflicting stakeholder feedback, because a reversed approval is often just a conflicting stakeholder note that arrived after sign-off instead of before it. The fix is related too, confirm at kickoff exactly who has the authority to approve, and make sure that person's sign-off is understood, by everyone on their team, to be genuinely final.

• Require a dedicated, recorded approve action, not a casual reply
• Timestamp and version-lock every approval automatically
• Put post-approval change-order pricing in the contract up front
• Keep every prior version archived even after final delivery
• Confirm at kickoff exactly who holds real sign-off authority

A Scenario Worth Planning For in Advance

An independent editor we spoke with delivers monthly recap videos for a mid-size events company, and for two straight quarters, the same pattern kept repeating, the marketing coordinator would approve a cut by email on a Friday, the editor would spend the weekend exporting and archiving, and by the following Wednesday a request would come in to restore a segment that had been cut in the approved version, always framed as "just a quick fix." Once the editor switched to a proper approve action tied to a specific version, with a short change-order clause added to the contract stating that anything requested after that click was billed separately, the pattern didn't disappear entirely, clients are still clients, but the coordinator started looping in her own manager before hitting approve rather than after, because the approval itself finally carried real weight. The editor's unbilled rework dropped close to zero within a single quarter, and just as importantly, the awkward "wait, didn't we already finish this" conversation stopped happening altogether.

How Different Project Types Handle This Differently

The stakes around a reversed approval shift depending on what kind of video is involved, and it's worth calibrating your process accordingly rather than treating every project identically. A Youtube Creator publishing weekly content usually has a fairly low-stakes version of this problem, a reopened approval mostly costs time. A Post Production House delivering a Commercial Video Production piece tied to a media buy or air date has a much higher-stakes version, because a reversed approval close to a hard deadline can jeopardize the placement entirely, not just your invoice. The formal sign-off step matters in both cases, but the change-order pricing conversation deserves extra weight, and probably a faster turnaround clause, on anything tied to an external deadline you don't control.

What Archiving Actually Protects You From

It's worth being specific about why version archiving matters here beyond just convenience. If a client reverses an approval and wants elements of the previous cut restored, having that exact version still accessible, not just the raw footage, but the assembled, graded, mixed version they originally approved, is the difference between a quick, billable half-hour of work and a multi-hour reconstruction you can't fairly charge for because you're effectively redoing work you'd already finished once. A Media Storage setup that keeps every approved version intact, tied to its own sign-off record, means you're never rebuilding something from scratch just because a client changed their mind about which "final" they actually wanted.

The Industry Is Only Producing More of This Pressure

Part of why this problem feels more common than it used to is that video output itself has scaled up across nearly every business, more campaigns, more channels, more stakeholders touching each asset before it ships. Research from Wyzowl's video marketing statistics consistently shows businesses producing and reviewing more video year over year, and every additional stakeholder added to a review chain is another chance for a "final" to get reopened by someone who wasn't fully looped in the first time. That trend isn't slowing down, so the editors and studios who build a real sign-off step into their process now are setting themselves up for a lot less unpaid rework as client review chains keep getting longer and more crowded.

Sign-Off Should Mean Something

An approval that can quietly unravel a week later isn't really an approval, it's just a pause in an open-ended conversation, and the way to fix that is to make sign-off a specific, recorded, version-locked action backed by a contract that treats anything after it as new, billable work. That's exactly what a proper Client Approval Workflow is for, and it's worth setting up before your next "final" delivery, not after the first time a client asks you to reopen one. Take a look at PlayPause pricing to see how formal approvals and version history work together, or contact PlayPause to set up a sign-off process that actually holds when a client changes their mind.