Client says "I never approved that": what to do

If a client claims they never approved a post you published, your position is whatever you can show. Don't argue from memory. Reply in writing with the record. Then fix it going forward: capture a tamper-evident record of approval the moment the client signs off, so the next time it happens you answer with a dated record, not an argument.
Key takeaways
  • Defend yourself from a record, not from memory.
  • A verbal "looks good" or a WhatsApp thumbs-up is worth little once money is on the line.
  • The fix is preventive: a verifiable record of approval the client can't quietly walk back.

It's never the big fights that get you. A freelancer I know — I'll call him Marco, solo, a handful of small brands a few cities over — got a quick "looks great, go" from a client in chat and scheduled the post. A week later the client brought on a new marketing lead who hated it, and suddenly nobody remembered approving anything. The "go" was buried somewhere in an old thread, and Marco was the one who "posted without sign-off." He ate the unpaid rework and nearly lost the account over a "go" he couldn't dig back up.

What actually counts as proof a client approved?

Proof is worth only what's hard to deny or edit later. Most of what solo managers lean on is weaker than it feels — and only one kind can't be waved away:

How different approval records hold up in a dispute
How you got the "yes"StrengthWhy
Verbal "looks good" on a callVery weakNo record — your word vs theirs
WhatsApp / Slack thumbs-upWeakAmbiguous, editable
Email "approved"MediumDated, but editable and scattered
Signed approve-link + tamper-evident recordStrongIndependent, dated, verifiable — the client taps to approve, no account
Verified approval · SMMapprove · public verification record · 2026-05-14 14:11 UTC · cert MZTAGUF23EP6Check it yourself

Only the last row doesn't depend on memory or goodwill. The link above is a live, public verification page anyone can check.

What should you do in the moment?

Answer in writing, never on a heated call — the record argues better than you will. Before you type a word, in this order:

  1. Don't reply or concede anything until you know where things stand.
  2. Pull every record of the approval — messages, emails, timestamps, and any approval link or file metadata.
  3. Reply in writing, open with the evidence, keep your tone flat.
  4. Offer a path forward; if it's out of scope, quote your rate for it.

A reply that leads with the record:

"Hi [name] — I checked my records, and this post was approved on [date] at [time] through the link I sent (here's the record: [link]). Happy to walk through it. If you'd like a change now, I can turn it around; here's my rate for revisions beyond the original scope."

How do you prevent this from happening again?

Make one written approval per post your one hard rule, captured the second they sign off. Send a single link, the client taps "approve" with no account, and you keep a dated record you can show anyone later. Do that, and "I never approved that" becomes a thirty-second lookup instead of a fight.

Frequently asked questions

Does the client need an account to approve?

No. A good approval link works with no login or app.

Is a screenshot enough as proof?

Better than nothing, but editable — and a determined client will say it's doctored.

Does this replace my contract?

No. The contract sets terms; the per-post record shows they were met.

Stop betting the account on a "looks good" you might not find later. Every client sign-off can come with a dated, verifiable record. Set it up for your next post — free to try.
Grig K.
Grig K.

Writes about client approvals, sign-off and disputes in social-media work — the everyday spots where a 'yes' goes missing and someone gets blamed. More from Grig K. →