IP Clauses in Contracts: What You Need to Know

Who owns the website you paid a freelancer to build? What about the software your contractor developed, or the logo your agency designed?

Without a clear IP clause in your contract, the default answer under US copyright law might not be what you expect. Intellectual property provisions are among the most disputed — and most frequently missing — clauses in business contracts. Getting them wrong can mean losing ownership of your own product, brand, or technology.

This guide explains what IP clauses do, how they work, and what every services contract, contractor agreement, and employment agreement needs to get right.

Why Default IP Rules Don't Protect You

Under US copyright law, the creator of an original work owns the copyright automatically — from the moment it's created, with no registration required. That means a freelancer who builds your website, designs your brand identity, or writes your marketing copy owns that work by default, unless you have a written agreement that says otherwise.

This surprises many business owners. They paid for the work. Surely they own it?

Not automatically. Payment for services doesn't transfer ownership of the underlying intellectual property. The freelancer owns the copyright to the deliverable. Your payment bought you the service, not the property rights.

The same logic applies to software code, written content, photography, architectural drawings, and any other copyrightable work created by an independent contractor. The contractor owns it unless there's a written IP assignment.

The Two Types of IP Provisions: Assignment vs. License

Every IP clause in a contract falls into one of two categories: assignment or license.

Type	What It Means	When to Use It
IP Assignment	Ownership transfers entirely from creator to client	You need to own the work outright — modify it, sell it, register it
Exclusive License	Creator keeps ownership but grants you sole use rights	You want substantial control without a formal ownership transfer
Non-exclusive License	Creator keeps ownership; multiple clients can use the work	Software components, stock assets, pre-existing tools

Assignment is what most clients actually need. An assignment clause transfers the copyright (and any other applicable IP rights) to the client, typically upon payment in full. After assignment, the creator has no remaining rights — they can't reuse it, resell it, or modify it without your permission.

Licensing is what many creators prefer. A license can grant broad usage rights while the creator retains underlying ownership and the ability to use the same work with other clients. For clients, a license carries real risk: if the relationship breaks down or the creator goes bankrupt, you're left with usage rights but no ownership — which can complicate financing, acquisition, and platform registration.

For anything you're building a business on — your website, your core software, your brand — push for full assignment, not a license.

The Work-for-Hire Doctrine

The work-for-hire doctrine under 17 U.S.C. § 101 is the only mechanism through which copyright vests automatically in the hiring party rather than the creator. It applies in two situations:

1. Employment relationship. Works created by an employee within the scope of their employment are automatically owned by the employer. No separate IP clause is needed — though employment agreements often restate this for clarity.

2. Specially commissioned works. For independent contractors, work-for-hire only applies to a specific, limited list of categories: contributions to collective works, parts of motion pictures or audiovisual works, translations, supplementary works, compilations, instructional texts, tests, answer materials for tests, and atlases. If the work falls into one of these narrow categories, it must also be designated "work made for hire" in a signed written agreement.

Software, websites, logo design, and marketing copy — none of these fall into the work-for-hire categories for independent contractors. That's the gap that trips up most businesses.

The practical takeaway: If you hire a freelancer to build your app, you cannot rely on work-for-hire. You need an explicit written IP assignment clause. If the freelancer's agreement grants you a "license" instead of an assignment — or contains no IP clause at all — you don't own your own product.

IP Clauses by Contract Type

How IP works in practice varies significantly by agreement type and stakes:

