Should a GC Carry the Low Bid or the Fuller Quote?

Key takeaways

• Carry the adjusted scope-complete bid, not the lowest raw quote.
• Bid leveling works only when every proposal is compared to one benchmark scope.
• Real scope gaps should be plugged before the carry is chosen.
• Means-and-method differences should be reviewed, not automatically treated as missing scope.
• Carry documentation should flow directly into buyout, procurement, submittals, and change management.

A general contractor should carry the subcontractor proposal that best matches the leveled scope baseline, not automatically the lowest raw quote. If the low bid needs add-backs for missing scope, compare the adjusted carry against fuller quotes and carry the proposal that cleanly covers the package.

Carry the scope-complete adjusted bid, not the raw low number

The lowest quoted price is the right carry only when it covers the same scope baseline as the competing bids. If required work is excluded, left unclear, or shifted to others without confirmation, it is not a true low bid.

Common gaps show up in the same places across trade packages:

• Drawing scope that is shown but not mentioned in the quote
• Specification requirements included by one bidder and skipped by another
• Trade interfaces such as backing, blocking, patching, sealants, trims, startup support, or coordination effort
• Logistics, phasing, temporary protection, freight, hoisting, or premium-time assumptions
• Alternates, allowances, and addenda handled differently by each bidder

A low bid can still be the right carry. It becomes the right carry only after it is normalized to the same scope baseline as the fuller proposal.

Level every bidder to one scope baseline first

The carry decision should start with one benchmark scope, not with side-by-side comparisons of quote wording. Bid leveling works when every bidder is compared against the same document set, package boundary, and inclusion list.

A practical benchmark usually includes:

• Drawing set and specification dates
• Addenda acknowledged
• Base bid scope
• Accepted alternates and unit prices
• Owner-furnished or vendor-furnished items
• Temporary work or protection assumptions that affect the trade
• Clarifications already issued through pre-bid RFIs
• Required submittal, closeout, and coordination deliverables tied to the package

After the benchmark is set, rewrite each quote into a normalized carry sheet. Do not level quote to quote. Level quote to benchmark.

For each bidder, sort the proposal into clear buckets:

• Included as quoted
• Included but qualified
• Excluded and needs add-back
• Assumed by others and needs confirmation
• Unclear and needs clarification

That structure exposes whether a quote is lean because of competitive buying or lean because of missing scope.

Plug real scope gaps, not means-and-method differences

A real scope gap should be plugged before the carry is chosen. A means-and-method difference should be reviewed for practicality and schedule fit, but it should not be treated as missing scope if the required end result is still covered.

Real scope gaps

These are required items one bidder did not cover.

Examples include:

• A roofing bidder excludes tapered insulation shown on the drawings
• A door hardware bidder excludes keying requirements in the specifications
• A mechanical bidder carries equipment but excludes required controls interface work
• An electrical bidder includes fixtures and devices but omits supports, whips, or branch work shown in the documents

Means-and-method differences

These are different execution approaches for the same required result.

Examples include:

• One concrete bidder carries a different crane assumption
• One framing bidder carries more prefabrication effort
• One painting bidder carries more containment labor
• One sitework bidder carries a different trucking plan

If the documents are ambiguous, do not let the leveling sheet become an internal interpretation exercise. Raise a clarification or RFI so the carry is based on a documented assumption.

Use visible plugs when missing scope would distort the comparison

Plugs should be used for identifiable missing scope, not as hidden contingency. The purpose is to compare bids on equal terms.

Good plug practice follows a few rules:

• Plug only identifiable scope. Tie it to a drawing note, specification requirement, addendum item, or known package interface.
• Use a rational basis. That basis can come from an internal budget, another bidder breakout, vendor budget pricing, or recent similar work.
• Keep the plug separate. Show the original quote, the plug amount, and the adjusted carry.
• Revisit the plug before buyout. If later clarification changes coverage, the adjustment can be updated without losing the original carry logic.

Plugs are often useful for:

• Missing freight or delivery handling
• Omitted submittal and closeout effort tied to the trade
• Temporary protection or patch-back responsibility at trade interfaces
• Addendum scope acknowledged by some bidders but not others
• Scope split confusion between vendor supply and trade installation
• Schedule or phasing requirements that clearly affect labor

When the low bid needs enough credible add-backs to stop being low, the fuller quote is usually the better carry.

Document the carry as a handoff package, not just a number

The final carry should be recorded in a form that procurement, project management, submittal coordination, and change management can use after award. If the downstream team does not inherit the same assumptions, avoidable scope disputes show up during buyout and execution.

A useful carry record should identify:

• Selected bidder and quoted amount
• Adjusted carry amount after plugs or accepted add-backs
• Drawing set, specification sections, and addenda used for leveling
• Accepted exclusions and why they were accepted
• Plugs applied, with short descriptions and basis
• Unresolved clarifications or confirmations still needed
• Alternates, allowances, and unit prices tied to the carry
• Vendor or material assumptions that affect buyout or lead times
• Trade-interface notes that need to stay in the scope letter

That record should then flow into:

• Buyout scope letters
• Procurement planning
• Submittal planning
• Change documentation

Documents are prepared within the contractor's established review and approval workflow.

Tribuild Consultancy is a multi-trade estimating, preconstruction, and project-administration company.

Because pre-bid decisions affect post-award work, the carry should support the full workflow, including proposals, buyout alignment, submittals, procurement tracking, and change documentation.

Use a simple decision path when choosing the carry

The clearest carry decision is usually the one that survives normalization with the fewest unresolved assumptions. In some packages, that will still be the low bidder. In others, the fuller quote is the better carry because it already matches the package boundary.

A practical decision path is simple:

• Level every bidder to one scope baseline
• Separate real scope gaps from means-and-method differences
• Add visible plugs for missing required work
• Compare adjusted carries, not raw quotes
• Document the final carry so the downstream team inherits the same assumptions

If you want to review one upcoming trade package or one estimating workflow, Tribuild can discuss additional bid capacity with your team.

Sources

• https://tribuildconsultancy.com
• https://www.abc.org/News-Media/Construction-Economics
• https://www.agc.org/news
• https://www.bls.gov/news.release/empsit.toc.htm