Subcontractors are sharper than they were five years ago. They know exactly which scope items are ambiguous. They know which drawings conflict. And they know how to write exclusions that look minor until the project is underway.
An Estimating Manager at a Canadian ICI GC put it plainly: "We have fewer subs who just kind of do a gentleman's agreement… they've become more quick to clarify that they're not including that one piece of scope."
That shift has real consequences for general contractors. If your bid-leveling process is still just comparing total prices and checking a few line items, you're leaving yourself exposed. Scope gaps that subs exclude quietly become change orders that GCs absorb loudly.
Arcadis's 2024 Global Construction Disputes Report put the average North American construction dispute value at $60.1 million. Errors and omissions in contract documents repeatedly rank as the leading dispute cause in North America. Most of those disputes start at bid leveling — or rather, at the moment bid leveling failed to catch the gap.
Bid leveling is the process of aligning subcontractor proposals so you can compare them on equal terms. It means adjusting for what each sub included, excluded, assumed, or left undefined — so you're not comparing a complete scope to a stripped-down one and calling it apples-to-apples.
Done well, bid leveling does three things:
Done poorly, it creates a false sense of completeness. You close out the bid, issue the subcontract, and find out six months later that the gap is yours to carry.
Use this checklist when reviewing sub proposals. It's organized by the most common omission patterns — the ones that cost GCs the most money.
The first habit in effective scope management is drawings-first, not boilerplate-first. When you level a sub bid, your reference point should be the project drawings and specifications — not the sub's own scope narrative.
Ask: does the sub's scope match what the documents actually show, or what they assumed the documents show?
A scope package generated from the full document set gives you a trade-by-trade baseline before bids arrive. That baseline makes this comparison faster and more defensible.
Missing scope is harder to catch than wrong scope. A sub who excludes something doesn't always list the exclusion — they just don't mention it.
Common silent omissions by trade:
For a deeper breakdown by trade, the Scope Gap Playbook chapter on trade-specific gaps covers each of these with operator-cited examples.
Exclusion lists are where subs protect themselves. They're also where GCs lose money.
A well-written exclusion is precise. A risky one is vague. Watch for:
The pre-bid walk is a scoping tool, not a courtesy. If you walked the site with subs before bid day, compare what they verbally flagged to what their exclusion list actually says. Gaps between the two are negotiating points.
A clarification is not an exclusion. But it functions like one if you don't address it before award.
Common clarifications that hide scope risk:
Clarifications that aren't resolved before contract award become disputes at buyout. The Pre-Construction Lead at a Top-ENR Canadian GC described the standard for airtight scope this way: "It's descriptive — bread, put it on a plate, use the open jar… You have to get to that level of detail or else they'll just be like, 'you didn't tell us that.'"
The most expensive gaps aren't inside a trade's scope. They're between two trades — the work that both subs assumed the other was handling.
Build a simple cross-trade gap log during bid leveling:
This log becomes your buyout checklist. Every gap resolved before award is a change order you prevented.
Before you issue a subcontract, run a final scope review with the sub. This is not a courtesy call. It's a checkpoint.
The goal is to confirm that what you think you bought matches what they think they're building. Ask directly:
Document the answers. Add them to the subcontract as schedule attachments. This is the difference between a scope of work that protects you and one that becomes an arbitration exhibit.
The Scope Gap Playbook chapter on subcontract language covers exactly how to structure these scope attachments — including the specific clauses that GCs most often get wrong.
These are the habits that produce the most expensive scope gaps. If you recognize any of them in your current process, that's where to start fixing.
The hardest part of bid leveling is knowing what to compare against. If your scope package was built from boilerplate, you're comparing sub bids to a starting point that was already incomplete.
Scope Agent builds complete, trade-by-trade scope packages directly from your project documents — drawings, specs, addenda — in under 60 minutes. Every scope item is referenced to the document it came from. That means when a sub excludes something, you can point to exactly where it's called out.
Provision has reviewed more than $100 billion in project value and processed over 100,000 construction documents. The scope packages it generates reflect what's actually in the documents — not what a template assumed would be there.
For contract and spec review during buyout, Risk Review flags risks with 99% accuracy on pre-built checklists, cutting contract review time by 80%. Every risk is cited to the exact clause, section, or page — so your team isn't hunting through 2,000-page spec books to find the clause a sub is disputing.
And when a question comes up mid-leveling — "does the spec actually require the sub to include this?" — Chat Agent gives you a cited answer in under 20 seconds, sourced to the exact page in your project documents.
GCs using Provision get through pursuits 2x faster. That speed doesn't come from cutting corners. It comes from having a complete, accurate scope baseline before the first bid hits your inbox.
See how the EllisDon team used Provision to save $1.8M in scope-related exposure on a single project. Or book a demo to see how Scope Agent handles your document set.
A Senior PM at a Toronto mid-market developer summed up the ROI of this process: "If we could catch three scope gaps or three missed items on every scope of work, then this thing pays for itself."
Three gaps per project. That's the bar. Most teams who do structured bid leveling clear it before they finish the first trade comparison.
Bid leveling is the process of comparing subcontractor proposals on equal terms. It means adjusting for scope inclusions, exclusions, clarifications, and assumptions so you're comparing real cost — not just price. The goal is to surface missing scope before you award the subcontract, not after the work starts.
Ambiguous drawings and specs give subs room to interpret. When documents conflict, subs price the lower-cost interpretation. When scope is undefined, subs exclude it. Subcontractors are also increasingly precise about writing exclusions — which means GCs who don't read them closely end up absorbing the gap. Arcadis's 2024 report puts the average North American dispute at $60.1M, with errors and omissions in contract documents ranking as the top dispute cause in the region.
Look for vague language like "any work not specifically noted herein," blanket assumptions about GC-furnished items, and coordination exclusions that could apply to critical interface work. Compare each exclusion to your project documents. If the spec assigns that work to the sub's trade, the exclusion is a scope gap — and it's yours to assign before award.
MEP consistently produces the highest-value inter-trade gaps — motor starters, generator conditioning, and the trench are common examples. Envelope subs frequently exclude cover board, flashings, and firestopping. Structural steel bids often omit embeds, anchor bolts, and hoisting for other trades. Concrete subs regularly exclude base plate grouting and concrete pumping.
On a complex commercial project with 15-20 trade packages, thorough bid leveling should take at least two to three hours per trade — longer for MEP. Rushing this step is one of the most common anti-patterns in pre-construction. GCs who do it in under an hour are typically comparing prices, not scopes. The cost of a missed scope gap almost always exceeds the time spent leveling.
An exclusion explicitly removes scope from the sub's price. A clarification states an assumption that affects how the sub priced their scope. Both carry risk if unresolved. Clarifications about design completeness, mobilization count, or GC-furnished items should be confirmed in writing before award — or they become the basis for a change order claim later.
Provision's Scope Agent generates complete, trade-by-trade scope packages from your project documents in under 60 minutes. That baseline gives you a defined reference point for comparing sub bids. Risk Review flags contract and spec risks with 99% accuracy, cited to the exact clause. Chat Agent answers document questions in under 20 seconds — so your team can confirm what a spec requires mid-leveling without hunting through a 2,000-page book.
Scope Agent builds trade-by-trade scope packages from your documents in under 60 minutes.
See Scope AgentMore Articles
