The Navy SBIR proposal requirements for the Department of the Navy’s (DON) 20.2 solicitation set out a detailed path from technical feasibility to prototype development and eventual transition. For small businesses developing technologies for Navy and Marine Corps needs, understanding those rules is as important as presenting a strong technical idea. The instructions covered topics N202-088 through N202-147 and applied specifically to that solicitation cycle; they should not be treated as current submission guidance for later announcements.
Start with compliance, not just the technical concept
The DON directed proposers to follow the Department of Defense SBIR/STTR Broad Agency Announcement (BAA), with DON-specific instructions taking precedence where they differed. A proposal had to meet the required submission rules or risk being deemed noncompliant and rejected. That makes administrative review an essential part of proposal development: technical merit cannot compensate for a missed mandatory requirement.
For Phase I, the Technical Proposal, or Volume 2, had a maximum length of 10 pages, regardless of page content. It also had to use a single-column, single-spaced format on standard 8.5-by-11-inch paper, with one-inch margins and a font of at least 10 points. Headers, footers, references, and text embedded in figures or tables could use smaller type, although the DON cautioned that evaluators might not be able to read it.
The technical volume also had to address the evaluation criteria in the DoD BAA and include both the Phase I Base work and an Option that advanced the effort toward Phase II. Proposers were expected to distinguish the tasks for each. The option was intended to help bridge the interval between Phase I feasibility work and a potential Phase II prototype effort.
Build the Phase I plan around feasibility and transition
Phase I was intended to establish whether a proposed solution was feasible—not simply describe a future product. The DON recommended using its topic-specific proposal template and suggested including estimated travel costs for a one-day meeting at the sponsoring Systems Command (SYSCOM) facility.
A useful technical plan therefore needed to connect the proposed work to evidence of feasibility, explain how technical risks would be examined, and outline performance goals and milestones for the next phase. The solicitation’s example topics illustrate the range of work involved, from navigation and sensing concepts to acoustic devices and advanced materials. The shared proposal challenge was to explain how the concept could be assessed and developed into a useful capability.
For projects involving fundamental research, proposers had to identify and describe that work with enough specificity to show why it qualified. Merely labeling work as fundamental research did not establish an exclusion from prior public-disclosure approval requirements. Any fundamental research for which the proposer requested that treatment had to be uploaded as a separate document in the Supporting Documents Volume.
Control costs and document them clearly
Under the 20.2 instructions, the Phase I Base request could not exceed $140,000, and the Option could not exceed $100,000. The Base and Option costs had to be separated and clearly identified in both the Proposal Cover Sheet (Volume 1) and Cost Volume (Volume 3). Each period of performance was exactly six months. The maximum Phase I proposal or award amount, including options and excluding Technical and Business Assistance (TABA), was $240,000.
Cost explanations needed enough detail for reviewers and contracting staff to understand what the work would require. In the online Volume 3 explanatory field, proposers had to itemize subcontractor, material, and travel costs. Subcontractor costs needed detail comparable to the prime contractor’s costs; material entries needed to list items and unit costs; and travel explanations needed to state purpose, trip count, destination, duration, and number of travelers.
The instructions also noted that the DON typically used firm-fixed-price contracts or small purchase agreements for Phase I, and that Basic Ordering Agreements could be used. These are solicitation-specific award provisions, so firms should verify the applicable terms in the announcement for which they are preparing a proposal.
Use supporting documents selectively
Volume 5 was optional and could hold specified supporting materials, such as letters of support, additional cost information, technical-data-rights assertions, and disclosures related to foreign citizens or prior support. However, the DON stated that it would not use information in Volume 5 during evaluation. The instructions warned that adding unlisted material—such as resumes, test data, technical reports, or publications—could make a proposal noncompliant. Even firms submitting no Volume 5 documents still had to answer the required yes-or-no question in the submission system.
Volume 6, covering Fraud, Waste and Abuse training certification, was not required by the DON at proposal submission. Separately, proposers needed to meet the Small Business Administration’s commercialization performance benchmarks as applied by the DON at the time of submission.
Understand TABA and its trade-offs
Firms could request discretionary Technical and Business Assistance to address technical decisions, project risks, or commercialization needs, including intellectual-property protection. For Phase I, the request could total up to $6,500, in addition to the award amount. The request had to identify the provider, its contact details, qualifications, proposed tasks, hours, rates, and total cost.
TABA could not be provided by the applicant, an affiliate, an investor, or a subcontractor or consultant already required to perform the paid research effort. The requested amount had to appear in the designated cost field, with supporting details in the explanatory material and, if needed, Volume 5. The DON also outlined a significant Phase II consideration: firms awarded TABA in a Phase II contract would not be eligible for specified DON transition assistance programs, including the SBIR Transition Program and Forum for SBIR/STTR Transition.
Plan beyond Phase I
The DON’s evaluation placed technical merit first, followed by the qualifications of key personnel and commercialization potential, which were of equal importance. Proposals exceeding the sponsoring SYSCOM’s cost limits could be rejected without evaluation. Phase II submissions were available to Phase I awardees, with the Phase I final report and transition materials helping inform assessment of prototype potential and the prospect of moving technology toward Phase III.
Phase III referred to follow-on work derived from, extending, or completing SBIR/STTR-funded work but supported by other than SBIR/STTR program funding. The DON described Phase III status as applying to qualifying follow-on or competitively awarded work, with protections for applicable SBIR/STTR technical data rights.
Practical takeaways for proposers
For the Navy SBIR 20.2 cycle, a competitive submission required both a credible technical approach and disciplined proposal management. Teams needed to verify the topic-specific rules, keep the technical volume within its limit, separate Base and Option tasks and costs, justify cost elements, and use supporting-document volumes only as instructed. Just as importantly, Phase I planning needed to show how feasibility work could lead to a prototype and a realistic transition path. For any later solicitation, use its current BAA and agency instructions rather than assuming these 20.2 rules still apply.