Bid day: the low bid was low because something was missing, and now you own it

The bid day call that takes four minutes

Leveling is finished on the phone, not in the spreadsheet. Four questions per bidder resolve most ambiguity:

• "What did you exclude?" Open-ended and first, because it surfaces what the written exclusions did not say.
• "Did you carry the specified product, or an alternate?" Substitutions are legitimate and must be visible before award, not discovered at submittal.
• "What are you assuming we provide?" This is where hoisting, power, dumpsters, layout and site access hide.
• "What schedule did you price?" Continuous work versus phased work is frequently a double-digit percentage difference in labor cost.

What to do with a bid that is too low

A bid substantially below the others is information, not a bargain. Three possibilities exist and each has a different response:

They missed scope. The most common. Leveling finds it, and the adjusted number is what should be compared. Awarding without correcting it means the GC either eats the difference or fights a change order with a sub who genuinely believes they are right.

They made an error. A transposed number, a missing page, a quantity mistake. The honest move is to point it out. A GC who awards on a known error gets a sub who discovers it at week two and either performs badly or fails — and the GC's reputation among subcontractors is a real asset in a tight market.

They are genuinely cheaper. Better buying power, closer to the site, hungrier for work, more efficient crews. This is real and it is why leveling exists: to distinguish a genuine advantage from a gap.

The response that serves best is the same in all three cases — a conversation before award, with the leveling matrix in hand and the specific items named.

Buyout: converting the estimate into commitments

Buyout is the period after award when the GC converts every line of the estimate into a signed subcontract or purchase order. It is where the project's margin is actually determined, and it is frequently rushed because the work has already started.

Three disciplines protect the number:

• Track buyout against the estimate line by line. Every scope bought below its estimate creates buyout savings; every scope bought above erodes margin. Knowing the running total in week three, rather than in month six, is what allows a correction while corrections are still possible.
• Buy the whole scope, not the cheap part. A subcontract that omits an interface item leaves a gap that the GC will self-perform at full cost and zero margin.
• Issue purchase orders with the same rigor as subcontracts. Material price validity, delivery dates, storage responsibility, return terms and who pays freight are the details that quietly consume savings.

A bid day and a buyout in numbers

A $4.2M project with 18 bid packages, comparing the raw low bids against the leveled result.

• Raw low bids total: $3,410,000.
• After leveling: 11 of the 18 packages had scope gaps in the low bid. Adjusted total: $3,588,000 — a difference of $178,000 that would have been discovered during construction.
• Award decisions changed on 4 packages, where the second bidder was cheaper once the missing scope was priced.
• Buyout result: tracked line by line, the project closed buyout $46,000 below the estimate, with the savings retained rather than absorbed by unrecorded scope gaps.

The instructive number is the $178,000. It did not represent a savings — it represented work that existed on the drawings and in nobody's bid. Leveling did not reduce the cost of the project; it revealed the cost before it became a surprise, which is what allowed the buyout savings to survive to the end.

Getting enough bidders to have a bid day at all

Leveling assumes competition. In a busy market the harder problem arrives earlier: packages with one bidder, or none. Coverage is won in the weeks before bid day, not on it.

• Send the invitation early and follow up by phone. Subcontractors triage invitations by whether they know the GC and whether the project looks real. A call converts an ignored email into a bid more reliably than any portal.
• Tell them what makes the project attractive: schedule, payment history, site conditions, the size of their scope and who else is bidding. Subs choose which invitations to work on, and they choose on information.
• Split or combine packages to fit the market. A package too large for the local subs gets no bids; three small packages that nobody wants to mobilize for get the same result. The right size is a function of who exists in that market.
• Answer questions fast during the bid period. A sub who cannot get an answer prices the risk or walks away, and both outcomes cost the GC money.

There is a reputational component that compounds. GCs known for paying on time, running organized sites and treating scope disputes fairly get more bids and better numbers — which is a competitive advantage built over years and impossible to buy in a week.

Self-perform or subcontract

Every bid day includes a decision that is frequently made by habit: which scopes to self-perform. The honest analysis has four parts, and it changes by project rather than by policy.

True cost, fully burdened. Self-performed work must carry the same labor burden, supervision, equipment, insurance and overhead that a subcontractor's price carries. Comparing a crew's wage rate to a sub's bid is the most common error, and it makes self-perform look artificially attractive.

Risk transfer. A subcontractor absorbs the risk of productivity, rework and warranty on that scope. Self-performing keeps it — which is fine when the work is well understood and expensive when it is not.

Schedule control. The argument in favor of self-perform is control: crews can be moved, sequenced and accelerated without negotiation. On projects where one trade drives the critical path, that control is worth paying for.

