How to Write a Case Study When Your Client Work Is Under NDA (With 4 Rewrite Templates)

Last updated: September 2026

You finally have a project worth putting in your portfolio.

The work was good. The results were real. You solved an actual business problem instead of making another fake project for your portfolio.

Then you remember one thing.

You signed an NDA.

Now you cannot show the client name. You cannot publish the dashboard. You cannot reveal the revenue numbers. You probably cannot upload that beautiful campaign either.

So what exactly are you supposed to put in your portfolio?

A suspiciously vague paragraph saying, “I helped a leading company improve its marketing”?

Please don't.

An NDA does not automatically mean you have to erase the project from your professional history. It means you need to be much more careful about what you reveal and how you describe your contribution.

I’m Riten, founder of Fueler, a skills-first portfolio platform building the career infrastructure for 100 million creative professionals. Fueler connects talented individuals with companies through assignments, portfolios, and projects, not just resumes or CVs. Think of it as Dribbble/Behance for work samples combined with AngelList for hiring infrastructure.

This guide explains how to turn confidential client work into a useful case study without exposing information you should not publish. You’ll learn what to remove, what you can focus on instead, how to talk about results without leaking numbers, and four rewrite templates you can use.

What Is an NDA and What Does It Mean for Your Portfolio?

An NDA, or non-disclosure agreement, is a contract that sets rules around confidential information. The exact restrictions depend on the agreement, so there is no universal “NDA checklist” that applies to every project.

For your portfolio, the important thing is understanding what your specific agreement actually restricts.

• Start with the definition of confidential information. Your NDA may cover financial information, customer data, product plans, internal processes, technical information, marketing strategies, or other proprietary material. Read this section before writing your case study. Do not rely on what you vaguely remember signing six months ago.

• Look for restrictions around public disclosure. Some agreements specifically address public announcements, publicity, or disclosure to third parties. A portfolio website is public, so do not assume that discussing your work is automatically allowed just because you personally created it.

• Check whether client identity is protected. Some projects allow professionals to mention the client but restrict project details. Others may require the client to remain anonymous. These are different restrictions, so your case study needs to reflect the actual agreement.

• Check how long confidentiality lasts. Some confidentiality obligations have a defined period, while certain information may remain protected longer. The agreement should tell you what applies to your project. If the wording is unclear, get appropriate legal advice instead of guessing.

• Remember that your work and the client's information are different things. “I redesigned the onboarding experience” describes your contribution. “I redesigned the onboarding experience for a product with 80,000 monthly users” adds information about the client. The second detail may require separate permission.

Why it matters

The first step in writing an NDA case study is not writing. It is knowing your boundaries. Once you understand what cannot be disclosed, you can build the case study around everything that remains: your role, decisions, process, execution, and approved outcomes.

What Can You Talk About in an NDA Case Study?

The biggest misconception about NDA projects is that everything becomes off-limits.

That is not necessarily true. Your agreement determines what is restricted, but your own contribution can often become the center of the case study.

• Explain your role. “I managed the content strategy” is very different from simply saying “I worked with a client.” Explain what you were responsible for, which parts you owned, and where you collaborated with other people.

• Describe the problem at a safe level. You do not need to reveal the client's internal documents to explain the challenge. “The company had an inconsistent content production process” may be enough to establish the problem without exposing internal information.

• Explain your approach. Research, planning, testing, iteration, execution, and decision-making can make a case study valuable even when the final output cannot be shown. Your process demonstrates how you think, not just what the client received.

• Discuss approved outcomes. If you have permission to publish a metric, use it. If you do not, describe the outcome without inventing precision. “The new process reduced manual coordination” is better than making up a percentage.

• Talk about lessons from the project. Explain what the project taught you about your craft, workflow, strategy, or decision-making. Just make sure your lesson does not accidentally reveal confidential information while trying to sound insightful.

Why it matters

Your portfolio does not need to reveal the client's entire business to prove that you are capable. A good case study answers a much simpler question: What problem did you work on, what did you do, and what happened because of your work?

What Information Should You Remove From an NDA Case Study?

Editing an NDA case study is less about deleting the entire story and more about removing information that belongs to the client.

The dangerous details are often the ones that seem harmless when you first write them.

• Remove confidential financial information. Revenue, profit margins, advertising budgets, pricing, salaries, deal sizes, customer acquisition costs, and financial forecasts can expose far more than you intend. If the information is protected, do not publish it just because you think nobody will care about the exact number.

