Go / No-Go Decision

Definition — what it is

A go/no-go decision is the deliberate determination of whether to pursue a specific opportunity, made before committing the cost of estimating and proposing. It weighs the probability of winning, the fit with the firm's capabilities and strategy, the risk the project carries, the client relationship, and whether the firm has the capacity to deliver if it wins. It exists because estimating and proposal effort is expensive and finite, and pursuing the wrong work consumes the capacity that would win the right work. A go/no-go decision is not a commitment to bid low or a guarantee of winning; it is a gate that concentrates the firm's limited pursuit resources on the opportunities worth chasing, and its discipline is often the difference between a firm that wins profitable work and one that is busy losing money.

Also known as: Bid/No-Bid Decision, Pursuit Decision, Opportunity Qualification, Go/No-Go, Bid Decision

Why it matters — what it protects

The go/no-go gate is where a firm decides how to spend its scarcest resource -- estimating and pursuit capacity. Every proposal costs real money and, more importantly, the time of the estimators and managers who could be pursuing better work, and a firm that says yes to everything spreads that capacity so thin it does nothing well. The discipline of declining the wrong pursuits is what lets the firm bring its full effort to the ones it can win and profit on, which is why the no-go is often the more valuable decision.

It is the earliest and cheapest place to avoid a bad project. Some jobs are losers before a number is ever calculated -- an impossible schedule, a litigious owner, a scope outside the firm's competence, a location that strains the workforce -- and the go/no-go is where those are declined at the cost of an hour's analysis rather than discovered after award at the cost of the project's margin. A firm's worst financial outcomes are frequently jobs it should never have pursued, and the gate is where they are stopped.

It protects delivery capacity, not just pursuit capacity. Winning is only good if the firm can actually staff and execute the work, and a go decision made without honestly assessing whether the crews, supervision, and bonding capacity exist to deliver is how a firm wins itself into a default. The go/no-go must weigh delivery capacity alongside winnability, because a job won and then failed is worse than a job never pursued.

Made consistently, it is how a firm builds a coherent backlog rather than a random one. A firm that applies clear criteria -- market, size, client, risk, geography -- accumulates a backlog aligned with its strengths and strategy, while one that chases whatever appears ends up with a scattered book of work it is not built to deliver well. The go/no-go decision, aggregated across many opportunities, is the mechanism by which strategy actually shapes the work the firm takes on rather than remaining a statement on a wall.

Lifecycle — how it moves

1. Opportunity intake

   An opportunity is identified -- a solicitation, an invitation, a relationship lead -- and captured with its basic parameters. Opportunities that never get logged are decided by default, usually by whoever has time, which is the opposite of a disciplined gate.

2. Preliminary screening

   The opportunity is checked against knock-out criteria -- geography, size, market, client history -- that can eliminate it quickly. Fast elimination on clear disqualifiers preserves analysis effort for the genuinely borderline decisions.

3. Winnability assessment

   The firm assesses its realistic probability of winning given the competition, the client relationship, and the selection method. Pursuing work the firm has little chance of winning burns capacity on a lottery ticket, however attractive the project.

4. Fit and strategy assessment

   The opportunity is weighed against the firm's capabilities, strategic direction, and portfolio balance. A winnable, profitable job that pulls the firm away from its strategy or its competence can still be the wrong pursuit.

5. Risk assessment

   The project's risk is evaluated -- schedule, contract terms, owner and design quality, site conditions, financial exposure. Onerous terms, a litigious owner, or an impossible schedule are the risks that make a job a loser before it is priced.

6. Capacity assessment

   The firm honestly assesses whether it can staff, supervise, and bond the work if it wins. A go decision that ignores delivery capacity is how a firm wins itself into a default it cannot execute.

7. Decision and rationale

   A go or no-go is decided by the appropriate authority and the rationale recorded. The recorded rationale is what lets the firm learn from the decision, calibrate its criteria, and defend the allocation of pursuit resources.

