What I Can Show When I Can't Show the Work
Photo: Siarhei V, CC BY-SA 4.0, via Wikimedia Commons
Every freelance practice accumulates a specific kind of gap. The best work — the engagement that ran eleven months, the one where the client called the result transformational — is often the work that cannot be shown. The agreement says no logo, no screenshots, no discussion of scope. What remains is a portfolio with a conspicuous absence where the strongest evidence should sit.
Most people solve this by saying nothing, which is a mistake, or by blurring a screenshot and calling it redaction, which is a worse one. There is a third path, but it requires reading the contract before designing the page.
What the agreement actually restricts
NDAs vary enormously, and freelancers routinely assume the strictest possible reading. Before deciding what can be published, I identify which of five specific things are actually restricted:
- The client's identity — sometimes prohibited, often merely unpublicized.
- The existence of the engagement — rarely restricted in professional services, occasionally so in product and finance work.
- The final deliverable — almost always restricted, and the easiest restriction to respect.
- Metrics and outcomes — frequently restricted because numbers are commercially sensitive.
- Process artifacts — almost never restricted, though few people ask.
That last line is where the portfolio lives. Wireframes, research plans, workshop agendas, information architecture drafts, editorial calendars, review notes with names removed: these are the materials of the work, and a well-drafted agreement usually says nothing about them. When it does say something, it says it in a clause I should have read at signing.
Four tiers of evidence
The structure I use has four levels, ordered by how much permission each requires.
Tier one: process artifacts, fully sanitized. Early sketches, anonymized research findings, a diagram of a decision tree. No client names, no internal terminology, no screenshots of a live product. These can usually be shown without a conversation.
Tier two: abstracted outcomes. A sentence describing what was built, in the vocabulary of the craft rather than the company. "Designed a three-tier navigation system for a catalog of roughly four hundred products." That sentence proves scope and skill without naming the catalog. It is also the form of description that survives a decade, since it does not depend on a company that may not exist later.
Tier three: the written case study, no images. How the problem was framed, what options were rejected, what changed after the work shipped. Written case studies are the most underused asset in a portfolio and the least likely to violate anything, because they document judgment rather than assets.
Tier four: the gated case study. Full visuals, real names, password-protected, granted case by case. This is the level that requires an explicit yes.
Most freelancers try to jump straight to tier four, fail to get permission, and publish nothing. Building tiers two and three first produces a portfolio that is useful even if every permission request is declined.
Redaction without erasure
Blurring a logo does not remove it. Blurring also signals, unmistakably, that something has been hidden, which draws attention to the absence and makes a page look cautious. The better approach is reconstruction: rebuild the layout with placeholder content and your own typography. The composition still demonstrates how you think about hierarchy and structure, and nothing confidential survives.
Two rules govern this. First, never obscure — replace. Second, never publish a screenshot you have not personally read line by line, including sidebars, browser tabs, and the small gray text nobody looks at.
The page itself
I keep the gated material in a single section marked "Confidential work — access by request," with a plain statement of what the visitor will find and a short form. Passwords are issued individually and rotated at the start of each year, and I keep a simple log of who holds current access. The log is not paranoia; it is the thing that lets me answer a client who asks, reasonably, who has seen their work.
Two scripts that do most of the work
At project start, before anything is signed:
"Before we begin, I'd like to ask about portfolio use. I'd like to include a short written case study — no client name, no screenshots, no metrics — unless you'd prefer I don't. If you're open to a named, illustrated case study later, I'll ask again at handoff. Would you like me to note your preference in the agreement?"
At handoff, when the work has landed well:
"I'd like to write a case study about this engagement. The version I have in mind uses your name and the final visuals, and I'll send you a draft for approval before anything goes live. If that's not possible, I can do a fully anonymized version instead — I'd just need twenty minutes to confirm which details are sensitive."
Both scripts share a structure: name the artifact, specify the level of disclosure, offer the lower tier as a genuine alternative, and put approval in the client's hands with a deadline. Permission requests fail when they are vague. They succeed when the client can say yes to something small.
When the answer is no
Sometimes the answer is no, and no is a complete answer. The portfolio does not collapse; it becomes a record of process and judgment, which is what hiring managers and collaborators are actually assessing. A reader who cannot see the logo can still see how you framed a problem, what you ruled out, and how you wrote about the outcome.
What must not happen is the work appearing anyway — on a laptop screen during an interview, on a slide, on a page behind a password that half the internet knows. The value of confidential work in a portfolio is entirely borrowed from the client's trust. Spend it once and it does not come back.