Bid/no-bid and go/no-go decision field guide for contractors

What the bid/no-bid decision is, and why the best bid is often the one you skip

A bid/no-bid decision, also called a go/no-go, is the call you make before estimating a job: do we pursue this, or do we pass. It is the gate that sits ahead of the takeoff. Estimating the work, counting devices and converting them to labor hours, is the next step, covered in the estimating and bidding guide. This decision comes first and decides whether that work is worth doing at all.

The most profitable estimating move a shop makes is frequently the bid it walks away from. That sounds backward until you count what a bid costs. Every invitation you accept pulls an estimator off something else, burns plan-review and takeoff hours, and ties up the people who could be chasing a job you would actually win. Say yes to everything and you spread the same estimating capacity across jobs you have no shot at.

The worst outcome is not losing a bid. It is winning the wrong one. A job that was underpriced, underscoped, or wrong for your crews shows up later as a margin fade you trace in job costing, which is its own guide. The go/no-go screen exists so that loss never gets the chance to land. Decide which jobs deserve the hours, then put the hours where you make money.

Why the screen matters more than the estimate

A sharp estimate on the wrong job still loses you money. That is the part that gets missed. Shops pour energy into estimating accuracy, the labor units and the material pricing, and almost none into deciding which jobs to estimate at all. The selection decision moves the result more than the takeoff does, because no amount of pricing skill fixes a job that was a bad fit before you started.

A low hit rate quietly bleeds the company. Bid twenty jobs to win two and you paid for eighteen losing efforts, and your estimators are exhausted, behind, and rushing the bids that mattered. Volume for its own sake lowers the win rate and the quality of every bid in the stack, because the team cannot do twenty jobs well.

Then there is the job you should have passed on and won anyway. It eats your best crew, runs negative, and the change orders never catch up to the bleed. You would have been better off losing it. Screen hard up front and you stop two failures at once: the wasted estimating hours on jobs you cannot win, and the won jobs that cost you to build. Win the right jobs, not the most jobs.

The real cost of a bid

Every bid costs money whether you win it or not, and most shops never put a number on it. A serious estimate is days of an estimator's time: plan review, the takeoff, supplier quotes, scope letters, the recap. On a mid-size electrical job that is real salary against an opportunity you might lose. Treat estimating as free and you will bid like it is free.

Put a rough cost-per-bid on your own process. Add the estimator hours at a loaded rate, the plan and software costs, and the opportunity cost of the bid you did not chase because this one took the desk. Industry rules of thumb peg bid preparation as a measurable slice of overhead, but your own number is the one that matters, since it depends on your estimating headcount and how deep you bid.

You cannot bid everything well. That is the constraint the whole decision turns on. Estimating capacity is finite, and the question is never whether to bid, it is which jobs get the limited hours. Once you accept that bidding is a cost you are spending, you start spending it on purpose. A consistent screen is just budgeting that cost toward the jobs most likely to pay it back.

What is a good win rate in construction?

Win rate, also called the hit rate or bid-to-win ratio, is jobs won divided by jobs bid. Across commercial construction the average runs roughly 20 to 30 percent, about one win for every four bids, with selective, relationship-driven shops reaching 40 to 50 percent. Hard-bid public work sits lower, where a 5-to-1 bid-to-win ratio is common, and negotiated or short-list work runs better, often 3-to-1 or tighter.

Here is the part that runs against instinct: bidding fewer, better-fit jobs usually raises the win rate and the margin at the same time. A team bidding twenty jobs a month at a 10 percent win rate wins two and pays for eighteen losses. The same team bidding ten qualified jobs at 30 percent wins three, pays for seven losses, books more work, and spends less than half the estimating cost doing it. Same revenue, better jobs, a fraction of the wasted hours.

Chasing volume is the trap. More bids feels like more activity, but it lowers the average quality of each bid and buries the jobs you could win under the ones you cannot. Track your own win rate by job type and by client before you trust any benchmark. The number that should drive the company is your historical hit rate on the work you actually want, not the industry average.

The go/no-go screen

The screen is a consistent set of questions you run on every opportunity before committing an estimator to it. It is the gate, and the point of making it consistent is that it stops the decision from being a mood. Without a screen, a shop bids whatever came in this week, whatever the owner has a hunch about, or whatever a salesperson talked the room into. That is how the calendar fills with losers.

Keep the first pass short. A quick screen of fifteen to thirty minutes catches the obvious passes: wrong trade scope, wrong size, a client you will not work for, a deadline you cannot make. Only the opportunities that clear that pass earn the deeper look, an hour or two on the real fit, risk, and win chance. You are spending estimating time in proportion to how serious the job is.

