Getting blamed for a post you didn't choose: how to protect yourself
- Blame settles on whoever can't show who made the decision.
- "It underperformed" and "it blew up" are different failures, but both end at the same question: who chose this?
- A record protects you when it is dated, pinned to the exact version, and in the client's own words.
- Set it up at kickoff as a speed habit, not in the post-mortem as a defense.
Before I moved to the business side, I managed social accounts for clients, and the meeting I keep coming back to is really a dozen meetings merged into one. Two concepts on the table. The client picks the louder one. Three weeks later the comments turn sour, and the review call opens with "why did we post that?" Except "we" isn't doing the asking. You are doing the answering. I still hear this story, almost word for word, from the social media managers I talk to every week.
Why does blame land weeks after the decision?
Because the decision and the failure live in two different memories. The choice took thirty seconds in a chat, with both options still visible and the client feeling confident. The failure arrives weeks later, when the alternatives are forgotten and the results are on a screen. In that room, the person who pressed publish looks like the person who chose. Your role quietly shifts from executor to author of the idea, and nobody is lying. They genuinely don't remember.
The room is also primed for doubt before you say a word. In Sprout Social's 2025 Index, only 57% of marketing leaders said their executives trust their social team. That's the seat you work in: in four rooms out of ten, that trust isn't a given. Carrying that alone has a price. In the 2025 Link in Bio survey of more than 2,500 social media professionals, 77% described themselves as burnt out and 45% were thinking about leaving the field.
Did the post underperform, or did it blow up?
Sort the failure first, because the accusation differs and so does what saves you:
| Failure mode | What the client asks | What actually protects you |
|---|---|---|
| Underperformed (quiet) | "Why isn't this working?" | A record of the agreed goal and who chose the direction, so the talk is about strategy, not about you |
| Backlash (loud) | "Why did you post this?" | A dated record of who approved that exact version, so responsibility sits with the decision |
There's a third variant worth naming: the post did fine, but someone above your approver hated it. The owner's spouse, the co-founder, the regional boss. The same named, dated record covers you there too, and it quietly protects your contact, who is suddenly also on the hook.
Backlash deserves a special note: it is not proof the decision was bad, and it is certainly not proof of who made it. Audiences split on almost anything now. A 2025 Gallup and Bentley University survey found Americans divided 51% to 49% on whether companies should speak on current issues at all, and in a 2019 YouGov study 29% said they had already stopped buying from a brand over its stance. A post can be perfectly crafted and still land in the wrong half of the room. When that happens, the inside question becomes "whose call was this?", and you want the answer written down somewhere calmer than anyone's memory.
What does a record that protects you look like?
It has four properties, and in my experience most of what managers keep falls short of at least two:
- Dated, beyond anyone's reach to edit. A chat thread can be deleted or rewritten; a record should survive both.
- Pinned to the exact version. Approval of draft three is not approval of draft four. If the record doesn't lock the content, it proves nothing about the post that ran.
- Named. It says who said yes, not "the client side".
- In their own words. "Approved, but soften the second line" is context that wins arguments months later.
This is the gap we built our approval link around: the client opens one link, taps approve on that exact version with no account, and that tap creates a dated, tamper-evident record anyone can verify later. Here is a real, public one:
Notice you didn't need an explanation from me to read it: date, version, who approved. None of this slows the work down, because review is already a step you wait on. In Adobe's 2018 study of in-house creative teams, 48% said work takes two to three days to get reviewed and approved, and for 29% it takes a week or longer. The approval moment already exists. A record is just its receipt.
How do you set this up without sounding paranoid?
You don't announce a defense system; to the client, this is just a faster way to get posts cleared. Five steps:
- Sell it at kickoff as convenience. Script: "For each post I'll send one link. You tap approve from your phone, nothing piles up in your inbox, and we both always know what's cleared to go." Every word is true, and no client hears suspicion in it.
- Write down who chose the concept, and echo it back. One line in your content plan: "Concept B, chosen by [name], [date]." Then echo it in the thread where they chose: "Locking in Concept B as you picked, drafting now." The private line jogs your memory; the echoed line is the one a difficult client can't dismiss as something you wrote for yourself. Both together take ten seconds and preserve the most-forgotten fact in this whole story. A fuller version of this habit lives in our client approval and sign-off guide.
- Make approval pin the final version. A thumbs-up in a thread approves a feeling. A sign-off link approves a file, a caption, and a date. If the client requests changes, the next approval covers the next version, so "I approved something different" can't grow legs.
- After a failure, bring the record, not your memory. Acknowledge the result first ("This one didn't land the way either of us wanted"), then move to data in "we" language: "We ran the version approved on March 4. Here's what the numbers say. What do we want to change about how we pick concepts?" The record sits on the table; you never have to say "you chose this" out loud.
- If blame keeps coming anyway, believe the pattern. Some clients blame as a habit, and no record cures that. I've seen managers eat months of free rework because the blame slowly started to feel deserved. It wasn't. Contract clauses help at the edges: results disclaimers and an approval deadline so silence can't stall you. But with a chronic blamer, the record does one last job: it shows you, in writing, that it isn't you. Blame rarely stays verbal; it turns into invoices that get harder to collect. Among freelancers surveyed by the Freelancers Union in 2015, 71% had struggled at least once to collect payment they were owed.
Frequently asked questions
The client says "you're the expert, you should have talked me out of it." Doesn't that beat the record?
No, because a good record holds your advice too. If you recommended the safer concept, that recommendation should be a line in the same plan or note. Expertise gets judged in hindsight; a dated record doesn't.
Is a screenshot of the chat enough to show who chose the post?
It's better than nothing, but it can be edited, carries no trustworthy date, and is easy to dismiss as out of context. If the client goes further and denies approving at all, that's a harsher version of this problem — we wrote up what to do when a client says they never approved a post separately.
Should I show the approval record during the angry meeting?
Have it ready; don't lead with it. Open with the data and "we" language, and let the record answer the direct question if it comes. A record that arrives as a weapon costs you the relationship even when it wins the argument.
What if the client won't follow any approval step?
Remove the friction first: if approving takes more than a tap from their phone, fix that before assuming bad faith. If they still refuse, put an approval deadline in your contract so silence becomes a decision too, a decision to delay, never to publish: "posts not approved by Thursday move to the next slot." Silence should cost the schedule, not put unapproved content live under your name. A client who insists on deciding nothing in writing is telling you who will own every failure.
Does a record help when the backlash is public?
It won't argue with the internet, and it shouldn't try. What it settles is the inside conversation: who approved what, when, in their words, so the team can handle the outside fire without a parallel fight about fault.
A social media manager and project manager by background, now on the business side of SMMapprove. Writes about client approvals and sign-off from both angles: the client work she has done herself, and the patterns she hears every day talking with other social media managers and agencies. The everyday spots where a 'yes' goes missing and someone gets blamed. More from Pauline P. →