Case studies without a client-permission problem

Case studies and testimonials create a permission problem the moment they identify a real client, quote a client’s exact words, or describe a client’s situation specifically enough that the client could recognise themselves. The safest way through it, for any case study, is written consent obtained before publication, not an assumption that a happy client would not mind. This page describes the general problem case studies create and the general solutions available to any business; it is not the place to invent an example case study to illustrate them, and none appears here.

Where the case study permission problem actually sits for clients

The risk is not that case studies exist. It sits in three specific places. Those are publishing a client’s name or identifying details without asking first, quoting a client’s exact words in a testimonial without confirming they are comfortable with those words being public, and describing a project in enough specific detail that the client is identifiable even without being named — a small town, a distinctive project type, a timeframe that only matches one recent job.

None of those three is solved by good intentions. Case studies are made safe by a small number of concrete practices, applied consistently rather than case by case.

Written consent and a signed confidentiality agreement, obtained properly

The most reliable protection is a short written consent, confirmed with the client before anything is published. It should cover what will be said about the project, whether their name or business name will appear, whether photographs will be used, and for how long the material will stay live. A verbal “sure, no worries” during a friendly phone call is not the same thing. It does not establish what was actually agreed to if the client later disputes it, and it gives the client nothing to refer back to either.

Asking does not need to be awkward. Most clients are willing when a specific, written request is put to them, and a written request is also the only version that protects the business if a question is ever raised later.

Anonymising a client’s case study, done properly

Where consent cannot be obtained, or where the business prefers not to identify a client at all, genuine anonymising is needed for case studies. That means removing enough detail that the person or business could not reasonably be identified by someone who knows them — not just omitting the name while keeping every other specific intact. Case studies that remove the name but keep the suburb, the exact project size and the exact month are not meaningfully anonymised if only one project like that happened in that period.

Anonymising step	Why it matters
Remove the name and business name	The obvious first step, and not sufficient alone
Generalise the location	A specific suburb combined with other detail can still identify the client
Round or generalise the timeframe and scale	An exact date and exact figure narrow the field to one possible match
Change or omit distinctive project features	The detail that makes a case study interesting is often the same detail that identifies the client

Metrics instead of testimonial quotes, where you didn’t ask for a release

Where consent for a direct quote is not available, use a general, verifiable metric about the type of work done instead — without attaching it to an identifiable client or a specific named outcome. That is a safer form of proof than an unattributed quote presented as though it came from a real person. The line to hold is that any figure used has to be genuinely true and able to be substantiated if asked, not a plausible-sounding number invented to fill a gap. Claims you cannot make sets out where an unsubstantiated figure crosses from marketing into a legal problem.

Ownership of the words and images themselves

A case study often involves photography and written material connected to a client’s premises or project. That raises a separate question from consent to be named: who owns the images and words being used, and whether the business publishing them actually holds the rights. Copyright in website content covers that question directly — worth reading before a case study reuses a client-supplied photo or a testimonial email without checking who holds the rights to the material itself.

An employee story and testimonials are a different consent question

A case study describing an employee’s work rather than a client’s project raises a related but distinct consent question. An employee is in an ongoing relationship with the business. They may feel less able to decline a request to appear in marketing material than a former client would. That is precisely why consent obtained under those circumstances deserves more care, not less. The same written-consent practice applies. Confirm specifically what will be published, including any photograph, and give a genuine, low-pressure chance to decline or ask for it to be removed later, kept separate from any performance or employment conversation.

What “verifiable” means for a metric used as proof in case studies

A metric used in place of a named quote is only doing honest work if it is something the business could actually produce and substantiate if a reader or a regulator asked. Examples include a genuine count of repeat customers, an actual number of years trading, or a real average response time drawn from records rather than impression. A rounded, plausible-sounding figure invented to fill the same slot a genuine metric would occupy is a fabricated statistic wearing the shape of a safer alternative, and it carries the same risk as an invented quote, not less.

What to do next

Before publishing any case study or testimonial, confirm three things in writing with the client: what will be said, whether they are named, and how long it stays live. Where that is not obtainable, generalise the detail until the project genuinely could not be traced back to one identifiable client, and use a verifiable metric rather than an invented quote to carry the proof instead.