The screen scores five things, and the rest of this guide is those five: is it our work (fit), do we know and trust the client, what is our real chance to win against the competition, can we handle it if we win (capacity), and what does the job risk and margin look like. Score them before the takeoff. The gate is cheap. The estimate is expensive.

Is this our kind of work?

Fit is the first question: does this job sit inside the work you do well. Trade scope, project type, size, and geography all factor in. A shop that runs tenant fit-outs all day is not the right shop for a substation, and a crew that owns a 50-mile radius loses money the moment it bids three states away. The jobs that fit your wheelhouse are the ones your labor units are calibrated for, so the estimate is more accurate and the build is more predictable.

Size is its own trap in both directions. A job far larger than your usual work brings cash-flow strain, bonding limits, and a schedule that can swamp the company. A job far smaller than your norm carries overhead it cannot support and distracts the people who run the work you are built for. The sweet spot is the size band where your crews, your PMs, and your systems already run smoothly.

A stretch job is not automatically a no. Sometimes the stretch is how a shop grows into a new market or a larger project class on purpose. The discipline is naming it as a stretch instead of pretending it is routine, so the risk and the thinner estimate get priced honestly. A job you call routine when it is really a reach is the one that surprises you in the field.

The client: do we know them, and do they pay?

The client is the factor that sinks more contractors than bad estimating does, because the best-built job in the world loses money if you do not get paid for it. Owner financial capability and payment history are at the top of every serious go/no-go list. Before you estimate, answer two questions: do we know this owner or general contractor, and do they pay their bills on time and in full.

A client you have worked for, who pays on the agreed terms and runs a clean job, lowers the risk on everything downstream. A client you do not know, or one with a reputation for slow pay, retainage games, or burying subs in disputes, raises it on everything. Slow pay and nonpayment are why lien rights and a tight accounts-receivable process exist, and a client who forces you to use them regularly is a client whose work costs more than the bid shows. Check pay history the way a surety checks yours.

The relationship question is just as practical. Are you the favorite on this job, or are you there to round out the bid list. Being the known, trusted bidder a GC actually wants to use is worth more than a sharp price, because it raises your win chance and usually comes with fairer terms. If you cannot tell whether the client wants you or just wants your number, find out before you bid.

What is column fodder?

Column fodder is a bid you are invited to submit only to fill out the count, with no real chance of winning. The trade slang varies, but the situation is universal: the GC or owner already has a favorite and needs a few more numbers to show the project was competitively bid, or to beat their preferred sub down on price. You are the throwaway bid that makes the column look full.

Spot it by the signals. The job came in late with no warning. You have never worked for this client and got no walkthrough, no real access, and no answers to your questions. The scope is vague and nobody will tighten it. A previous contractor is clearly already wired in. When the invitation feels like a courtesy rather than a contest, it usually is.

Bidding column fodder is paying full estimating cost for a lottery ticket someone else already won. It is one of the fastest ways to wreck your win rate, because every one of those losses counts against you in the denominator while teaching you nothing. Decline it cleanly and stay on the list for the next one. If you suspect you are fodder, ask the GC directly where you stand. A straight answer tells you whether to spend the hours.

The competition and your real chance to win

How many bidders are on the job, and who, changes the math completely. A wide-open hard bid with eight or ten contractors is a low-probability, low-margin race where the winner is often the one who made the biggest mistake. A negotiated job or a three-name short list is a different animal, with a real chance to win and room to hold a fair number.

Find out the bidder count before you commit. A GC who will tell you it is a short list of three is signaling you are a contender. One who will not say, or admits it is wide open, is telling you the odds. The number of competitors is one of the four signals contractors weigh most heavily, alongside the client, the project risk, and the profit potential, and it deserves that weight because it sets the ceiling on your win chance.

Knowing who you are bidding against matters as much as how many. If the incumbent who built the last three phases is bidding, you are probably column fodder. If the field is shops that habitually buy work below cost, you either match a price that loses money or you lose the job. Either way the honest read is the same: pick the contests you can actually win, and let the crowded races go to whoever wants the loss.

Do we have the capacity to take this on if we win?

Capacity is the question shops skip when work is tight and regret when it is not: do we have the bandwidth to build this well if we win it. Crew, project management, bonding, and cash all have to be there. Winning a job you cannot staff is how you blow the schedule, burn out your foremen, and damage the relationship that got you the work in the first place.

Look at the backlog honestly. Your backlog is the work already under contract and not yet built, and surety companies watch the ratio of your equity and working capital to that backlog precisely because an overextended contractor is a contractor about to fail. A common surety benchmark is liquid capital around 10 percent of backlog. If a new win would push you past what your people, your cash, and your bonding can carry, the right answer is no even when you would win it.