Contract Type	IP Default	What You Need
Contractor Agreement	Creator owns (work-for-hire doesn't apply)	Full written assignment upon payment; carve-out for pre-existing IP
Services Agreement	Creator owns unless assigned	Assignment of all deliverables; define what background IP is retained
Employment Agreement	Employer owns (work-for-hire applies)	Scope of "employment" defined; moonlighting/side-project carve-outs
Founders Agreement	Each founder owns their contributions	IP assignment to company as condition of equity issuance
MSA / SOW	Depends on MSA terms	Background vs. foreground IP defined per SOW

One scenario deserves special attention: founders agreements. Many startups discover too late that a co-founder left before formally assigning their IP to the company. The code, the architecture, the initial designs — technically still owned by a departed founder. This is a deal-breaker that investors specifically check during due diligence. Every founders agreement must include an IP assignment clause transferring all founder-created work to the company as a condition of equity issuance, before anyone writes a line of production code.

Key Components of an IP Assignment Clause

A well-drafted IP assignment clause needs to address five things:

1. What's Being Assigned

Define the IP clearly. "All deliverables" is a starting point, but consider being specific: source code, design files, documentation, test cases, datasets, model weights, and any other tangible output of the engagement. Ambiguity about what's included becomes a dispute waiting to happen.

2. Pre-Existing IP ("Background IP")

Contractors bring tools, libraries, frameworks, and methods they developed before your engagement. These shouldn't be swept into the assignment — you'd be unintentionally claiming the contractor's entire toolkit.

A standard carve-out reads: Provider retains ownership of all pre-existing intellectual property and grants Client a perpetual, worldwide, royalty-free license to use such pre-existing IP solely as incorporated in the deliverables.

This gives you the right to use their tools in your product without acquiring ownership of the underlying framework they built their practice on.

3. When Assignment Occurs

Assignment typically triggers on full payment. Some agreements transfer ownership milestone by milestone, tying IP delivery to payment checkpoints. The critical thing is to ensure delivery and payment stay coupled — clients shouldn't receive full IP assignment before payment, and creators shouldn't receive final payment without delivering complete rights.

4. Warranties

The creator should warrant that:

• The work is original and not copied from a third party
• They have the authority to assign it (no conflicting obligations to a prior employer or current client)
• The deliverable doesn't infringe any third-party patents, copyrights, or trademarks

5. Further Assurances

Include a clause requiring the creator to execute any additional documents needed to perfect the assignment — copyright registrations, patent applications, domain transfers, or platform account transfers. Without this, you may find yourself unable to register your own copyright or patent because the original creator needs to countersign and is no longer reachable.

Moral Rights: The Clause Many Contracts Miss

In the US, moral rights are narrow. Under 17 U.S.C. § 106A, they apply mainly to works of visual art — fine art, photography in limited editions — giving artists rights of attribution and integrity. Most standard business contracts don't need to engage with them.

In the EU and UK, moral rights are far more significant and often inalienable. Under French law (droit moral), creators retain the rights of paternity (attribution) and integrity — even after assigning all economic rights. German copyright law (Urheberrecht) takes a similar position. In the UK, moral rights exist under the Copyright, Designs and Patents Act 1988 (CDPA) but can be waived in writing.

If you're contracting with creators based in France, Germany, or other EU countries, include an explicit moral rights waiver clause. Without it, a creator could theoretically object to how you modify, rebrand, or attribute their work even after a full IP assignment has occurred.

Jurisdiction Notes

United States

Copyright assignment must be in writing to be effective under 17 U.S.C. § 204(a). Oral promises to assign IP are not enforceable. Always get it in writing, signed by the assignor.

In California, Labor Code § 2870 limits employer IP claims on employees. Workers retain rights to inventions developed entirely on their own time, without company equipment or resources, and unrelated to the employer's current or reasonably anticipated business. Many states have enacted similar employee IP protection statutes — check your state's rules if you include broad IP assignment language in employment agreements.

United Kingdom

Under the CDPA § 90(3), assignment must be in writing signed by the assignor. Notably, UK law allows assignment of future copyright — IP for works not yet created — which provides flexibility for ongoing engagements. Employer ownership of employee-created works is established in CDPA § 11(2); contractors retain ownership unless there's a written assignment.

European Union

EU copyright law is harmonized at a high level through directives, but assignment rules vary by member state. In France and Germany, blanket assignments of all future works are generally unenforceable — assignments should be specific about the works covered, the territory, and the duration. Moral rights are robust in most civil law countries and typically cannot be contracted away.

Israel

Under Israel's Copyright Act (5768-2007), works created by an employee in the course of employment belong to the employer. Contractor IP remains with the creator absent a written assignment. Israel follows broadly common law traditions, and written IP assignment clauses are standard and enforceable.

Common Mistakes to Avoid

• Relying on payment alone. Payment for services doesn't transfer IP. You need a written assignment.
• Accepting "license" language. If the clause says "Client receives a license to use the deliverables," you don't own the work. Insist on "assigns all right, title, and interest."
• No background IP carve-out. Assigning all IP without carving out pre-existing tools could unintentionally transfer the contractor's entire software library or design system.
• Missing a moral rights waiver. Critical for EU and UK engagements.
• Forgetting AI-generated content. If a contractor uses AI tools to generate portions of the deliverable, specify who owns those outputs and ensure the contractor has the right to assign them.
• No further assurances clause. Without it, you may need a contractor's signature to register your copyright — and they may be unreachable.

Protect What You're Building

IP clauses aren't bureaucratic formalities. They determine who actually owns the product, brand, or technology you've invested in building. A freelancer agreement without an IP assignment clause is a business risk, not a contract.

Ready to create agreements with proper IP assignment built in? Draft a Contractor Agreement or Services Agreement — describe your engagement in plain English and get a professionally structured draft in minutes. If you're a founding team, start with our Founders Agreement template to lock down IP before anyone writes a line of code.

---

This article is for informational purposes. Pactlio generates professional drafts for review — not legal advice.