Getting a case study approved without losing the story

A case study goes to the client for approval and comes back with the numbers removed, the client name replaced with "a leading provider", and every specific detail softened.

What is left is unusable, and the whole exercise is wasted. The cause is almost always that approval was treated as a final step rather than a design constraint.

Why clients cut things

Understanding the reasons makes them negotiable.

Commercial sensitivity. Revenue, margin, cost and volume figures that they do not want competitors seeing. Entirely reasonable.

Contractual restriction. Some agreements prohibit publishing figures or even naming the relationship. Not negotiable at all, and worth knowing before you write.

Internal politics. The person who approved the project is not the person approving the publication, and the second one has different incentives.

Legal review by default. A legal team with no brief will remove anything that could conceivably be questioned.

Fear of looking like they had a problem. The before is the part that makes a case study work and the part a client is least comfortable publishing, because it says they were failing at something.

That last one is the real obstacle in most cases, and it is the one that responds to framing.

Design for approval up front

Ask at the start of the engagement, not at the end. A line in the agreement about publishing the work, with approval rights, makes the conversation routine. Asked cold two years later it is a favour.

Find out the restrictions before writing. Which figures can be used, whether the name can be used, who approves. Ten minutes at the beginning saves a rewrite.

Write it with them rather than for them. A client who contributed to the draft defends it internally. One who receives a finished document reviews it adversarially.

Send it to your contact first, informally, before it goes to legal or communications. They will tell you what will be cut and frequently how to phrase it so it is not.

Keeping the substance when the specifics go

Almost every restriction has a form that preserves the argument.

Percentages instead of absolutes. A client who will not publish revenue will frequently publish a percentage change.

Ratios and multiples instead of dollar figures.

Ranges instead of exact numbers.

Directional statements with a mechanism. Describing what changed and why it changed is persuasive even without the number, provided the mechanism is specific.

The operational detail instead of the financial one. How long something took, how many steps were removed, what the team stopped doing. Frequently less sensitive and equally convincing.

Sector and size instead of the name. "A Sydney structural engineering practice of about thirty people" carries most of the credibility of a name for a reader in that market.

The thing not to do is replace a removed number with a vague adjective. "Significant growth" is worse than no claim at all, because it reads as a number somebody would not print.

Framing the before so they will approve it

The before does not have to be a failure. It usually was not.

"They had outgrown a system that worked for a smaller business" is true, publishable, and does the same job as "their process was broken". "They were relying on referrals and wanted a second channel" is a position of strength rather than weakness.

The story is about a decision they made, not a problem they had. Written that way, clients approve the before, because it makes them look like people who act.

What to never do

Never publish without approval, including a draft on a preview link that is publicly reachable.

Never fabricate, embellish or attribute a quote they did not say. A quote goes in exactly as given or it is rewritten by them.

Never anonymise and then make the client identifiable anyway through details, photographs or context. If it is confidential, it has to actually be confidential.

Never use their photography or logo without permission, which is separate from approving the text.

When approval is refused

It happens, and the work is not wasted.

An anonymised version, cleared in principle, is usable. A version for private use in proposals and sales conversations, rather than published, retains most of the value where the objection is to public visibility.

And the refusal itself is information for the next engagement: ask earlier, and write the permission into the agreement.