Publish a useful case study without naming the client

Agree what may become public

Start with the contract and a specific publication request. Ask which project facts, images, quotations, metrics and dates may be used. Approval for a logo in a portfolio is not automatically approval for revenue figures, employee feedback or a detailed account of a difficult implementation.

Give the approving person the actual draft and intended placements, including previews and social excerpts. Record the approved version and any conditions. If the client declines, publish a general method article using clearly labelled hypothetical material rather than quietly disguising their project as something else.

Separate organisational confidentiality from information about individuals. A business might permit a process description while an employee’s name, quotation or email remains inappropriate to publish. The ICO’s anonymisation guidance explains that identification can be direct or indirect. Its guidance is under review, so check its current status before relying on it for a legal assessment.

Remove combinations that reveal identity

Review industry, city, staff size, launch date, unusual software, office photographs and exact numbers together. Any single detail may look harmless while the combination points to one organisation or person. Searchable phrases from a quotation can also reveal the original source.

Use broader descriptions only when doing so preserves the meaning of the case. “A regional service company” may be sufficient where the exact town adds nothing to the lesson. If the specialised context is essential to understanding the work but cannot be disclosed, that project may not be suitable for a public case study.

The ICO distinguishes pseudonymisation from anonymisation: replacing identifiers does not necessarily remove personal-data obligations. Treat “anonymous case study” as a publishing description, not a certification that every underlying record is legally anonymous.

A worked example with useful detail

Imagine a hypothetical maintenance business whose enquiry form repeatedly asked customers to supply information they did not have. A useful case study could explain the initial requirement, the unnecessary question, the new “not sure” route and how the team reviewed the information reaching its inbox.

The case can show a recreated flow diagram using neutral labels, with a caption explaining that it is an explanatory reconstruction. It should not present a synthetic interface as an original client screenshot. It can describe that the final form reached the intended team if that was verified, without claiming that sales improved.

Include the hard constraint: perhaps the dispatch team still required an accurate service address before confirming a visit. The interesting decision is what moved later in the process and why. This provides transferable value without revealing the client’s distinctive branding, customer records or private operational details.

Preserve honesty when figures are withheld

If an exact figure cannot be published, do not invent a replacement and leave readers to assume it is real. Use an approved range, a qualitative statement with appropriate support, or omit the metric. Label transformed or hypothetical figures clearly and avoid a chart that implies an undisclosed measured dataset.

Explain measurement limits near the result. A shorter completion time for an internal task is not evidence of higher profit. A comparison across different months may also reflect staffing, seasonality or changes elsewhere. Describe the observations and the uncertainty separately.

The FTC’s truth-in-advertising overview requires truthful, non-misleading advertising in its jurisdiction. Confidentiality does not make an unsupported promotional claim acceptable. The workflow here supports editorial accuracy; it does not substitute for reviewing rules relevant to the service and audience.

Inspect images, files and previews

Review every screenshot at full size. Check browser tabs, account menus, names, email addresses, filenames, invoice references, map labels and content in sidebars. A blur that looks adequate in a thumbnail may leave text readable in the original file. Prefer removing sensitive content before producing the public asset.

Check image metadata, downloadable documents, captions, alt text and social preview descriptions. A neutral article title does not help if the attachment filename names the client. Publish only the reviewed derivative and preserve the private original separately.

Use a reviewer who was not involved in writing the case study. Ask them what they can infer about the organisation and people, and whether each result means what the evidence supports. Review the mobile version too: a small disclaimer must not disappear while a large result figure remains prominent.

Keep the story useful after approval

Lead with the decision a similar business could learn from, then explain the constraints and supported result. Avoid an empty success story in which every detail has been removed. A precise account of one change is more useful than broad praise without enough context to assess it.

Retain the final approval, evidence ledger and public URL. Assign an owner to handle correction or withdrawal requests, and review the case when services or claims change. The strongest confidential portfolio is selective: it publishes what can be explained responsibly and leaves the rest private.

Continue with the relevant checks

Check permission for every public image. Review social previews as part of the publication. Write image descriptions that match the approved public asset.