Examples
Worked examples
- Is an instance
An incoming postdoctoral researcher signs the university's Proprietary Information and Invention Assignment Agreement (PIIA). Exhibit A, 'List of Prior Inventions,' lists a patent-pending diagnostic assay developed at their previous employer; because it is listed and dated before the agreement's effective date, it stays outside the university's IP assignment clause.
- Is an instance
A physician joining a medical device company as a paid consultant checks 'Yes' on the agreement's prior-inventions question and attaches a one-page list of two issued patents from an earlier role, protecting sole ownership of those patents from any later company claim.
Counter-examples
Looks similar, but isn't
- Not an instance
A faculty member submits an invention disclosure to the technology transfer office for a new compound conceived while running a federally funded lab experiment. This is a forward-looking report of new IP created during the funded relationship, governed by the institution's IP policy and, for federal awards, Bayh-Dole reporting obligations -- not a listing of pre-existing IP, and not this concept.
Editorial commentary
A prior inventions disclosure (also called a prior inventions exhibit or prior inventions schedule) is the attachment to an employment, consulting, founder, or IP assignment agreement in which an individual lists every invention, discovery, or other IP they created before the agreement’s effective date. Its purpose is definitional rather than administrative: it draws a documented line between IP the agreement’s forward-looking assignment clause will capture and IP the individual already owned before the relationship began.
What makes something a prior inventions disclosure
A clause or attachment is doing this job specifically when it has three features:
- It is tied to a specific effective date. The agreement’s IP assignment clause applies going forward from that date; the prior inventions exhibit is the mechanism for excluding everything that predates it.
- It uses an affirmative yes/no format, not a blank field. Standard language reads something like “I have no inventions or improvements to disclose” versus “See the list below” — the individual must actively check one box or the other. This matters because a blank exhibit is ambiguous (did the signer forget, or genuinely have nothing to list?), while a checked “No” is an affirmative representation the institution can rely on.
- It states the consequence for a listed item. Typically the individual retains full ownership of anything listed. Many forms pair this with a narrow “background IP” license-back: if a listed prior invention ends up incorporated into later work product, the individual grants the employer/institution a non-exclusive right to use it within that work product, without transferring ownership.
How it differs from an invention disclosure to a technology transfer office
The phrase “invention disclosure” is used for two genuinely different documents in research administration, and the overlap in name is a frequent source of confusion:
- Prior inventions disclosure (this page) is backward-looking and individual-initiated as part of onboarding paperwork. It lists what the person already owned before joining the institution or engagement, specifically to keep it out of the institution’s IP.
- (New) invention disclosure to a TTO is forward-looking and arises during the relationship. A researcher discloses a new invention conceived or reduced to practice while employed or funded, which is how the institution’s technology transfer office learns of IP that may fall within its ownership and, for federally funded work, within Bayh-Dole Act reporting obligations. See the full walkthrough in The Technology Transfer Process: From Invention Disclosure to Licensing and Revenue Distribution, and the comparison of that disclosure against a subsequent patent application.
Because a Bayh-Dole “subject invention” is by definition one conceived or first actually reduced to practice under a federally funded project, an invention already listed on a prior inventions exhibit — having predated the funded relationship entirely — falls outside that definition from the start; it was never in scope for the institution’s reporting obligations under the standard patent rights clause at 37 CFR 401.14.
Why the yes/no checkbox matters
The checkbox format exists because silence and a genuine “nothing to disclose” need to be distinguishable in a document that may matter years later. If a dispute arises over who owns a piece of IP, the institution’s position is strongest when the individual affirmatively represented, at the start of the relationship, either a complete list of pre-existing inventions or a checked “none.” An unchecked, blank exhibit gives neither party a clean record to point to.
This is the same underlying problem that California Labor Code Sections 2870 and 2872 address from the other direction: Section 2870 protects an employee’s inventions developed entirely on their own time, without employer resources, from being swept into an assignment clause (with limited exceptions for inventions related to the employer’s business or resulting from work performed for the employer), and Section 2872 requires the employer to give the employee written notice of that protection alongside any assignment agreement. A prior inventions exhibit and Section 2870-style protection are distinct mechanisms — one excludes inventions that predate the agreement, the other excludes certain inventions made during employment on the employee’s own time — but both exist to keep an assignment clause from capturing more than it is entitled to.
Why it matters for the individual
For the person signing, a complete prior inventions list is protective: without it, there is no documented boundary showing that a given piece of IP existed before the relationship, which leaves room for a later argument that it was actually developed using the institution’s resources or time. This is a particular concern for incoming faculty, postdocs, and industry consultants who arrive with a patent, patent application, or unpatented invention already in hand from a previous position.
Why it matters for the institution
For the university or company, the exhibit closes off a different risk: without it, the institution has no record of what IP a new hire or consultant already held, and may later find itself unable to distinguish its own assignable IP from something the individual brought in — or, conversely, may end up using someone’s pre-existing IP in institutional work product with no license in place to do so. Technology transfer offices and sponsored-programs offices generally rely on the same underlying agreement (often a Proprietary Information and Invention Assignment Agreement, or PIIA) that also carries the institution’s forward-looking IP assignment terms, so the prior inventions exhibit and the ongoing invention-disclosure obligation described in university IP policy are typically governed by the same document, just opposite ends of its timeline.
Related terms
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="Prior Inventions Disclosure"
vocab-term-identifier="https://casrai.org/dictionary/term/prior-inventions-disclosure" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/prior-inventions-disclosure",
"name": "Prior Inventions Disclosure",
"identifier": "https://casrai.org/dictionary/term/prior-inventions-disclosure",
"description": "A prior inventions disclosure is the exhibit or schedule attached to an employment, consulting, or IP assignment agreement in which an individual lists every invention they created before the agreement's effective date, using an affirmative yes/no format, so that pre-existing IP is documented as excluded from the agreement's forward-looking assignment clause rather than left ambiguous.",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/tech-transfer#set",
"url": "https://casrai.org/dictionary/term/prior-inventions-disclosure",
"sameAs": [],
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"@id": "https://casrai.org/#organization"
},
"dateModified": "2026-07-18T09:04:01",
"inLanguage": "en"
}






