The Go/No-Go Decision Framework for Construction Bids

Every construction firm has bid on a project they knew — deep down — they probably shouldn't pursue. Maybe it was outside their typical scope. Maybe they had no relationship with the client. Maybe the timeline was impossible and the fee structure was brutal. But the revenue looked attractive on paper, so they went for it anyway. And then spent six weeks and $25,000 in pursuit costs on a proposal that finished third out of three.

The go/no-go decision is supposed to prevent exactly that scenario. But most firms make these decisions backwards: they decide to bid first and then look for evidence to support the decision. The right approach runs in the opposite direction — objective evaluation first, emotional commitment second.

This article is part of our complete guide to pursuit management for construction firms — where we cover the full pursuit lifecycle from opportunity identification through win rate improvement.

Why most firms are making go/no-go decisions backwards

The pattern is remarkably consistent across the industry. An RFP arrives, and within minutes someone in leadership says "we should bid this." The reasoning varies — it's a big number, it's a prestigious client, we need the backlog, we "should" be able to win this. Once that initial commitment is made, the entire evaluation process becomes about confirming the decision, not testing it.

People start looking for reasons to say yes instead of reasons to say no. The BD director inflates the strength of their client relationship. The operations team assumes they'll figure out the staffing. Precon hand-waves the estimate risk. By the time the proposal is halfway written, nobody remembers to ask whether this was actually a good use of the firm's resources.

This is the sunk cost trap in its purest form — and it starts before you've spent a single hour on the proposal. The antidote is a structured decision framework that forces honest evaluation before emotional commitment sets in.

The five criteria that should drive every bid decision

A reliable go/no-go framework evaluates every opportunity against the same set of criteria. No exceptions, no "this one's different" rationalizations. Here are the five that matter most:

1. Client relationship and access. Do you have an existing relationship with this client? Have you worked for them before? Do you know who the decision-makers are and what they care about? A warm relationship doesn't guarantee a win, but the absence of one is a significant headwind — especially in an industry where past performance and trust are primary selection factors. If you're walking in cold against incumbents who've built that trust over years, your probability is low.

2. Project type and size fit. Have you done similar work successfully? Is the project size within your typical range — not just your technical capability, but the range where you operate most efficiently and have the strongest references? A firm that excels at $15-40M education projects should think carefully before pursuing an $80M healthcare renovation, even if the technical capabilities overlap.

3. Team capacity and availability. This is where self-deception is most common. You need to evaluate who will actually be available when the proposal is due and — more importantly — when the project would start. That project executive finishing a job in three months? They're not available for a pursuit with a six-week timeline if their current project is hitting a critical phase. Be honest about real capacity, not theoretical capacity.

4. Competitive position. Who else is likely to pursue this project, and how do you stack up? If the incumbent is re-bidding and has performed well, your probability drops significantly. If you're one of three equally qualified firms in a commodity market, the decision comes down to price — and that's a race to the bottom most firms should avoid.

5. Risk profile. What does the contract structure look like? Are there unusual liability provisions, liquidated damages clauses, or technical risks that are outside your comfort zone? A project with a 50% gross margin potential but a contract that puts all schedule risk on the contractor isn't a good bet — it's a gamble.

Each of these criteria deserves an honest rating. If you're scoring below average on three or more, it's probably a no-go — regardless of how attractive the revenue looks.

How to run a go/no-go meeting that produces real decisions

A go/no-go meeting is only as good as the information feeding into it and the willingness of participants to be honest. Here's how to make it work:

Get the right people in the room: BD lead, operations leader, precon representative, and potentially a project executive who would run the job. Not the entire leadership team — that creates groupthink. A focused group of four to six people with direct knowledge of the client, project type, and current workload.

Distribute information beforehand. Everyone should come having read the RFP, not hearing it for the first time in the meeting. Prepare a one-page summary: project scope, estimated value, client name, delivery method, key dates, and any known intelligence about competition or client preferences.

Before you can evaluate whether to pursue a project, you need a thorough analysis of the RFP itself. Our guide to RFP response strategies for construction firms covers the analysis framework that feeds directly into this decision.

Structure the conversation around the five criteria. Go through each one. Require honest assessment, not optimism. Designate someone to play devil's advocate — a role that rotates so it doesn't become one person's permanent burden. Document the decision and the reasoning, whether it's go or no-go. That record is invaluable three months from now when you're evaluating whether your decision-making process is actually working.

Common decision mistakes that kill win rates

After years of observing go/no-go processes across construction firms, certain patterns emerge:

Chasing revenue over fit. The $200M project that would double your firm's revenue sounds exciting — but if your largest project to date is $40M, you're not a credible contender. Owners see through it, and your proposal shows it.

Bidding to "stay busy." This is the most dangerous reason to pursue work. It leads to accepting unfavorable terms, underpricing to win, and taking on projects that distract from better opportunities. Every hour spent on a poor-fit pursuit is an hour not spent on a strong one.

Ignoring red flags in the RFP. Unrealistic timelines, contradictory requirements, heavy risk transfer to the contractor, or an evaluation criteria that heavily weights price in a market where you're not the low-cost provider. These red flags exist for a reason — the owner is telling you something about how the project will be run.

Not factoring in opportunity cost. Every pursuit you undertake has a hidden cost: the pursuits you can't undertake because your team is occupied. That $30M project you probably won't win might prevent you from pursuing the $20M project where you're the clear favorite.

Letting ego drive the decision. "We should be able to win this one" or "They can't give it to [competitor] again" are emotional arguments, not strategic ones. Ego-driven pursuits almost always end in losses — and the rationalizations afterward are remarkably consistent.

What to do after the decision — whether it's go or no-go

A go/no-go decision isn't the end of the process — it's the beginning of either a pursuit or a strategic relationship decision.

If it's a go: Document the rationale and the win probability assessment. Assign the pursuit team immediately. Schedule the kickoff within 48 hours. Set clear milestones for strategy development, first draft, red team review, and final production. The momentum from a good go decision should carry straight into pursuit execution.

If it's a no-go: Communicate the decision promptly and professionally to anyone who was tracking the opportunity. If you have a relationship with the client, consider reaching out to stay visible — "We've evaluated the opportunity and it's not the right fit for us at this time, but we'd love to stay connected for future projects." A graceful no-go can actually strengthen a relationship by demonstrating selectivity and honesty.

Log the reasoning. Six months from now, when a similar opportunity arises, you'll want to remember why you passed. Was it the client, the project type, the timing, the risk? That institutional memory helps you make faster, better decisions over time.

Teams that track their go/no-go history and outcomes over time make better decisions — a centralized database like ProjectPortfolio helps you see which types of projects you actually win, making each subsequent bid decision more informed.

Ready to make data-driven bid decisions? See how ProjectPortfolio helps construction teams evaluate opportunities against their real project history and win patterns.