• Remove private customer information. Customer names, email addresses, account information, private feedback, databases, and identifiable user information should not appear in a public portfolio without appropriate authorization. Changing someone's name is not enough if the surrounding details still identify them.

• Remove internal screenshots. Dashboards, project-management boards, internal presentations, private documents, analytics screens, and communication threads can contain several confidential details at once. Cropping a screenshot does not automatically make it safe.

• Remove proprietary strategies. A company's acquisition strategy, pricing model, product roadmap, technical process, or internal operating system may be part of what gives it an advantage. You can discuss the problem and your role without publishing the mechanism behind that advantage.

• Remove combinations of details that identify the client. This one is easy to miss. You might remove the company name but leave the industry, launch date, location, product description, customer segment, and exact result. Put together, those details may make the client obvious.

Why it matters

Anonymizing a case study is not just about removing a logo. You need to think about what someone could learn by combining the information you leave behind. Protect the client's information while keeping your own professional contribution visible.

How Do You Anonymize a Client Without Making Your Case Study Useless?

There is a difference between making a client anonymous and making the project meaningless.

“A company hired me for marketing.”

Nobody learns anything from that.

Instead, preserve the context that helps someone understand the work without exposing the client's identity.

• Use the industry and business type. You might describe the client as “a B2B SaaS company,” “a D2C consumer brand,” or “a healthcare business.” Only include details you are actually permitted to disclose. The goal is useful context, not detective bait.

• Describe company scale broadly. Instead of publishing exact employee counts, revenue, or customer numbers, you might say “a growing startup” or “a mid-sized company.” This gives the reader enough context to understand the environment without exposing sensitive business information.

• Use a neutral label. “Confidential B2B SaaS client” works perfectly well. You can also use “Client A” if several projects need to be discussed. Just make sure the label does not become an excuse for removing every useful detail.

• Keep the challenge specific. “The client wanted to improve its content operation” is vague. “The marketing team struggled with inconsistent briefs and an unpredictable publishing process” gives the reader something real to understand.

• Keep your contribution visible. Anonymize the client, not yourself. Explain what you researched, created, changed, tested, managed, or improved. That is the part future employers and clients actually need to evaluate.

Why it matters

The reader does not necessarily need the client's name. They need enough context to understand the situation and enough evidence to judge your ability. Good anonymization removes identifying information while leaving the professional story intact.

How Do You Show Results When the Client Numbers Are Confidential?

This is probably the hardest part of writing an NDA case study.

You know the exact result.

You just cannot publish it.

That does not mean the result has to disappear.

• Describe the direction of change. If exact numbers are confidential, you can sometimes say that conversion improved, production became faster, lead quality increased, or manual work decreased. Only make claims that accurately reflect the approved information.

• Use before-and-after states. Explain what the workflow looked like before your involvement and what changed afterward. For example, “Content requests were handled through scattered messages. I introduced a structured briefing process that gave the team one consistent workflow.”

• Use approved project metrics. Not every number is commercially sensitive. The number of assets created, interviews conducted, experiments run, pages redesigned, or workflows documented may be safe to mention if it does not expose confidential information.

• Explain the operational outcome. If you cannot say that revenue increased by a particular amount, explain what changed in the business process. Maybe the team could launch campaigns faster, reduce manual work, make decisions more easily, or create content more consistently.

• Say that the exact figures are confidential. There is nothing embarrassing about this. A simple note such as “Exact performance figures are confidential under the client agreement” tells the reader why the number is missing. It is much better than pretending the number never existed.

Why it matters

Results make case studies credible, but results are not always giant percentages. A clear before-and-after story, approved metric, operational improvement, or documented outcome can still show impact without exposing private business information.

How Do You Show Work You Cannot Actually Publish?

Sometimes the client does not allow the final work to appear publicly.

That creates a second problem.

How do you prove you actually did the work?

The answer is to make the thinking behind the work visible.

• Show your decision-making. Explain why you chose a particular approach. If you changed a content structure, explain what problem led to the change. If you redesigned a workflow, explain what was failing before. Decisions demonstrate professional judgment.

• Show your process. Research, audits, planning documents, testing frameworks, wireframes, content structures, and workflows can all demonstrate your approach, provided the versions you show do not contain confidential information.

• Explain your iterations. Real projects rarely go perfectly on the first attempt. Explain what changed after testing, feedback, or new information. This makes your case study feel much more like real work and much less like a polished school assignment.

