The Navy SBIR proposal requirements published for the 2020.1 cycle illustrate how a public-sector innovation program can structure early technology development around both feasibility and transition to use. For industrial automation companies, system integrators, and engineering teams pursuing defense-related research, the instructions are a useful historical example of how proposal compliance, prototype milestones, and commercialization planning can fit together. These rules applied to the 2020.1 cycle and should not be treated as current submission guidance.
Navy SBIR proposal requirements depended on the topic track
The Department of the Navy (DON) separated its 2020.1 solicitations into three categories: Accelerated Delivery and Acquisition of Prototype Technologies (ADAPT), standard topics, and a Direct to Phase II topic. The instructions covered ADAPT topics N201-X01 and N201-X02 and standard topics N201-001 through N201-087. Each track had its own submission requirements; the document did not provide the Direct to Phase II instructions in the sections reproduced here.
This distinction mattered because the proposal format, Phase I structure, and funding limits were not interchangeable. A proposer first needed to identify the applicable topic and follow its corresponding instructions, alongside the broader Department of Defense SBIR/STTR announcement.
ADAPT: a shorter path focused on rapid prototyping
ADAPT was designed to address high-priority Navy challenges through a distinctive award structure intended to accelerate prototype delivery. Its Phase I technical volume was limited to five pages, and the award consisted of a Phase I Base only, with no Phase I Option. The Base could not exceed $200,000 and had a maximum performance period of four months. Discretionary Technical and Business Assistance (TABA) was not permitted in Phase I.
Because ADAPT topics covered multiple Focus Areas, applicants had to select a primary Focus Area and identify its number in the proposal title. Secondary Focus Areas could also be included. The Navy provided a topic-specific template to help applicants organize the technical volume and address feasibility within the compressed format.
The ADAPT structure continued beyond Phase I through a competitive, milestone-based Phase II process:
- Round I: Prototype demonstration of viability, with a maximum firm-fixed-price amount of $500,000 and a performance period of up to six months.
- Round II: Pilot testing in an operational environment, with a maximum amount of $1 million and a performance period of up to nine months.
- Round III: Further operational testing in multiple user scenarios, if needed. Any SBIR funding was subject to availability, capped at $1.5 million, and required a 1:1 match from non-SBIR government or private funds.
Movement from one round to the next depended on meeting defined milestones. In practical terms, the staged structure linked early feasibility work to prototype demonstration and progressively more operational testing, rather than treating Phase II as a single undifferentiated development period.
Standard topics: more room for technical detail and an option
Standard-topic applicants had a technical volume limit of ten pages. Unlike ADAPT, their Phase I proposal had to include an Option that advanced the effort toward Phase II and helped bridge the period between the feasibility study and prototype work. The Phase I Base could not exceed $140,000, while the Option could not exceed $100,000. Each period was limited to six months, and the combined Phase I amount, excluding TABA, could not exceed $240,000.
The instructions recommended clearly separating Base and Option tasks, costs, and periods of performance. Option work was typically intended for exercise upon selection for Phase II, so it should support a rapid transition from feasibility into prototype development. This is a useful planning principle for technology proposals generally: connect each funded task to the next decision point, rather than presenting disconnected research activities.
Technical merit, cost detail, and submission compliance
For both tracks, Phase I proposals were expected to address the feasibility of a solution to the selected topic. The Navy stated that technical merit was the most important evaluation factor, followed by the qualifications of key personnel and commercialization potential, which were of equal importance. Proposals that exceeded the applicable cost limits could be rejected without evaluation.
Applicants also had to follow precise formatting and supporting-document rules. Technical volumes required single-column, single-spaced text on standard 8.5-by-11-inch pages, one-inch margins, and a minimum 10-point font, subject to limited exceptions for items such as references or text embedded in figures. For standard topics, the technical volume also had to include the Phase I Option within the ten-page limit.
Cost submissions required enough detail to explain subcontractor, material, and travel expenses. Material costs needed itemized listings and per-item costs; travel information needed to state its purpose, location, duration, number of trips, and personnel. The instructions also limited what could be submitted in the optional Supporting Documents Volume. Including unapproved material, such as resumes or technical reports, could make a proposal noncompliant.
From feasibility to operational relevance
The program’s deliverables and transition provisions reinforced the connection between technical work and adoption. ADAPT Phase I deliverables included kickoff briefing material, a progress report, and a final report. Awardees seeking consideration for competitive Phase II selection also had to provide a Phase II proposal and feasibility briefing materials. Phase II decisions considered these materials alongside the final report.
The instructions also highlighted practical schedule risks. Human-subject research, animal testing, or recombinant DNA work could require approvals that delayed a short Phase I effort. Government-furnished equipment was discouraged because obtaining approval could take time. For topics involving classified work or export-control restrictions, proposers were advised to explain how research activities could be separated from restricted work.
Commercialization and transition planning were part of the program design, not an afterthought. ADAPT Phase I awardees could participate in a business accelerator focused on areas including market identification and transition planning. Standard-topic applicants could request TABA, subject to specified limits and documentation requirements.
Conclusion: design the proposal around the next milestone
The 2020.1 Navy SBIR instructions show why defense technology proposals must combine a credible technical approach with disciplined compliance and a clear path forward. ADAPT emphasized a compact feasibility effort and milestone-based prototype progression; standard topics allowed a longer technical volume and required an option structured to support Phase II transition. For industrial automation and engineering teams, the broader lesson is to align scope, budget, schedule, evidence, and operational objectives with the solicitation’s specific track. Because these instructions are historical, applicants should consult the current solicitation and agency guidance before preparing any proposal.