Technology Transfer & Innovation

Technology Transfer & Innovation

Technology transfer is the set of processes, agreements, and offices through which discoveries made in universities, government laboratories, hospitals, and other research institutions move into practical use — usually via patenting and licensing to an existing company, or via a new company founded around the technology. In most U.S. research universities this work is centralized in a Technology Transfer Office (TTO), sometimes branded an Office of Technology Licensing, Innovation and Commercialization Office, or Research Enterprise office. Equivalent functions exist under different names internationally: Knowledge Transfer Offices in the UK and EU, and Technology Licensing Offices in Japan and elsewhere.

For a research administrator, technology transfer intersects almost every other part of the sponsored-research lifecycle: it starts with an inventor’s disclosure obligation under a sponsored award, runs through contracting instruments the same office negotiates — material transfer agreements, sponsored research agreements, and confidentiality agreements — and increasingly overlaps with research security and export control review before a technology, material, or piece of software can leave the institution. This page is CASRAI’s hub for that whole area: invention disclosure and patenting, the federal funding rules that govern IP ownership, licensing and commercialization mechanics, the contracts that move technology and materials between organizations, the funding and support pathways that turn research into startups, and the export-control questions that increasingly sit alongside all of it. It is a newer, still-growing part of CASRAI’s coverage — treat the linked pages here as the current state of a section that will keep filling in, not a finished catalog.

From lab notebook to patent application: invention disclosure and novelty

Technology transfer formally begins with an invention disclosure: a written report an inventor submits to their institution’s TTO describing what was invented, when, by whom, and under what funding. Disclosure is not optional where federal funds were involved — it is the trigger for the institution’s obligations under the Bayh-Dole Act (below), and delaying it has real legal consequences, because U.S. patent law runs on a first-inventor-to-file system.

Since the America Invents Act took effect for applications filed on or after March 16, 2013, 35 U.S.C. § 102 defines what counts as prior art against a patent application: anything patented, described in a printed publication, in public use, on sale, or otherwise publicly available before the application’s effective filing date — including the inventor’s own earlier disclosures. Section 102(b) provides a narrow one-year grace period for disclosures that trace back to the inventor, but that grace period is a U.S. peculiarity: most major foreign patent offices, including the European Patent Office and China’s CNIPA, apply an absolute-novelty standard with no general grace period, so a conference poster or a paper submitted for peer review can destroy patent rights outside the U.S. immediately, even while U.S. rights are still intact. The Supreme Court’s Helsinn Healthcare S.A. v. Teva Pharmaceuticals decision (2019) added that a confidential commercial sale can still trigger the on-sale bar under Section 102(a) — confidentiality doesn’t exempt a transaction from counting as prior art. The practical implication research administrators repeat to faculty: talk to the TTO before a publication, poster, thesis defense, or sales conversation, not after. See 35 U.S.C. § 102: Patent Novelty and Invention Disclosure Timing for the full mechanics, including how the disclosure-timing clock interacts with the Bayh-Dole election-of-title deadline described next.

Once a disclosure is filed, the TTO typically runs (or commissions) a prior art search and, where relevant, a freedom-to-operate analysis — a review of whether practicing the invention would infringe someone else’s live patent, which is a distinct question from whether the invention itself is novel enough to patent. If the office decides to pursue protection, the usual first filing is a provisional patent application (a lower-cost, informal filing that establishes a priority date and starts a 12-month clock to file a full non-provisional/utility application), sometimes followed by a Patent Cooperation Treaty (PCT) application to preserve the option of filing in multiple countries later. Not every disclosure is patented at all: software, datasets, and certain research tools are frequently protected as copyright or released under an open-source license instead, and some biological materials move under a material transfer agreement with no patent involved at all.

The Bayh-Dole Act: federal funding, election of title, and march-in rights

Most U.S. university technology transfer exists in its current form because of the Bayh-Dole Act of 1980 (codified at 35 U.S.C. §§ 200–212). Before Bayh-Dole, the federal government generally retained title to inventions made with federal research funding, and very few of the resulting patents were ever licensed or commercialized. Bayh-Dole instead allows universities, nonprofits, and small businesses to elect to retain title to inventions made under federal funding agreements, in exchange for a defined set of obligations: disclosing the invention to the funding agency, filing for patent protection within set deadlines, giving the government a nonexclusive, royalty-free license to practice the invention, giving preference to small businesses in licensing, and sharing royalty income with the inventor.

The standard implementing regulation is 37 CFR 401.14, which sets out the mechanics in detail. A recipient institution must disclose each subject invention to the funding agency within two months of an inventor’s written disclosure to the institution’s own patent personnel, and must then elect in writing whether to retain title within two years of that disclosure — a window the funding agency can compress to as little as 60 days if a public disclosure has already started the one-year statutory bar under 35 U.S.C. § 102(b) running. Institutions typically manage this disclosure and reporting obligation through iEdison, an interagency system maintained by the federal government that lets recipients report inventions and utilization to multiple funding agencies in one place. See 35 U.S.C. § 102: Patent Novelty and Invention Disclosure Timing for how this election deadline and the patent-novelty clock interact, and CASRAI’s federal grant closeout guide for where invention reporting fits into award closeout more broadly.

Bayh-Dole also gives the funding agency march-in rights (35 U.S.C. § 203): the authority to require the patent holder to grant a license to a third party, or to grant one itself, if the invention is not being made available on reasonable terms, if health or safety needs aren’t being met, or if certain public-use requirements aren’t satisfied. March-in rights are one of the most publicly debated provisions in technology transfer policy — and, notably, no federal agency has ever actually exercised them in the more than four decades since the Act passed. The National Institutes of Health alone has received and denied six march-in petitions. That non-use is itself a policy fact worth knowing: it is central to arguments that Bayh-Dole’s current balance shouldn’t change, and equally central to periodic proposals (including “reasonable pricing” framework debates in the pharmaceutical context) to use march-in more actively. A research administrator advising faculty or leadership on this shouldn’t overstate march-in as a live operational risk to a specific license — historically, it has not been one — while still being accurate that the legal authority exists and is periodically the subject of renewed federal review.

Bayh-Dole applies specifically to funding agreements; separately, some federal contracts (as opposed to grants or cooperative agreements) use an alternate patent-rights clause under the Federal Acquisition Regulation rather than the Bayh-Dole standard clause, and the government’s own in-house Cooperative Research and Development Agreements (CRADAs) with federal laboratories follow a different statutory framework (the Stevenson-Wydler Act) again, with its own IP allocation rules distinct from a Bayh-Dole grant. Distinguishing which framework governs a given collaboration — grant, cooperative agreement, procurement contract, or CRADA — is one of the more consequential judgment calls a research administrator or TTO makes early in a project, because it determines who owns what before an invention even exists.

Licensing structures: how institutions commercialize IP

Once an institution owns or controls rights to an invention, a licence is the instrument that lets someone else use it: a signed agreement to exploit a piece of IP — a process, product, dataset, or piece of software — typically in exchange for compensation. The two structural choices every license negotiation starts from are exclusive versus non-exclusive. An exclusive license grants one licensee the sole right to practice the technology (often within a defined field of use or territory), which is usually necessary to justify the capital a company will need to invest in bringing an early-stage academic invention to market, but concentrates all commercialization risk in one licensee. A non-exclusive license lets the institution license the same technology to multiple parties — more common for research tools, platform technologies, and software where broad dissemination benefits the field more than exclusivity would. A licensee can also be granted the right to grant sublicenses to further parties, which is common in pharmaceutical and platform-technology deals where the original licensee itself develops a distribution or manufacturing network.

Because an early-stage university invention is rarely far enough along for a company to commit to a full license immediately, many deals start with an option agreement: a time-limited right to evaluate the technology and negotiate license terms later, without committing either party to the full license yet. Compensation structures combine several elements: an upfront fee, ongoing royalties (usually a percentage of net sales, sometimes with contractual audit rights so the licensor can verify what’s being reported), milestone payments tied to development or regulatory events, and — especially in startup licenses where the licensee cannot pay meaningful royalties yet — an equity stake in the licensee company instead of, or alongside, royalties. Where a licensed technology itself builds on IP the institution didn’t originate — a sponsor’s pre-existing know-how, or IP from an earlier project — contracts distinguish background IP (what a party brought into the collaboration) from foreground IP (what the collaboration itself generates), a distinction that has to be settled before a sponsored research agreement is signed, not after an invention shows up.

The Association of University Technology Managers (AUTM), the main professional body in this field, has run an annual U.S. and Canadian licensing survey since 1991, tracking institution-level invention disclosures, patent filings, licenses executed, startups formed, and licensing revenue — the closest thing this field has to a standardized economic impact benchmark, and the reason “how does our TTO compare to peer institutions” questions usually start with the AUTM survey rather than any single institution’s own numbers. Not every license generates revenue that offsets the university’s own patenting costs — a well-known finding across AUTM data over the years is that most institutional technology transfer programs run at a net cost, with returns concentrated in a small number of high-value licenses, which is part of why licensing strategy (which inventions to patent at all, exclusive vs. non-exclusive, how hard to negotiate upfront cash vs. equity) is a real portfolio-management discipline, not a formality applied uniformly to every disclosure.

Contracts that move technology, materials, and confidential information

Much of a TTO’s day-to-day work is contract negotiation, not just patenting. A Material Transfer Agreement (MTA) governs the transfer of tangible research materials — cell lines, reagents, plasmids, animal models, prototype hardware — between institutions, and sets terms for what the recipient can and can’t do with the material, whether results using it can be published, and who owns any new IP created using it. CASRAI’s practical MTA process guide walks through the negotiation lifecycle in detail. A close relative for U.S. federal laboratories specifically is the Cooperative Research and Development Agreement (CRADA), which lets a federal lab and a non-federal partner (university, company) collaborate under Stevenson-Wydler Act authority, with its own distinct IP-allocation defaults from either an MTA or a Bayh-Dole grant.

A sponsored research agreement is the contract that funds a specific research project at the institution, whether the sponsor is a federal agency, foundation, or company — and, for industry sponsors specifically, is typically where the background/foreground IP allocation and any option-to-license terms described above get negotiated up front. Before substantive technical discussions happen at all, a confidentiality agreement (NDA) is usually the first document signed, protecting both sides’ unpublished information during evaluation — institutions frequently maintain both one-way and mutual templates depending on whether information will flow in one direction or both. For multi-institution or multi-country collaborations, particularly EU Horizon Europe-funded projects, a consortium agreement allocates IP, decision-making authority, and access rights across every partner before the project starts, using standardized templates like DESCA in the European context. And where a researcher from another institution or country will work on-site, a visiting scholar agreement increasingly folds in IP assignment, conflict-of-interest, and export-control terms alongside the traditional appointment logistics — a shift discussed further below.

Software and data outputs raise a parallel licensing question that runs alongside patent licensing: whether to release code or a dataset under an open-source or Creative Commons license instead of, or in addition to, pursuing a patent. CASRAI’s guide to Creative Commons licenses for research data covers the CC0/CC-BY/CC-BY-NC distinctions relevant to that decision; TTOs increasingly weigh in on open-source licensing choices for research software the same way they weigh in on patent strategy, since the choice of license affects both downstream reuse and any later commercialization option. Underlying authorship of a resulting copyrightable work, and any copyright transfer agreement a publisher later asks for, is a related but legally distinct question from inventorship on a patent — see the cross-cluster note below.

From research to startup: SBIR/STTR, I-Corps, and spin-outs

Licensing to an existing company is one commercialization path; forming a new company — a university spin-out (or spin-off) — is the other, and federal programs exist specifically to bridge the gap between a lab result and a fundable startup. The Small Business Innovation Research (SBIR) and Small Business Technology Transfer (STTR) programs require federal agencies with extramural R&D budgets above set thresholds to set aside a fixed percentage of that budget for small businesses (SBIR: 3.2%, at agencies with extramural R&D budgets above $100 million; STTR: 0.45%, at agencies above $1 billion) — both funded through a phased structure: Phase I proof-of-concept awards (commonly in the tens of thousands to low hundreds of thousands of dollars, agency-dependent), Phase II awards to develop the technology further (commonly one to several million dollars), and a non-federally-funded Phase III where the technology is expected to reach the commercial market. STTR specifically requires a formal partnership between the small business and a research institution, making it a more direct technology-transfer vehicle than SBIR, where a university partnership is common but not structurally required.

Before a team is ready for SBIR/STTR, the NSF I-Corps program is a common on-ramp: a structured, cohort-based customer-discovery curriculum (built on Steve Blank’s “Lean LaunchPad” methodology, running since the early 2010s and now delivered through a national network of regional I-Corps Hubs plus a competitive I-Corps National Teams program) that requires a minimum number of customer interviews during a several-week program, intended to test commercial viability before committing further grant funding to a technology. See CASRAI’s NSF I-Corps program guide for team-role structure, eligibility, and funding specifics, including how I-Corps participation, Bayh-Dole licensing, and SBIR/STTR funding typically sequence relative to each other. Universities frequently pair I-Corps-style customer discovery with their own proof-of-concept or gap funds, industry affiliates programs, and startup incubators or accelerators to keep a spin-out alive in the period between “interesting lab result” and “fundable company” — a stage sometimes described in the field’s own literature as the technology-transfer “valley of death.”

Underlying all of this is a common vocabulary for describing how far along a technology is: Technology Readiness Level (TRL), a 1–9 scale originated by NASA in the 1970s and later formalized by the U.S. Department of Defense, running from TRL 1 (basic principles observed) through TRL 9 (proven in an operational environment). TTOs and funding agencies alike use TRL as shorthand for how much further development — and what kind of funding vehicle — a given disclosure needs before it’s ready to license or spin out. A spun-out company still burning through its early funding is tracked the same way a sponsored grant is on the university side: a startup’s burn rate and a sponsored project’s own award milestones (including milestone payments in industry-funded translational work) are the same underlying financial-monitoring discipline applied to different vehicles, and the institution’s own de minimis indirect cost rate election matters just as much on an SBIR/STTR subaward to a university partner as on any other federal award.

Export control and research security in technology transfer

A technology, material, or piece of software doesn’t have to physically cross a border to trigger export-control review — sharing controlled technical data with a foreign national on U.S. soil, a deemed export, is treated the same as a physical export under U.S. law. Two overlapping federal regimes govern this: the Export Administration Regulations (EAR), administered by the Commerce Department’s Bureau of Industry and Security, cover dual-use items; the International Traffic in Arms Regulations (ITAR), administered by the State Department, cover defense articles and services. See CASRAI’s deemed export and ITAR and EAR dictionary entries, and the fuller export control (EAR/ITAR) and international research collaboration guide, for how these regimes actually apply to a research project.

Fundamental research performed openly and intended for publication is generally exempt from these controls under the long-standing “fundamental research exclusion,” but that exemption narrows fast once a project involves proprietary sponsor data, publication restrictions, or export-controlled inputs — exactly the kind of terms that show up in industry sponsored research agreements and some MTAs. A growing share of TTO and research-security review now centers on identifying export-controlled research and sensitive technology categories (advanced semiconductors, quantum information science, advanced biotechnology, and similar critical- and emerging-technology lists that vary by jurisdiction and are updated periodically) before a collaboration, material transfer, or visiting researcher arrangement is finalized, alongside handling requirements for Controlled Unclassified Information (CUI) where a federal sponsor requires it. Where foreign investment in, or acquisition of, a U.S. technology company (including university spin-outs) is involved, a separate review regime — the Committee on Foreign Investment in the United States (CFIUS) — can also come into play. This is also why the research security policy function at many institutions now sits organizationally close to, or inside, the technology transfer and international agreements function, and why visiting scholar agreements increasingly build in export-control screening as a standard clause rather than an afterthought. See CASRAI’s Research Integrity & Compliance hub for the research-security and export-control material that sits primarily in that cluster rather than this one.

Where technology transfer connects to other CASRAI clusters

Technology transfer rarely operates in isolation from the rest of research administration. It shares a border with export control and research security, covered in depth on CASRAI’s Research Integrity & Compliance hub. Invention disclosure and Bayh-Dole reporting are steps inside the broader federal award lifecycle covered in CASRAI’s guides to Uniform Guidance (2 CFR 200) and federal grant closeout. Faculty involvement in a spin-out they’ve licensed technology to routinely triggers institutional conflict-of-interest disclosure obligations — see CASRAI’s conflict of interest disclosure form guide for how those disclosures are typically structured. And research materials moving under an MTA or a data-heavy sponsored research agreement connect directly to CASRAI’s Research Data Management hub, particularly around data-sharing terms and licensing.

Two related but genuinely distinct concepts are worth separating explicitly, because the vocabulary overlaps in ways that cause real confusion: inventorship on a patent is a legal determination (who conceived of at least one claim of the invention) governed by patent law, while authorship on a resulting publication is an editorial determination governed by journal policy and standards like ICMJE’s criteria, covered on CASRAI’s CRediT & Authorship Attribution hub. The same individual is very often both an inventor and an author on related outputs, but the two lists frequently don’t match exactly — a common, and legitimate, source of confusion for early-career researchers navigating both a patent disclosure and a manuscript from the same project.

Finally, where a technology or dataset incorporates Traditional Knowledge held by an Indigenous community — increasingly relevant in bioprospecting, agricultural, and ethnobotanical research — commercialization and benefit-sharing questions raise governance considerations that sit alongside, and sometimes ahead of, the standard Bayh-Dole/licensing framework described above; CASRAI’s broader data-governance coverage in the RDM cluster addresses the related CARE Principles for Indigenous Data Governance.

Frequently asked questions

Do I have to disclose an invention if my research wasn’t federally funded?
Most university IP policies require disclosure of any patentable invention made using institutional resources, facilities, or during the course of employment, regardless of funding source — the Bayh-Dole Act specifically governs federally funded inventions, but an institution’s own IP policy is typically broader. Check the specific institution’s policy rather than assuming Bayh-Dole is the only trigger.

What’s the difference between an exclusive and a non-exclusive license?
An exclusive license grants one licensee sole rights (often within a defined field of use or territory); a non-exclusive license lets the institution license the same technology to multiple parties. Exclusivity is usually needed to attract the investment required to commercialize an early-stage invention, but it also means the institution is betting the technology’s whole commercial future on one licensee.

Has the government ever actually used its Bayh-Dole march-in rights?
No federal agency has exercised march-in rights in the more than four decades since the Act passed in 1980, though the authority remains on the books at 35 U.S.C. § 203 and is periodically the subject of policy review and petitions (NIH alone has received and denied six).

Is a provisional patent application the same as a full patent?
No. A provisional application is an informal, lower-cost filing that establishes a priority date and starts a 12-month clock to file a full non-provisional (utility) application claiming that priority date; it is never itself examined or granted.

Does SBIR/STTR require a university partner?
STTR structurally requires a formal partnership between the small business and a research institution; SBIR does not require one, though many SBIR-funded startups still license technology from, and maintain informal ties to, the university where the underlying research originated.