How to Present Project Evidence on Your Website Without Breaching Client Trust

c
ceofounder
13 min read 23 views
How to Present Project Evidence on Your Website Without Breaching Client Trust
Portfolio & Case Studies

How to Present Project Evidence on Your Website Without Breaching Client Trust

Good project evidence is specific enough to be useful and careful enough to protect the people and organisations involved.

Prospective clients often want to understand what an organisation has actually delivered. A portfolio can help — but publishing client names, screenshots, data or photographs without permission can damage the very relationship it is supposed to strengthen.

Explain the problem and your role

A helpful project page describes the context, the need, the work your organisation was responsible for and what changed. A reader should be able to tell whether you designed a website, facilitated training, built software, supplied products or supported a wider project led by someone else.

✗ Vague

“We delivered excellence.”

✓ Specific

What the need was, what you were responsible for, and what changed.

Accurate attribution protects both credibility and relationships.

Use outcomes you can support

Where a verified outcome is available and approved for publication, explain how it was measured and over what period. If there is no verified metric, describe the delivered capability or process instead. Do not turn an illustrative benefit into a client result.

Numbers attract attention — but an unsupported percentage can undermine an otherwise strong portfolio.

Get specific approval

Ask the client what can be published. Each element below may require a different decision. Keep written approval with the project record and identify any conditions, such as anonymisation or a publication date.

Ask one by one

Each element is a separate permission

A “yes” to one is not a “yes” to all of them.

Organisation name
Logo
Project title
Images
Quotations
Metrics
Screenshots
Links

Permission to use a logo does not automatically mean permission to display internal dashboards or identifiable individuals.

Remove unnecessary sensitive details

Review screenshots for names, emails, phone numbers, financial figures, access tokens and confidential project information. Replace sensitive content with fictional demonstration data where a screenshot is essential — and label it accordingly.

Do not assume that blurring a few fields makes an entire screen safe to publish.

Make the page valuable to the next buyer

Organise evidence by the challenge or capability relevant to the reader. Explain constraints and decisions, not only the final visual. A school comparing learning platforms needs a different explanation from a retailer evaluating e-commerce. A concise, accurate project page is more useful than a gallery of unlabeled images.

Use a repeatable case-study outline

A concise structure tells readers how the result came about without overstating the organisation's role. Include enough context to make the example understandable, but remove unnecessary internal detail.

Reusable template

Seven sections, every time

  1. Context The setting and the organisation involved
  2. Challenge The problem that needed solving
  3. Scope What was inside — and outside — the work
  4. Your contribution Exactly what your organisation did
  5. Approach The decisions and constraints that shaped it
  6. Outcome What changed, and how it was verified
  7. Lesson learned What you would carry into the next project

If the project was part of a larger partnership, credit the other contributors accurately.

Create a pre-publication review

Three different checks serve three different purposes. Keep the final approved text and assets together so future staff know what was authorised — and do not accidentally reintroduce removed information during a redesign.

Check 1

Project lead

Verifies the technical facts.

Check 2

Client contact

Reviews public-facing references.

Check 3

Authorised manager

Approves claims and sensitive details.

Anonymise carefully

Removing a name does not always make a case study anonymous if the location, dates, project type or images identify the client. If anonymity is required, assess the whole story and remove or generalise combinations of details that could reveal the subject.

If the remaining story becomes misleading or too vague to be useful, seek broader permission or choose another example.

Make evidence useful for comparison

Prospective buyers need to understand what the example proves and what it does not. Explain the starting problem, constraints, scope and deliverables rather than implying that every client will get the same outcome. Where no performance measure is available, describe the process or capability delivered and label it accurately.

Honest boundaries can improve trust more than exaggerated certainty.

Publish project evidence responsibly

1

Choose a project that answers a clear question for a prospective client. Gather the facts about the challenge, your actual role, deliverables and any outcome that can be supported.

2

Request written approval for the specific text, names, images, quotations and metrics you intend to publish. Review screenshots and documents for confidential information, personal details and third-party rights. If the client needs anonymity, assess whether the complete story could still identify them.

3

Structure the page around the buyer's question and explain the scope and limits of the example. Keep the approved version on record so future website updates do not reintroduce removed material. Reuse the same approval workflow for subsequent case studies.

Approval note
“We propose to publish the project name, a short description of our role and two approved screenshots. We will not publish personal data, financial details or internal documents. Please confirm the text and images attached.”

A clear request is easier to review than a broad request for permission to “use the project.”

Frequently asked questions

Can a portfolio include anonymised client work?

Possibly, but assess whether the combined details still identify the client and whether publication is permitted.

What if there are no measured results?

Describe the work delivered and the documented process. Do not invent a metric to make the page look more impressive.

Action checklist

  • The organisation's role is clearly described.
  • Every result or metric can be substantiated.
  • Written permission covers each proposed asset.
  • Screenshots are checked for sensitive information.
  • The case study answers a buyer's practical question.

Final thought

Your portfolio should demonstrate competence without treating client information as marketing material by default. Build a repeatable approval process and publish only what the organisation is entitled to share.

Building a project-led website?

To create a site with a portfolio structure that earns trust rather than testing it, talk to Stonehenge Digital KE about the website service.

Explore the Portfolio & Organisational Website Service →
Share Written by ceofounder

Interested in Portfolio & Organisational Website?

Let's build this for your business

A professional, mobile-first website that makes your business look credible and gets found on Google.

Leave a Comment

Share Your Thoughts