Turn a drawing set into defined construction scopes, then surface the work that no trade owns, the work two trades both think is theirs, and the conditions too ambiguous to price — before contracts are written.
Why it matters
A quantity that is off by a little costs a little. Work that nobody carried in their number becomes a change order, a schedule impact and an argument about whose scope it was.
A takeoff tells you how much there is. Scope gap analysis tells you whether every condition in the documents has a trade responsible for building it.
Ambiguity is cheapest to resolve while the subcontracts are still drafts. Once the package is awarded, the same question costs a negotiation.
Capabilities
Elements, assemblies and quantities from the set are organized into the construction scopes a project is actually bought out in — not just a division list.
Conditions the documents describe but no trade package covers: the transitions, accessories, backing, flashing and cleanup scope that falls between bid packages.
Where two packages both appear to include the same work — the duplicate cost you pay for once in the bid and twice in the field if nobody catches it.
Details that stop short, notes that defer to others, assemblies referenced but never drawn, and 'by others' language with no other — each surfaced with where it appears.
A per-trade view of conditions identified, conditions assigned and conditions in question, so you can see coverage across the job at a glance.
Gaps carry an indication of exposure, so the conversations that matter happen before award instead of after the first RFI.
Each gap comes with the question that resolves it, ready to go out as a bid clarification, an addendum request or an RFI to the design team.
When a revised set lands, run it again: gaps that closed, gaps that remain and gaps the revision introduced, compared side by side.
How it works
Drawings and specifications as issued, across architectural, structural, civil and MEP. Quantity takeoff and scope analysis run against the same understanding of the project.
The documented conditions are grouped into construction scopes and mapped against the trade packages the project will be bought out in.
Unassigned work, overlaps, ambiguity and 'by others' language are called out with their location in the set and the question that resolves each one.
Take the clarifications into the bid process, tighten the packages, and rerun on the next issue to confirm nothing reopened.
Coverage
The gaps that cost money are rarely in the big items. They live in the transitions between packages, and in the language a set uses when a decision has not been made yet.
Elements and quantities analyzed
Construction scope reviewed
Developments analyzed
FAQ
Every solution runs on the same project model, so the work you do here carries forward into everything that follows.
Schedule Private Demo