8. Feedback and calibration

   Outcomes -- wins, losses, and the profitability of won work -- are fed back against the original go/no-go rationale. Without this loop the gate never learns, and the same misjudgments repeat pursuit after pursuit.

Anatomy — the data it carries

Opportunity identification

Project name, client, location, size, and market. The basic parameters that drive the initial screening and portfolio-balance view.

Client and relationship history

Prior experience with the owner, their payment history, and how they treat contractors. Often the single strongest predictor of whether a job will be profitable or painful.

Selection method

Low-bid, best-value, qualifications-based, or negotiated. Determines both winnability and how much the firm's non-price strengths can help it.

Competition assessment

Who else is likely pursuing and the firm's position against them. Shapes the realistic win probability that drives the pursuit-cost calculation.

Win probability

The firm's honest estimate of its chance of winning. The denominator of the pursuit-cost decision; inflated optimism here wastes capacity on unwinnable work.

Strategic and portfolio fit

How the opportunity aligns with the firm's direction, competence, and current backlog mix. Keeps individually attractive jobs from pulling the firm off strategy.

Contract and terms risk

Delivery method, liquidated damages, retainage, indemnity, and other flow-down risk. Onerous terms are a common reason to decline a job that otherwise looks attractive.

Schedule feasibility

Whether the required schedule is achievable with the firm's resources. An impossible schedule is a loser regardless of price.

Delivery capacity

Whether crews, supervision, and bonding capacity exist to execute if won. The check that prevents winning into a default.

Estimated pursuit cost

The cost to estimate and propose. Weighed against win probability and expected value to decide whether the pursuit is worth the effort.

Decision and authority

The go or no-go and who made it. Establishes accountability and the level at which pursuit resources are being committed.

Rationale and conditions

Why the decision was made and any conditions attached to a go. The record that enables learning, calibration, and consistency across pursuits.

Failure modes — how it breaks

Chasing everything

The firm treats every opportunity as a go and spreads its estimating capacity across too many pursuits. It brings a thin, rushed effort to all of them, wins little, and wins that little on numbers assembled under pressure -- the busiest path to unprofitable work.

Optimism bias in win probability

The firm consistently overestimates its chance of winning because saying no feels like giving up. Pursuit capacity is spent on lottery tickets, the expected value of the pursuit portfolio is negative, and the pattern repeats because the optimism is never checked against actual win rates.

Ignoring delivery capacity in the go decision

A winnable, attractive job is pursued and won without honestly assessing whether the firm can staff, supervise, and bond it. The firm wins itself into a project it cannot execute, and the default that follows is far more expensive than the pursuit ever was.

Terms and client risk waved through

The project looks good on scope and price, so onerous contract terms, a litigious owner, or a poor payment history are noted and pursued anyway. The risk that should have been a knock-out becomes the reason the job loses money, discovered only after award.

Decision by default

No one formally decides, so the opportunity is pursued because someone started estimating it, or dropped because no one picked it up. Pursuit resources are allocated by inertia rather than judgment, and the firm's strategy plays no part in what it chases.

No feedback loop

Outcomes are never compared against the go/no-go rationale, so the gate never learns. The firm repeats the same misjudgments -- the client it should have declined, the market it keeps losing in -- because nothing closes the loop between the decision and its result.

Metrics — how it is measured

Win rate by segment

Wins against pursuits, segmented by market, client, and selection type. Reveals where the firm's go decisions are sound and where its optimism is misplaced.

Hit rate on go decisions

Share of go decisions that resulted in a win. Calibrates whether the gate is selecting winnable work or chasing lottery tickets.

Pursuit cost per win

Total estimating and proposal cost divided by wins. Measures how efficiently pursuit capacity is converted into won work.

Profitability of won work

Realized margin on projects that came through the gate. Tests whether go decisions select profitable work, not just winnable work.

No-go rate

Share of opportunities declined. A very low rate signals a firm chasing everything; the no-go is a sign of discipline, not defeat.

Capacity-conflict incidence

How often won work exceeded the capacity assessed at go. Flags a gate that ignores delivery capacity and wins into overload.