Bonding and prequalification are part of capacity, not a separate hurdle. A job that needs a bond larger than your single-project or aggregate limit is a job you cannot take regardless of fit, and pushing your surety to stretch on one job can cost you the capacity for the next three. Know your limits before you bid, because finding out at award is how a win turns into a default.

Reading the project risk before you bid

Project risk is everything about the job that can turn a fair estimate into a loss, and most of it is visible before you ever do a takeoff. Scope clarity is the first read. A clean, complete, well-coordinated set of drawings is a low-risk job. A design that is half-finished, full of conflicts, and labeled for pricing anyway is a job where the scope gaps become your cost overruns.

Schedule is the next red flag to check. An aggressive or unrealistic schedule, especially one with liquidated damages attached, shifts the owner's time risk onto you. Liquidated damages are a fixed daily penalty for finishing late, and owners sometimes set them as a weapon rather than a fair estimate of their loss. Read the LD number and the milestones before you decide the job is buildable on the time given.

The rest of the risk read is the site, the design completeness, and the payment terms. A congested site, phased occupied work, or a long unfunded front before the first payment all raise the real cost of the job above the bid. None of these are automatic no-bids on their own. Stack three or four of them on one job, though, and you are looking at the kind of work that pays a premium to do and a penalty to do badly. Price the risk or pass on it.

Read the contract terms before you bid, not after you win

The contract terms can turn a profitable job into a trap, and they are part of the go/no-go decision, not an afterthought for the lawyers once you win. Read the onerous clauses before you commit the estimating hours, because some of them are reason enough to decline no matter how good the work looks.

Pay-if-paid is the one to find first. A pay-if-paid clause makes the owner's payment to the GC a precondition of the GC paying you, which shifts the owner's credit risk onto your shoulders. Pay-when-paid only delays your payment a reasonable time and is less dangerous, but the two get used interchangeably in conversation, so read the actual language. No-damages-for-delay is the next flag: it can leave you with only a time extension and no money when the owner's delays blow up your costs. Broad indemnity clauses can make you liable for losses you did not cause.

Retainage and the prompt-payment terms round it out. Retainage held longer or higher on you than on the GC, or terms that quietly waive your lien rights, are clauses worth pushing back on before bid day. Enforceability of these clauses varies by state, and some jurisdictions void the worst of them, so confirm against your own counsel and the project's governing law. The point stands either way: price the terms, negotiate the ones you can, and walk from the ones you cannot live with.

Margin potential versus the race to the bottom

Margin potential is the honest read on whether the job can actually make money, and it is a go/no-go input, not just an estimating output. Some jobs are structured to be profitable: a fair scope, a reasonable schedule, a client who pays, and a field that is not stacked with shops buying work below cost. Other jobs are a race to the bottom before the first number is drawn.

You can usually feel the race-to-the-bottom job early. It is the wide-open hard bid where the only way to win is the lowest price, the work is a commodity, and the winner takes a thin or negative margin and hopes to make it back on change orders. Sometimes the change-order game works. More often it is how a shop stays busy and broke at the same time. If the only path to winning is a price you cannot build to, that is a no-bid, not a challenge.

Weigh the likely margin against the risk you just read. A thin margin on a clean, low-risk job for a client who pays can be worth taking. The same thin margin on a high-risk job with onerous terms is a loss waiting to be booked. Margin and risk travel together, and the job worth bidding is the one where the margin is large enough to pay for the risk you are accepting.

When a thin job has strategic value

Sometimes the numbers say marginal and you bid anyway, on purpose, for a strategic reason. Strategic value is the part of the decision that lives outside the single-job margin. A first job with a client you want for the long term, an entry into a market or a project class you are trying to grow into, or work that keeps a key crew together through a slow stretch can all justify a thinner bid.

The discipline is deciding it on purpose instead of rationalizing it after the fact. A strategic bid is a known investment with a named payoff: this gets us in with this GC, this proves we can do this project type, this holds the crew until the backlog refills. Write the reason down. A thin job you took for a clear strategic reason is a different thing from a thin job you talked yourself into because you wanted the work.

Keep strategic bids a small, deliberate share of the pipeline. A shop where every marginal job gets a strategic excuse is a shop with no screen at all. The strategic exception works because it is rare and chosen. Make it the rule and you are back to bidding everything, just with a better story.

What goes on a bid/no-bid scorecard?