• Be honest about collaboration. If you worked with a designer, developer, founder, or marketing team, explain your part. Do not claim the entire project just because you were involved in it.

• Create safe supporting visuals. When appropriate, you can create simplified diagrams, recreated examples, or generic versions that demonstrate your method without reproducing confidential client material. Make it obvious that the visual is illustrative if it is not the original work.

Why it matters

When the final deliverable cannot be shown, your process becomes the evidence. A recruiter cannot see the confidential campaign, but they can see whether you know how to research, make decisions, solve problems, test ideas, and execute.

How Do You Rewrite an Existing Case Study for NDA Compliance?

You do not always need to throw away the original case study.

Take it sentence by sentence and ask: Does this sentence demonstrate my ability, or does it reveal something that belongs to the client?

Then rewrite accordingly.

• Replace names with context. “I worked with XYZ Technologies” can become “I worked with a B2B SaaS company on its inbound content strategy.” This keeps the professional context while removing the client's identity.

• Replace sensitive numbers with truthful outcomes. If you cannot publish “revenue increased by 28%,” do not turn it into “revenue increased by approximately 30%.” Instead, describe an approved outcome or explain that the exact figure is confidential.

• Replace private assets with descriptions. Instead of publishing an internal dashboard, explain what you built: “I created a reporting workflow that helped the team monitor campaign performance across its main channels.”

• Replace vague statements with actions. “I helped improve their marketing” says very little. “I audited the existing content workflow, rebuilt the briefing process, and introduced a repeatable publishing system” tells the reader what you actually did.

• Add a short confidentiality note. One sentence is enough: “Client identity and selected performance details have been omitted because the project is covered by a confidentiality agreement.” You do not need a three-paragraph legal disclaimer.

Why it matters

The goal is not to make the case study look empty. It is to move the information around. Take attention away from confidential client details and put it on your decisions, execution, contribution, and results you are allowed to discuss.

What Should the Structure of an NDA Case Study Look Like?

An NDA case study can follow almost the same structure as any strong portfolio case study.

The difference is what you choose to put inside each section.

• Context: Introduce the client broadly. Mention the industry, type of business, project category, and your role where permitted. Keep the description useful but avoid details that could identify the company unnecessarily.

• Challenge: Explain what needed to change. Focus on the problem your work addressed rather than revealing internal business information. The reader should understand why the project existed in the first place.

• Approach: This should be one of the strongest parts. Explain your research, decisions, workflow, testing, iterations, and implementation. Your approach is often safer to discuss than the client's internal information.

• Outcome: Explain what changed. Use approved metrics where possible. Otherwise, describe measurable deliverables, operational improvements, before-and-after states, or other outcomes that you can genuinely support.

• Your contribution: Finish by making your ownership clear. Explain exactly what you handled and what was shared with the broader team. This prevents the case study from becoming a generic description of a project.

Why it matters

This structure gives the reader the information they actually need. They do not need access to the client's private data to understand your professional ability. They need to understand the problem, your approach, your decisions, and the result.

4 NDA Case Study Rewrite Templates You Can Use

If you already have a case study written, these templates can help you rewrite the sensitive parts without starting over.

Template 1: Anonymous Client

Client: Confidential B2B SaaS company
Project: Content strategy
Role: Content Strategist
The challenge:
The client needed a more consistent content process. Content requests were handled across different channels, making planning and production difficult to manage.
What I did:
I audited the existing workflow, identified the biggest bottlenecks, rebuilt the content planning process, and introduced a clearer system for briefs, production, reviews, and publishing.
Outcome:
The new process created a more consistent content operation and made responsibilities clearer across the team. Client-specific performance data has been omitted because of confidentiality requirements.

Template 2: Confidential Results

Project: Growth campaign for a confidential client
The problem:
The existing campaign structure was not producing the quality of results the team expected.
My approach:
I reviewed the existing messaging, identified weak points in the campaign structure, developed new creative directions, and tested different approaches before scaling the stronger-performing concepts.
The result:
The revised campaign improved performance against the original approach. Exact campaign figures cannot be shared publicly because they are covered by the client agreement.

Template 3: Cannot Show the Final Work

Project: Brand and content project for a confidential client
I cannot publicly display the final deliverables from this project because of confidentiality restrictions. Instead, this case study focuses on the work behind them.
The challenge:
The client needed to [describe the general problem].
My process:
I began with [research/audit], identified [problem], and developed [solution]. I then worked through [testing/revisions/collaboration] before the final delivery.
What it demonstrates:
This project strengthened my experience in [skill 1], [skill 2], and [skill 3].

