The IP Assignment Clause — Who Owns the Work (and When) in Your Contracts
Copyright defaults surprise people: in many jurisdictions, work you create for a client belongs to you until a written document says otherwise — and work contractors create for you belongs to them. The IP assignment clause is the paragraph that overrides the default, and getting it wrong means either losing work you thought you owned or re-buying your own portfolio later.
This guide covers the default rules, the assignment-on-payment structure that protects both directions, the license alternative for ongoing work, and the third-party materials trap hiding in most deliverables.
The short answer
- Absent written assignment, independent contractors retain copyright in most jurisdictions — the "work for hire" doctrine is narrower than people assume.
- Assignment-on-payment structures align ownership with payment: unfinished engagements do not hand over rights.
- Third-party components (fonts, stock, libraries, AI tools) come with their own license chains — assignment language cannot transfer what the creator never owned.
Who this playbook is for
Built for solo founders delivering creative or technical work who need ownership clarity both ways — as provider and as hirer.
Step 1: Know the defaults before writing anything
Baselines: employees’ work product is typically employer-owned; independent contractors’ is typically theirs absent writing; "work for hire" applies to specific categories and agreements in the US and less broadly elsewhere. Translation: as a solo provider, your pre-assignment work is yours; as a hirer of contractors, what you bought is access, not ownership — until the clause says otherwise.
Step 2: Write assignment-on-payment as the standard
The balanced formulation: "Upon receipt of full payment, Provider assigns to Client all right, title and interest in the final deliverables, excluding pre-existing tools and third-party materials." This aligns incentives: ownership transfers when payment completes; unpaid engagements leave rights with the maker. Both sides understand the switch is tied to settled invoices.
Step 3: Carve out your pre-existing materials explicitly
As provider, retain your tools, frameworks, templates and know-how — the clause lists them as "Provider Materials, licensed to Client for use within the deliverables." Without the carve-out, a broad assignment hands clients your internal machinery. As hirer, accept this clause happily — your contractor’s toolkit staying theirs is what keeps their prices sane.
Step 4: Handle third-party materials honestly
Deliverables contain fonts, stock images, code libraries, AI-generated components — none assignable by you because you never owned them. The clause discloses: third-party materials remain under their own licenses, identified in a list. This transparency is what prevents the year-two surprise when a client’s new designer asks where the font license lives.
Step 5: Use licenses where assignment is wrong for the deal
Not every engagement should transfer ownership: licensing fits ongoing content (client gets broad license, you retain work for portfolio and reuse), subscription deliverables, and template-based products. The license clause specifies scope (exclusive?, territory, duration, modifications allowed?). Assignment is the default expectation; the license is the deliberate alternative when your business model says so.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| Template setup | Assignment-on-payment + carve-outs, lawyer-reviewed once | once |
| Per contract | Check third-party materials are disclosed | 10 min |
| Per engagement type | Assignment vs license decided deliberately | in-flow |
| Annually | IP clause review with contract refresh | included in review |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| Contracts with IP clauses | 100%, both directions | The baseline that overrides defaults |
| Third-party disclosures on file | Every deliverable | The license-chain transparency metric |
| Portfolio rights retained where intended | Per your business model | The license-vs-assignment strategy working |
| IP disputes | Resolved by the clause, quickly | The paragraph doing its job |
Common mistakes to avoid
- Assigning everything including your toolkit. Broad "all work product" clauses hand clients your internal systems; the Provider Materials carve-out is one sentence that preserves your business.
- Assuming payment invoices transfer rights. Invoices are accounting; the assignment is a legal act in the signed agreement. The clause is where ownership actually moves.
- Ignoring AI-tool terms in deliverables. Increasingly relevant: AI-generated components carry platform terms your assignment cannot override — disclose them alongside fonts and stock in the third-party list.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Lawyer-reviewed contract template | The clause, fitted to your jurisdiction |
| Your deliverables checklist | The third-party materials list, per project |
| License clause variants | For the engagements where retention is right |
| Your portfolio policy | The reuse rights you keep, stated openly |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- Client Data Protection for Solo Founders
- GDPR for Solopreneurs
- Trademark Basics for a One-Person Brand
FAQ
Q: Who owns work before full payment?
Under assignment-on-payment, the provider does — the client has use per the agreement, ownership moves at settled payment. This is standard and fair both ways: it protects providers from delivering into non-payment and clients from paying into ambiguity. The alternative (assignment on creation) mainly benefits non-payers.
Q: Can a client demand ownership of my pre-existing tools?
They can demand; you negotiate. Reasonable clients accept the Provider Materials carve-out universally — it is standard industry practice. A client insisting on owning your internal machinery is announcing they plan to replicate you in-house, which is itself useful information about the engagement.
Q: What rights should I keep for my portfolio?
Standard provider language: the right to display deliverables in a portfolio and describe the engagement, unless the client’s confidentiality agreement says otherwise. State it in the contract — retroactive portfolio permissions are awkward; front-loaded ones are normal.
Q: How does this apply to work contractors do for me?
Identically, mirrored: your contractor agreements need assignment-on-payment to you, with their tools carved out to them. As the hirer, you are the client in this transaction — the same clause structure protects you from the default where the contractor keeps everything they make.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.