How to read an SBIR debrief: reviewer comments decoded

The debrief is an underused asset

Most firms who lose an SBIR take the loss, maybe read the debrief once, and move on. That is a mistake. The debrief is the only direct signal the firm receives from the reviewers about why the proposal did not win, and the same reviewers often read the firm's next proposal. A careful read of the debrief — across multiple dimensions — surfaces the specific weaknesses that need to be fixed before the next submission, and reading well requires understanding the specific language conventions reviewers use.

1. Step 1 — Request the debrief: Submit the debrief request within 5 days of award notification for DoD. Many agencies have tight windows — don't miss it.
2. Step 2 — Map scores to criteria: Each reviewer comment maps to a scored criterion (technical, commercialization, team, price). Identify which criterion drove the score gap.
3. Step 3 — Separate opinion from fact: "Unclear methodology" is fixable. "Not aligned to our priorities" means you picked the wrong topic, not that you wrote poorly.
4. Step 4 — Prioritize the resubmit: Fix the criterion with the largest gap first. A 2.5 vs 5.0 on commercialization is more urgent than a 3.5 vs 4.0 on technical merit.
5. Step 5 — Document lessons: Build a debrief log across all submissions. Patterns reveal systemic weaknesses in your proposals, not just one-off reviewer opinions.

The three outcome categories

Outcome	What it means	What to do
Selected	Funded. Review is positive.	Read the debrief anyway — it identifies strengths to repeat and weaknesses to fix in Phase II.
Selectable, not selected	Would have been funded if more money were available. Proposal was above the line but ran out of budget.	Near-miss. Resubmit with modest revisions. High probability of winning next cycle.
Not selectable	Did not meet the scoring threshold. Specific weaknesses identified.	Substantive revision required. Address the specific weaknesses before resubmission.
Non-compliant	Failed a formal requirement (page count, missing section, late submission).	Compliance issue, not a technical issue. Fix the compliance and resubmit.

"Selectable, not selected" — read it as a near-win

"Selectable but not selected" is a specific status. It means the proposal scored above the agency's funding threshold but not enough proposals scored above it to exceed the budget. In practical terms, you wrote a winning proposal but another proposal scored higher in the same topic. Most "selectable not selected" proposals win on resubmission if the firm makes modest improvements.

The correct read: you have a proposal that is 90% of the way there. Identify the 10% — usually a specific weakness flagged in the debrief — and fix it. Resubmit to the same agency or a similar topic at another agency. Rate of conversion from "selectable not selected" to "selected" on the next cycle is often 40-60%.

Reviewer language — what it actually means

Reviewers write in a consistent style that rewards careful reading:

• "Adequate" = weak. Reviewers use "adequate" to describe sections that meet the bar but do not score strongly. "The technical approach is adequate" means you lost points there.
• "The proposal does not clearly address..." = missing. When a reviewer says something is not addressed, they usually could not find it. Sometimes it was there but buried; that is still a reviewer-attention failure.
• "Could benefit from..." = should have had. A polite way to say a section was incomplete.
• "Ambitious" = skeptical. When applied to a schedule, budget, or milestone, "ambitious" usually means the reviewer thinks it is unrealistic.
• "Not well-connected to the topic" = off-topic. A serious criticism. The proposal was written for a different problem than the topic asked.
• "The team is well-qualified" = the only clearly positive note. Team language is usually direct; ambiguity there is rare.

Scoring patterns to watch

Debriefs often include scores on the evaluation criteria dimensions (technical, commercialization, team, cost). Patterns:

How to request a debrief

At most agencies, debriefs are available on request after declination notification. Submit the request within 30 days (some agencies have strict windows). Debriefs are usually written summaries, sometimes with optional phone debrief. Ask for both. The phone debrief sometimes surfaces context that the written version omits.

The revision playbook

Based on debrief feedback, a typical revision targets 3-5 specific changes:

1. Address the specific weakness named. Rewrite the weak section, do not just polish it.
2. Strengthen commercialization if flagged. Add customer conversations, letters of support, specific dollar projections.
3. Clarify win themes. If scores were middling, the proposal did not stand out. Sharpen and repeat the win themes.
4. Tighten the SOW. Many "ambitious" critiques trace to a SOW that over-promised. Reduce scope where appropriate.
5. Update the bio and past performance. Any new delivery, publication, or customer reference gets added.

Resubmitting — same agency or pivot?

A "selectable not selected" proposal is usually worth resubmitting to the same agency. A "not selectable" proposal with scores near the threshold can be revised for the same agency. A "not selectable" proposal with low scores should be rewritten for a different topic at a different agency. Submitting a poorly reviewed proposal to the same agency twice without substantive revision hurts the firm's standing.

Frequently asked questions