The AI shift — what actually changes

Conversational

The decision stops being a gut call in a hallway and becomes something you can interrogate with data. You can ask how the firm has historically fared with this client, this market, and this selection method, what the realistic win rate is for comparable pursuits, whether current backlog leaves capacity to deliver, and which risk factors in the solicitation resemble past losers -- with each answer grounded in the firm's own history.

Generative

The assessment shifts to a reviewed draft. From the opportunity's parameters and the firm's history, a system drafts a go/no-go analysis -- winnability against comparable pursuits, client and terms risk flagged, capacity checked against current backlog, and pursuit cost weighed against expected value -- which the decision-maker uses as an evidenced starting point rather than a blank sheet.

Orchestrated

The decision stops being an isolated judgment. It is informed by the firm's actual win-rate history for similar work, the current backlog and delivery capacity, the client's payment and dispute history, and the pipeline mix, so the go/no-go reflects both winnability and deliverability and is consistent with the firm's strategy rather than made in isolation.

Autonomous

The routine motion runs without a person driving it: opportunities screened against knock-out criteria on intake, comparable win rates and client history surfaced, capacity conflicts flagged against backlog, and clear disqualifiers routed as recommended no-gos with evidence -- while humans own every actual go/no-go decision, especially the borderline and strategic ones the data cannot settle alone.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — A new opportunity has landed and you need an evidenced read before committing pursuit effort.

We have a new opportunity: a forty-million-dollar best-value healthcare renovation with this owner, in this market, due in three weeks. Give me an evidenced go/no-go read from our own history. How have we fared with this owner before on schedule, payment, and disputes; what is our realistic win rate on best-value healthcare work of this size against the likely competition; does our current backlog leave the supervision and bonding capacity to deliver this if we win; and which risk factors in the solicitation -- schedule, liquidated damages, phasing around an occupied facility -- resemble jobs that lost money for us before. Weigh the estimated pursuit cost against the expected value. Do not make the decision; give me the evidence for it.

What good output looks like: An evidenced assessment across winnability, client history, capacity, and terms risk grounded in the firm's own record, with pursuit cost weighed against expected value -- decision support, not a decision.

Follow-ups:

• Which single factor here is the strongest argument for a no-go?
• If we go, what conditions or risk mitigations should we attach to the pursuit?
• How does taking this on affect our backlog mix and delivery capacity next year?

Generative — Producing a structured go/no-go analysis to bring to the pursuit review.

Draft a structured go/no-go analysis for the pursuit review on this opportunity. Cover each factor with evidence: opportunity parameters and portfolio fit, client and relationship history, selection method and likely competition, an honest win-probability estimate benchmarked against our comparable pursuits, contract-terms and schedule risk, delivery-capacity check against current backlog and bonding, and estimated pursuit cost against expected value. For each factor, state the evidence and flag it green, yellow, or red. Conclude with the strongest arguments for go and the strongest for no-go laid side by side, and any conditions that should attach to a go. Do not render the final decision -- present the case both ways for the review to decide.

What good output looks like: A factor-by-factor go/no-go analysis with evidence and risk flags, the case argued both ways, and conditions identified -- a decision brief for the review, not a verdict.

Follow-ups:

• Which yellow factors could be turned green by a conversation with the owner before we decide?
• Compare this opportunity's profile to the last three similar jobs and their outcomes.
• Draft the no-go rationale in case that is where the review lands, for the record.

Orchestrated — Screening the pipeline so pursuit capacity goes to the right opportunities.

Screen our current pipeline of open opportunities so we allocate pursuit capacity well. For each opportunity, pull our historical win rate for that client, market, and selection type, check it against our knock-out criteria, and assess whether our current backlog and estimating capacity can support both the pursuit and the delivery if we win. Rank the opportunities by expected value -- win probability times expected margin, net of pursuit cost -- and flag any that conflict with delivery capacity we have already committed, any with a client or terms profile that resembles past losers, and any clear knock-outs we should decline now. Tell me where pursuing everything currently open would over-commit our estimating team. Do not decide any of them; prepare the allocation view.

