Process
7/27/2026

The approval was for a different picture

A client approves a design, the team improves it before it ships, and technically nothing got worse. Why that's still a mistake, and the simple rule that fixes it for good.

The version that wasn't the one approved

We were running a launch post for a retail client: an announcement graphic going out on Instagram, Facebook, and their Google Business Profile at the same time. The client looked at a design and said yes to it.

Before it went live, we made it better. Cleaner layout, stronger version of the same idea. It wasn't a different concept, just a sharper execution of the one already approved.

We published the improved version under that approval. That was the mistake, and it wasn't a small one: the client had approved a specific picture, and the picture that went out was not that picture.

Better is not the same as seen

The instinct that got us there is a normal one: we improved the work, so surely the client would approve it too, probably more enthusiastically than the original. That's a prediction, not a fact, and it isn't ours to make on their behalf.

Approval doesn't attach to an idea. It attaches to the exact thing that was in front of them when they said yes. Change the thing, even for the better, and the approval no longer covers it.

That's not a legal technicality, it's the difference between "we did what you agreed to" and "we did what we figured you'd agree to." Only one of those is actually consent.

Who's holding the risk

Here's why it matters more than it sounds: the client is the one standing behind whatever goes out under their name, not us. If a color, a phrase, or an image lands wrong with their customers or their community, they hear about it first.

We caught this one fast and pulled the post from all three channels within a day, but a same-day removal is still a removal. The clean version of that same week is: send the changed piece back, get an actual yes, publish once.

Small, local businesses carry context an outside team won't always have on day one: what a color means in their community, what tone their audience expects, what a past post already got wrong. That context lives with the client. Approval is how it gets applied before something ships, not cleaned up after.

The rule, not the story

The fix isn't "be more careful." Careful doesn't scale, and it fails the next time someone's moving fast. The fix is a rule that doesn't depend on anyone remembering to apply it: any visible change to an already-approved piece goes back for a fresh yes before it ships anywhere, no exceptions for "it's basically the same" or "it's obviously better."

That includes edits that feel too small to matter, because "too small to matter" is a call the client should get to make, not the agency. If a version wasn't in front of them, it wasn't approved, no matter how it compares to the one that was.

In practice that means shipping a little slower in the moment a piece gets improved late. It's worth it. A short delay for a real yes costs nothing next to publishing something the client never actually saw.

Where this shows up beyond design

This isn't really about graphics. It applies to anything published on a client's behalf where the live version can drift from the version that got a yes: a revised email draft, updated landing page copy, a changed ad creative, a tweaked automated message.

The pattern to watch for is the same everywhere: someone improves something after approval and assumes the improvement inherits it. It doesn't. Every visible thing carrying a client's name deserves its own look before it ships.

If you work with a vendor who publishes on your behalf, ask directly: do you see the exact final version before it's live, every time, or just the first draft? The honest ones will tell you which.

Working on something like this? Tell us what you need or see the related service.

Ready to talk?