A scorecard turns the five questions into a number you can compare against a threshold. Score each factor, weight it by how much it matters to your shop, and total it. Many contractors rate each factor on a simple scale, apply a weight, and sum the weighted scores into a percentage of the maximum. A common pattern sets a clear pursue above roughly 75 percent, a clear no-bid below about 40 percent, and treats the middle band as the decision worth a real conversation in the room.

Set automatic red flags that override the score. A client who does not pay, a bond requirement past your limit, or a pay-if-paid clause you cannot accept is a no-bid regardless of how the rest scores. The weights and the threshold are yours to calibrate from your own win history, so the table below is a starting shape, not a rule. Tune it against the jobs you actually won and the jobs that actually made money.

Combine the scorecard with experience

The scorecard is a tool, not an oracle. A veteran estimator who has bid for a particular GC for a decade knows things the form cannot capture: how that owner behaves when the schedule slips, whether the drawings from that engineer are usually clean, how the field really runs once the contract is signed. The number organizes the judgment. It does not replace it.

The discipline cuts the other way too. Gut feel without the scorecard is how a shop bids on optimism and habit, talking itself into the same loser it bid last year. The form forces the quiet objections into the open, where the room has to either price the weak factor or pass on the job. The best decisions come from running the score and then arguing honestly about what the score missed.

Calibrate the scorecard against your own results. Pull last year's go/no-go decisions, set them next to what you actually won and what those jobs actually earned in job costing, and adjust the weights toward the factors that predicted your real outcomes. A scorecard that has never been checked against results is just a feeling with a spreadsheet around it.

The clean no-bid is a decision, not a failure

A no-bid is a choice you made to protect your estimating hours and your margin, and treating it as a loss is how shops end up bidding everything. Declining a job you would not win, or would not profit from, is exactly what the screen is for. The shops with the best win rates say no more often than the shops chasing volume, and they are more profitable for it.

Decline it professionally. A short, prompt no-bid letter or call to the GC keeps the relationship intact and keeps you on the list for the next invitation, which is the one you might actually want. Going silent or scrambling out a half-effort bid to be polite costs you both ways: you waste the hours and you signal that your number cannot be trusted.

Say no early. The moment a job fails the screen, decline it, so the GC has time to find another bidder and your estimator gets the hours back for a job worth winning. A fast, clean no-bid is a professional courtesy that builds the relationship. A slow, sloppy one burns it.

Once it is a go, commit fully

The decision is binary for a reason: either bid to win or do not bid. A half-effort bid is the worst of both worlds, since it spends the full estimating cost and still loses, while teaching you nothing because you never gave the job your real number. The screen exists so that the jobs you say yes to get everything you have.

Once a job clears the gate, the question changes from whether to bid to how to win it. That is the estimating and bidding work: the accurate takeoff, the right labor units, the tight scope letter, the relationships that get your bid read seriously. Cutting that effort because you are stretched is a sign the job should have been a no-bid in the first place. If it was worth the yes, it is worth the full bid.

Protect the go decisions by limiting them. A shop that says yes to the right, smaller number of jobs can put real effort behind each one. That is the whole payoff of the screen: fewer bids, every one of them a genuine attempt to win, none of them a courtesy you regret.

Track every decision against its outcome

The screen only gets smarter if you track what it decided and what happened next. Log every bid/no-bid call, the score behind it, and the result: bid and won, bid and lost, or no-bid. Then break the win rate down by job type, by client, by project size, and by who you bid against. The pattern in that data tells you what to chase and what to stop chasing.

Most shops never close this loop, which is why they keep bidding the same losers. The numbers usually surprise people. A shop convinced it should chase a certain GC discovers it has won one of the last eleven and burned a month of estimating doing it. Another finds that the small negotiated jobs it almost passed on are the steadiest margin it has. You cannot see either pattern without the log.

Keep the record where the work already lives. A field platform like FieldOS that already holds the jobs, the customers, and the outcomes is the natural place to track go/no-go decisions and win rate, so the bid history sits next to the job-cost result instead of in a spreadsheet nobody opens. The decision and its consequence belong in the same system, because that is the only way the next decision learns from the last one.

A full pipeline is what lets you be selective

Selectivity is a luxury that a healthy pipeline pays for. When the funnel is full of opportunities, you can decline the bad ones without fear, because another is right behind it. When the funnel is empty, you bid out of desperation, and desperation bids the worst jobs at the thinnest prices for the riskiest clients. The screen only works if there is enough flow to feed it.

This is why business development and the go/no-go decision are the same problem from two ends. Keeping the funnel full, through relationships, repeat clients, and a steady flow of qualified leads, is what gives the screen something to choose from. A customer relationship system that tracks the leads and the client history feeds the same data the screen needs, so the pipeline and the decision share one record of who you work for and how it went.

