A Preconstruction Guide from Briq
The Go and No Go Playbook
A scoring framework for deciding what to chase, and a way to find out whether your decisions are any good.
Every construction firm has a go/no-go process. Most of them are informal, most of them work reasonably well, and almost none of them get better over time.
A firm can run pursuit decisions on experienced judgment for years and never find out which parts of that judgment were correct. Win rate gets tracked. The jobs that were declined do not get tracked at all, so nobody ever learns whether the no bids were right. The result is a process that produces defensible decisions and no institutional learning.
This guide lays out a scoring framework, a way to weight it against your own history, and the small set of things you have to track afterward if you want the process to improve.
What's inside
- The three errors, and which one actually costs the most
- Why most go/no-go processes cannot improve
- The seven factors that cover the decision
- How to derive your weights from your own last twenty five pursuits
- Four outcomes instead of two
- Naming the strategic bid honestly
- Three failure modes in the meeting itself
- The four things to track afterward
- The scorecard, a worksheet you can use on the next pursuit
- Eight questions to ask any vendor, including us
- Where Briq fits
Get the field guide — free, with an instant download.
Read the argument
The full guide adds the worksheets and the vendor questions. The argument is below, ungated.
How do construction firms decide which bids to chase?
Every construction firm has a go/no-go process. Most of them are informal, most of them work reasonably well, and almost none of them get better over time.
That last part is the real problem. A firm can run pursuit decisions on experienced judgment for years and never find out which parts of that judgment were correct. Win rate gets tracked. The jobs that were declined do not get tracked at all, so nobody ever learns whether the no-bids were right. And because the reasoning behind each decision is rarely written down, there is nothing to compare against the outcome even when the outcome arrives. The result is a process that produces defensible decisions and no institutional learning, where the same debates happen every year with the same people reaching the same conclusions from memory.
What are the three ways go/no-go decisions fail?
Go/no-go decisions fail in three distinct ways, and they are not equally expensive.
The visible error: chasing work you were never going to win. Six weeks of preconstruction disappear into a pursuit that, in hindsight, had an incumbent, a relationship you did not have, and a price you could not reach. Everyone remembers these. They get discussed. They are also the least damaging of the three, because at least the cost is measurable.
The invisible error: declining work you would have won. Nobody tracks it, so nobody argues about it. A job gets passed on because the team was busy, or because it looked unfamiliar, or because it arrived on a bad week — and it goes to a competitor who was not obviously better positioned. There is no line item anywhere in the business for this, and at most firms it is the more expensive error.
The one that hides: the unexamined courtesy bid. A pursuit everyone privately knows will not be won, submitted to stay on a list or maintain a relationship. That is sometimes a legitimate business decision. It becomes a problem when it is never named as one, because then it consumes full preconstruction effort against zero expectation and never appears in any analysis of where pursuit hours went.
The pursuits you declined are the half of the decision nobody measures.
Why don't most go/no-go processes improve?
A decision process improves when three conditions are met. Most go/no-go processes meet none of them.
The reasoning has to be recorded at the time. Not the decision — the reasoning. Which factors drove it, and how confident anyone was. Written after the outcome is known, the reasoning is reconstructed rather than remembered, and reconstruction always favors whoever was loudest.
The outcome has to be recorded for both answers. Win and loss data on the go decisions is standard. Outcome data on the no-bids is almost never collected: who won it, roughly what it went for, and whether it turned out to be work you would have wanted. That information is usually obtainable, and almost nobody obtains it.
Someone has to compare the two. Quarterly is enough. Which factors actually separated the wins from the losses, and which factors everyone believed mattered turned out not to?
Without all three, the process is not a model. It is a habit with a meeting attached.
What factors should a go/no-go framework score?
Most frameworks either have four factors, which is too blunt, or forty, which nobody completes. Seven categories cover the decision and stay usable under bid-day pressure:
- Fit — is this the work we do? Type, size, delivery method, geography, self-perform scope, answered from your real project history rather than the aspirational version.
- Relationship — do we know the owner, the design team, or the construction manager, and how well?
- Competition — who else is bidding, how many, and is there an incumbent?
- Economics — is the margin real after the terms? Payment history, retainage, allowances, contract value against effort.
- Risk — what is in the contract and the schedule that could cost more than the job is worth?
- Capacity — can we actually execute it? People, bonding, the right superintendent, backlog room at that time.
- Timing — when did we learn about it, and how much pursuit time is left?
Two notes from practice. Capacity is the factor most often scored by the wrong person — preconstruction should not answer it alone, because preconstruction is not the group that has to staff the job. And timing is the factor most often ignored, yet frequently decisive: a strong pursuit found three weeks late is often a weaker bet than an average pursuit found three months early.
How should you weight the factors?
The seven factors are the same everywhere. The weights are not — a negotiated-work firm and a hard-bid civil contractor should not weight relationship the same way. Rather than guessing, derive the weights from your own history in an afternoon:
- Pull your last twenty-five to thirty pursuits, wins and losses both, plus any no-bids you have records for.
- Score each retrospectively on the seven factors, one to five, using only what was known at the time of the decision. That distinction is the whole exercise.
- Find the factors where wins scored consistently high and losses consistently low. Those are your real drivers. Factors that scored the same across both outcomes are telling you nothing, however much they dominate the meeting.
- Weight accordingly, and write the weights down.
Most firms find two or three factors carry most of the signal — and frequently they are not the factors people assumed. The point of the exercise is not the weights. It is finding out which of your assumptions were never true.
Should go/no-go be a binary decision?
A binary go-or-no-go forces every pursuit into one of two boxes, which is why the marginal ones get argued about for an hour and then decided by whoever cares most. Four outcomes handle the real range:
- Go. Full pursuit, full effort, normal resourcing.
- Go with conditions. Bid it, with a specific named condition attached — a cap on preconstruction hours, a required site walk, a scope clarification before pricing continues. The condition has an owner and a date.
- Strategic bid. The courtesy bid, named honestly: submitted to hold a position or maintain a relationship, with a hard hours cap and a stated reason. Naming this category is the single highest-value change most firms can make, because it moves these pursuits from invisible to budgeted.
- No bid. Declined, with the reasoning recorded and the outcome tracked.
What should you track after the decision?
Four things, and this is the entire feedback loop: the outcome of every go decision; the outcome of every no-bid, including who won it and whether it turned out to be work you wanted; preconstruction hours actually spent against what was budgeted at the decision; and the score at decision compared against the outcome, reviewed quarterly.
None of this requires new software. It requires that someone owns the quarterly comparison and that the meeting produces a written record rather than just a decision.
The question underneath any tool you might buy for this — including ours — is simple: does it improve the decision, or does it record the decision faster? Recording it faster is worth something. It is not worth what the category charges for it.