Template 4: Client Name Cannot Be Disclosed

Client: Confidential [industry] company
Project: [project type]
Role: [your role]
Context:
I worked with a [company type] that needed to [general objective]. The client name and selected project details have been omitted because of confidentiality requirements.
The problem:
[Describe the actual problem without revealing sensitive information.]
My contribution:
I owned [responsibility 1], [responsibility 2], and [responsibility 3]. The biggest challenge was [challenge], which I addressed by [action].
Outcome:
The project resulted in [approved outcome]. Exact client metrics are not publicly available.

Why this is helpful?

These templates give you a structure without encouraging you to make up numbers or hide behind vague language. Replace every bracket with information you can genuinely support. If you cannot support it, leave it out.

What Are the Biggest NDA Case Study Mistakes?

Most portfolio mistakes happen because someone tries to make the case study more impressive.

Ironically, that is often what makes it less trustworthy.

• Assuming an anonymous client means everything is safe. You can reveal confidential information without naming the company. A unique product, exact launch date, customer segment, or unusual financial result may identify the client.

• Changing confidential numbers slightly. Turning 26% into “around 30%” is not a clever workaround. If the number is confidential, do not publish a modified version unless you have permission to do so.

• Uploading careless screenshots. Dashboards and documents can contain customer names, internal URLs, financial figures, comments, and other information that you did not notice initially. Review every visible element before publishing.

• Inventing results because the original numbers cannot be shared. This is never worth it. A truthful case study with limited metrics is stronger than an impressive case study built around numbers you cannot defend.

• Taking credit for the whole project. If five people worked on the project, explain your contribution honestly. Hiring managers can usually tell when someone is taking credit for work they barely touched.

Why it matters

A portfolio should make someone trust you with their work. Handling confidential client work responsibly is itself evidence of professionalism. Do not sacrifice that trust for a slightly flashier case study.

How Does This Connect to Building a Strong Career or Portfolio?

NDA projects can become some of the most valuable experiences in your career, even when you cannot publicly display the final work. Document your responsibilities, decisions, process, and approved outcomes while the project is still fresh. That gives you evidence to discuss during interviews and future applications. A strong portfolio is not just a gallery of finished work. It is a record of how you solve real problems.

Final Thoughts

An NDA does not make your work invisible.

It simply changes what you are allowed to show.

Instead of building your case study around the client's name, screenshots, or revenue figures, build it around the problem you solved and the decisions you made.

Be specific about your contribution.

Be honest about what you cannot disclose.

And never invent details to make the project look more impressive.

A good NDA case study can still make a hiring manager think, “This person knows how to do the work.”

That is the part worth showing.

How Do I Write a Case Study When My Client Work Is Under NDA?

Start by reviewing what your NDA actually restricts. Remove confidential names, numbers, screenshots, customer information, and proprietary details. Then focus the case study on your role, problem-solving process, decisions, deliverables, and approved outcomes.

Can I Mention an NDA Client in My Portfolio?

Only if your agreement or the client gives you permission to disclose the client's identity. If the client name is restricted, describe the company using safe, general context such as industry or business type, provided those details themselves are permitted.

How Can I Show Results From Confidential Client Work?

Use results that you are allowed to disclose. If exact figures are confidential, describe approved directional outcomes, operational improvements, before-and-after states, or non-sensitive project metrics. Never invent, round, or disguise confidential numbers.

Can I Show Screenshots From an NDA Project?

Not unless you are permitted to disclose the information contained in them. Screenshots can expose confidential dashboards, customer data, financial information, internal documents, or private communications. When permission is unclear, leave the screenshot out or use an appropriately recreated, non-confidential visual.

Is NDA Client Work Worth Including in a Portfolio?

Yes, if you can describe it honestly within your confidentiality restrictions. You do not need to show the entire final deliverable. A case study can demonstrate your role, decisions, process, problem-solving, and approved outcomes without revealing the client's private information.

Why 100,000+ professionals use Fueler

Fueler helps professionals showcase proof of work through projects, assignments, case studies, and achievements.

• Thousands of professionals use Fueler to create their digital portfolio

• Thousands of projects are published on Fueler. Check here

• Startups and Companies hire through proof of work on Fueler

• Used by freelancers, creators, marketers, video editors, writers, designers, and product managers

Our mission is to help the next 100 million professionals build a verified professional identity through proof of work