Skip to content

Strategy

Work made for hire and software ownership: what the clause misses

What to check in the ownership clause before you sign or get acquired: the assignment, the chain of people, and what the vendor keeps.

Computing America. Applications, integrations, data analysis and AI/ML engineering.

Send the clause
3 min readComputing America
An open key cabinet with one hook empty and three keys still hanging.

In short

  • Work made for hire is a doctrine of copyright law. Copyright is one of four rights you need; it reaches neither the invention (patent), the method or tuned parameters (trade secret), nor the marks (trademark).
  • The doctrine applies to employees' work within the scope of employment. For a contractor it needs a signed agreement and a work in one of nine statutory categories, and software isn't named among them.
  • What works is a present assignment of the vendor's copyright in everything it makes for you (code, designs, logos), written as a fallback after the work-made-for-hire language, plus confidentiality terms to protect the trade secrets.
  • The chain has to reach the keyboard: every employee and subcontractor under written assignment before they contribute, or the break surfaces during acquisition diligence.
  • Escrow gives conditional access to source, released only on events the agreement names. If the vendor holds the repository, it is the minimum to ask for; if you hold it from the first commit, there is nothing to escrow.

A work made for hire clause settles at most copyright, and for contractor-written software it often doesn't apply at all. If you're about to sign, or be acquired, the gap between the phrase and the rights it carries is what a diligence team will find.

What the phrase covers, and what it misses

Fig. 1
  1. Copyright

    The code, designs and logos the vendor made

    Within: Hire clause or assignment.
  2. Patent

    The invention in the code; held by the inventor until assigned

    Within: Written assignment.
  3. Trade secret

    The method and tuned parameters; exists while kept secret

    Within: Confidentiality and your own use.
  4. Trademark

    The names and marks; arises from your use of them

    Within: Confidentiality and your own use.

Work-made-for-hire language reaches only copyright; patents need a written assignment, and trade secrets and marks rest on secrecy and use.

Source17 U.S.C. § 201(b); 35 U.S.C. § 261 (patents are assignable by an instrument in writing); 18 U.S.C. § 1839(3) (a trade secret needs reasonable measures to keep it secret); USPTO ("You establish rights in your trademark by using it"). A classification, not a legal opinion.

The doctrine works differently from an assignment: under 17 U.S.C. § 201(b) (opens in a new tab), the hirer of a work made for hire "is considered the author" from creation, while an assignment moves ownership from an author who held it first.

The doctrine also has a scope problem. 17 U.S.C. § 101 (opens in a new tab) defines a work made for hire as either work prepared by an employee within the scope of employment, or a specially ordered or commissioned work. The commissioned work must fall inside a closed list of nine categories and be covered by a signed written agreement. The nine:

  • A contribution to a collective work
  • Part of a motion picture or other audiovisual work
  • A translation
  • A supplementary work
  • A compilation
  • An instructional text
  • A test
  • Answer material for a test
  • An atlas

Software isn't named on that list, so a contractor's code usually falls outside it, though a part can fit a category such as an audiovisual work.

The chain has to reach the keyboard

An assignment from a vendor can only convey what the vendor holds. If its engineers, contractors or offshore subcontractors aren't under present assignment to the vendor, the chain has a break, and you'll find it during diligence on an acquisition.

  • Every individual contributing to your deliverables, employees and subcontractors alike, under written assignment to the vendor before they contribute.
  • A present assignment, not a promise to assign, plus an obligation to sign whatever documents perfect it later.
  • Waiver of moral rights, which persist in some jurisdictions and can survive an assignment.
  • Subcontractors named before signature, with approval rights on any added afterward.

What the vendor keeps, and what that means

Development firms typically carry pre-existing components: internal libraries, scaffolding, deployment tooling. Keeping those is legitimate, and demanding assignment of a vendor's whole toolchain doesn't help you. What you need is a perpetual, irrevocable, transferable license to everything embedded in your system, broad enough to cover selling the business, with the components listed by name. Push back on the phrase “Vendor's proprietary materials.”

If a vendor keeps ownership of what it builds for you and licenses it to you, it is free to license the same code to your competitors unless the contract forbids it. Sometimes a lower price makes that worth it. If you take the trade, ask for a cooling-off period before the work can be licensed to a defined list of competitors (eighteen months, for example).

Where escrow fits

Escrow answers a different question: the vendor holds the source and might go away. If you hold the repository from the first commit, escrow has nothing to hold, and its release conditions and dispute process are cost without cover. If the vendor does hold it, escrow is the minimum to ask for: it releases the source to you only on the events the agreement names.

The parts people forget

  • Open-source components listed with their licenses. A copyleft license in the wrong place can obligate you to publish source you consider proprietary.
  • Third-party code and content identified, with a clear answer on who pays the license fee and what terms flow through to you.
  • Feedback clauses removed. Some contracts assign the vendor rights in anything you tell them, including during support calls, which can cover your own business logic.
  • Accounts, repositories, registrars and cloud tenancies in your name. Owning the code is worth less if the deployment pipeline lives in someone else's organization.
  • Documentation and architecture decision records as deliverables. Code you can't build, deploy or operate is hard to use.

Sources

  1. 1.17 U.S.C. § 101: Definitions (work made for hire) (opens in a new tab), Legal Information Institute, Cornell Law School
  2. 2.17 U.S.C. § 201: Ownership of copyright (opens in a new tab), Legal Information Institute, Cornell Law School

Next step

Send us the ownership clause.

Paste the intellectual-property and license language out of the contract. We will tell you what it assigns, what it leaves your vendor holding, and which sentence is usually missing.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing