What to Do When a Client Approves a Video Then Requests Major Changes in Round Four

It happens to almost every agency. You deliver the final video. The client clicks approve. You breathe out. Then, three days later, an email arrives with a bullet-pointed list of significant changes. Not small tweaks. Major creative pivots. And the email has the casual energy of someone who thinks this is still part of the original project.

A client who requests major changes after approval in round four is not necessarily acting in bad faith. They may have shown the approved video to a stakeholder who was not involved in the review process. They may have second-guessed themselves once the adrenaline of approval wore off. They may have had a brand refresh that happened while your project was in post. Whatever the reason, you are now holding an approved deliverable and an inbox full of new notes.

Here is how to handle it without blowing up the relationship.

Separate Emotion From Process

The first thing to do is nothing, for at least an hour. Client requests major changes after approval is genuinely frustrating, and replying immediately when you are frustrated tends to damage relationships. Let the initial reaction pass before you respond.

When you do respond, your tone should be neutral and factual. Not warm and apologetic (that signals the changes are fine and free), and not cold and legalistic (that signals you are looking for a fight). Something like: "Thanks for sending these through. I want to make sure we handle this properly since we're working from the approved version. Let me get back to you by end of day with a clear path forward."

That reply buys you time, keeps the tone professional, and signals without stating that this is not just a free round of changes.

Pull the Approval Record

Before anything else, find the approval record. If you used a dedicated video review tool like PlayPause, this is a ten-second exercise. Every approval in PlayPause is timestamped and linked to the specific version the client signed off on. You have the date, the time, the reviewer's name, and the version number.

If your approval process was email-based, find the approval email. Screenshot it. Whatever you have.

You need the record not necessarily to use it immediately, but to have it ready. If the client later says they never formally approved, or that they only approved provisionally, the record is your grounding point. For more on building this habit before you need it, see how agencies prove a client approved a video when the client claims they never did.

Categorize the Changes

Read through the client's list carefully and sort the requests into two categories.

Changes that are scope additions: New creative directions, new assets, new concept elements, anything that was not part of the original brief or any approved revision. These are billable.

Changes that are genuine errors: Something that appeared in the approved version that was factually wrong, that violates brand standards that were never communicated, or that has a compliance issue. These deserve a more nuanced conversation.

Most post-approval change requests are scope additions. The client simply wants something different from what they approved. That is a commercial transaction, not a service recovery situation.

Have the Scope Conversation Directly

Once you have categorized the changes, call the client. Not email. A phone call keeps the conversation from becoming adversarial through written back-and-forth.

The conversation framework: acknowledge the feedback, confirm you can handle it, be honest that this is post-approval work, and give a price before they say yes or no.

"I've gone through the notes. Most of these are changes to the approved creative direction, which means they fall outside the scope of the original project. I can absolutely do this work, and I want to give you a clean path forward. The change order would be around [X] for these items. Does that work?"

Not everyone will say yes immediately. Some will push back. When clients push back on post-approval change orders, they are often not disputing the logic, they are testing whether the limit is real. Hold it calmly. "I understand it feels like we're close to the finish line. The approved version is the finish line on this project. This is genuinely new work."

Decide What to Absorb and What to Bill

Not every post-approval change needs to go through a change order. Use judgment. If the client is long-term, high-value, and this is genuinely the first time they have done this, absorbing one small item as goodwill is a reasonable business decision. Make sure they know you are doing it. "I'm going to handle [small item] as a goodwill gesture. The [larger item] I'll need to bill for separately."

What you should never do is absorb major creative changes silently. That sets a precedent that approvals do not mean anything, and it will happen again on the next project.

For high-value long-term clients, this conversation is also an opportunity to propose a clearer approval structure going forward. Frame it as protecting them: "To avoid this situation on future projects, let's add a stakeholder review step before the final approval so everyone who needs to see it has weighed in."

Reinforce Your Process for the Future

After this project closes, look at your approval process and find the gap. The most common gaps:

• No pre-approval stakeholder checklist, so the client approved without their decision-maker seeing it
• Approval via email rather than a dedicated tool with a clear approval action
• No language in the SOW defining what constitutes a revision versus a new scope item

Tools like PlayPause add a natural checkpoint because the client must click an explicit approval button rather than just replying "looks good." That intentional action raises the psychological weight of the approval and reduces post-approval second-guessing.

Also look at whether the client's change request reveals something about the review process. If a senior stakeholder who was not in the loop is driving round four from outside the process, your scope protection starts with getting clients to consolidate feedback before sending it to the edit suite.

• Pull the version-specific approval record
• Confirm authorized approver named in SOW
• Categorize all notes before responding
• Issue change order for scope additions promptly
• Brief client on improved approval structure for future projects

Protect the Relationship Long-Term

Dealing with post-approval change requests is a test of your agency's professionalism. The clients who see you handle it calmly and clearly tend to respect you more, not less. You are demonstrating that you run a real operation with real commercial structures.

The clients who are genuinely not a good fit will reveal themselves during this conversation. That information is valuable too.

For the broader scope management toolkit, see how a client video approval workflow prevents scope creep, how to enforce revision limits in a video retainer without losing the client, and how to write a revision policy that clients actually read and respect.

PlayPause gives you the timestamped approval records and version history you need to have this conversation from a position of documented clarity. Try it free and build the approval foundation before you need it.