Creative and professional work is often delivered under a confidentiality obligation, and that can feel like a wall between you and a public portfolio. Designers, consultants, engineers, and freelancers are regularly told that their best recent project cannot be shown, named, or described in any detail. The result is a portfolio that is thinner than the actual experience behind it.
The gap is usually smaller than it looks. Most agreements restrict specific information, not the existence of your skills. Learning what is genuinely off limits, and what can be described in general terms, lets you document complex work without breaking your word. Where the boundary is unclear, the right move is to ask the client or seek proper legal advice rather than to guess.
Reading the agreement before you assume
Non-disclosure agreements vary widely. Some protect only named commercial data, such as pricing or a client list. Others are broad, covering the fact that you worked together at all. Many sit somewhere in between, protecting the project's specifics while allowing you to say you did the work.
Read the clause that defines what is confidential before deciding what you can share. Look for terms about duration, the definition of confidential information, and any carve-outs for information that later becomes public. A provision that lasts two years restricts you far less than one with no end date.
This is a matter of contract, and the interpretation can be subtle. For anything significant, take advice from a qualified legal professional rather than relying on a lay reading. The point here is to know which questions to ask.
Describing your method without revealing client detail
The safest material to publish is usually your own approach. The way you run a discovery session, structure a design system, test a prototype, or manage a handover is your knowledge, and it generally travels with you from one project to the next.
Describe the method in a decontextualised form. Instead of naming the client and their market, explain the problem type you solved and the process you applied. A phrase such as "a regulated business needed to simplify a signing-up journey" says something useful without exposing who the client was or what the product does.
Show the reasoning rather than the raw artefacts. A sketch, a schematic, or a redrawn diagram that captures your thinking can demonstrate seniority without reproducing protected material. Always redraw from scratch rather than editing a client file, and remove any identifying marks.
Building evidence from what is permitted
Even under a strict agreement, there is often a legitimate version of the work you can present. Consider what the client has already made public, what you created yourself before the engagement, and what can be abstracted without losing its value.
Public information is a useful anchor. If the client has announced the project, written about it, or shown images, you can generally reference that material as long as you stay within the terms of your agreement. Where a client is happy to be named, a short, accurate credit may be all you need.
Results often survive anonymisation better than process images. Describing that a service became faster, a process clearer, or a workflow simpler is usually acceptable when no figures or client names are attached. Keep such statements modest and truthful, since an anonymous claim that cannot be checked is worth little anyway.
Asking for permission and negotiating scope
Confidentiality is a default, not necessarily a permanent limit. Clients sometimes agree to a case study, an anonymised example, or a private presentation with no public release. It costs nothing to ask, and the request is easier to grant when it is specific.
Make the ask concrete. Say which images you would like to use, where they would appear, and how the client would be described. Offer options: a named case study, an unnamed one, or a version approved in writing before publication. Framing the request as a choice rather than a demand makes agreement more likely.
If a client says no, treat that as final unless your agreement says otherwise. A portfolio is not worth a broken relationship in a field where most work arrives by referral.
Keeping your own private record
Whatever you can publish, keep a complete private record of every project. Dates, your exact role, the methods you used, and the outcomes you observed are worth capturing while the work is fresh. This file supports future applications, interviews, and internal reviews, and it means you never have to reconstruct a project from memory.
Store it securely and separate from anything public. A private record is not a loophole. It is the factual basis from which a permitted, anonymised description can later be written.
Practical checklist
- [ ] Read the confidentiality clause and note exactly what is protected before sharing anything.
- [ ] Identify the duration and any carve-outs for information that later becomes public.
- [ ] Seek qualified legal advice when the scope of an agreement is unclear.
- [ ] Describe your method in general terms rather than reproducing client artefacts.
- [ ] Redraw or recreate diagrams yourself instead of editing protected files.
- [ ] Reference only material the client has already made public, and stay within the agreed terms.
- [ ] Ask in writing for a named, unnamed, or pre-approved version of a case study.
- [ ] Keep a secure private record of dates, your role, methods, and outcomes for every project.
Contributing to BGTC Voice
Working under confidentiality is part of professional life, and knowing how to document it well is a skill worth passing on. If you have built a method for presenting restricted work without breaking an agreement, writing for BGTC Voice lets other practitioners learn from it. Submissions should describe the approach you used, avoid any confidential specifics, and stay within what your agreements allow.