What is a go / no-go decision on a public contract?
A go / no-go is the decision, made early, to respond or not to a public contract, based on a quick review of the tender documents (the full set of papers issued for the contract). It is settled before any drafting effort begins, on substantive grounds: does the need match what the company knows how to do, are the conditions workable, is the opportunity worth mobilizing for. It is a decision of discipline, not enthusiasm.
Responding to everything spreads effort thin and lowers the quality of every response; a clear-eyed go / no-go concentrates strength on contracts that are actually winnable.
What criteria should guide the decision to respond or not?
The decision to respond rests on a few substantive questions, asked in order. The table links each question to the signal it gives.
| Question | "Go" signal | "No-go" signal |
|---|---|---|
| Is the need in our line of business? | a clear match with the technical specification | a peripheral need or one outside our expertise |
| Are the conditions workable? | realistic deadlines, resources, contract terms | unreachable constraints |
| Are we credible on the criteria? | evidence and references aligned | no evidence on a heavily weighted criterion |
| Is the effort justified? | enough time available before the deadline | a file out of reach within the timeframe |
| Is the opportunity worth it? | strategic interest and feasibility | mobilization with no real prospect |
A single clear "no-go" on a disqualifying question, such as a missing capacity required on pain of rejection, is enough to walk away, even if everything else looks favorable.
Why read the award criteria before deciding?
Reading the award criteria before deciding lets you measure your credibility exactly where the contract will be decided. Award criteria and their weighting are typically announced in advance in the tender documents (in the United States, under the Federal Acquisition Regulation; in the United Kingdom, under the Procurement Act 2023). Checking your evidence against this grid at the go / no-go stage avoids discovering, after drafting, that you are weak on the heaviest criterion.
A go / no-go that ignores the weighting judges the opportunity on instinct; one that reads it judges the opportunity where it will actually be scored. At this stage, the go / no-go is only a quick check: am I credible, or not, where the contract carries weight. The detailed measurement of the gap on each weighted criterion is a separate analysis, covered in how to assess your chances of winning a public contract; the go / no-go also weighs effort, risk, and strategic interest.
When is a quick decision enough, and when do you need a formal analysis?
For a familiar contract, close to opportunities already won, a quick decision based on experience is enough. For a new, large, or high-stakes contract, a formal analysis, written and shared among the people involved, protects against a poorly weighed commitment. Generic AI can help summarize a set of tender documents for a first read; matching requirements to the company's evidence is what really illuminates credibility. The line is the stakes: the bigger the opportunity, the more the decision deserves to be documented.
On the Optivalue.ai platform, which publishes this site, analyzing a file requires 0 training, 0 IT project, and 0 data used outside the customer's own environment, which makes it possible to inform a go / no-go decision as soon as the tender documents are downloaded.
Mistakes that skew a go / no-go decision
- Deciding without reading the tender rules: the criteria and their weight are the first input into a go / no-go decision.
- Confusing interest with credibility: being interested in an opportunity does not replace the evidence expected on the criteria.
- Ignoring a disqualifying requirement: a missing capacity required on pain of rejection dooms the bid, whatever its other strengths.
- Underestimating the effort: a file out of reach within the deadline produces a rushed, poorly scored bid.
- Not documenting the decision: an unwritten go / no-go gets relitigated at every disagreement, with no record of the reasoning.
Frequently asked questions
When should you make the go / no-go decision?
As soon as you download the tender documents, after a quick read of the tender rules and the technical specification. The earlier the decision, the less effort is lost if you walk away.
Is a no-go a failure?
No. Walking away from a low-chance opportunity frees up time for contracts where the company is credible. No-go discipline improves the quality of the responses that actually get submitted.
Who should take part in the decision?
The people who know the need, the capabilities, and the resources available. A shared go / no-go decision commits the people who will produce and deliver the response.
Does the go / no-go decision depend on expected competition?
The level of competition is one factor among others, but it is hard to estimate in advance. Credibility on the announced criteria remains the most reliable signal for the decision.
Decide on a real contract using your own documents
Bring a real set of tender documents. You will see requirement-extraction coverage, sources cited on every page, and a gap analysis of your response, not a prepared demo.
Written by the compliance and presales team at Optivalue.ai. Last reviewed: 5 September 2026. This page does not constitute legal advice.
Sources cited
- Public procurement rules on the publication and weighting of award criteria (in the United States, the Federal Acquisition Regulation; in the United Kingdom, the Procurement Act 2023); the applicable rule in each market should be verified.