Go/No-Go Decision

A go/no-go decision is the formal management checkpoint, typically occurring at one or more points in the capture lifecycle and again at RFP release, at which a government contractor's leadership team evaluates the opportunity's qualification criteria, competitive position, and resource availability to decide whether to commit or continue investing pursuit resources.

What is a Go/No-Go Decision?

The go/no-go decision is the operational mechanism that enforces proposal investment discipline. Most firms have multiple go/no-go checkpoints: an initial gate when an opportunity is first identified (decide whether to begin intelligence gathering), a mid-capture gate (decide whether to commit full capture resources), and a final gate at RFP release (decide whether to submit a proposal). Each gate uses an increasingly detailed assessment as more information is available.

The criteria evaluated at a go/no-go checkpoint overlap with opportunity qualification but are applied with greater rigor as the opportunity matures. Key questions at RFP release include: Has the win strategy held up against the actual solicitation requirements? Is the pricing target achievable? Are teaming arrangements finalized? Is the proposal team resourced and available? Is the evaluation approach in Section M consistent with what was expected from customer engagement?

An honest go/no-go process produces "no go" decisions a meaningful percentage of the time. A firm that never says no go either has a highly selective opportunity identification process upstream or lacks the discipline to override BD enthusiasm with strategic judgment. The cost of writing a non-competitive proposal is not just the proposal writing cost, it is also the opportunity cost of resources that could have strengthened a winnable pursuit.

The go/no-go decision framework also structures the accountability conversation: after a loss, comparing the original go/no-go criteria against the outcome provides invaluable lessons for future decisions. See how to build a go/no-go decision framework for a practical implementation guide.

Why Go/No-Go Decisions Matter for Government Contractors

Win rate improvement is largely a function of bid discipline. Contractors who submit proposals on every RFP they receive, regardless of competitive position, waste resources, demoralize proposal teams, and obscure the signal about where the firm actually wins. A firm with 20% win rate that submits 50 proposals per year wastes the BD cost of 40 losing proposals. Applying go/no-go discipline to shift to 25 proposals at 40% win rate produces the same revenue with half the proposal cost.

Example

An IT services firm receives an RFP for a $7M SDVOSB set-aside contract at NIH. The go/no-go gate reveals: good technical fit (the firm has three similar contracts), SDVOSB certification confirmed, but only one relevant NIH past performance reference (weak customer relationship), a perceived incumbent advantage (the incumbent has eight ratings on PPIRS for this exact program), and a pricing requirement that yields less than 8% margin. The team votes no go. The BD rep redirects to a different NIH set-aside where the firm has a strong program manager relationship and no known incumbent.

Frequently Asked Questions

Who participates in a go/no-go decision meeting?

The meeting typically includes: the capture manager (presenting the opportunity and strategy), a senior BD or executive sponsor (advocating for the business case), the proposal manager (assessing resource availability and timeline), a pricing lead (confirming the pricing strategy), a contracts specialist (confirming vehicle access and compliance requirements), and a technical subject matter expert (assessing capability fit). Leadership, CEO, VP of BD, or a bid review board, makes the final call.

What happens to opportunities that receive a no-go decision?

A no-go decision means the firm declines to submit a proposal on this solicitation. The opportunity is removed from active pursuit but may be retained in the pipeline for future monitoring, particularly if the reason for no go was timing, teaming, or resource availability rather than a fundamental strategic misfit. If the contract recompetes in three years, the conditions that produced a no go may have changed. Tracking why each no-go decision was made creates a valuable historical record for future recompetes.

Can a go decision be reversed after the RFP is released?

Yes. A go decision at an earlier gate is not irrevocable. If the RFP reveals conditions that fundamentally change the competitive assessment, unexpected evaluation criteria, a pricing requirement that cannot be met, a scope that requires capabilities the firm does not have, or a timeline that cannot be met, the firm should revisit the decision with a late-stage no-go call. Walking away after committing initial proposal resources is better than submitting a non-competitive proposal.

How does the go/no-go decision differ from the bid/no-bid decision?

In many organizations the terms are used interchangeably. When distinguished, "go/no-go" applies to earlier stage capture gates (should we invest in capture?), while "bid/no-bid" applies specifically to the final gate at RFP release (should we submit a proposal?). The final gate has the highest stakes because at that point the firm has already invested capture resources and faces a discrete decision about whether to spend the additional proposal writing cost.