Case studies when you do not have permission to name clients
Without permission to name a client, publish only a scope and level of detail you are authorised to share.
AI-assisted practical guide · Editorial approach
The useful starting point
Without permission to name a client, publish only a scope and level of detail you are authorised to share. If permission is absent entirely, use clearly labelled internal work or illustrative examples. Do not disguise a speculative project as a confidential client case study.
Understand the decision
Record what was delivered, what evidence exists and which details can be published. Removing a name may not prevent identification through images or project specifics. Agree the wording and assets with the responsible owner. If results are unavailable, describe the verified process or deliverables rather than inventing metrics to make the story sound complete.
A practical approach
Start with an actual conversation or task. Write down what the reader will be able to decide or do after reading. Gather the business facts before drafting and label examples that are illustrative. Edit for usefulness: remove sections that repeat the introduction and add the missing decision, limitation or concrete action. A short complete answer is more useful than a long article assembled only to meet a target word count.
- Document publication permission and its scope.
- Check whether details identify the customer indirectly.
- Separate internal, concept and client work.
- Use only measured results you can substantiate.
Illustrative example
A studio could show an internal redesign of its own enquiry journey and explain the implemented changes. A separate concept could demonstrate an industry direction with an explicit illustrative label. Neither should be presented as a commissioned hospital project merely because the design looks realistic.
A mistake to avoid
Do not treat anonymous as equivalent to authorised. Confidentiality and consent questions remain even when the client name is removed.
What to review
Review proof provenance, approval records and consistency between portfolio labels, article copy and sales presentations.
Turn the guide into a working brief
Give each article a clear owner, source record and next step that matches the subject. Connect it to a relevant service, practical tool or related guide instead of attaching the same urgent sales pitch everywhere. Publish only material you can maintain. Review performance through relevant questions, useful conversations and accepted enquiries, and improve articles where readers still ask the question the page was supposed to answer.
Common questions
What should I prepare before asking for help?
Start with this checklist: Document publication permission and its scope. Check whether details identify the customer indirectly. Separate internal, concept and client work. Use only measured results you can substantiate. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Review proof provenance, approval records and consistency between portfolio labels, article copy and sales presentations. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- Google Search Central: helpful, reliable content
Reference for useful content, truthful authorship and evidence. The business methods and illustrative examples in this guide are original editorial material.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.