How to review subcontractor exclusions and qualifications

Subcontractor bids bury risk in exclusions and qualifications. Identify them, classify impact, normalize the comparison, and lock decisions into the subcontract scope letter before award.

Guide3 min read

Published

Tower crane against an overcast sky
On this page
  1. Exclusions vs qualifications
  2. Step 1: Read and annotate every proposal
  3. Step 2: Categorize by impact
  4. Step 3: Normalize and price the differences
  5. Most common traps to hunt for
  6. Integrate findings into the subcontract
  7. Sample bid-review matrix
  8. KPI and quality gates
  9. Common pitfalls

Every subcontractor proposal lists exclusions (what is not included) and qualifications (conditions on what is). Those lines often move more money than the cover price. A $1.9M mechanical bid with $280K of exclusions is really $2.18M of work waiting for the GC. Read and document them before you compare numbers.

This review sits in leveling and pre-award: after scope generation and solicitation, once proposals and addenda acknowledgments are in, and before final bid review. Pair it with bid coverage so you know both who bid and what they left out.

Exclusions vs qualifications

  • Exclusions omit work from the price. Example: "Excludes permanent HVAC zoning controls, GC to supply." The GC must cover that work somewhere.
  • Qualifications attach conditions to included work. Example: "Price assumes Owner furnishes switchgear ($50K extra if not)." The work is in until the assumption fails.

Exclusions carve out scope. Qualifications create contingent cost. Both belong in the leveling matrix as separate rows so the true comparative cost is visible. See also tabulation vs leveling vs evaluation.

Step 1: Read and annotate every proposal

Do not judge a bid from the summary page. On the first pass, read the full proposal top to bottom (including appendices) and log every exclusion and qualification:

  • Exact wording
  • Trade or item affected
  • Whether it is an exclusion (not doing the work) or a qualification (conditional inclusion)

Use a comparison matrix with space for each bidder's conditions. The dedicated Exclusions section, end pages, and buried assumptions (owner-furnished equipment, labor limits, alternate methods, warranty conditions) are where the money hides.

Step 2: Categorize by impact

ImpactSignalsWhat to do
HighOften $25K+; major risk shift to GC; multi-trade items (penetrations, firestopping); six-figure CO potentialClarification or add price before award; never bury in the low number
MediumMoves the comparison but is not alone decisiveRecord in matrix; clarify if it changes award rank
LowBoilerplate already handled contractually or immaterialNote once; rarely changes award

Focus bid-day hours on high and medium items. For each: do you trust the qualification, or must you clarify? For exclusions: was the omission intentional, or will the work simply land on the GC?

Step 3: Normalize and price the differences

For each high-impact item, decide before award:

  • Clarify: ask the sub to confirm the exclusion or provide an add price ("Your bid excludes commissioning; confirm or price to include")
  • Plug: if the GC will cover it, insert a documented estimate into GC scope
  • Accept and carry: if neither side will price it into the sub's number, track it as GC-held scope and budget it (carry number methodology)

Then normalize the comparison: add or subtract so you compare like-for-like. Raw lows with different exclusions are not comparable. Mechanics of the leveling pass: construction bid leveling.

Most common traps to hunt for

ItemWhy it bites
Commissioning vs startupMEP often prices startup of their equipment but not formal owner commissioning, especially labs and hospitals
BAS / controls interfaceWho provides central programming is a classic trade fight; get written confirmation
Penetrations and firestoppingWho cuts, who patches, who supplies firestop, expensive and usually excluded unless explicit
As-builts and closeoutSubs price product submittals; owners still expect as-builts and O&Ms, track who did not
Site safety / supervisionFire watch, confined space, and similar duties assumed "by GC" when the spec says otherwise
Owner-furnished equipmentChillers, generators, switchgear assumed OFCI, wrong assumption means steep add cost

These are the clauses that most often become change orders when the exclusions column is skimmed.

Integrate findings into the subcontract

Review without contract follow-through leaves the risk intact. Attach a subcontract scope letter to each buyout that states what is in and out, using your leveling notes:

  • List high-impact exclusions as GC-responsible or as negotiated inclusions with price
  • Confirm or void each material qualification in writing
  • Prefer negotiation into price or explicit GC carry over unilateral "notwithstanding" language without sub agreement

If a qualification is not addressed before award, it often survives as a hidden clause. Lock the scope now, then run final bid review before submission.

Sample bid-review matrix

Scope / itemBidder ABidder BBidder C
Concrete foundations$250,000; excludes over-excavation beyond 15 ft$260,000; excludes underside reinforcement fix$245,000; full scope included
Electrical switchgear$80,000; excludes switchgear (owner)$85,000; assumes 600V; excludes transformer beyond$78,000; includes switchgear
Mechanical HVAC$150,000; excludes owner chillers$148,000; excludes VFDs for boilers$160,000; includes equipment
CommissioningExcludedStartup onlyIncluded
Notes / actionsClarify over-excavation (high)Confirm switchgear add-priceReview OFCI assumption

At award, every high-impact row is priced in, carried, or explicitly assigned.

KPI and quality gates

Track change orders on past jobs that trace to missed exclusions. A simple scope gap index (uncovered high-impact items carried into subcontract unsigned) should trend toward zero. Quality gates:

  1. Peer review of the completed matrix before submission
  2. Bid-tab meeting on anomalies (too-low bid vs obvious exclusions)
  3. Pre-award audit: final scope letter vs leveling notes

Common pitfalls

  • Reading only summary pages
  • Ignoring qualifications until they trigger
  • Parking everything in a blunt contingency instead of quantifying each item
  • Letting subcontract language diverge from leveling decisions

FAQ

Do all exclusions need to be resolved before award?

High- and medium-impact items should be resolved or priced before signing. Low-impact boilerplate can be deferred into allowances if you make that decision consciously and document it.

What if two bids exclude the same item?

Treat it as a scope gap. Clarify with design (RFI or addendum), then obtain a price or carry the work. Universal exclusion does not mean the work disappeared, see also [spot scope gaps](/resources/spot-scope-gaps-before-you-carry).

How does this differ on negotiated GMP jobs?

You still identify exclusions and qualifications so the final subcontract and GMP know what is included. Negotiation continues, but silent assumptions still become disputes.

Why not just build a bigger contingency?

Contingency is blunt. Unaddressed exclusions often exceed typical contingency and arrive as cost plus time. Clarify, negotiate, or assign each item up front.

What if a late bid arrives after leveling started?

Usually exclude it. If rules allow a grace period, run a full exclusions pass and confirm addenda acknowledgment before merging it into leveled totals.

ShareLinkedInX

Related reading

Guide4 min

Construction addenda management for GC estimators

Addenda are official bid-document revisions. Log them, distribute them, retakeoff the deltas, and require subcontractor acknowledgments so your estimate and every bid reflect the final scope.

Tower crane above steel reinforcement
Guide6 min

How to set a carry number you can defend

The method for getting from a submitted subcontractor bid to the number that actually goes in the estimate, including evaluated cost, expected-value risk pricing, and the duplicate-contingency trap.

Construction scaffolding interior

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.