# Invention Assignment Agreements: What You're Actually Signing Away > Invention assignment agreements (PIIAs): why employers need them after Stanford v. Roche, ‘hereby assigns’ vs ‘agrees to assign,’ and what you can negotiate. Guide | Author: Lidiia Levitska | Source: Intellectual Property Law (outsideipcounsel.com) Canonical: https://outsideipcounsel.com/guides/invention-assignment-agreements/
Quick answer: An invention assignment agreement (usually part of a PIIA — Proprietary Information and Invention Assignment Agreement) is the contract that transfers ownership of what you invent to your employer, because U.S. patent law otherwise leaves inventions with the individual inventor — the rule the Supreme Court enforced in Stanford v. Roche (2011). The core package: a present assignment ("hereby assigns," which passes title automatically), a duty to disclose inventions, a prior-inventions schedule, a further-assurances clause, and confidentiality terms. State statutes like [California Labor Code § 2870](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB§ionNum=2870) carve out truly unrelated off-hours inventions, and the prior-inventions exhibit and named side-project carve-outs are your main points of leverage. This is general education, not legal advice — have an attorney licensed in your jurisdiction review your specific situation.
Somewhere in your day-one onboarding stack — between the direct-deposit form and the handbook acknowledgment — was a document with a name like "Proprietary Information and Invention Assignment Agreement." You signed it in about ninety seconds. That **invention assignment agreement** is quite possibly the most consequential contract of your career: it decides who owns your ideas, and its wording has swung ownership of patents worth hundreds of millions of dollars. This guide explains why employers require these agreements, what each standard clause actually does, the two words that decide ownership, and what's realistically negotiable. ## Why these agreements exist: inventors own by default Copyright has the work-made-for-hire doctrine, which hands employee-created works to the employer automatically. **Patent law has no equivalent.** Title to an invention vests in the **individual human inventor**, and drawing a paycheck — even a paycheck specifically for doing R&D — doesn't move it. The Supreme Court made the stakes vivid in *Board of Trustees of Stanford University v. Roche Molecular Systems*, 563 U.S. 776 (2011). A Stanford researcher signed the university's form promising he "agree[d] to assign" future inventions to Stanford. Later, while visiting a private company (Cetus, whose line of business Roche acquired), he signed *that company's* form stating he "will assign and do[es] hereby assign" his inventions. He then co-invented PCR-based HIV-testing methods. When Stanford sued Roche for patent infringement, it lost — the Court held that even under the Bayh-Dole Act's framework for federally funded research, the invention belonged first to the inventor, and the inventor had already conveyed it to Cetus via the present assignment. Stanford's promise-of-future-assignment came up empty. Every well-advised employer internalized the lesson: **if you want to own what your people invent, get it in writing, and get the writing right.** Two common-law doctrines give employers partial fallbacks without a contract — **hired-to-invent** (an implied duty to assign when someone was employed specifically to create the invention) and **shop rights** (a nonexclusive, royalty-free license when the employee used company time or resources). Both are narrow, litigation-dependent, and no substitute for an agreement, as the [employee IP pillar](/guides/who-owns-what-you-create-at-work/) explains. ## Anatomy of the standard PIIA The typical package — PIIA, CIIA (Confidential Information and Invention Assignment), or "Employee Innovations Agreement" — bundles five components. Know what each one does before you sign. **1. The assignment itself.** You assign to the company all inventions, discoveries, works of authorship, and improvements that you conceive or reduce to practice during employment, subject to statutory carve-outs. Watch the temporal and subject-matter breadth: "during the period of employment" reaches off-hours work unless a statute or carve-out says otherwise. **2. The disclosure duty.** You must **promptly disclose** inventions to the company — often including ones you *believe* fall outside the assignment, so the company can evaluate the claim. Employees skip this at their peril: concealing an invention, then commercializing it later, is the classic fact pattern in constructive-trust litigation. **3. The prior-inventions schedule.** An exhibit where you list inventions and works you made *before* joining, which are excluded from the assignment. More on this below — it's the part almost everyone gets wrong. **4. Further assurances.** You promise to execute confirmatory assignments, patent applications, and declarations later, and you typically appoint the company your **attorney-in-fact** to sign if you're unavailable or uncooperative. This is what lets companies perfect title years after an inventor has left. **5. Confidentiality / trade-secret terms.** Obligations not to use or disclose the company's confidential information, surviving termination indefinitely for trade secrets. These interact with everything from [protecting source code](/guides/how-to-protect-source-code/) to departure disputes, and they're enforceable even in states hostile to non-competes. ## "Hereby assigns" vs. "agrees to assign": the two words that decide ownership Here is the drafting point that decided *Stanford v. Roche* and dozens of cases since. Under the Federal Circuit's **FilmTec doctrine** (*FilmTec Corp. v. Allied-Signal Inc.*, 939 F.2d 1568 (Fed. Cir. 1991)), contract language matters enormously: - **"I hereby assign"** — a **present assignment of future rights**. Title to an invention passes to the employer **automatically, by operation of the contract, the instant the invention exists**. No further signature needed. If two parties hold competing claims, the present assignee generally wins. - **"I agree to assign" / "I will assign"** — a mere **promise to assign in the future**. The employee keeps legal title until a separate assignment is actually executed. The employer holds, at best, equitable rights it must go to court to enforce — and it can lose the race to a third party holding present-assignment language, exactly as Stanford did. If you're an employer, audit your form for the magic words (competent forms say something like "hereby irrevocably assigns and agrees to assign"). If you're an employee, understand that with a present assignment there is **no later moment of choice** — your future inventions within the agreement's scope are the company's the moment you conceive them. ## The prior-inventions exhibit: actually fill it out The prior-inventions schedule exists to protect *you*, and the single most common mistake employees make is leaving it blank — usually because it's page nine of the onboarding packet and HR is waiting. Why it matters: - **A blank schedule is evidence.** Most agreements state that if nothing is listed, you represent there *are* no prior inventions. When you later claim your app predated the job, the blank exhibit will be Exhibit A against you. - **Listing preserves ownership without disclosure of secrets.** You can describe items at a non-confidential level ("mobile fitness-tracking application, ~14,000 lines of code, begun March 2024") — enough to identify, not enough to hand over. - **It forces the conversation early.** If the employer objects to an item, better to negotiate before you've invested two more years in the project. Founders should care too: acquirers and investors read these schedules during diligence, and a key product listed on a *founder's prior-inventions exhibit at a previous employer* — or missing paperwork generally — is exactly the kind of chain-of-title defect that stalls financings, as covered in [IP assignment gaps](/guides/ip-assignment-gaps/) and [who owns your startup's IP](/guides/who-owns-startup-ip/). ## Holdover clauses: claims that outlast the job Many agreements include a **holdover (or "trailer") clause**: inventions you conceive for some period *after* leaving — commonly six months to a year — are presumed to belong to the former employer if they relate to your work there or derive from its confidential information. The rationale is real (people don't invent on a start-date/end-date schedule, and some employees "hold" inventions until after resigning), but so are the abuses, and courts police these clauses. The general pattern: holdover clauses are enforceable only if **reasonably limited in time and scope** — tied to the employer's actual confidential information or the employee's actual work, for a short period. Unlimited or industry-wide trailers function as de facto non-competes on inventing and tend to fail; New Jersey's Supreme Court in *Ingersoll-Rand Co. v. Ciavatta*, 542 A.2d 879 (N.J. 1988), articulated the reasonableness framework most courts echo. In California, an aggressive holdover clause also collides with the state's hostility to restraints on lawful employment. If you're planning a departure, holdover language is one of the three documents to read first — see [quitting to start a competitor](/guides/quitting-to-start-a-competitor/). ## State statutory carve-outs: the floor employers can't drain About ten states impose a statutory limit on how much an assignment clause can grab. The template is **California Labor Code § 2870**: an employer cannot require assignment of an invention you developed **entirely on your own time without using employer equipment, supplies, facilities, or trade secrets** — *except* inventions that (1) relate to the employer's business or actual or demonstrably anticipated R&D, or (2) result from work you performed for the employer. California's § 2872 further requires the agreement to *notify* you of the carve-out. Washington, Illinois, Minnesota, and several other states run the same play with local variations. Two things to internalize: the carve-out is **narrower than it sounds** (the "relates to the employer's business" exception swallows most side projects in your own field), and clauses purporting to grab protected inventions are void as to those inventions but don't invalidate the rest of the agreement. The mechanics, state list, and worked examples are in [California Labor Code § 2870, explained](/guides/california-labor-code-2870/), and the practical side-project analysis is in [can my employer claim my side project?](/guides/can-my-employer-own-my-side-project/). ## What's negotiable — and the red flags **Realistic asks for employees:** - **A named carve-out** for an existing project: listed on the prior-inventions schedule *plus* a sentence acknowledging you may continue developing it on your own time without employer resources. This is routine and usually granted. - **Open-source treatment**: either an exclusion for contributions to named projects or a pointer to a sane company OSS policy, so your weekend pull requests aren't technically company property. - **Holdover trims**: shorten the trailer period and tie it explicitly to trade secrets rather than "any related invention." - **Statutory notice**: confirm the § 2872-style notice is present if you're in a carve-out state. **Red flags worth pushing back on (or at least pricing in):** - Assignment of inventions conceived **before** employment with no schedule mechanism - **Perpetual or unlimited holdover** periods - Assignment of "all inventions during employment" in a **non-carve-out state** with no relatedness limit at all - Present-assignment language plus attorney-in-fact powers **without** any disclosure-review process for claimed exclusions - For contractors: an employment-style PIIA that ignores the very different contractor defaults — see [contractor vs. employee IP ownership](/guides/contractor-vs-employee-ip-ownership/) For a sense of how these fights end when they reach court, browse the [patent case archive](/topics/patents/). ## The bottom line Invention assignment agreements exist because patent law gives inventions to inventors, and *Stanford v. Roche* proved that even a sophisticated employer loses when its paperwork only *promises* a future assignment while someone else's *presently conveys*. Know the five-part anatomy, respect the power of "hereby assigns," actually fill out the prior-inventions exhibit, and treat holdover clauses and statutory carve-outs as the negotiable edges of an otherwise standard deal. Employees who read the document before signing — and employers who audit their forms — almost never end up in these lawsuits. For the full ownership map across copyrights, patents, and trade secrets, start at the [employee IP pillar](/guides/who-owns-what-you-create-at-work/). --- *This article is general legal information for educational purposes only. It is not legal advice, does not create an attorney-client relationship, and may not reflect the most current law in your area. Invention ownership disputes turn on specific facts and exact contract language. For advice about your situation, consult an attorney licensed in your jurisdiction.* ## Frequently asked questions ### What is a PIIA or invention assignment agreement? A Proprietary Information and Invention Assignment Agreement (PIIA, sometimes CIIA) is the standard contract employers use to secure ownership of what employees create. It typically bundles five things: a present assignment of inventions and works to the company, a duty to promptly disclose inventions you conceive, a prior-inventions schedule listing what you're excluding, a further-assurances promise to sign future paperwork, and confidentiality obligations protecting the company's trade secrets. Nearly every technology employer requires one at hiring because, without it, patentable inventions belong to the individual inventor by default. ### Why do employers need invention assignment agreements at all? Because U.S. patent law vests ownership in the individual inventor, not the employer — being on payroll doesn't transfer title. The Supreme Court confirmed this in Stanford v. Roche (2011), where Stanford lost rights in HIV-test patents because a researcher's later agreement with a private company used present-assignment language ('hereby assigns') while Stanford's own form only promised a future assignment ('agree to assign'). Copyright's work-made-for-hire doctrine covers employee-created works, but nothing similar exists for patents, so a written assignment is the only reliable path to company ownership. ### What is the difference between ‘hereby assigns’ and ‘agrees to assign’? Timing of title — and it decides ownership fights. Under the Federal Circuit's FilmTec doctrine, 'hereby assigns' is a present assignment: title to a future invention passes to the employer automatically the moment the invention comes into existence, with no further act needed. 'Agrees to assign' is only a promise to convey later; until the employee actually signs an assignment, the employee holds legal title, and a third party who obtains a present assignment first can take priority. That exact contrast cost Stanford its claim in Stanford v. Roche. ### Can I negotiate an invention assignment agreement? Often, within limits. The realistic asks are a specific carve-out naming an existing side project (listed on the prior-inventions exhibit with the company's written acknowledgment), an exclusion or clear policy for open-source contributions, narrowing any holdover clause that claims inventions conceived after you leave, and confirming the agreement contains the state-required notice — such as California Labor Code § 2872's notice of the § 2870 carve-out. Employers rarely rewrite the core assignment for a rank-and-file hire, but naming your side project on the schedule is a routine and usually granted request.