Watch the pipeline as a leading indicator. A thinning funnel is the early warning that you are about to start bidding badly, weeks before it shows up in the win rate or the job-cost results. Fill the funnel when you are busy, not when you are slow, so the screen never has to choose between a bad job and no job at all.

Debrief every win and every loss

The decision loop does not close at award. After every bid, win or lose, ask why and feed the answer back into the screen. A win debrief is quick but worth it: were we the favorite, was our number right, did the strategic reason pay off. A loss debrief is where the real learning hides, and most shops skip it because losing stings.

Ask the GC where you landed and why. A simple call after a loss often gets you the spread between your number and the winner, which tells you whether you were close and unlucky or off by a mile and never in it. Losing by 2 percent on a job you fit is a different lesson from losing by 30 percent because your labor units were stale. Both belong in the record.

Feed it forward. A pattern of close losses on a job type you want might mean your overhead allocation is heavy or your relationships are thin. A pattern of wide losses might mean the work is a commodity race you should stop entering. The debrief is what turns a year of bids into a calibrated screen, and the job-cost result on the wins is what tells you whether the jobs you chose actually paid.

What to document for each decision

A go/no-go decision nobody recorded is a decision you cannot learn from. The log is what lets you check the screen against reality and calibrate it. Capture the factors you scored, the call you made, and the outcome, so the next decision on a similar job starts from evidence instead of memory.

Keep it light enough that it actually gets filled in. A scorecard, a one-line reason, and the eventual result are enough. The table below is the working set: the factor, the question it answers, and the note worth keeping so the record means something when you read it back next year.

Common mistakes

• Bidding everything that comes in, which lowers the win rate and the quality of every bid in the stack.
• Running no consistent go/no-go screen, so the bid calendar fills with whatever the week brought.
• Spending full estimating cost on column fodder for a job that was wired for someone else.
• Ignoring capacity and winning a job the crews, cash, or bonding cannot carry.
• Skipping the contract terms and discovering pay-if-paid, no-damages-for-delay, or broad indemnity after the win.
• Winning a job you should have passed on, then watching it run negative in job costing.
• Never tracking decisions against outcomes, so the screen never learns and the same losers keep getting bid.

Field checklist

Standards and references

There is no code that governs which jobs to bid, the way the NEC governs how to wire them. The discipline comes from bid-management and go/no-go practice published by the trade and finance associations, and from your own numbers. The Associated General Contractors (AGC), the American Society of Professional Estimators (ASPE), and the Construction Financial Management Association (CFMA) all publish guidance on bid strategy, estimating practice, and the financial ratios that bound how much work a contractor can safely carry.

The strongest reference is your own data. Your historical win rate by client and job type, your job-cost results on past wins, and your real cost per bid tell you more about what to chase than any benchmark, because they are measured on your shop and your market. Calibrate the screen against them and re-check it as the work changes.

Two external limits are hard, not advisory. Your surety's single-project and aggregate bonding capacity, and the capital-to-backlog ratios behind them, set a ceiling on what you can take on regardless of how a job scores, and CFMA guidance describes how sureties read those numbers. The contract terms are governed by the project's law and your own counsel, and enforceability of clauses like no-damages-for-delay and pay-if-paid varies by state. The throughline holds across all of it: screen before you estimate, do not be column fodder or overcommit, and win the right jobs rather than the most jobs.

Terms and definitions

The bid/no-bid decision carries its own vocabulary, and the same idea shows up under different names across a sales meeting, an estimating department, and a banker's office.

Bid/no-bid and go/no-go are the same decision: whether to pursue a job. Win rate, hit rate, and bid-to-win ratio all describe how many bids turn into wins. Column fodder is the throwaway bid you are invited to submit only to fill the count. The cost of bidding is what an estimate costs you whether you win it or not, and the backlog is the work you have under contract but have not yet built.

Bid/no-bid (go/no-go)

The decision, before estimating, of whether to pursue a job at all

Win rate / hit rate

Jobs won divided by jobs bid; also expressed as a bid-to-win ratio like 4-to-1

Column fodder

A bid invited only to fill the count, with no real chance of winning

Cost of bidding

The estimating hours and opportunity cost a bid consumes, won or lost

Backlog

Work under contract but not yet built; sureties limit it against your capital

Pay-if-paid

A clause making the owner's payment a precondition of the GC paying you

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• How do you estimate electrical work?
• What is job costing?
• What is a three-way match in accounts payable?
• What KPIs should a contractor track?
• What is prevailing wage?