← All posts

February 25, 2026 · 7 min read

IP Assignment Clauses Explained for Freelancers (With Redlines)

An IP assignment clause says who owns the work when the engagement ends. In most client contracts, the answer is the client — including, if you're not careful, tools you built before the project started.

What IP assignment actually transfers

Intellectual property in a freelance context includes: code, designs, copy, strategies, processes, methodologies, and anything else you create. A broad assignment clause transfers all of it to the client.

The problem isn't assigning the deliverable — that's normal and expected. The problem is the phrase "including any tools, frameworks, or methods used in performance of the services," which you'll find in probably half the contracts sent to freelancers.

That phrase means: if you used a component library you've built over four years, it now belongs to the client. If you used an internal design system, it now belongs to the client. If you committed code from a personal project, that code now belongs to the client.

The three types of IP at risk

Pre-existing IP: Work you created before the engagement. Reusable code libraries, design systems, templates, frameworks, methodologies. This is the most dangerous category because it's often the most valuable thing you own.

Background IP: Knowledge, techniques, and processes you bring to every engagement. Your way of structuring a project, your testing approach, your debugging toolkit. Broad clauses can capture this too.

Third-party IP: Open-source libraries you include in deliverables. Assigning these to the client is legally meaningless (you don't own them), but it creates a warranty problem — you're warranting clean title to something you can't actually assign.

What a dangerous clause looks like

"Contractor hereby irrevocably assigns to Client all right, title, and interest in and to all work product, inventions, discoveries, developments, improvements, and any other intellectual property conceived, created, or developed by Contractor during the term of this Agreement, whether or not related to Client's business, including all tools, frameworks, and methods used in performance of the services."

The red flags: "all right, title, and interest," "whether or not related to Client's business," and "including all tools, frameworks, and methods." Together these three phrases assign everything you touch.

The redline you need

There are two parts to fixing an IP clause: narrowing the assignment to the actual deliverable, and carving out pre-existing work.

"Contractor assigns to Client all right, title, and interest in and to the specific deliverables described in Exhibit A, created solely for this engagement and fully paid for under this Agreement ('Deliverables'). The assignment does not include: (a) any pre-existing intellectual property of Contractor ('Pre-existing IP'), including tools, frameworks, libraries, and methodologies developed before or outside this engagement; (b) any open-source software incorporated in the Deliverables, which is licensed under its respective open-source license; or (c) Contractor's general knowledge, skills, and experience. Contractor grants Client a perpetual, irrevocable, royalty-free license to use any Pre-existing IP incorporated in the Deliverables."

The license grant at the end is important — the client still gets to use your tools in the deliverable, they just don't own them.

The "work made for hire" angle

Some contracts use "work made for hire" language under US copyright law. Under the Copyright Act, work made for hire transfers copyright automatically to the employer — but only for certain categories of work and only for employees, not independent contractors, unless both parties sign a written agreement designating it as such.

A contract that says "all work product is work made for hire" is either legally meaningless (most freelance work doesn't qualify) or overreaching. Either way, push back with the assignment language above, which achieves the client's legitimate goal without the ambiguity.

Portfolio use rights

While you're negotiating IP, also add an explicit portfolio carveout. Many IP clauses inadvertently prevent you from listing the engagement in your portfolio or showing samples:

"Notwithstanding any confidentiality obligations, Contractor may include Client's name and a general description of the services in Contractor's portfolio and marketing materials. Contractor may show non-confidential samples of Deliverables to prospective clients."

IP assignment is the clause we see most often — and most often unsigned without reading. ClauseCheck flags missing pre-existing IP carveouts and suggests the right redline for your role (designer, developer, writer, or consultant).

Scan your contract free →

Not legal advice. ClauseCheck is an automated tool — its output is informational only and is not a substitute for a licensed attorney.

← All articles