/ Construction · Scope Gap Detection
The exclusion was on page six. You found it at change order.
Every sub scopes differently, and the gaps between what they each include only show up when someone reads all the fine print against each other — under bid-day pressure, that's exactly the reading that gets skipped. Revelry does that comparison on every quote and flags the mismatches with the source language cited.
/ The Real Cost
A gap found after award isn't a discount. It's your margin.
Before award
Gaps surfaced while you can still price them
A flagged exclusion before award is a question for the sub. The same exclusion after award is a change order you eat. The whole value of detection is the timing.
Cited, not guessed
Every flag points at the language
Each mismatch links the exact wording in each quote — "included" in one, silent in another, excluded in a third. Your estimator reads the flag, not five full quote packages.
We won't put a dollar figure on "what you would have missed" — that's not traceable, and we only claim what is. What's traceable: every gap, flagged and cited, before the award decision instead of after it.
/ The Bigger Picture
Scope gaps are step two of bid leveling.
Detection runs inside the leveling workflow: quotes normalized to your template first, then inclusions and exclusions mapped against each other, then the leveled tab your estimator awards from.
Bring the bid that burned you.
Run last quarter's quotes through on the demo. See what it flags that the tab missed.