Under the U.S. Copyright Act (Title 17 U.S.C.), the definition of work made for hire
stands as a core rule to determine copyright ownership, especially for customized
software developed by commissioned teams or in-house developers. The United States
Copyright Office (USCO) accepts copyright applications for computer software via its eCO
system, and clearly classifies qualified software as work made for hire where the
commissioning party or employer holds full copyright. Misjudging this rule frequently
triggers prolonged ownership conflicts between developers and clients. This case analyzes
a typical software copyright dispute arising from unclear agreements on commissioned
creation, explains the identification standards for work made for hire, and delivers practical
suggestions for global tech companies and outsourcing teams.
A U.S.-based financial institution commissioned an independent software development
studio to build a customized data management system in 2024. The two parties signed a
general development contract that only defined delivery standards and service fees, without
explicitly stating the copyright ownership or whether the finished program would be
regarded as work made for hire. After the studio completed and delivered the software, the
financial institution applied for copyright registration at USCO and listed itself as the sole
copyright owner, claiming the customized software was commissioned work made for hire.
The development studio filed an objection and subsequent litigation, arguing that it was an
independent contractor rather than a formal employee, and thus retained all copyright of the
self-developed software. During the trial, the court reviewed the cooperation mode, work
arrangements and contract clauses. It ruled that the two sides did not sign a written agreement
confirming work made for hire, and the studio maintained operational independence throughout
the development process. In accordance with USCO and federal judicial rules, the customized
software could not be deemed work made for hire. The final verdict affirmed the studio’s
copyright ownership, and the financial institution was only granted a non-exclusive right to use
the software.
Two categories of works qualify as work made for hire under U.S. copyright laws. The first refers to
works created by employees within the scope of their employment, where the employer
automatically becomes the legal copyright owner. The second covers specially commissioned
works falling into eight statutory categories including software and audiovisual works, which
shall be recognized as work made for hire only if both parties sign a clear written agreement
in advance. Oral commitments or general cooperation contracts without ownership clauses cannot
serve as valid proof.
Copyright registration information from USCO creates a preliminary presumption of ownership,
yet this presumption can be overturned by sufficient counter-evidence. Even if one party
successfully completes registration, the opposing side can submit development records,
communication logs and original contracts to prove its legitimate rights. For commissioned
software projects, the lack of a dedicated work-made-for-hire agreement becomes the biggest legal
loophole.
Independent contractors and regular employees are treated differently. Courts and USCO will
judge identities by examining working hours, management methods and operational independence.
Independent outsourcing teams are not naturally subject to the work made for hire rule, which
sets a higher threshold for commissioning parties to obtain full copyright.
When commissioning external teams to develop software or digital works, enterprises must sign
a separate written agreement to clarify that the deliverables are work made for hire, and
specify complete copyright transfer before project initiation. Standard cooperation contracts cannot
replace this dedicated document.
For in-house R&D teams, add explicit clauses on work made for hire and copyright ownership in
labor contracts, so as to secure corporate ownership of all works completed during employment.
After development, complete USCO copyright registration in a timely manner with the company listed
as the rights holder.
Retain full project files including development drafts, progress records and signed contracts. These
materials form a complete evidence chain to respond to ownership challenges and copyright
objections during or after USCO registration.
If enterprises only need the right to use the software instead of full copyright, they should define
the scope of authorized use, restrictions on re-licensing and modification rights in the contract to
avoid subsequent disputes.
The identification of work made for hire is pivotal to software copyright ownership in the United
States. This typical dispute proves that formal written agreements are indispensable for
commissioned projects. For global technology companies, financial institutions and outsourcing
service providers, standardizing contract terms and clarifying ownership in advance are the
most effective ways to prevent copyright conflicts. Combined with standardized USCO
registration procedures, such practices can fully protect legitimate rights and maintain stable
cooperation in long-term digital project development.
Hyperlink List：
● IPcrossark:
