Short Answer: You Keep the Patent, the Government Keeps a License
Under the Bayh-Dole Act, a small business that invents something while performing a federally funded project may elect to keep title to that invention — the patent is yours, filed in your company's name, and you can license or sell it. What the government retains is a nonexclusive, nontransferable, irrevocable, paid-up license to practice the invention for government purposes worldwide, plus a set of reporting duties, a US manufacturing preference, and rarely used march-in rights. On the data side, SBIR and STTR awards give you a protection period during which technical data you generated and properly marked cannot be disclosed outside the government or used to compete against you. So the honest framing is not "who owns it" but "what strings are attached to what you own." Projects House is an engineering firm, not a law firm or a grants consultancy; this article is educational, and the exact terms in your award document and agency supplement govern.
Subject Inventions: The Term That Defines the Boundary
Bayh-Dole applies to subject inventions — inventions conceived or first actually reduced to practice in the performance of the federally funded work. That definition draws a line you should care about a lot. Work you did before the award, on your own money, with dated records, is not a subject invention. Neither is work done later on a separate privately funded program with separate staff and separate documentation. Everything conceived inside the funded project is.
The practical consequence: keep the funded work bounded and documented. Separate timekeeping, separate lab notebooks, and separate design files make the boundary provable years later when an acquirer's diligence team asks which patents carry a government license. Loose bookkeeping tends to resolve against you, because the burden of showing an invention was not a subject invention falls on the company. Good invention records help here in the same way they help with priority — see keeping an inventor's notebook.
The Three Deadlines That Actually Cost People Their Rights
Losing title under Bayh-Dole almost never happens because of a dispute. It happens because a deadline slipped. The sequence, reported through the government's iEdison system or the agency's equivalent:
- Disclose each subject invention to the funding agency within a short window — generally two months — after the inventor discloses it to your company's patent personnel.
- Elect title in writing within a defined period after disclosure, generally two years, and sooner if a statutory bar such as a publication or public use is looming.
- File a patent application within the period after election, generally one year, and before any statutory bar date.
Miss these and the agency can request title. Agencies are usually willing to grant extensions if you ask before the deadline rather than after. Two operational habits prevent almost all of this pain: put the deadlines on the same calendar as your technical reporting, and give one named person responsibility for both. For the wider reporting rhythm, see SBIR grant reporting, milestones, and deliverables.
You also must include a government support statement in the patent itself, identifying the award. It is a one-line requirement people forget, and it is visible on the front page of the granted patent forever.
SBIR Data Rights: The Part That Protects Your Know-How
Patents cover inventions. Most of what makes a hardware company valuable is not patented — it is test data, drawings, firmware, process parameters, and the manufacturing package. SBIR and STTR awards address this with a data rights clause: technical data and software you developed under the award, when properly marked with the required legend, are protected for a defined period. During it, the government may use the data for internal purposes but may not release it outside the government or use it to have a competitor build your product.
Three things determine whether this protection is real for you:
- Marking. Unmarked deliverables can lose the protection. Every drawing, report, and file that leaves your building under the award needs the legend the award specifies.
- Scope. Data developed at private expense before or outside the award is generally in a stronger position still. Data developed with government funds gets the protection period; data developed under a government contract with no restrictions at all can end up with unlimited rights.
- Deliverable design. You control what you deliver. A final report that demonstrates results without dumping your complete manufacturing data package into the record is not evasion; it is normal practice. Keep the manufacturing data package as company property and deliver against the statement of work.
The US Manufacturing Preference
Bayh-Dole includes a preference for US industry: for products embodying a subject invention or produced through its use, exclusive licensees who intend to sell in the United States generally must agree that the products will be manufactured substantially in the United States. Agencies can waive this on a showing that domestic manufacture is not commercially feasible or that reasonable efforts to find a domestic manufacturer failed, but the waiver is a request, not a right.
Read that in the context of your production plan. If your roadmap ends with an Asian contract manufacturer and an exclusive US license, that is a conversation to have with the agency and counsel early rather than at term sheet stage. The comparison in manufacturing in China versus the USA is worth revisiting when a federal award is part of the picture, because the calculus changes.
March-In Rights, and Why They Are Rarely the Real Risk
The government may, in narrow circumstances, require you to license a subject invention to a third party — chiefly when the invention is not being brought to practical application, or when health or safety needs are unmet. In practice this authority has been exercised essentially never after a formal proceeding, and it applies to companies that shelved the technology, not to companies commercializing it. Track it as a compliance item, not a planning constraint. The more common real-world friction is far more mundane: annual utilization reporting on each subject invention, which you owe for as long as the agency asks.
Grants and Patents Are Complementary, Not Substitutes
Founders sometimes treat a federal award as an alternative to filing. It is the opposite. An award tends to accelerate publication, presentations, and public demonstrations — all of which can be statutory bars — so the filing calendar gets tighter, not looser. The sequence that works is: file a provisional patent application before any public disclosure, prosecute on the normal schedule, and report the invention to the agency in parallel. Ownership questions with contractors and employees deserve the same early attention, since a federal award does not fix a broken assignment chain — see who owns the IP in product development.
Three Questions to Answer Before You Sign
- What is in scope? Write down what the funded work covers and what stays on private funding, and structure records to match.
- Who owns the calendar? Name the person responsible for invention disclosure, election, filing, and utilization reporting, and put every date in one place.
- Where will it be built? If US manufacture is not the plan, understand the preference and the waiver path before you promise an investor an exclusive license.
For program selection and the funding landscape around these rules, see our government funding guide and how non-dilutive money fits with equity in combining grants with private investment.
Build the Technology, Keep the Rights
Clean IP out of a federal award is mostly an engineering discipline problem: bounded scope, documented work, and deliverables designed on purpose. Projects House builds the hardware, firmware, and documentation behind federally funded programs and keeps the record straight enough that ownership is never in question. Tell us about your project through the contact form and we will help you plan the technical work so the rights follow it.