How-to
How to find scope gaps in a bid package
A scope gap is work you'll be on the hook for that the documents never clearly handed to a trade. They're the reason a bid that looked complete comes up short after award. Here's where they hide and how to catch them before the number leaves your desk.
Where scope gaps hide
Four places account for most of them:
- Exclusions — a subcontractor's quote excludes an item, quietly shifting it back to you.
- Addenda — a late addendum changes scope and never makes it into the takeoff.
- Referenced-but-unattached specs — a section points to a standard or schedule that isn't in the package.
- Division boundaries — an item mentioned in one division and assumed to live in another, owned by neither.
A working checklist
Run the package against this before you price. None of it is exotic — it's just disciplined, and it's the part that gets skipped under a deadline.
- Read every exclusion in every sub quote and assign each excluded item to someone — you, or another sub.
- Confirm every addendum is reflected in your takeoff, not just acknowledged.
- Chase every reference: if a spec points to a wage schedule, geotech report, or standard detail, make sure you actually have it.
- Walk the division boundaries — site/structure, structure/MEP, finishes/equipment — and ask who owns each item that touches two.
- List what a complete package should contain and flag the slots that are empty (the bond form, the wage determination, the permits).
The part most reads skip: the silences
The checklist above catches the gaps that are written down. The harder ones are the silences — requirements implied by the project but never stated in the documents. Those don't show up by reading what the package says; you find them by noticing what a complete package would have and this one doesn't.
Or read the package in one pass
Doing this by hand on a multi-volume set, against a clock, is where things slip. BidScan reads the package — specs, addenda, and exclusions — naming anything it could not read rather than passing over it, and returns a cited read in minutes: the obligations, the cost drivers, and the gaps and silences, each pointed back to where it lives in your documents. Your first scan is free.
Common questions
What is a scope gap?
Work that's your responsibility but isn't clearly assigned to a trade in the documents — hiding in an exclusion, a late addendum, a referenced-but-unattached spec, or on a boundary between divisions.
Why do scope gaps matter so much?
A single missed gap can erase the margin on a job. They're hard to catch because the package looks complete — the gap is in what isn't clearly assigned, not in an obvious error.
Can software find scope gaps automatically?
It can surface candidates fast — BidScan reads the package and flags gaps, exclusions, and unstated obligations with a citation to the source. The estimator still decides; the tool makes sure nothing is passed over without being named.
Keep reading
Read your next bid with BidScan
BidScan reads your package and cites every finding — the gaps, the obligations, and the silences. Your first scan is free, and there is nothing monthly to start.