The client changed their mind after approving. What do you do now?

By Pauline P.· Updated August 2026 · 7 min read

What does the old approval mean now?

It means the client approved V1. It does not mean they can never change their mind, and it does not mean every later edit is automatically approved. Keeping those ideas separate prevents two bad reactions: waving the old approval at the client as if it ends the conversation, or silently replacing V1 and pretending the same yes now covers different content.

Publishing tools follow a similar rule. Hootsuite says a post that changes after approval should go through the approval workflow again (Hootsuite, social media approval workflow). The useful rule is simple: V1 remains the approved record; V2 is pending until someone approves V2.

What should you do in the first five minutes?

1. Pause the post. If V1 is scheduled, unschedule it before the deadline turns a discussion into an accidental publication.
2. Freeze the approved version. Keep its caption, creative, approval time and approver together. Do not edit the only copy.
3. Ask what changed. Was a fact wrong, did a new stakeholder object, or did the client simply prefer a different direction?
4. Do not quote a fee before you assess the work. “I’ll check the impact and come back with the updated timing” is safer than promising “no problem” and discovering a rebuild.

This pause is normal change control, not confrontation. The UK government’s model-services guidance asks a change request to describe the change and its likely cost and date before implementation (UK Government, Model Services Contract guidance). A solo SMM does not need the government form; the useful principle is to assess consequences before saying yes.

Who fixes it, who pays, and does it need new approval?

Two practitioner discussions show why the classification matters. One developer started production after the client had approved the mockups, then received requests that would rework roughly half the project; respondents recommended pricing the request and offering a scope swap, later phase, or paid addition (r/webdev). In another discussion, a designer was three revision rounds in when the client changed direction completely; replies separated the included rounds from a restart and advised giving notice before hourly pricing began (r/graphic_design). Both needed the new request made visible before more work.

Do not turn the table into an automatic invoice. The Freelancers Union contract builder separates included revisions from extra revisions and says material changes to services and fees need prior written consent from both parties (Freelancers Union Contract Creator). Your own agreement still controls what is included. If it says nothing, explain the added work and ask for agreement instead of announcing a surprise charge.

What can you say without starting a fight?

For a change that is included:

Yes — I can make that change. I’ve paused the approved version so it won’t publish. I’ll send the updated V2 for a fresh confirmation before it goes live.

For a new direction outside the agreed work:

I can make that change. It changes the approved [caption / creative / direction] and adds [specific work]. The updated fee is [amount] and delivery moves to [date]. If you confirm those two points, I’ll prepare V2 and send it for approval.

Both replies accept the new request without erasing the old decision. AIGA’s standard design agreement uses the same boundary: changes outside scope may change fees and delivery dates, while a substantive change can require a revised proposal approved in writing before work begins (AIGA Standard Form of Agreement, section 4).

Why shouldn’t you silently edit the approved post?

Because after the edit you can no longer answer the simplest question: “Is this the thing the client approved?” The answer would be no, even if only one line changed. A versioned process keeps the answer precise: V1 was approved at one time; V2 contains these changes and is waiting for a new decision.

Keep the old caption, creative, approval time and approver together, then duplicate the post into V2. That record does not decide who owes money; it tells both sides which version received the yes. The broader client approval and sign-off guide compares ways to keep tamper-evident proof of client approval without turning the process into another meeting.

What if the post is already live?

Do not default to “delete it immediately.” First identify the risk. If the post contains a false claim, private information, a rights problem or a safety issue, stop distribution and follow the client’s escalation process. If the content is accurate and the client merely prefers a different direction, preserve the published URL, screenshot and time before agreeing whether to edit, replace or remove it. That record prevents the correction from turning into a dispute about what actually ran.

Then write the remedy as a new decision: what changes, where it changes, who makes it and whether the revised content needs approval. Sprout Social records changes and comments in Approval Activity, and after an approval its documented options for a scheduled message are to edit or delete it (Sprout Social Help Center). Even when the platform workflow differs, the editorial rule holds: preserve the event, decide the remedy, approve the remedy.

How do you prevent the next reversal from becoming a dispute?

Add five short rules to onboarding or the statement of work: name one final approver; define what “approved” means; state when a scheduled post freezes; say that any changed version needs reapproval; and explain how out-of-scope changes affect price and timing. Upwork’s milestone workflow uses mutual acceptance for changes to future milestones and warns against starting the next milestone before it is accepted and funded (Upwork Help). Your version can fit in one paragraph.

The important shift is not a tougher contract. It is a visible state change: approved V1 → change requested → V2 pending → V2 approved. Once everyone can see that sequence, a changed mind becomes a manageable request instead of an argument about the past.

Last updated: August 1, 2026.

Pauline P.

Researches public data and practitioner accounts about social-media work, with a focus on client feedback, approvals and sign-off. More from Pauline P. →