Extract the approved substance

A useful case study may describe the problem, your contribution and an agreed result. It does not require publishing message screenshots or email threads. Those records can contain information unrelated to the project claim. Use approved summaries or quotations with appropriate context instead.

Keep the account verifiable through the right route

Retain supporting records through the organisation’s process where appropriate, but separate that from public presentation. A profile can make the relevant evidence understandable without exposing every interaction behind it. The reader needs a fair account of the work, not unrestricted access to the relationship. Before publishing, ask whether each included detail supports the stated project lesson. Remove personal contact information and unrelated discussion even when the overall story is approved.

Imagine this

Hypothetical scenario

A hypothetical project story uses an approved outcome summary rather than a screenshot of a client email containing private contacts and unrelated comments. The public account remains useful and focused.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.