“Work made for hire” is a copyright-law doctrine, not a patent or invention-assignment concept — and confusing the two is one of the most common IP-ownership mistakes at research institutions. Under 17 U.S.C. § 101, a work made for hire is either (1) a work prepared by an employee within the scope of employment, or (2) certain categories of specially ordered or commissioned works where the parties sign a written agreement designating it as work made for hire. When a work qualifies, the employer or commissioning party is treated as the “author” for copyright purposes from the moment of creation — no separate assignment document is needed. This guide explains how that doctrine actually applies to universities, research institutes, and their technology transfer offices (TTOs), where it interacts uneasily with academic custom, federal funding terms, and the very different ownership rules that govern patents on the same campus.
The two-part statutory test
Section 101 of the Copyright Act defines a work made for hire narrowly. A work falls into the doctrine only if it satisfies one of two distinct prongs:
- Employee prong. A work prepared by an employee within the scope of their employment. Whether someone is an “employee” for this purpose is not determined by job title or how payroll classifies them — the Supreme Court held in Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), that courts must apply the common-law agency factors: the hiring party’s right to control the manner and means of the work, the skill required, who supplies tools and a workplace, the duration of the relationship, whether the hiring party can assign additional projects, how the work is paid for and taxed, and whether the work is part of the hiring party’s regular business, among other factors. No single factor controls.
- Specially ordered or commissioned work. A work created by someone who is not an employee (a contractor, consultant, or vendor) can only be a work made for hire if (a) it was specially ordered or commissioned, (b) it falls into one of nine statutory categories — a contribution to a collective work, part of a motion picture or audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, test-answer material, or an atlas — and (c) both parties sign a written instrument, before or at the time of creation, expressly stating the work is made for hire. Miss any one of those three requirements and the doctrine simply does not apply, no matter what the contract calls itself.
If neither prong is met, copyright vests by default in the individual human creator, and it takes an affirmative written assignment to move it anywhere else. That default-to-the-creator rule is what makes the doctrine consequential in a university setting, where a large share of copyrightable output — code, datasets’ selection and arrangement, course materials, manuscripts — is created by people whose employment status is genuinely mixed.
Why this is not the same question as who owns an invention
Research administrators who work primarily on the patent side of a technology transfer office sometimes assume an equivalent “hired to invent” rule governs copyright the way it governs certain patent rights. It does not. Patent ownership under U.S. common law and under the Bayh-Dole Act (35 U.S.C. §§ 200–212) for federally funded inventions generally still requires an enforceable assignment obligation — typically built into the invention-disclosure and IP-assignment terms of an employment agreement, faculty handbook, or a signed patent policy — before title actually transfers to the institution; an employee’s mere status as an inventor does not itself vest patent ownership in the employer the way work-for-hire vests copyright ownership in an employer automatically. Copyright is the reverse: if the employee prong of § 101 is satisfied, ownership vests in the institution immediately and automatically, with no assignment paperwork required at all. A single research output — say, a funded software tool with an accompanying patentable method — can therefore have its patent rights turn on a signed assignment obligation while its copyright in the source code turns on nothing more than whether the programmer was an “employee” acting “within the scope of employment” on the day they wrote it. TTOs that run both intake processes off a single unified “IP assignment” mental model routinely miss this distinction, and it matters most exactly where it’s least obvious: research software, databases, and instructional materials, where copyright — not patent — is usually the operative right.
The academic “teacher exception” — custom, not statute
Faculty members are, in the ordinary agency-law sense, employees of their university, which would put scholarly writing, lecture notes, and research papers squarely inside the § 101 employee prong and therefore owned by the institution. In practice, most U.S. research universities have never operated that way. A long-standing customary exception — often called the “teacher exception” or “academic exception” — has universities disclaiming ownership of traditional scholarly works (journal articles, books, lecture notes) that faculty create using their general academic freedom, even though those same faculty are unambiguously employees for other purposes. This exception is not written into the Copyright Act; it survives (where it survives) purely because individual institutions choose, through their IP or faculty handbook policy, to carve scholarly and pedagogical works out of what they otherwise claim as employer-owned work product. Because it is a matter of institutional policy rather than federal statute, its scope varies significantly by institution and by the type of work at issue — many policies distinguish scholarly articles and books (exempted) from software, courseware built for institutional use, or works created with “significant use of university resources” or grant funding (often reclaimed by the institution). Research administrators and TTO staff should treat their own institution’s IP policy — not the general doctrine — as the controlling document for any specific work.
Where this comes up most often at research institutions
Research software and code
Software written by paid staff, postdoctoral researchers, or research programmers acting within the scope of their employment is typically a work made for hire and owned by the institution outright. Software written by graduate students is a genuinely harder case: a student is usually not an “employee” under the CCNV v. Reid factors unless they hold a paid research- or teaching-assistant appointment and the work in question falls within the duties of that appointment — student status alone does not create an employment relationship for § 101 purposes. Institutions commonly close this gap not by stretching the work-for-hire doctrine but through an independent IP policy requirement that students sign an assignment agreement as a condition of using lab resources, grant funds, or participating in a sponsored project — a contractual route that does not depend on satisfying the employee prong at all.
Federally funded works
Work-for-hire status under § 101 is unaffected by the source of funding — a federal grant does not itself make a work “for hire” to the government. What federal funding does change is the rights the funding agency retains in a copyrighted work the grantee institution owns. Under the Uniform Guidance at 2 CFR § 200.315, the federal government generally retains a royalty-free, nonexclusive, irrevocable license to reproduce, publish, or otherwise use — and to authorize others to use — copyrightable material first produced under a federal award, even though the institution (or, if the institution’s policy assigns it there, the individual creator) retains the underlying copyright. That license obligation is separate from, and layered on top of, whatever the work-made-for-hire analysis already determined about who owns the work.
Consultants, contractors, and outside developers
When an institution engages an outside contractor — a software developer, instructional designer, or media producer — to build something, work-for-hire status is never automatic even with a contract in hand. The engagement must fall into one of the nine statutory categories, and the agreement must contain express work-for-hire language signed before or at the time the work is created. Many contractor-built deliverables (custom software is the single most common example) simply do not fit any of the nine categories, meaning the work-for-hire route is unavailable regardless of contract language. TTOs and sponsored-programs offices should not rely on a “work made for hire” clause alone in contractor agreements for software or other out-of-category work; the agreement should also include a present-tense copyright assignment clause (“Contractor hereby assigns…”) as a backstop, since an assignment does not depend on satisfying the work-for-hire categories.
Practical implications for TTOs and IP policy
- Audit which prong applies before assuming ownership. “The university funded it” or “it was created on campus” is not itself sufficient to establish work-for-hire status — the analysis turns on employment status and scope of duties (or, for contractors, the narrow statutory-category-plus-signed-agreement test), not on funding source or location of creation.
- Don’t conflate copyright and patent intake. A single invention-disclosure or IP-assignment form that treats “we own it” as a single yes/no answer can obscure that patent rights and copyright in the same output may rest on entirely different legal grounds and, occasionally, different owners.
- Write institutional exceptions into policy, not custom. Because the teacher exception has no statutory basis, an institution’s IP policy should say explicitly which categories of work (scholarly articles, courseware, software, data) are retained by creators versus claimed by the institution, rather than relying on unwritten tradition that can be inconsistently applied or later disputed.
- Use assignment clauses as a backstop for contractors and students. Where work-for-hire status is doubtful or unavailable (most student work, most out-of-category contractor deliverables), a signed present-tense assignment clause secures ownership independently of whether the work-for-hire test is met.
Frequently asked questions
Does work made for hire apply to patents?
No. “Work made for hire” is a copyright-specific doctrine under 17 U.S.C. § 101. Patent ownership by an institution generally depends on an enforceable assignment obligation in an employment agreement, faculty handbook, or signed IP policy, not on work-for-hire status.
Are university faculty employees for work-for-hire purposes?
Under the common-law agency factors from CCNV v. Reid, faculty are typically employees of their university. Whether a specific scholarly work is nonetheless treated as institution-owned depends on that institution’s own IP policy — many universities customarily exempt traditional scholarly and pedagogical works (the “teacher exception”) even though faculty are employees for other purposes, but this exception is a matter of institutional choice, not federal law, and does not typically extend to software or courseware built with significant institutional resources.
Who owns software a graduate student writes in a university lab?
It depends on whether the student is an “employee” under the CCNV v. Reid factors — generally true only if they hold a paid research- or teaching-assistant appointment and the software falls within that appointment’s duties. Many institutions close this gap through a separate signed assignment agreement required as a condition of lab access, grant participation, or enrollment, rather than relying on work-for-hire status alone.
Does federal grant funding make a work “for hire” to the government?
No. Funding source does not determine work-for-hire status. What changes under federal funding is that the government typically retains a royalty-free license to use copyrighted material produced under the award, per 2 CFR § 200.315, regardless of who owns the underlying copyright.
Is a signed contract enough to make a contractor’s work a work made for hire?
Not by itself. The engagement must also fall into one of the nine statutory categories listed in 17 U.S.C. § 101 (contribution to a collective work, audiovisual work, translation, supplementary work, compilation, instructional text, test, test-answer material, or atlas). Custom software commonly falls outside all nine categories, so institutions typically add an express present-tense assignment clause to contractor agreements as a backstop.
