Verification note (checked 2026-07-17): the agency-by-agency instrument split described below (which SBIR/STTR agencies typically use contracts versus grants or cooperative agreements) converges across multiple independent government-contracts and SBIR-consulting sources, and the SBIR-specific data-rights clause citation (DFARS 252.227-7018) and its 20-year protection period were checked directly against Acquisition.gov and corroborating law-firm client alerts. Individual solicitations can and do vary by year and by specific program component — confirm the actual instrument type from the funding opportunity announcement or draft award document itself, not from agency reputation alone, before an applicant or subcontracting university relies on it for planning.
SBIR awards are not all the same kind of document
Researchers and research administrators often talk about “getting an SBIR grant,” but that phrase is only sometimes literally accurate. The SBIR program‘s own governing statute and the SBA’s government-wide SBIR/STTR Policy Directive allow a participating agency to fund a Phase I or Phase II award as a grant, a cooperative agreement, or a procurement contract — and which of those three an applicant actually receives depends heavily on which of the eleven SBIR agencies is making the award, not on anything the applicant chooses. For a small business, the practical difference shows up in invoicing, reporting, deliverable acceptance, and intellectual-property terms. For a university that later licenses the underlying technology, or that sits underneath the award as an STTR partner or subcontractor, the difference shows up in which compliance regime — the Uniform Guidance (2 CFR 200) or the Federal Acquisition Regulation (FAR) — actually governs the money.
This page focuses specifically on that instrument-type question within SBIR/STTR itself. For the general legal test that separates a grant from a contract, see CASRAI’s Grant vs. Contract vs. Cooperative Agreement comparison; for what changes administratively once an award of any kind is a contract, including the FAR flow-down and data-rights mechanics referenced throughout this page, see Federal Contracts vs. Grants for University Research, which covers SBIR Phase III’s sole-source contract authority in detail. This page instead asks: within Phase I and Phase II specifically, why does the instrument type vary by agency, and what does an applicant or a university subcontractor need to do differently when it lands as a contract?
Why the instrument type tracks the agency’s mission, not the SBIR program itself
The underlying legal test is the same one that governs any federal award: the Federal Grant and Cooperative Agreement Act of 1977 (31 U.S.C. §§ 6303–6305) asks whether the agency’s principal purpose is acquiring a good or service for its own direct use, or providing assistance to carry out a public purpose with no direct benefit flowing back to the government. SBIR itself doesn’t override that test — each participating agency applies it to its own SBIR topics, and the outcome tends to track the agency’s underlying mission:
- Agencies that fund open-ended research and development — most notably NIH (through its Seed program) and NSF (through America’s Seed Fund) — structure the large majority of their SBIR Phase I and Phase II awards as grants. A biomedical or basic-research SBIR topic looks, to the funding agency, like assistance toward a public research purpose, not a deliverable the agency itself is acquiring.
- Agencies that need a specific deliverable for their own operational or mission use — most notably the Department of Defense, and also NASA and the Department of Homeland Security for many of their topics — structure a large share of their SBIR Phase I and Phase II awards as procurement contracts instead. A DoD SBIR topic soliciting a defined prototype, capability demonstration, or piece of software the service intends to use directly reads as acquisition under the 1977 Act’s test, the same reasoning that puts DoD’s broader R&D contracting (see CASRAI’s federal contracts vs. grants guide) on the FAR side of the line rather than the Uniform Guidance side.
- Other agencies mix instrument types by topic or component. DOE and USDA’s NIFA SBIR programs, for example, more commonly use grants, but this is a general tendency rather than a fixed rule enforced program-wide — a specific solicitation can depart from the agency’s typical pattern.
The consequence for an applicant: two companies can each win an “SBIR Phase I award” in the same fiscal year, one from NIH and one from DoD, and be operating under entirely different rulebooks — one under 2 CFR 200’s assistance framework, the other under Title 48’s FAR — despite both having gone through a recognizably similar SBIR proposal and review process.
What actually changes when an SBIR award is a contract
The differences aren’t cosmetic. A company (or a university sitting underneath one as an STTR partner or subcontractor) that expects grant-style administration and receives a contract instead will find several things work differently:
- Payment structure. SBIR grants are typically cost-reimbursement instruments: the recipient draws down funds against actual allowable costs incurred, consistent with 2 CFR 200 Subpart E cost principles. SBIR contracts are frequently structured as firm-fixed-price awards tied to specific milestones or deliverables in a statement of work — payment follows delivery and government acceptance of a defined output, not incurred cost, which changes both cash-flow timing and the internal accounting a small business needs to track.
- Reporting cadence and content. A grant’s progress-report cycle is generally lighter and more narrative. A contract carries formal deliverable-acceptance procedures under the FAR’s Inspection and Acceptance and Changes clauses, and missing a deliverable is a performance issue under the contract’s default-and-termination provisions rather than a matter the program officer works through informally.
- Who negotiates the terms. Grant terms and conditions are largely standardized and published with the funding opportunity. A contract’s statement of work, delivery schedule, pricing, and specific FAR/DFARS clause set are individually negotiated before award, and any change afterward goes through a formal contract modification rather than a prior-approval request.
- Which office should be involved. A university encountering an SBIR-related contract — as an STTR research-institution partner, or as a subcontractor to a small business’s Phase I/II contract — is better served routing it through contracts/legal expertise rather than assuming the sponsored-programs workflow built around grant terms will cover it, the same distinction CASRAI’s federal contracts vs. grants guide covers for federal awards generally.
One thing that does not change: cost allowability itself. As with any FAR-governed contract with an educational institution or small business, FAR Subpart 31.3 points back to 2 CFR 200 Subpart E for determining which costs are allowable — an SBIR contract doesn’t require relearning cost allowability from scratch, even though the surrounding administrative framework (deliverables, acceptance, disputes) is entirely different from a grant’s.
Intellectual property and data rights: the sharpest divergence
Patent rights follow the same basic path regardless of instrument type: the Bayh-Dole Act framework for federally funded inventions applies to SBIR/STTR awards whether they’re structured as grants, cooperative agreements, or contracts. What diverges sharply is technical data and computer software rights — and here, SBIR/STTR contracts carry a dedicated rights structure that is more protective of the small business than the general FAR data-rights framework applied to ordinary procurement contracts.
For DoD SBIR/STTR contracts specifically, the governing clause is DFARS 252.227-7018 (“Rights in Noncommercial Technical Data and Computer Software — Small Business Innovation Research Program”), not the general DFARS 252.227-7013 clause used on ordinary defense procurement contracts. Its central feature is the SBIR/STTR data protection period: the government’s rights in data and software the small business generates under the award are limited for a period running from the date the underlying SBIR/STTR funding agreement was awarded. A DoD rule finalized in the DFARS made that protection period a single, non-extendable 20 years from the award date (effective for contracts and subcontracts awarded on or after January 17, 2025), replacing an earlier, shorter period that could be extended by follow-on SBIR awards. After the protection period expires, the government’s rights convert not to full Unlimited Rights but to perpetual Government Purpose Rights — the government and other federal contractors working on the government’s behalf may use the data for government purposes, but the company retains the ability to restrict commercial use by third parties. Non-DoD SBIR/STTR agencies apply an equivalent SBIR data-rights protection under their own acquisition regulations, per the SBA’s government-wide Policy Directive, even though DFARS 252.227-7018 itself is DoD-specific language.
None of this vocabulary — protection periods, government purpose rights, data-rights markings — exists in a standard SBIR grant’s terms and conditions. A grant leaves data handling to funder open-science and data-management-plan policy; a contract specifies, clause by clause, exactly what the government can and cannot do with the data and software the award produces. For a university evaluating whether to license the underlying technology from an SBIR-funded spinout, or serving as an STTR partner institution, understanding which instrument type funded the work — and therefore which data-rights clause set applies — matters directly to what the university itself can promise a future licensee about freedom to use associated technical data.
What this means for a university subcontractor or STTR partner
- Confirm the instrument type from the actual award document, not from which agency issued the solicitation in general — a specific DoD topic can still be a grant, and a specific NIH topic can, less commonly, be structured as a contract or cooperative agreement.
- If it’s a contract, expect FAR/DFARS flow-down obligations as a subcontractor, reviewed clause-by-clause rather than assumed from a standard subaward template — see CASRAI’s federal contracts vs. grants guide for how flow-down review actually works.
- Route contract-instrument SBIR/STTR subawards to contracts or legal staff early, particularly for the data-rights clause set, rather than through a purely grant-oriented sponsored-programs intake process.
- Track invention reporting the same way regardless of instrument type. Whether the underlying award is a grant or a contract, Bayh-Dole invention-disclosure and iEdison reporting obligations still apply where the university itself is a recipient or subcontractor with intellectual-property rights at stake — see CASRAI’s iEdison guide.
- Don’t assume Phase III follows the same instrument type as Phase I/II. Phase III commercialization work is frequently a separate, sole-source contract under 15 U.S.C. § 638(r)(4) even when the originating Phase I/II award was a grant — covered in detail in the federal contracts vs. grants guide linked above.
Frequently asked questions
Is an SBIR award a grant or a contract?
It depends on the agency and often the specific topic. Some agencies — most notably NIH and NSF — issue the large majority of their SBIR/STTR Phase I and Phase II awards as grants. Others — most notably the Department of Defense, and often NASA and DHS — issue a large share of theirs as procurement contracts. Confirm the instrument type from the actual funding opportunity or draft award document rather than assuming based on agency reputation alone.
Does the funding instrument type affect eligibility to apply for Phase II?
No. Whether a completed Phase I was structured as a grant or a contract does not itself affect eligibility to compete for Phase II — the phase-eligibility rules turn on having completed a qualifying Phase I project, not on which instrument type funded it.
Why does DoD use contracts for SBIR while NIH mostly uses grants?
Under the Federal Grant and Cooperative Agreement Act of 1977, the instrument follows whether the agency is acquiring a deliverable for its own direct use (a contract) or providing assistance toward a public research purpose with no direct government benefit (a grant). DoD SBIR topics frequently solicit a specific prototype or capability the service intends to use directly, which reads as acquisition; NIH and NSF SBIR topics more often fund open-ended research and development, which reads as assistance.
Do SBIR data rights work the same way on a grant as on a contract?
No. Data and software rights terminology — protection periods, government purpose rights, limited rights — comes from the FAR/DFARS contract framework and the SBIR/STTR Policy Directive’s data-rights provisions; it does not appear in a standard SBIR grant’s terms and conditions, which instead leave data handling to the funder’s open-science and data-management-plan policies.
Can a university be the prime recipient of an SBIR contract?
No. Regardless of instrument type, the small business is always the prime SBIR/STTR awardee. A university can only participate as a subcontractor, or — under STTR specifically — as the required partnering research institution, receiving a subaward or subcontract from the small business rather than the award directly from the federal agency.
Related CASRAI resources
For SBIR/STTR program structure, eligibility, and the three-phase model, see the SBIR dictionary entry. For Phase II specifics, see the SBIR Phase II entry. For the general grant-vs-contract legal test, see Grant vs. Contract vs. Cooperative Agreement. For what changes administratively once any federal award is a contract — FAR flow-down, cost allowability, and Phase III sole-source authority — see Federal Contracts vs. Grants for University Research. For invention reporting obligations that apply regardless of instrument type, see iEdison: Invention Reporting and Utilization Reports. For SBIR/STTR’s current statutory authorization status, see SBIR/STTR Reauthorization. For the broader picture, see the Technology Transfer & Innovation pillar.
