9 November 2026
Who Owns Your Work? Understanding IP Assignment Clauses
# Who Owns Your Work? Understanding IP Assignment Clauses
You spend three weeks designing a brand identity system. The client loves it, pays the invoice, and everyone moves on. Six months later, you want to feature that project in your portfolio — and you get a cease-and-desist letter. The work you created no longer belongs to you. It never did, legally speaking, because buried in the contract you signed was an intellectual property assignment clause that transferred all rights the moment you put pen to paper.
This scenario plays out constantly in the freelance world. Not because clients are villains, but because IP assignment clauses are standard boilerplate — and most freelancers don't fully understand what they're signing away.
Let's fix that.
What Is IP Assignment, Exactly?
Intellectual property assignment is the legal transfer of ownership over creative or inventive work from one party to another. When you create something — a logo, a piece of software, a marketing strategy, a written report — copyright in that work is born the moment it's created. In most jurisdictions, that copyright belongs to you, the creator, by default.
An IP assignment clause changes that. It's a contractual provision that says: *any work you produce under this agreement belongs to us, not you.* Full stop.
This is different from a licence, which lets someone use your work while you retain ownership. An assignment is a permanent transfer. Once you've assigned the IP, you typically can't use that work again without permission — even though you made it.
Assignment clauses often include language like:
- *"All work product created under this agreement shall be considered work made for hire..."* - *"Freelancer hereby assigns all right, title, and interest in and to the deliverables..."* - *"Client shall own all intellectual property rights in perpetuity throughout the universe..."*
Yes, that last one is real. And yes, it means what it sounds like.
Why Clients Include These Clauses (And Why That's Not Always Unreasonable)
Before getting defensive, it's worth understanding why IP assignment exists in the first place. If a company hires you to build their customer-facing app, they have a legitimate business need to own that code outright — they can't run their product on work they're only licencing. Same goes for brand assets, proprietary research, or anything that becomes core to how their business operates.
From a client's perspective, paying for something they can't fully control is a risk. If you retained rights to their logo, you could theoretically licence it to a competitor. They don't want that exposure, and frankly, you wouldn't either if the roles were reversed.
So IP assignment isn't inherently predatory. The issue is when the scope goes far beyond what's reasonable — or when freelancers sign away rights without realising the implications.
Three Scenarios Where This Gets Costly
Scenario 1: The Portfolio Problem
A UX designer completes a full app redesign for a fintech startup. The contract included a broad IP assignment clause with no carve-out for portfolio use. When she adds the project to her website and LinkedIn, the startup's legal team contacts her. She has to remove it. That project — one of her strongest pieces of work — is now invisible to potential clients. She can't even describe the project in detail without risking breach of contract.
Scenario 2: The Reuse Trap
A freelance developer builds a custom content management module for a media company. He's used a similar module structure for years — it's part of his standard toolkit. The contract's IP assignment clause is written broadly enough to capture not just the deliverable, but the underlying methodologies and code architecture. Technically, he's now assigned ownership of tools he's been building his practice on. Using them for the next client could expose him to a claim.
Scenario 3: The Speculative Work Catch
A copywriter pitches three campaign concepts as part of her proposal process. The client picks one and commissions it, but the contract includes language assigning all work created *in connection with* the engagement. The two concepts the client didn't choose? Also assigned. She can't recycle them for another client or her own projects.
None of these situations require malicious intent. They're the natural result of signing standard corporate contracts without reading the IP provisions carefully.
What to Look For — and What to Push Back On
Not all IP assignment clauses are equal. Here's what to pay attention to:
Scope of assignment. Does it cover only the final deliverables, or does it sweep up drafts, concepts, background IP, and tools you bring to the project? A well-scoped clause should cover what the client is actually paying for — not everything you touch.
Background IP carve-outs. You should retain ownership of any IP you owned before the engagement — your frameworks, your code libraries, your design systems. Good contracts explicitly carve this out. If yours doesn't mention it, that's a gap worth addressing.
Portfolio rights. Ask for a clause that explicitly allows you to display the work in your portfolio and use it to promote your services, even if the underlying IP transfers to the client. Most reasonable clients will agree to this.
Moral rights. In some jurisdictions (including the UK and much of the EU), you have moral rights as a creator — the right to be credited, and the right not to have your work distorted. These are separate from copyright and sometimes need to be explicitly waived. Know whether you're being asked to waive them.
The word 'perpetuity.' When an assignment is in perpetuity throughout the world (and yes, sometimes the universe), that's permanent and total. That's often appropriate for commissioned work — but make sure it's priced accordingly.
Negotiating these clauses is not being difficult. It's being professional. Any client with a legitimate legal team will understand a conversation about IP scope. If they react badly to reasonable questions about contract terms, that tells you something important about working with them.
How to Price When You're Assigning IP
Here's something most freelancers undervalue: a full IP assignment is worth more than a licence. If a client wants to own everything you create, outright and forever, that should be reflected in your rate.
Think of it this way. If you retain rights, you could potentially reuse that work, licence it to others, or build on it in future projects. When you assign the IP, you lose all of that future value. The client gains it. That transfer has a price.
Some freelancers charge a flat IP transfer fee on top of their project rate — anywhere from 20% to 100% of the base fee depending on how valuable the work is likely to be. Others build it into their day rate for certain types of work. Either approach is legitimate, but you need to be intentional about it.
If you're doing creative work and not factoring IP into your pricing, you're leaving money on the table every time.
Read the Clause Before It Costs You
IP assignment clauses are often buried on page seven of a fifteen-page service agreement, written in dense legal language designed more for comprehensive coverage than clarity. That doesn't mean you can ignore them — it means you need a faster way to surface what matters.
Before signing any client contract, make sure you understand what you're assigning, what you're keeping, and whether the terms reflect what you've actually negotiated. If you're reviewing contracts regularly, tools like JuriScans can help you identify IP-related clauses quickly so you spend less time hunting through boilerplate and more time negotiating the bits that actually affect your business.
The goal isn't paranoia — it's clarity. Know what you're signing. Know what you're giving up. And make sure the price is right for both.