NDA IP Clause: Who Owns Your Work? What Every Freelancer Must Know
Most freelancers assume IP ownership is something you negotiate in the contract — the statement of work, the services agreement, the engagement letter. The NDA is just confidentiality, they think. A formality to handle before the real paperwork starts.
That assumption is wrong. An intellectual property clause tucked into an NDA can transfer ownership of everything you create during an engagement — and in some drafts, everything you've ever built — to the client, before the actual project scope is even defined. Without a pre-existing IP carve-out, an NDA can cover everything you've ever built.
Understanding how IP clauses work in NDAs, what makes them dangerous, and how to protect yourself before you sign is one of the most important things a freelancer, contractor, or advisor can do. This post walks through the mechanics, the risks, and the specific language you need in your counter-proposal.
For a broader picture of NDA risk, NDA Red Flags covers the most dangerous clause types across the full document. If you're also concerned about competitive restrictions in your NDA, NDA Non-Compete Clause covers that terrain separately.
What IP Assignment Clauses Do in NDAs
IP assignment clauses do exactly what they sound like: they assign ownership of intellectual property from you to the client. The clause typically appears under a heading like "Intellectual Property," "Work Product," "Ownership of Deliverables," or "Proprietary Rights."
In a services agreement or statement of work, an IP assignment clause is expected. You build something for a client, they pay you, they own the deliverable. That's a normal commercial transaction.
The problem arises when the same language appears in an NDA — a document you're often asked to sign before the project scope is discussed, before you know what you'll be building, and before any payment terms are set. The IP assignment in the NDA may be broader than what appears in any subsequent services agreement, and in most standard contract structures, the later document doesn't automatically override the earlier one unless it explicitly says so.
What makes IP clauses in NDAs particularly aggressive is scope. A well-drafted IP assignment in a services agreement covers the specific deliverables described in that agreement. An IP clause in an NDA — drafted for maximum client protection — often covers:
- "All work product created in connection with this Agreement or any discussions between the parties"
- "Any inventions, discoveries, or improvements conceived during the term"
- "All materials developed using Confidential Information"
"Discussions between the parties" and "in connection with" are dangerously open-ended. Under that language, a prototype you sketch on your own time while thinking about a client's problem could be covered. A tool you build to complete the project more efficiently could be covered. Work you do after the formal engagement ends but that "relates to" anything the client told you could be covered.
Work Made for Hire vs. Everything You Create
There's a legal concept called "work made for hire" that governs copyright ownership in the US. Under US copyright law, work made for hire means the hiring party — not the creator — is considered the legal author and owner. For employees, this happens automatically. For independent contractors, it only applies to specific categories of works (commissioned works in defined categories like translations, compilations, or audiovisual works) and only when there's a written agreement explicitly designating the work as made for hire.
Freelancers often assume that "work made for hire" language in an NDA is fine because it maps to standard copyright doctrine. What they miss is that IP assignment clauses in NDAs are often broader than work made for hire, and they're not limited to copyrightable work. A strong IP assignment clause captures:
- Copyright — ownership of written content, designs, code, and other creative works
- Trade secrets — processes, formulas, or methods you develop
- Patents — inventions and improvements, including provisional patent rights
- Moral rights — in jurisdictions that recognize them, the right to attribution and integrity of your work
An NDA that assigns all of these broadly isn't describing work made for hire. It's a sweeping transfer of any intellectual property that could be argued to have arisen from the engagement. That's a fundamentally different legal instrument — and it can reach work you created independently.
What a Pre-Existing IP Carve-Out Means (and Why It's Non-Negotiable)
A pre-existing IP carve-out is language that explicitly excludes from the IP assignment any intellectual property you owned or developed before the engagement began. Without it, the IP assignment clause — depending on how broadly it's drafted — can claim work you did before you ever heard of this client.
Without a carve-out:
"Contractor hereby assigns to Client all right, title, and interest in and to any and all work product, inventions, improvements, designs, or other materials created, conceived, or developed by Contractor in connection with Contractor's work for Client or through the use of Client's Confidential Information."
The phrase "through the use of Client's Confidential Information" is the trap. Once you're working inside a client's ecosystem — using their systems, receiving their internal documents, building on their existing platform — almost any work you do could be argued to have been developed "through the use of" their information. That language extends to your existing tools if you touch them during the engagement.
With a carve-out:
"Contractor hereby assigns to Client all right, title, and interest in and to any work product created specifically for and delivered to Client under this Agreement ("Deliverables"). Notwithstanding the foregoing, Contractor retains all right, title, and interest in and to any intellectual property developed by Contractor prior to the commencement of this engagement ("Pre-Existing IP"), including without limitation any tools, frameworks, libraries, templates, or methodologies. To the extent Contractor incorporates Pre-Existing IP into any Deliverable, Contractor grants Client a non-exclusive, perpetual, royalty-free license to use such Pre-Existing IP solely as incorporated in the Deliverable."
The carve-out does three things: it limits the assignment to actual deliverables, it preserves your ownership of everything you brought to the table, and it gives the client the license they need to use the finished work without taking ownership of your building blocks.
That license grant — non-exclusive, perpetual, royalty-free, limited to use in the deliverable — is a critical part of the carve-out. Without it, a strict reading of the IP assignment could mean the client can't actually use the final product if it incorporates your pre-existing code or templates. Including the license resolves this and makes the clause easier for clients to accept.
The Portfolio Risk
Beyond ownership of your tools, IP assignment clauses in NDAs carry a second risk that freelancers often overlook: the right to show your work.
When a client owns the deliverables, they typically also own the right to control how those deliverables are displayed, reproduced, or described. If the NDA or the IP assignment is broad enough, the confidentiality provisions and the IP ownership together can prevent you from:
- Adding the project to your portfolio
- Describing the work in a case study or on your website
- Sharing screenshots or samples with prospective clients
- Listing the company as a past client in your credentials
Some NDAs have explicit "no publicity" clauses that prohibit you from mentioning the client without written consent. Combined with a broad IP assignment, the result is an engagement that disappears from your professional record entirely — even if it was your best work.
If portfolio rights matter to you — and for designers, developers, writers, and videographers, they usually do — you need to address this separately, either in the NDA itself or in the services agreement. Negotiating a carve-out that allows you to display the work in your portfolio with attribution, subject to removing any client-specific confidential information, is standard practice in most creative and technical fields. Most clients will accept it.
Tools, Frameworks, and Code Built Before the Engagement
For developers and designers, the pre-existing IP risk has a specific shape that's worth naming directly.
If you have a component library you've built over five years. A design system. A deployment pipeline. A project scaffolding tool. A set of utility functions. A collection of reusable modules. These are assets you bring to every engagement — they're part of what makes you efficient and valuable.
Under a broad IP assignment clause in an NDA, the moment you use any of those tools in a client's project, they potentially become covered by the assignment. The clause doesn't say "we own things you built for us." It says "we own things you built using our information" or "in connection with our work." If you're on their Slack, accessing their codebase, and your pre-existing library is integrated into their product, the argument that your library was developed "in connection with" the engagement isn't frivolous.
The same logic applies to frameworks and templates. A Figma component library you use across clients. A contract template you've been refining for years. A video editing preset pack. These aren't deliverables — they're your professional infrastructure. A pre-existing IP carve-out explicitly protects them.
Some clients will try to define pre-existing IP narrowly: "only things listed in Exhibit A at signing." That's a reasonable compromise — it provides certainty for both sides. If you go this route, prepare the exhibit before you sign and be thorough. Include everything you might conceivably use during the engagement, because omissions from the exhibit will fall under the assignment.
How to Add a Pre-Existing IP Carve-Out
If the NDA you've received has a broad IP assignment clause and no carve-out, here is the counter-language to propose:
Counter-language to propose:
"Notwithstanding any other provision of this Agreement, Contractor retains all right, title, and interest in and to any intellectual property, including without limitation software, tools, frameworks, libraries, methodologies, templates, designs, or other materials, that Contractor developed or acquired prior to the commencement of this engagement ("Pre-Existing IP"). Any Pre-Existing IP incorporated into work product delivered to Client shall remain the sole property of Contractor. Contractor grants Client a non-exclusive, perpetual, worldwide, royalty-free license to use, reproduce, and distribute such Pre-Existing IP solely as integrated into the deliverables provided under this Agreement and solely for Client's internal business purposes."
When proposing this language, frame it simply: "I want to make sure both sides are protected on ownership. I've added a carve-out for tools and frameworks I've built before this engagement — the deliverables themselves remain yours. Happy to provide a list of specific pre-existing assets if that helps."
Most clients respond well to this framing. It doesn't challenge the legitimacy of their IP claim over your actual work product — it just clarifies the line between what you're building for them and what you brought to the table.
What to Do If Client Refuses
If a client declines to add a pre-existing IP carve-out, you have a narrower set of options — but not zero.
Ask for a defined scope instead. Even if they won't add a full carve-out, they may agree to define "work product" narrowly: limited to specific named deliverables rather than anything created "in connection with" the engagement. A narrower definition of what's assigned can achieve much of the same protection as a carve-out.
Negotiate an exhibit of excluded assets. If the client won't remove the assignment language, propose a schedule attached to the NDA that lists your pre-existing assets by name. They retain the broad clause; you retain ownership of specifically listed items. This approach has limitations — anything you forget to list is covered — but it protects your core infrastructure.
Assess the actual exposure. What tools would you use on this project? If the engagement is narrow enough that your pre-existing IP isn't implicated — you'll be delivering a one-off report, not building software on top of your existing framework — the clause may carry lower practical risk than it appears.
Price it in. If the clause stands as drafted and you proceed, the client is effectively licensing your infrastructure permanently through the IP assignment. That has value. It's not unreasonable to adjust your rate to reflect the transfer.
Walk away from high-stakes mismatches. If the engagement involves deep use of proprietary tooling or frameworks that represent years of your work, and the client won't carve them out, that's a legitimate reason to decline. The IP transfer under a broad clause could be worth more than the project fee — that's not a trade worth making.
Consult an attorney before signing if the engagement is large and the IP exposure is significant. The value of what's at stake in an IP assignment often exceeds the cost of an hour of legal advice.
FAQ
Can an NDA actually transfer ownership of code I wrote before the project started?
Yes, if the IP assignment clause is drafted broadly enough and there's no pre-existing IP carve-out. Language that assigns "anything developed in connection with this agreement" or "using Confidential Information" can reach pre-existing work if you used or incorporated it during the engagement. This isn't theoretical — it's one of the most common IP disputes in freelance and contractor relationships. A carve-out prevents it.
What's the difference between the IP clause in an NDA and the IP clause in a services agreement?
The NDA is typically signed first, before project scope is defined. An IP clause in an NDA covers anything created "during discussions" or "in connection with the relationship" — which can be broader than the specific deliverables described in a later services agreement. If both documents have IP clauses and they conflict, which one governs depends on the specific contract language (look for an integration clause). Never assume the services agreement automatically overrides the NDA.
Do I need to disclose my existing tools to get a pre-existing IP carve-out?
Some clients will require you to list pre-existing IP in an exhibit at signing as a condition of the carve-out. This is reasonable — it gives them certainty about what's excluded. If a client requires a disclosure list, prepare it carefully before signing and be inclusive. Anything you might use during the engagement should be on the list. Omissions become the client's property under the assignment.
If I create something new during the project but on my own time using my own resources, does the client own it?
Possibly, under a broad IP clause. The phrase "in connection with this Agreement" doesn't limit coverage to hours you billed or systems you worked in. If the invention or creation is related to the client's business or uses ideas you were exposed to through the engagement, it may fall within the clause. This is why the carve-out needs to be explicit about pre-existing IP — and why you should also watch for clauses that cover future inventions "relating to" the client's business even after the engagement ends.
Is the IP clause in an NDA the same as a work-made-for-hire provision?
No. Work made for hire is a specific copyright doctrine that determines authorship for certain categories of commissioned works. An IP assignment clause in an NDA is broader — it can cover patents, trade secrets, and moral rights in addition to copyright, and it applies through an explicit contractual transfer rather than the statutory work-made-for-hire framework. Some NDAs use both mechanisms in combination for maximum coverage. Either way, without a carve-out, your pre-existing work is exposed.
Know What You're Signing Before You Sign It
An IP clause in an NDA isn't a technicality. It's a transfer of property rights — potentially including property you've built over years of professional practice. The good news is that most clients will accept a pre-existing IP carve-out when it's proposed professionally, because the carve-out doesn't threaten their legitimate interest in owning what you build for them. It just draws the line between your deliverables and your professional infrastructure.
Read the IP section. Find the carve-out — or notice its absence. Propose the language. Most of the time, that's the entire negotiation.
For a faster path through any NDA, NDA Guard automatically flags IP assignment clauses with no pre-existing carve-out — risk-scored, in plain English, with counter-language ready to paste. You can also review NDA Red Flags for the full list of high-risk clause types, or NDA Non-Compete Clause if competitive restrictions in the same document are also a concern.
Protect your work product. Protect your pre-existing IP. They're not the same thing.