The silence
What the documents don't say — the silences that cost you a bid
The hardest part of reading a bid isn't what's on the page. It's what's missing. Every tool in this category will summarize what the documents say — the obligations, the dates, the line items. The money is in what they don't say: the requirement that's implied but never stated, the schedule that's referenced but never attached, the scope that sits on a boundary nobody owns.
BidScan reads your package — naming anything it could not read rather than passing over it — and flags those silences plainly: not as a guess, but as a question to run down before you price. Silence is a finding. That's the one lit gap in our mark: the thing nobody told you, made visible.
A silence is a gap between what's required and what's stated
Most scope problems aren't hidden in fine print. They're hidden in the absence of print. A spec says "bonds as required" and never names the amount or the form. A supplementary condition says the job is prevailing-wage and never attaches the rate schedule. A drawing references an equipment pad that no division claims. Nothing on the page is wrong — there's just nothing there, and the nothing is the obligation.
Tools that read what the documents say will sail right past these, because there's no sentence to extract. You only catch a silence by knowing what a complete package should contain and noticing the slot that's empty.
Three silences that show up again and again
These are the recurring ones — the kind BidScan is built to surface. Each is shown as a representative example, not a specific job.
1 · The bond that's required but never specified
The package tells you bonds are required. It doesn't tell you the penal sum, the acceptable form, the surety rating, or when they're due. If you price on the assumption it's a standard payment-and-performance pair and the owner wanted a maintenance bond on top, that's real money you didn't carry.
“The successful bidder shall furnish bonds as required by the Owner.”
2 · The wage determination that's referenced but not attached
Public work says it's subject to prevailing wage and points to a determination "in effect for the locality." The actual rate schedule — the classifications, the fringe, the effective date — isn't in the package. The labor number you carry depends on a document the bid never handed you. Silence, and an expensive one.
“All work is subject to the prevailing wage rates in effect for the project locality.”
3 · The scope referenced across a division boundary
An item gets mentioned in Division 1 and assumed to live in someone else's division — the equipment pad coordinated "with the work of Division 26," but the concrete itself never scoped to a trade. On a boundary like that, every bidder quietly assumes it's the other guy's. The one who assumed wrong eats it.
“Coordinate the equipment pad with the work of Division 26.”
Why public works and landscape feel it hardest
The silences bite hardest where the obligations are statutory and the packages are uneven — public works and site/landscape work. Prevailing wage, bonding, DBE participation, certified payroll: each is a requirement that may be implied by the project type and never spelled out in the documents you were handed. Miss one and you either eat the cost or pull your bid. Catch it before you price and it's just a number you carried.
Naming the silence, without inventing the requirement
There's a discipline here that matters. BidScan flags a silence as a question — "the documents don't state the bond form; confirm before pricing" — it does not invent a requirement and assert it as fact. Where the package goes quiet, it says so plainly and points to where the quiet is. Every finding traces back to a place in your documents, including the findings that are about an absence. We don't fill the gap for you. We make sure you see it.
Common questions
What is a scope gap in a bid?
A scope gap is work that's your responsibility but isn't clearly assigned to a trade in the documents — often sitting on a boundary between divisions, in an exclusion, or implied by an addendum. It's the most common source of a bid that looks complete but isn't.
What is an unstated obligation?
An unstated obligation is a requirement the project carries that the documents never spell out — a bond whose form isn't named, a wage determination that's referenced but not attached, a permit nobody assigned. It's real, and it's a cost, even though no sentence in the package states it.
How is this different from bid leveling?
Bid leveling compares many subcontractor bids after they come in. Finding the silences happens earlier — reading your one bid package before you price it, so the gaps and unstated obligations surface while you can still account for them.
Does BidScan invent requirements that aren't in the documents?
No. Where the documents go silent, BidScan flags the silence as a question to confirm and points to where the gap sits, rather than filling it with a guess. It reports what the documents say and what they leave unsaid; confirming a requirement is still your call.
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.