Proof Without Names: How UK Freelancers Build a Portfolio Behind Closed NDAs

Your best project lands. The client loves it. Then the comms team sends a polite email saying you cannot mention them, quote the brief, or show the work. Suddenly your portfolio has a hole where your strongest proof should be. If that sounds familiar, you are not bad at self-promotion. You are dealing with a normal UK freelance problem: good work often sits behind an NDA.

The good news is that a portfolio does not need a wall of logos to be credible. It needs evidence that you can think, write, edit, and handle a real brief. An anonymised case study can do that, provided it is specific, honest, and signed off. Here is a practical way to build one without turning your portfolio into a vague collection of ‘confidential clients’.

Treat the NDA as a boundary, not a brick wall

Start with the contract, not the portfolio page. Read the confidentiality clause properly. Some NDAs restrict the client’s name but say nothing about describing the type of work. Others are broader and cover briefs, metrics, screenshots, deliverables, or anything that could identify the client. The wording matters.

Ask the client what is actually restricted. A short email is enough: ‘I would like to write a short anonymised case study about the project. Before I draft anything, can you confirm whether the restriction covers your name only, or also the brief, process, and outcomes?’ Get the answer in writing. This is not legal advice, and if the contract is unusually strict, take proper advice. But a calm question often reveals more room than the clause first suggests.

Build a permission ladder

Permissions are rarely all-or-nothing. Think of them as a ladder, and ask for the lowest rung that still gives you useful proof:

• No mention of the project at all.
• An anonymous sector mention, such as ‘a UK membership organisation’.
• An anonymous sector plus role, such as ‘a content lead at a UK membership organisation’.
• A named client with limited details and written approval.
• A named client with a quote and a full case study.

Most cautious clients will not jump to the top rung. That is fine. An anonymous sector plus role can still show you understand the context. The key is to ask clearly, offer an easy opt-out, and keep the approved version on file.

Make anonymity credible, not coy

A case study that says ‘a client’ and ‘some content’ proves nothing. You need enough texture to show judgement without handing over identifying details. Use categories instead of names: sector, company size band, project length, team shape, and the kind of constraint involved. For example, ‘a UK B2B software firm with a small marketing team’ is useful. ‘A Leeds-based fintech scaling its first customer newsletter’ may be too identifying.

Keep the decisions. Keep the tension. Keep the bit where the brief changed halfway through or the approval process stalled. Those details are what make a case study believable. You can remove the client’s name and still explain that the original draft was too technical for a non-specialist audience, or that three teams had to sign off before publication.

Redact the labels, keep the plot

Redaction is not about deleting everything interesting. It is about removing the details that point to a specific organisation while preserving the story’s shape. Take out names, exact dates, product names, screenshots, unusual locations, and one-of-a-kind metrics. Merge minor details. Replace a very specific job title with a broader role. Swap a niche product description for a plain category.

Then ask the client to review the anonymised version. This does two things: it reduces the risk of an accidental reveal, and it gives you a written record that the client is comfortable with the wording. Keep that approval. If the client’s team changes next year, you will be glad you did.

Describe outcomes without quoting the brief

You do not need to quote the brief to show a result. Use process outcomes, relative outcomes, or ranges. ‘The review cycle moved from a three-day back-and-forth to same-day sign-off’ is useful if it is true and approved. ‘The client reported fewer rounds of edits’ is softer but still credible. ‘The final draft was approved without a second legal pass’ says something about clarity and risk.

Be careful with numbers. Do not invent precision to make a case study sound impressive. If you cannot share exact figures, say so plainly: ‘The client has not approved publication of performance metrics, but the final copy was signed off by their compliance team without further amendments.’ That is honest, and honesty is the point.

Keep a private redaction ledger

Behind every good anonymised case study is a private note you never publish. Record the original client, the project dates, the permission level, the approved wording, and who signed it off. Add a short note about what was removed and why. This is not bureaucracy for its own sake. It protects you if a client asks how their work is being represented, and it saves time when you want to reuse the same case study on a different page.

A mini template that works

Try this structure:

• Context: an anonymous but specific description of the client and the situation.
• Problem: what was going wrong with the copy, content, or process.
• Constraints: the approval chain, the audience, the deadline, the NDA.
• What I did: the editorial decisions you made and why.
• Outcome: the approved result, described as precisely as the NDA allows.
• Sign-off: a line confirming the client approved the anonymised version.

That is enough for a portfolio entry. It shows how you work, not just who you worked for.

Ask for a yes that is easy to give

Make the request simple. Explain that you will not name the client, quote the brief, or share screenshots. Offer to send a draft before anything goes live. Give them a clear way to say no. A client who feels cornered will say no; a client who feels in control is more likely to say yes to a modest anonymised write-up.

The Get Writer Help view is simple: your portfolio is evidence of how you think. Names are nice, but they are not the only proof. A quiet, well-written case study with the labels removed can be more convincing than a logo wall with no story behind it.