IP Assignment Agreement Template: Who Owns Contractor Code?

IP Assignment Agreement Template: Who Owns Contractor Code?
You paid for the code. Under US law, that doesn't mean you own it. Software written by a contractor usually isn't "made for hire", because software isn't one of the nine kinds of commissioned work that can be [E19]. So the copyright stays with its author until they sign a written transfer [E21]. Here is our IP assignment agreement template, clause by clause.
An IP assignment agreement is a signed document in which the person who created work, such as code, transfers their intellectual property rights in it to someone else, usually the client who paid for it.
Key takeaways
- Under US law, a copyright transfer is valid only in a writing signed by the owner or the owner's agent [E21].
- Software isn't one of the nine categories of commissioned work that can be "made for hire", so a "work for hire" label alone usually doesn't give a US client a contractor's code [E19].
- "Hereby assigns" transfers ownership now; "agrees to assign" is only a promise, the lesson of Stanford v. Roche (US) [E22].
- In the US, purely AI-generated material isn't protected by copyright, so an assignment of AI-assisted code transfers only whatever rights exist [E33, E34].
Download the IP assignment agreement template (Word + PDF, free, no form)
Download: Word (.docx) · PDF.
Template, not legal advice. Have a lawyer in your country review it before you sign.
The template is yousource's own adaptation. Sections 2, 4 and 5 are based on section 2 of the Common Paper Professional Services Agreement v1.1, published under CC BY 4.0 [E2], a licence that allows adaptation "for any purpose, even commercially", with credit [E6]. Use and change ours in any way, including commercially; just keep the Common Paper credit line.
Disclosure: yousource sells Dev On Demand.
Why paying a contractor doesn't make you the owner
Three US rules sit between paying for code and owning it.
A transfer needs a signed writing. Under 17 U.S.C. § 204(a), "A transfer of copyright ownership, other than by operation of law, is not valid unless an instrument of conveyance" is in writing and signed by the owner or the owner's agent [E21]. An invoice isn't that.
"Work for hire" is narrow. Commissioned work is made for hire only in nine categories, such as a translation, a compilation or a test, and only with a written agreement that expressly says "work made for hire", signed by all parties [E19]. Software isn't on the list. The Copyright Office says: "If a work fails to satisfy any of these requirements, it is not a work made for hire." [E19]
The label doesn't decide who is an employee. The facts do. CCNV v. Reid lists factors such as skill, who supplies the tools, duration, and whether the person runs their own business [E20].
So you need a signed document worded as a transfer.
What each clause in the IP assignment agreement template says
1. What this covers
"Work" is everything the Contractor or its team creates for the Client on the Project, from "source code, tests, scripts" to "documentation, designs". Its own tools (Schedule 1) and open-source software are excluded; sections 4 and 5 handle them.
2. "Hereby assigns", not "agrees to assign"
The Contractor "hereby assigns to the Client all rights in the Work, including copyright and all other intellectual property, worldwide."
The reason is a US patent case. In Stanford v. Roche (2011), Stanford's "agree to assign" was read as a promise to assign later. A later agreement saying "will assign and do[es] hereby assign" transferred the rights at once, so Roche got them [E22]. As Taft's bulletin puts it: "An agreement to assign one's patent rights is not the same as a patent assignment." [E22] That reading was the Federal Circuit's, not the Supreme Court's [E22].
Common Paper's §2.1 says "assigns", not "hereby assigns" [E23]. We strengthened it. For anything that can't be transferred today, the Contractor "agrees to transfer it as soon as it can."
2 (continued). Option A or B: on creation or on payment
- Option A, on creation: "ownership passes as each piece of Work is created."
- Option B, on payment: "ownership of each piece passes when the Client pays for it. Until then, the Client may use, copy and change it for the Project."
Common Paper offers the same choice of "Time of Assignment": "as they are created" or "upon payment of associated Fees" [E23]. Option A favours the Client. Option B protects the Contractor if an invoice goes unpaid, and the temporary licence lets the Client keep working.
On all yousource contracts to date, the client owns the code once it is paid for. That's Option B.
3. The Contractor's team signs too
A vendor can only pass on rights it holds. Because a US transfer needs a writing signed by the owner [E21], a freelancer who never signed still holds their rights. A contractor IP assignment is only as good as that chain. So each person ("employee, freelancer or subcontractor") must have "signed a written agreement giving their rights in the Work to the Contractor or directly to the Client" before starting, shown to the Client on request.
4. The Contractor's own tools, with a licence back
The Contractor keeps tools and code it had before the Project, or built outside it without the Client's information, if listed in Schedule 1. If they end up in the Work, the Client "gets a permanent, free, worldwide licence to use, copy, change and distribute them as part of the Work, and to let its own contractors and customers do the same."
Common Paper's §2.3 licence is narrower: "only as necessary to use the Deliverables" [E23]. The gate: "Anything not listed in Schedule 1 needs the Client's written approval before it goes in."
5. Open source: a list, and approval before copyleft
Daeryun Law warns that a GPL component may require the entire product to be open sourced if it is distributed [E27]. The same guide says a seller should disclose all open-source components [E27]; Schedule 2 is that list. Section 1 leaves open-source software out of the transfer.
Every component goes in Schedule 2 "with its version and licence" ("a software bill of materials export is fine"). Any component under a "copyleft" licence that could require the Client to publish its own code, such as GPL, LGPL or AGPL, needs "the Client's written approval (email is enough)" first.
6. AI-assisted code: whatever rights exist
None of the IP assignment templates we read addressed AI-generated code [E41].
The US Copyright Office says "Copyright does not extend to purely AI-generated material, or material where there is insufficient human control over the expressive elements", and "prompts do not alone provide sufficient control" [E33]. Human authors keep copyright in their own contributions and "creative modifications of the outputs", judged "case-by-case" [E33]. In Thaler v. Perlmutter, the Supreme Court declined to hear the appeal on 2 March 2026, leaving the human-author rule in place [E34].
An assignment can only transfer rights that exist. So the Contractor "transfers whatever rights exist" in AI-assisted Work and "does not promise that every AI-generated line is protected by copyright." It uses only approved tools "on plans where the provider does not train on the Client's code", and a person on its team "reviews and tests all AI-assisted Work before delivering it." That review is a quality rule; whether an edit earns copyright stays case by case [E33].
7. Credit and changes (moral rights)
The Contractor and its team give up, as far as the law allows, "any right to be named as author of the Work or to object to changes to it", and otherwise "agree not to use them against the Client."
In the UK, moral rights can be waived "by instrument in writing signed by the person giving up the right" [E24]. Neither the right to be identified nor the integrity right applies to "a computer program" [E25]. So under UK law, section 7 mostly matters for non-code work, such as docs and designs [E25].
8. Paperwork later
The Contractor signs "any document the Client reasonably needs to record or defend its ownership, at the Client's cost." If it doesn't within [10] business days of a written request, "the Client may sign that specific document in the Contractor's name."
Some sample contracts back a promise to sign later paperwork with a power of attorney [E26]. Ours is narrower: one document at a time. The template adds: "Some countries have extra signing rules for this kind of authority. Ask your lawyer."
9. Promises by the Contractor
Original work, apart from Schedules 1 and 2 "and AI-assisted work under section 6"; no infringement "as far as it knows"; no rights given to anyone else; team agreements signed. The AI exception keeps section 9 in line with section 6, which makes no promise about AI-generated lines.
10. US only: work made for hire
"The Client's ownership comes from the transfer in section 2." Work-made-for-hire status is only a back-up, because contractor software usually falls outside the nine categories [E19]. Delete it if US law can't apply.
How the IP assignment fits with your NDA
An NDA protects your information; an IP assignment decides who owns the code. Section 11 links them: "Confidentiality of the Work is covered by the NDA", and on ownership, "this agreement wins" over the main contract. Our software development NDA template covers the other half.
How to use it
- Fill in the basics: names, main contract, project, NDA, start date, law and courts.
- Tick Option A or B in section 2.
- Fill in Schedules 1 and 2.
- Keep or delete section 10, and delete the italic notes.
- Have a lawyer review it.
Bringing in an outside engineer? See our developer onboarding guide and development team contract guide.
Frequently asked questions
Who owns code written by a contractor?
Under US law, usually the contractor, until they sign a written transfer [E21]. Contractor-written software usually isn't work made for hire [E19].
Is software "work for hire" if the contract says so?
Usually not, when a contractor writes it. The label works only for nine categories of commissioned work, and software isn't one [E19].
Can a contractor assign AI-generated code?
Only whatever rights exist. In the US, purely AI-generated material isn't protected by copyright; human contributions can be [E33, E34].
Do I need an NDA as well?
Usually, yes. An NDA covers how your information is used; an IP assignment transfers ownership of the work. Without one, section 11 falls back on the main contract for confidentiality.
Sources
- [E2] Common Paper, Professional Services Agreement v1.1: https://commonpaper.com/
standards/ professional-services-agreement/ - [E6] Creative Commons, CC BY 4.0: https://creativecommons.org/
licenses/ by/ 4.0/ - [E19], [E20] U.S. Copyright Office, Circular 30, Works Made for Hire (rev. 08/2024): https://www.copyright.gov/
circs/ circ30.pdf - [E21] 17 U.S.C. § 204 (Cornell LII): https://www.law.cornell.edu/
uscode/ text/ 17/ 204 - [E22] Taft Law Bulletin, Stanford v. Roche, 131 S.Ct. 2188 (18 Jul 2011): https://taftlaw.com/
news-events/ law-bulletins/ stanford-university-v-roche-molecular-131-s-ct-2188-2011 - [E23] Common Paper, Professional Services Agreement v1.1, §2.1 and §2.3: https://commonpaper.com/
standards/ professional-services-agreement/ - [E24] UK Copyright, Designs and Patents Act 1988, s.87: https://www.legislation.gov.uk/
ukpga/ 1988/ 48/ section/ 87/ data.html - [E25] UK Copyright, Designs and Patents Act 1988, s.79 and s.81: https://www.legislation.gov.uk/
ukpga/ ; https://www.legislation.gov.uk/1988/ 48/ section/ 79 ukpga/ 1988/ 48/ section/ 81 - [E26] Law Insider, further assurance sample clauses: https://lawinsider.com/
clause/ further-assurance - [E27] Daeryun Law, What Should Corporations Evaluate in an Open Source License Agreement? (27 May 2026): https://www.daeryunlaw.com/
us/ insights/ open-source-license-agreement-in-nyc - [E33] U.S. Copyright Office, Copyright and Artificial Intelligence Part 2: Copyrightability (Jan 2025): https://www.copyright.gov/
ai/ Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf - [E34] Baker Donelson, Supreme Court denies certiorari in Thaler v. Perlmutter (5 Mar 2026): https://www.bakerdonelson.com/
supreme-court-denies-certiorari-in-thaler-v-perlmutter-ai-cannot-be-an-author-under-the-copyright-act - [E41] Juro, IP assignment agreement template: https://juro.com/
contract-templates/ ; Business-in-a-Box, assignment of IP rights: https://www.business-in-a-box.com/intellectual-property-assignment-agreement template/ assignment-of-intellectual-property-rights-D5206