Blog · SBIR

Five Ways a Navy SBIR Phase I Proposal Loses, and the Fix for Each

Chris A. Grable · October 7, 2026

Navy evaluators do not rank Phase I proposals against each other. Each is scored alone against the criteria, with technical merit weighted most heavily and key personnel and commercialization potential tied behind it. That should reassure a small firm: it competes with the topic, not with the field. It also means several avoidable errors can end a proposal before its merits are fully weighed, though a sound proposal can still go unfunded. In UDC's experience, five errors come up most often.

1. The proposal breaks a format rule

Compliance is checked before merit, and a failed check ends the review. Under the current Navy Phase I instructions, the Technical Volume is rejected if it:

runs past ten pages, whatever the content;
is not single-column and single-spaced on letter-size pages with one-inch margins;
uses body text smaller than 10-point;
proposes a Base or Option period that is not exactly six months.

A Cost Volume over the caps, or one in which the small business performs less than two-thirds of the work in either the Base or the Option, is also rejected, as is any encrypted, password-protected or locked file unless the topic directs otherwise. Technical substantiation placed in the Supporting Documents volume is not considered. And since 1 October 2026 a firm may submit only one proposal per topic; if it sends more, only the latest one submitted before the deadline is evaluated. The fix: treat every rule as pass-fail and confirm it against the active instructions, because the figures move between releases.

2. It proposes a build when the topic asks for feasibility

Phase I exists to establish an idea's scientific, technical and commercial merit and feasibility. Many Navy topics ask for feasibility; some ask for a design, a concept or an initial prototype, so the topic's own Phase I paragraph sets the scope. A work plan sized for Phase II signals that the team misread the program, and it rarely fits the money. The current ceilings are $200,000 for the Base and $115,000 for the Option, a $315,000 Phase I maximum before assistance funding. FY26 Release 1 used $140,000 and $100,000, which is why a prior-cycle cap should never be carried forward. The fix: name the one key feasibility question, the risk behind it, the work that answers it and the measures that will show it succeeded.

3. Success has no number attached

An objective with no threshold gives the evaluator nothing to score. The program BAA also allows Government-approved AI tools to help evaluators with preliminary tasks such as summarizing content, while final judgments stay with Government personnel. A proposal whose point survives a summary has the advantage. The fix: write decision thresholds in the form "feasible if X performs to Y with margin Z," use headings that match the template and state each claim once.

4. Transition gets a paragraph

Commercialization potential is scored, and the evaluation of key personnel includes the ability to commercialize the results. In UDC's experience, technical teams write strong science and a thin business case. For a NAVAIR topic, UDC recommends naming the program office, platform and mission owner, the need as the topic author described it, the test environment and the funding path into Phase II and Phase III, then covering dual-use and commercial markets as the template requires. A named PMA or end user with a transition path informed by the topic author is the strongest evidence; a generic claim that the Navy needs the technology is the weakest. Letters of support count against the ten pages and earn their space only when they add a named customer.

5. Nobody spoke to the topic author

During pre-release, which has run roughly three to five weeks in recent schedules, a firm may contact the Topic Point of Contact directly with questions about the topic's requirements. Once that window closes, direct contact ends and questions move to DSIP Topic Q&A, where answers are posted for everyone and which closes two weeks before the topic does. The topic author can explain the requirement but cannot advise on a solution, so a call spent pitching wastes the one window that counts. The fix: use the call to learn what the operator or program is trying to do, what stands in the way and what a useful answer must accomplish, then write to that need.

One last point. Funding is limited and the Navy may cap the number of awards under any topic, so a sound proposal can still go unfunded. A debrief must be requested within 15 calendar days of the select or non-select notice and usually comes in writing. UDC recommends asking every time: it is the main formal source of feedback on that specific proposal.

Public sources

The paper behind this post cites these public documents, among others.

The full guide adds a seven-step compliance workflow, a page-by-page Volume 2 storyboard, a discriminators menu with the trap behind each, a pre-submission checklist, and four Author's Notes written from the evaluator's chair.

How to Write a Winning SBIR Proposal

See what is in the paper