What should an IP clause in a software contract say?
It should state who owns what was delivered, carve out anything you brought with you, and say whether you retain any right to use the result. Four clauses do almost all the work: assignment or licence, background IP, licence back, and moral rights. Everything else is detail.
Most software contracts settle ownership in a paragraph nobody reads, which then decides what happens to years of your work. The paragraph is not complicated. It is just boring, and it arrives at the point in a project where everyone wants to start.
Not legal advice. This is what the clauses do and which wording to notice.
The four that matter
the IP paragraph │ ├── 1. assignment or licence ──► who owns the deliverable ├── 2. background IP ──────────► what you keep of your own ├── 3. licence back ───────────► what you may still use └── 4. moral rights ───────────► standard waiver, low impact
1. Assignment or licence
The operative sentence. Look for “hereby assigns”, “all right, title and interest”, or “work made for hire”.
Two things to check.
Scope. What exactly is assigned? “All deliverables” is broad. “The Software as defined in Schedule 1” is narrow and leaves your tooling, build scripts, and infrastructure code alone. Narrow is better for you and is very often sufficient for the client.
Timing. “Assigns upon payment in full” is materially different from “assigns upon creation”. The first means an unpaid invoice leaves ownership with you, which is real leverage. Push for it.
If the clause grants a licence rather than assigning, the substance moves to its terms: exclusive or not, perpetual or not, modifiable or not, transferable or not. A non-exclusive licence is the version that leaves your asset intact.
2. Background IP
The clause that stops a broad assignment swallowing everything you brought with you.
You want something to the effect that pre-existing intellectual property, and anything developed independently of the engagement, remains yours, with the client receiving a licence to whatever is embedded in the deliverable.
Without this, a broad assignment can be read to capture the internal library you have carried between eleven projects. That reading is usually not what anyone intended and is very hard to unwind afterwards.
This is also the clause that most often preserves something licensable from an otherwise fully assigned engagement.
3. Licence back
The one people do not think to ask for, and the one that changes the long-term picture most.
Weak version: you may continue to use general skills, knowledge, and techniques acquired during the engagement. This is close to meaningless, since nobody can take your skills anyway.
Strong version: a perpetual, non-exclusive, royalty-free licence to use, modify, and exploit the assigned work for your own purposes. This lets you reuse the code even though the client owns it.
Middle versions exist and are usually where a negotiation lands: reuse of components and utilities but not the deliverable as a whole.
Read the exact scope. It is the difference between an engagement that ends your relationship with the code and one that does not.
┌─ WORTH CHECKING ─────────────────────────────────────────────────────┐ │ │ │ Private, finished, owned by you, and doing nothing. │ │ │ │ [ See what your repos are worth ] │ │ │ └──────────────────────────────────────────────────────────────────────┘
4. Moral rights
In the UK and much of Europe, authors hold moral rights: to be identified, and to object to derogatory treatment of their work. They cannot be assigned, but they can be waived, and commercial contracts waive them as a matter of course.
For software the practical consequence is small. It is standard, expect it, and do not spend negotiating capital on it.
The wording worth pushing back on
“All intellectual property created during the term of this agreement.” During the term, not under this engagement. Read literally, that reaches your weekend project. Ask for it to be limited to work performed under the agreement.
A work made for hire clause with no assignment fallback. As covered in work for hire versus license, the US statutory category is narrow and commissioned software often sits outside it. A clause relying on it alone leaves both parties less certain than they think.
Assignment on creation with no payment condition. You have handed over the asset before being paid for it.
No background IP carve-out at all. The single most common gap in short freelance agreements.
The five minute version
If you read nothing else in a contract, find the intellectual property paragraph and answer four questions.
Who owns the deliverable. Is my own pre-existing work carved out. Can I still use any of this afterwards. Does ownership depend on being paid.
Four answers, five minutes, and it determines what you are holding a decade later.
What to read next
- Work for hire versus license, the underlying distinction
- Who owns the code you wrote for a client, auditing what you already signed
- What disqualifies a repo, how ownership decides eligibility
Common questions
- What is background IP?
- Anything you already owned before the engagement, or developed outside it: your libraries, scaffolding, internal tooling, and general know-how. Without a carve-out, a broad assignment can sweep it into the client's ownership along with the deliverable.
- What is a licence back?
- A clause returning some right to use the assigned work to you. Scope varies enormously, from general skills and know-how only, through to a full non-exclusive right to reuse the code. It is the difference between an assignment that ends your relationship with the work and one that does not.
- Are moral rights relevant to software?
- They exist in the UK and much of Europe, cover attribution and objecting to derogatory treatment, and are routinely waived in commercial agreements. For software the practical impact is small, but the waiver is standard and expected.
- Should assignment be conditional on payment?
- It is strongly in your interest. If ownership only transfers on payment in full, an unpaid invoice means the client never acquired the copyright, which is considerably more leverage than a debt collection letter.
- Can I negotiate these clauses as a solo freelancer?
- Usually yes, and more easily than people expect. Most templates ask for total ownership because that is what the template says, not because anyone assessed the need. Asking what the client intends to do with the software resolves most of it.