The SBIR Phase II Milestone Table That Actually Gets You Paid

Most rejected Phase II proposals have a strong technical section and a milestone table that silently kills them. The table is where a reviewer learns whether you understand that a proposal becomes a contract.

Here is the structure, taken from real won proposals, not theory.

The five columns, every row

If a row is missing the dollar amount, you have told the contracting officer you do not know how billing works. If a row is missing an acceptance criterion, you have told them there is no way to know when to pay you. Both make the contracting officer ask the wrong question about you: can these people manage an award?

Make a report the accepted artifact

The report is what gets accepted, archived, forwarded, cited, and paid against. A prototype can disappear into a lab; a report cannot. So even when the milestone is a test campaign or a hardware build, make the engineering report the artifact acceptance hangs on: "Phase 2 Hover Flight Validation Test Report," "Capital-Flow Validation Report," "Final Report and Transition Roadmap." Some topics also require the hardware itself as a deliverable. Deliver both; let the report be the thing the Government accepts against.

A useful real-world detail: milestones often double as the required quarterly reports. State that explicitly ("this constitutes a quarterly report") and you have just made one piece of work satisfy two obligations.

Acceptance: write the sentence the contracting officer needs

Vague: "Successful completion of flight testing."

Fundable: "The Government accepts the milestone upon delivery of the Phase 2 Hover Flight Validation Test Report demonstrating stability within the stated tolerance."

The difference is that the second sentence can be checked, accepted, and paid against without a meeting. Phrase every acceptance criterion as the Government accepts [named artifact] demonstrating [observable threshold]. "Working demonstration on the configured environment" beats "successful integration" for the same reason: one is observable, the other is an opinion.

The payment shape that does not spook reviewers

Lay the payments out and a pattern appears across winning proposals:

M1  kickoff / requirements report      small      $50,000
M2  engineering review / test plan     small      $50,000
M3  major work block                   heavy      $350,000
M4  major work block                   heavy      $350,000
M5  major work block                   heavy      $350,000
M6  major work block                   heavy      $300,000
M7  final report / transition roadmap  small      $50,000
                                                 ──────────
                                                 $1,500,000

Both ends are light. A small kickoff (a requirements and roadmap report), the bulk of the budget in the middle where the actual work happens, and a small final wrap-up report. The part that matters most is that the first milestone is small: front-loading payment reads as risk to a reviewer. A small final report milestone is completely normal and appears in real wins. If anyone tells you the final milestone must be large, they are guessing; the won proposals say otherwise. One honest caveat: this is a strong DoD pattern, not a universal law. NIH, NSF, and DOE Phase II payment structures differ. Confirm the shape against your component's instructions.

Two arithmetic rules that are not optional:

• The sum equals the ceiling, within a few dollars. The government dislikes cents and dislikes leaving ceiling unaccounted. Land it clean.
• No make-work. Do not pad with tiny obvious filler milestones to reach the number. A reviewer who sees "synthetic test data preparation: $12,000" sees a team reaching.

Reconcile the schedule and the cost volume

The milestone table in the work plan and the per-milestone allocation in the cost volume must show the same totals. A mismatch between them is the single fastest way for a contracting officer to lose confidence, because it is the one error that takes no domain knowledge to spot. Build the table once, reference it everywhere.

The thirty-second check

Before you submit, count: does every milestone row have a dollar amount? Does every row have a "the Government accepts X" sentence? Does the sum hit the ceiling with no cents? Is M1 the small one? Four questions. The free Reviewer Scorecard runs them, and the open-source linter enforces them deterministically so it is not on your memory at 2am the night before the deadline.

Get the milestone table right and you have removed the most common silent cause of a Phase II rejection. Back to the main playbook.