When your business pays a developer to build software, you expect to own the result. That expectation is often wrong. Under US copyright law, who owns software depends on whether the creator was an employee or a contractor, what type of work was created, and — most importantly — what the written agreement actually says.
Two legal mechanisms determine software IP ownership in commercial contracts: the work-for-hire doctrine and IP assignment agreements. These are not interchangeable. Each covers a different set of circumstances, and relying on the wrong one for a given situation leaves your company without legal ownership of software it paid to have built.
This article explains how each mechanism works, where each applies, and how to structure your software development contracts to ensure your company owns what it commissions.
1. What Is Work-for-Hire?
Work-for-hire is a legal doctrine under the US Copyright Act (17 U.S.C. § 101) that treats certain works as if they were created by the hiring party rather than the actual creator. When a work qualifies as work-for-hire, the copyright vests in the employer or commissioning party from the moment of creation — no additional assignment is required.
The doctrine applies in two distinct situations.
Works Created by Employees
A work created by an employee within the scope of employment is automatically a work made for hire. The employer owns the copyright. This covers code written by a full-time software engineer as part of their job duties, provided the work falls within their defined role and was created during employment. The phrase “within the scope of employment” is the source of frequent disputes. Code written on an employee’s personal devices during personal time, for a purpose arguably unrelated to their role, may not qualify — even if the employer later incorporates it into a product.
Works Commissioned from Contractors (Nine Specific Categories Only)
For independent contractors, the work-for-hire doctrine applies only if two conditions are both met: (1) the parties have a written agreement expressly stating the work is a work made for hire, and (2) the work falls into one of nine specific statutory categories listed in the Copyright Act. Those categories include contributions to collective works, parts of motion pictures, translations, supplementary works, compilations, instructional texts, tests, answer material for tests, and atlases. Computer software is not on that list.
A standalone software application or a custom codebase commissioned from an independent contractor does not qualify as a work made for hire under the contractor provisions of the Copyright Act, regardless of what the written agreement says. Labeling it work-for-hire in the contract does not change this legal reality.
2. What Is an IP Assignment?
An IP assignment is a written contractual transfer of intellectual property ownership from the creator to the commissioning party. Unlike the work-for-hire doctrine, which operates by operation of law, an IP assignment works because both parties agree in writing that the creator transfers their ownership rights to the other party.
IP assignments can cover copyright, patents, patent applications, trade secrets, trademarks, moral rights (where waivable), and future rights in derivative works. A comprehensive IP assignment in a software development contract transfers all these categories, not just copyright.
The critical distinction in assignment language: a present-tense assignment (“Contractor hereby assigns to Company all right, title, and interest in the Work”) transfers ownership immediately. A future-tense promise (“Contractor agrees to assign”) creates a contractual obligation to assign in the future — courts have found that the latter does not automatically transfer ownership and may require a separate legal action to enforce.
Understanding the different types of intellectual property is the starting point for knowing which rights your assignment agreement needs to cover.
3. Why the Distinction Matters for Software Contracts
The practical consequence of relying on work-for-hire language for contractor-created software is that your company may not own the code it paid to have built. The contractor retains the copyright by default. If the relationship ends well, the contractor may never assert this right. If it ends badly, the contractor can theoretically demand licensing fees, seek an injunction against your use of the code, or assign their rights to a third party.
This risk is not hypothetical. IP ownership disputes between companies and former contractors arise in litigation and in M&A due diligence. A gap in IP documentation — a contractor who was paid but never signed an assignment agreement — can delay or restructure an acquisition, block a fundraising round, or create leverage for a bad-faith claim.
The correct structure for contractor-created software is an explicit IP assignment clause in the software development agreement, supplemented by work-for-hire language in the event any portion of the work qualifies under the statutory categories. Using both is belt-and-suspenders practice.
4. Patent Rights Are Not Covered by Work-for-Hire
The work-for-hire doctrine covers copyright only. It does not transfer patent rights. An employee who invents a patentable method, algorithm, or process during the course of employment does not automatically assign that patent to the employer under the work-for-hire doctrine — patent law operates differently from copyright law.
Patent rights transfer only through a written assignment. For software companies building products that may incorporate patentable technology, both employee and contractor agreements must include explicit patent assignment language — not just a copyright work-for-hire clause. This is one reason why intellectual property legal counsel is valuable when drafting software development agreements: a generalist contract template rarely addresses the patent dimension correctly.
5. What a Complete Software Development Agreement Should Include
A properly drafted software development agreement addresses IP ownership comprehensively, covering both the work-for-hire doctrine and IP assignment in the same document. Key provisions include a work-for-hire clause stating that to the extent permitted by applicable law all work product is a work made for hire; an IP assignment clause assigning all right, title, and interest in all work product — including copyright, patent rights, trade secret rights, and moral rights — to the commissioning party effective immediately upon creation; a prior IP carve-out schedule identifying pre-existing IP the contractor retains; a cooperation clause requiring the contractor to assist with patent filings and additional documentation; representations and warranties that the delivered work is original and does not infringe third-party rights; and open source restrictions requiring disclosure of any open source components used and confirming license compatibility with commercial use.
A contract attorney who understands technology law structures these provisions to work together and to account for the specific IP categories your product involves.
6. AI-Generated Code Adds a New Layer of Complexity
Software developers increasingly use AI coding assistants to generate portions of code. This practice creates a new IP consideration: code generated by an AI tool may have uncertain copyright status, and some AI-generated code is derived from open source repositories that carry license obligations.
The US Copyright Office has taken the position that works generated entirely by AI without human creative input are not eligible for copyright protection. If a significant portion of your commissioned software was generated by an AI tool without meaningful human authorship, the copyright status of that code is unclear — and the contractor’s ability to assign rights they may not hold is questionable.
Software development agreements in 2026 should address AI tool usage directly: requiring disclosure of AI-generated portions, warranting that AI-generated code does not incorporate copyleft open source material, and confirming that the contractor has reviewed and validated AI outputs for licensing compliance. The difference between copyright, patent, and trademark protection matters here because AI-generated outputs may create different gaps in each category.
Frequently Asked Questions
If I pay a contractor to build software, do I automatically own the copyright?
No. Under US copyright law, a contractor retains ownership of work they create unless a written agreement transfers those rights to you. Payment alone does not create a copyright transfer. You need a signed IP assignment agreement before work begins.
Can I rely on work-for-hire language in my contractor agreement to cover software?
Not for copyright purposes. Custom software built by an independent contractor does not fall within the nine statutory categories eligible for work-for-hire treatment under the Copyright Act, regardless of what the contract says. You need an IP assignment clause in addition to work-for-hire language.
Does work-for-hire cover patent rights?
No. The work-for-hire doctrine applies to copyright only. Patent rights do not transfer to an employer or commissioning party by operation of law — they require a separate written assignment. Software development agreements should include explicit patent assignment language.
What is a prior inventions schedule and should I include one?
A prior inventions schedule lists IP the contractor developed before the engagement and wants to retain. Including one protects both parties: it gives the contractor certainty about what they keep, and it gives the commissioning company a clear record of what was assigned versus what was pre-existing.
How should I handle IP ownership when developers use AI coding assistants?
Your software development agreement should require contractors to disclose any use of AI coding tools, identify AI-generated portions of the code, and warrant that those portions comply with applicable open source license terms. The contract should also warrant that the delivered work does not include training-data-derived code that could create downstream license obligations or copyright disputes.
Structure Your Software Contracts to Actually Own What You Build
The gap between expecting to own software and legally owning it is a contract drafting problem. Work-for-hire language is not enough for contractor-created software. A well-structured software development agreement addresses both copyright and patent rights, carves out pre-existing IP, restricts open source use, and requires cooperation on future IP registration.
Hansen Tong at TOSLawyer.com drafts and reviews software development agreements, contractor IP assignment agreements, and the full range of technology contracts for startups and software businesses. Contact TOSLawyer.com to get your contracts structured correctly before your next development engagement.