Capacity cost. A crew tied up self-performing is unavailable elsewhere, and the correct comparison includes what that crew would have produced on another project.

The common conclusion among builders who run this analysis honestly is narrower self-performance than instinct suggests: keep the scopes where the company is genuinely better and that control the schedule, and subcontract the rest to specialists whose entire business is that trade.

Six mistakes on bid day and in buyout

• Comparing raw numbers. Bids that look comparable rarely are, and the difference is scope rather than price.
• Building the matrix from the bids instead of the documents. Scope that every bidder excluded disappears entirely.
• Skipping the interface rows. Hoisting, temporary utilities, patching and cleanup cause a disproportionate share of post-award disputes.
• Awarding on a known error. It produces a failing sub and a damaged reputation among the subcontractor community.
• Not tracking buyout against the estimate. Margin erodes invisibly, one package at a time.
• Treating purchase orders casually. Freight, storage and price validity quietly consume the savings that were carefully won.

Five numbers to track

Five metrics govern this work. Number of scope gaps found per bid package, which measures whether leveling is being done or assumed. Buyout variance against estimate, by package, tracked weekly during buyout rather than reviewed at the end. Percentage of packages awarded to the raw low bidder versus the leveled low bidder, which shows how often the two differ in your market. Post-award scope change value, separated between owner changes and gaps that leveling should have caught. And bidder coverage per package, since a package with two bidders is a pricing risk before it is anything else.

Frequently asked questions

What is scope leveling and why does it matter?

It is the process of putting every subcontractor bid on the same basis before comparing them, because the spread between the low and the high bid frequently has nothing to do with pricing and everything to do with what each company decided to include. The tool is a matrix with bidders as columns and scope items as rows, and the discipline that matters is that the rows come from the specification and the drawings rather than from the bids — building the row list from what the project requires prevents an item that every bidder excluded from disappearing entirely. Each cell is marked included, excluded or unclear, with unclear driving a follow-up call. Rows should also cover the interface items that cause most post-award disputes: temporary utilities, hoisting, patching, cutting, cleanup, layout, protection, permits and off-hours work.

What should you ask subcontractors on bid day?

Four questions, which take about four minutes per bidder and finish the leveling that the spreadsheet started. What did you exclude — open-ended and first, because it surfaces what the written exclusions did not say. Did you carry the specified product or an alternate, since substitutions are legitimate but must be visible before award rather than discovered at submittal. What are you assuming we provide, which is where hoisting, power, dumpsters, layout and site access hide. And what schedule did you price, because a bid based on continuous work is not comparable to one that accommodates the actual phasing, and the difference is frequently a double-digit percentage of labor cost. Those four minutes cost less than any single post-award scope gap, and the answers regularly reveal that the low bidder is not low.

What should a GC do about a bid that is far below the others?

Treat it as information rather than a bargain, because there are three possibilities with different responses. They missed scope, which is the most common — leveling finds it and the adjusted number is what should be compared, since awarding without correcting means the GC either eats the difference or fights a change order with a sub who believes they are right. They made an error, such as a transposed number or a missing page, in which case the honest move is to point it out: awarding on a known error produces a sub who discovers it at week two and performs badly or fails, and a GC's reputation among subcontractors is a real asset in a tight market. Or they are genuinely cheaper, through better buying power, proximity or efficiency — which is exactly what leveling exists to distinguish.

How should buyout be managed?

Line by line against the estimate, starting immediately rather than at the end. Three disciplines protect the number. Track buyout against the estimate for every scope: each package bought below its estimate creates savings and each bought above erodes margin, and knowing the running total in week three rather than month six is what allows a correction while corrections are still possible. Buy the whole scope rather than the cheap part, because a subcontract that omits an interface item leaves a gap the GC will self-perform at full cost and zero margin. And issue purchase orders with the same rigor as subcontracts, since material price validity, delivery dates, storage responsibility, return terms and freight are the details that quietly consume savings that were carefully won on bid day.

How do you get enough bidders on a package?

Coverage is won in the weeks before bid day, not on it. Send invitations early and follow up by phone, because subcontractors triage by whether they know the GC and whether the project looks real, and a call converts an ignored email more reliably than any portal. Tell them what makes the project attractive — schedule, payment history, site conditions, the size of their scope and who else is bidding — since subs choose which invitations to work on and they choose on information. Split or combine packages to fit the market, because a package too large for the local subs gets no bids and one too small is not worth mobilizing for. And answer questions fast during the bid period, since a sub who cannot get an answer either prices the risk or walks away.