What Is an IP Assignment Clause? What Freelancers and Employees Risk by Signing One

A freelance designer spent 200 hours building a design system for a client. Clean components, a full icon library, a typography scale she'd refined over a decade of work. Six months after the project wrapped, the client sent a cease-and-desist. They claimed ownership of the entire system, including templates she'd been selling independently for years. The contract had a blanket IP assignment clause on page 8. She had never noticed it.

She lost $15,000 in template revenue, and that's before legal fees.

This happens more than you'd think. IP assignment clauses are standard in creative and technical contracts, but most people who sign them don't understand what they're handing over. Here's what you need to know.

What "IP Assignment" Actually Means

IP stands for intellectual property: code, designs, writing, illustrations, inventions, processes, formulas, anything your mind produces and your hands (or keyboard) execute. Intellectual property law gives the creator ownership of that work by default.

An IP assignment clause overrides that default. It says: anything you create for us, as a result of this engagement, belongs to us. Not you. The clause doesn't just license your work to the company. It transfers full ownership. You become the manufacturer; they become the owner.

If you build a feature, write copy, or design a logo under a contract with an IP assignment clause, the company owns the copyright from the moment it's created. You can't reuse it, resell it, or put it in your portfolio without their permission, unless the contract says otherwise.

Work for Hire vs. IP Assignment: The Short Version

You'll sometimes hear "work for hire" used interchangeably with IP assignment. They're related but not the same thing.

Work for hire is a concept baked into copyright law. For W-2 employees, work created within the scope of employment is automatically owned by the employer without needing a contract clause. For independent contractors, work for hire only applies to certain categories of work, like contributions to collective works or motion pictures, and only if both parties sign a written agreement saying so.

IP assignment is a contractual mechanism. It's used when work-for-hire doctrine doesn't automatically apply, which is most of the time with freelancers and contractors. The result is the same: ownership transfers to the company. But the legal path is different, and that distinction matters when you're trying to figure out what you actually signed.

The Four Dangerous Variations

Not all IP assignment clauses are equal. Some are reasonable. Others are written to take everything they can get.

Blanket assignment is the most aggressive version. Instead of covering work created specifically for the client's project, it assigns anything you create during the contract period, full stop. Working nights on a personal app? In scope. Building out a template library for your own business? Also potentially in scope. The clause sweeps broadly, and courts have sometimes enforced this even when the work had nothing to do with the client.

Moral rights waiver is common in creative contracts and often overlooked. Copyright law in some countries gives creators moral rights: the right to be credited, and the right to object if their work is modified or used in a way that damages their reputation. A moral rights waiver strips those protections away. You're agreeing in advance that they can alter your work, remove your name from it, or use it in contexts you'd find objectionable.

Prior work assignment is rarer, but when it appears it's a genuine trap. Some contracts try to claim ownership of work you created before the engagement started. The clause might say something like "all IP related to the subject matter of this agreement, whether created before or after the effective date." That phrase "before or after" should be an immediate red flag.

Related work clause is perhaps the most dangerously vague. Instead of limiting the assignment to deliverables, it covers anything "related to" the company's business or industry. If you're a developer working for a fintech startup and you build a side project in the payments space, that clause could reach it. "Related to" gets interpreted broadly in disputes, which means the company gets to argue about what falls inside it.

The Own Time and Equipment Trap

Employment contracts, not just freelance agreements, often contain language that looks something like this: "Employee assigns to Company all inventions conceived or developed during employment, whether on Company time or not, using Company equipment or not, if related to Company business or Company's anticipated research and development."

That "whether or not" construction is doing a lot of work. It tries to claim your side projects even if you built them on weekends with your own laptop. The "related to Company business" clause is the real danger. If you work for a marketing software company and you build a personal productivity tool with any marketing angle, you could be in their territory by that definition.

The good news is that this kind of overreach is partially unenforceable in several states.

What State Law Says

California Labor Code Section 2870 limits what employers can claim. If you created the invention entirely on your own time, using only your own resources, and the invention doesn't relate to the company's actual or demonstrably anticipated business, they can't own it. Several other states have passed similar protections: Delaware, Illinois, Minnesota, North Carolina, and Washington all have statutes that restrict employer IP claims on outside work.

If you live in one of these states, an overreaching clause isn't automatically enforceable. But "not enforceable" is not the same as "free." You'd still have to fight it, which costs time and money. The better move is to carve it out before you sign.

How to Protect Your Side Projects

Before you sign any employment or consulting agreement, do three things.

First, document and date your prior work. If you have a side project, a template library, a codebase, or any creative asset you want to protect, establish a clear paper trail that it existed before this engagement. Git commit history, dated files, published work, old invoices, all of that helps.

Second, ask for a written carve-out by name. Don't just ask for "a carve-out for my outside work." Get specific. "The parties agree that Company claims no rights to [specific project name], a [brief description] created by Employee prior to and independent of this engagement." Vague carve-outs get argued over later. Specific ones don't.

Third, get clarity on what "related to company business" means in practice. Ask your future employer or client to define it. If they can't give you a clear answer, assume they'll interpret it as broadly as possible.

What a Moral Rights Waiver Means for Your Work

If you're a designer, photographer, or writer, this one deserves more attention than it usually gets.

When you waive moral rights, you're agreeing that the company can modify your work without your approval. They can crop your photos. They can restyle your design system. They can rewrite your copy until it sounds nothing like you wrote it. They can put your work in a context that embarrasses you, and you have no legal basis to object. They can remove your name from the credits entirely.

For brand identity work, editorial illustrations, or anything you'd want in your portfolio, a moral rights waiver affects your reputation, not just your income. Know that you're agreeing to it.

How Clausely Flags This

Clausely specifically looks for blanket IP assignment language, prior work provisions, and the own time and equipment trap. When it finds them, it quotes the exact clause and explains what you'd be signing away. It also flags moral rights waivers separately, since those tend to get buried in sections labeled "intellectual property" or "proprietary information" where most people stop reading after the first sentence.

You upload your contract, and within a couple of minutes you have a plain-English breakdown of exactly what you're agreeing to give up.

Read the Clause Before You Sign It

IP assignment is one of the most financially consequential clauses in any creative or technical contract. It's also one of the most invisible. Companies count on the fact that you'll skip to the signature page.

Read the clause. Understand what it covers. Find out whether your state limits it. Ask for carve-outs by name before you sign. Once ink is on paper, unwinding an IP assignment is expensive, slow, and uncertain. Asking for a revision before signing costs you nothing but a few minutes and a conversation.

The designer who lost $15,000 didn't lose it because she didn't have legal rights. She lost it because she didn't know what she'd agreed to. Don't be her.

For the specific red flags that appear in freelance developer contracts and freelance designer contracts, those guides go deeper on the IP patterns that appear most often in each type of engagement.