Who owns the work? IP ownership clauses explained
Intellectual property clauses decide who owns code, designs, inventions, and content created under a contract. Learn work-for-hire vs. licence, background IP traps, and what freelancers must check.
The short answer
An IP ownership clause decides who owns the intellectual property — code, designs, documents, inventions — that gets created during a contract. The default under law varies by country and by whether you are an employee or contractor, so the clause matters enormously. The key questions: is IP assigned (transferred) or licensed, what happens to tools and knowledge you brought in ("background IP"), and when does ownership actually transfer.
Assignment vs. licence
An assignment transfers ownership: the client owns the work outright and can modify, resell, or build on it without you. A licence keeps ownership with you but gives the client permission to use it in defined ways.
Neither is automatically right. Clients paying full freight for custom work usually expect assignment. If you sell productised work — templates, frameworks, reusable components — a licence protects your ability to sell the same foundation again.
The background IP trap
Almost nothing is built from zero. Developers bring libraries, designers bring systems, consultants bring frameworks. This pre-existing material is "background IP", and a badly drafted clause can sweep it into the assignment.
If your contract assigns "all intellectual property created or used in connection with the services" to the client, you may have just handed over your entire toolkit. The fix is simple: assign only the new deliverables, and license your background IP to the client as needed.
- Foreground IP — new work created for this project.
- Background IP — tools, code, methods you had before or develop independently.
- Third-party IP — open-source libraries and stock assets, whose licences neither of you controls.
When does ownership transfer?
The classic freelancer trap: the contract says IP transfers "upon creation" or "upon signing". You deliver, the client disappears, and they own work they never paid for.
The professional standard is transfer upon full payment. Until the invoice clears, you keep the IP — which is your only real leverage against non-payment.
Moral rights and portfolio rights
In many countries, creators keep "moral rights" — the right to be credited and to object to derogatory treatment — even after assigning economic rights. Some contracts ask you to waive them; in some jurisdictions that waiver is not even enforceable.
If you want to show the work in your portfolio, say so in the contract. Otherwise the confidentiality clause may quietly ban it.
Sample clause language
Illustrative wording, written for this guide — not copied from any real contract.
Upon receipt of full payment, the Contractor assigns to the Client all intellectual property rights in the Deliverables created specifically for this engagement. The Contractor retains all rights in Background IP and grants the Client a perpetual, non-exclusive licence to use Background IP as incorporated in the Deliverables.
Payment-gated transfer, new deliverables assigned, toolkit protected — the standard professional structure.
Contractor hereby assigns to the Company all right, title and interest in any and all inventions, works, and intellectual property created, conceived, or used in connection with the services, whether or not related to the Deliverables, effective immediately upon creation.
Transfers your pre-existing tools and side projects, before payment, forever.
Red flags to look for
- Assignment "upon creation" or "upon signing" instead of upon payment.
- Language sweeping in background IP: "all IP used in connection with the services".
- An employment-style IP clause applied to an outside contractor.
- No portfolio or self-promotion carve-out when the work is also confidential.
- Moral rights waived worldwide with no credit provision.
What to ask for
- Make assignment effective on full payment, not on delivery or signing.
- Define deliverables narrowly and list your background IP explicitly in a schedule.
- Grant a licence of background IP instead of assigning it.
- Ask for a portfolio carve-out, even if it requires written approval per piece.
- Clarify open-source: deliverables may include open-source components under their own licences.
Find this clause in your own contract
Upload a PDF, Word file, or image and Lawly AI will pull out the clauses that matter, quote the exact wording, and explain the risk in plain English.
Frequently asked questions
If a client pays me, don't they automatically own the work?
No. In most jurisdictions a contractor keeps copyright unless the contract assigns it (or a valid work-for-hire rule applies). Payment buys what the contract says it buys.
What is 'work made for hire'?
A US doctrine where certain commissioned works are owned by the client from creation. It applies only to narrow categories and to employees; outside the US it often does not exist. Never rely on it — use an explicit assignment.
Can I reuse code I wrote for one client for another?
Only if you kept the rights. If the contract assigned everything, reuse may infringe your client's copyright — which is why the background IP carve-out matters so much.
Related guides
This guide is general educational information about how these clauses usually work. It is not legal advice, and contract law differs by jurisdiction. For a decision that matters, speak to a qualified lawyer.