Prepare an evidence card before writing
Collect the project name or approved anonymisation, period, brief and your role. For each proposed claim, record where the evidence exists and who can confirm it. If support is missing, revise or remove the claim rather than hiding the gap behind words such as successful.
An illustrative website assignment might deliver a new page structure and editing workflow. That does not establish increased client sales. The latter needs different evidence and a reasonable interpretation. Do not turn an intended improvement into a measured result.
Build around a real decision
Choose a concrete difficulty: a service was hard to understand or project material lacked organisation. Explain what the team knew, which option it chose and why. Readers can learn from this even when publishable numbers do not exist.
Explain the boundaries. Did you provide design but not content, or a pilot without the rollout? Say so. Avoid taking credit for the full contribution of other suppliers, the client or a shared team.
| Claim | Evidence to check |
|---|---|
| We developed a new structure | Approved delivery and actual responsibility |
| Visitors found things more easily | Which observation or research supports that? |
| The result increased | Definition, period and basis for comparison |
| The client says | An approved quotation with accurate context |
Choose visuals that support the explanation
A before-and-after example needs comparable tasks. Explain what changed and why. An attractive screenshot without context may serve as portfolio material, but it is not automatically evidence of better usability.
Check for private information, confidential documents and interfaces you cannot publish. Distinguish a conceptual illustration from a real project photograph. Record the photographer and permissions in the media register. Finding material in an old folder does not establish permission to republish it.
Have the right people review the complete page
Send the full presentation for factual review, including heading, captions and metadata. An accurate paragraph can become misleading beneath an exaggerated headline. Use an internal approval checklist rather than leaving permissions to a writer's assumption.
Keep the reviewed version and decisions with the material. If a statement cannot be approved, a more limited or anonymised description may be possible by agreement. Do not invent a different client name or fictional quotation and present it as genuine.
Plan how the story stays current
Assign responsibility for changed project status, links and publication conditions. A planned launch may later be completed, but verify that before updating the wording. An older example need not be wrong; it needs clear context.
Link to the service that actually relates to the contribution and useful explanatory guides. The aim is to help a reader assess the next step with reasonable expectations. A project story does not guarantee the same outcome for a different client.