What good output looks like: A pipeline ranked by expected value with capacity conflicts, client-risk resemblances, and clear knock-outs flagged -- an allocation view that concentrates pursuit capacity, with the decisions left to the human.

Follow-ups:

• Which two opportunities should we decline now to protect capacity for the top of the list?
• Where are we over-committing the estimating team in the next month?
• Which pursuits improve our backlog mix versus concentrate it further?

Autonomous — Standing policy for running the go/no-go gate across all incoming opportunities.

Run our go/no-go gate continuously under these rules. On intake, log every opportunity with its parameters and screen it against our knock-out criteria -- geography, size, market, client blacklist -- routing clear disqualifiers to me as recommended no-gos with the evidence. For opportunities that pass screening, surface our historical win rate for the client, market, and selection type, the client's payment and dispute history, and a capacity check against current backlog and bonding, and flag any that would over-commit delivery or estimating capacity. Maintain the feedback loop: when pursuits resolve, compare wins, losses, and won-work margin against the original rationale and surface where our win-probability estimates are systematically off. Never make a go or no-go decision yourself, never commit pursuit resources, and never decline an opportunity without my sign-off -- prepare the evidence and route every decision to me.

What good output looks like: A running gate that screens, evidences, and surfaces capacity conflicts and calibration errors as a short exception queue -- while every go/no-go decision and every commitment of pursuit resources stays a human decision.

Follow-ups:

• Show me every clear knock-out you would recommend declining this week and why.
• Where are our win-probability estimates systematically too optimistic by segment?
• Which open opportunities are creating a capacity conflict right now?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Whoever has time

   Opportunities are pursued or dropped by default, based on who noticed them and had capacity. There are no criteria, no record, and no learning from outcomes.

1. Level 1 — Informal gut check

   A manager makes a go/no-go call from experience with little structure. Some clear knock-outs are caught, but win probability, capacity, and terms risk are weighed inconsistently and rarely recorded.

2. Level 2 — Structured gate

   A defined go/no-go process weighs winnability, fit, risk, and capacity against criteria, records the rationale, and feeds outcomes back to calibrate the criteria over time.

3. Level 3 — Assisted

   Go/no-go analyses are drafted from the firm's own win-rate and client history, capacity conflicts are flagged against backlog, and pipeline opportunities are ranked by expected value for review.

4. Level 4 — Operated

   Screening, evidence-gathering, capacity-conflict flagging, and calibration feedback run unattended inside guardrails, while every go/no-go decision and every commitment of pursuit resources remains a human decision.

Common questions

Why is a no-go decision valuable rather than a missed opportunity?

Because pursuit capacity is finite, and every proposal the firm produces for work it cannot win or should not want is capacity taken from work it can win and profit on. A disciplined no-go concentrates the firm's estimating and management effort on the opportunities worth chasing, which raises both the win rate and the quality of the effort on those pursuits. A firm that never says no is not maximizing opportunity; it is spreading itself too thin to win well, and its worst financial outcomes are frequently jobs it should have declined.

Should delivery capacity really affect whether to bid?

Yes, and ignoring it is one of the most dangerous go/no-go errors. Winning work the firm cannot staff, supervise, or bond does not create profit; it creates the conditions for a default, an overrun, or a reputational failure that costs far more than the pursuit ever did. The go/no-go must honestly weigh whether the crews, supervision, and bonding capacity exist to execute if the pursuit succeeds, because a job won and then delivered badly is worse than a job never pursued.

How do you keep the go/no-go decision from being pure optimism?

By closing the feedback loop: comparing actual outcomes -- wins, losses, and the realized margin on won work -- against the win probabilities and rationale recorded at the gate, and using the comparison to calibrate future estimates. Firms consistently overestimate their chance of winning because declining feels like defeat, and the only reliable corrective is data on their own actual win rates by client, market, and selection type. Without that loop the gate never learns, and the same optimistic misjudgments repeat pursuit after pursuit.