Direct answer
Before publishing a client case study or testimonial, confirm the work, role, scope, claims, client naming, quotation, testimonial source and every logo, image, screenshot or media asset that will appear. A historical draft, an old project file or a live-looking website is not evidence of current public-use permission.
Why it matters
Proof should reduce buyer uncertainty, but it must not turn private client material into a marketing asset by assumption. The risk is not only a wrong result claim. A case study can misstate the work, suggest an approval that never happened, use a client name without agreement or show media whose public rights have not been confirmed.
A practical release check
Start with the source record. State the problem, Richard's role, the delivered scope and any outcome only as far as the available evidence supports them. Review each public sentence for scope drift, especially claims about results, impact, performance or ongoing client relationships.
Then confirm the permission boundary separately: client naming, testimonial attribution and quotation treatment, current route or link, and public rights for logos, screenshots, photographs, video and third-party assets. Keep the published treatment proportionate to the verified evidence. Where permission or proof is incomplete, use an approved anonymous example, process explanation or omit the item.
Limits
Permission to do the work does not automatically include permission to publish it. Contracts, confidentiality obligations, privacy requirements, licences and regulated contexts may require specialist or client review. This is a publication-control checklist, not legal advice.
Soft next step
Create a release record for each proposed case study that separates confirmed evidence, required permissions, approved public assets and claims that must be removed or softened.