The line nobody quoted is the change order you eat later. Bid Reasoner maps each subcontractor bid to your scope of work and flags both directions — the items a bidder missed and the items it added — so you award on complete coverage instead of the bid that left the most out.
You get 9 bids on a drainage package. Three are within 4% of each other; one is 18% under. The low bid wins the meeting — until, six weeks into the job, you find it never priced the trench-shoring line that your scope clearly called for. Now it's a change order, at the sub's number, with no competition left to keep it honest.
Scope gaps hide in plain sight because every bidder formats their bid differently — different line wording, different units, different item numbers. Eyeballing whether bidder A's "excavation" covers the same work as bidder B's three separate items is exactly the kind of line-by-line cross-check that gets skipped under deadline. The bid that excluded the most work looks like the best price.
Three steps from a folder of differently-formatted PDFs to a clean coverage view.
Bid Reasoner reads your scope of work and every bidder's PDF, extracting and normalizing each line item so your SOW and all the bids share one structure — regardless of how each sub laid theirs out.
Each bidder's items are matched to your SOW, lining up like-for-like work even when the wording, units, or item numbers differ. No more guessing whether two differently-named lines mean the same thing.
Items in your SOW a bidder didn't quote surface as coverage gaps; items it quoted that weren't in your SOW surface as scope creep — each shown against the peer median so you can price the exposure.
A real coverage check runs both ways. One side protects your budget; the other keeps the comparison fair.
The SOW items a bidder never priced. These are the change orders waiting to happen: the unquoted line you only notice once the work is underway and the competition is gone. Bid Reasoner lists them per bidder, so a suspiciously low total gets explained before it gets awarded.
The items a bidder quoted that weren't in your SOW. Some are genuine value-adds worth keeping; some are padding, or work meant for a different package. Either way you need to see it, so you're not comparing a stripped bid against one that priced in extra scope.
Once gaps and creep are visible, you send the gaps back as clarifications, re-level on matched scope, and compare totals that actually cover the same work — so the lowest responsible number wins, not the most incomplete one.
Coverage gap analysis is one part of the full leveling pass. It pairs with subcontractor bid analysis — the per-bidder read — and feeds side-by-side bid comparison, where matched scope makes the totals comparable. For the whole workflow, see bid leveling software.
Coverage gaps are checked inside the same engine that levels, scores, and risk-flags every bid.
scoring dimensions per bidder — price, scope, schedule, compliance, performance, risk.
decision modes, from Lowest Responsible Bid to Best Value to Scope Completeness.
deterministic risk rules with fixed numeric thresholds — unbalanced, outlier, and front-loaded flags.
US states supported — bidders normalized against the peer median, no government pricing data required.
| Excel / manual | Generic bid software | Bid Reasoner | |
|---|---|---|---|
| Matches differently-worded line items | By eye, line by line | Exact-text only | Normalized & matched |
| Lists what each bidder didn't quote | Manual diff | Rarely | Per-bidder gap list |
| Flags extra scope a bidder added | Easy to miss | No | Creep flagged both ways |
| Prices an unquoted line | Look it up yourself | No | Against peer median |
| Turns gaps into clarifications | Retype an email | No | Suggested, ready to send |
A scope gap is a line item in your scope of work that a bidder did not quote. The number looks complete, but a piece of the work isn't priced — so the lowest total can be the bid that simply left the most out. Bid Reasoner maps every bidder against your SOW and flags exactly which items each one missed, so you compare bids on the same scope instead of on whoever excluded the most.
Bid Reasoner reads each bid PDF, extracts and normalizes every line item, and matches it to your scope of work — even when bidders use different wording, units, or item numbers. It then lists, per bidder, every SOW item that bidder didn't quote, so you can see coverage gaps across all five to fifteen bids in one view rather than diffing spreadsheets by hand.
A scope gap is work that was missing from a bid before you awarded; a change order is what you pay for that same missing work after you've signed. They're the same line, caught at two different times. Finding the gap pre-award lets you send it back as a clarification and re-price it competitively; finding it post-award means you eat it at the winning sub's number.
Yes. Scope gap analysis runs in both directions. Alongside the items a bidder missed, Bid Reasoner flags scope creep — items the bidder quoted that were not in your SOW — so you can tell genuine value-adds from padding, and you don't compare a stripped-down bid against one carrying extra work it priced in.
No. Scope gap analysis compares each bidder against your own scope of work and against the peer median of the bids you received, so it works in any US state with no government data required to start. Built-in DOT baselines for select states (currently New York and New Jersey) are a head start where they apply, not a prerequisite.
No. Bid Reasoner is not takeoff or quantity-estimating software. It analyzes the subcontractor bids you receive — leveling them, scoring them, and checking each one against your scope — rather than generating quantities or your own estimate. It complements estimating tools like HeavyBid and B2W.
Bring one package's bids and your scope of work. We'll map them, flag every gap and extra item, and show you what the low bid actually leaves out — on the call.