Takeoff answers a counting question: how many linear feet, how many fixtures, how many cubic yards. Scope qualification answers an ownership question: which trade is carrying this, and what did nobody price at all.
They fail differently. A takeoff error gives you a wrong number for work you knew about, so you're off on the number (quantity x unit rate). A scope gap gives you no number at all, because the work was never named on anyone's sheet. The second one is what turns into a change order.
Provision does scope qualification. We do not do quantity takeoff. If quantities are your bottleneck, buy a takeoff tool! There are several really good ones. If your bottleneck is that a $400K item wasn't in anybody's package, that's a different purchase.
Takeoff converts drawings into measured quantities. The tools do it well. Load a set, the software identifies and counts conditions, you get quantities you can price.
The failure mode is bounded. A wrong count means you priced a known item incorrectly. That's recoverable, it usually surfaces in review, and a second estimator catching it is a normal part of the workflow.
What takeoff won't tell you is whether the item belonged in that package to begin with. It counts what you point it at. It has no opinion on what you didn't point it at.
Scope qualification is deciding, for every element on the project, which subcontractor package carries it and how that obligation gets written. It produces the scope sheet, and downstream, the scope of work attached to each subcontract.
This failure mode has no ceiling. Nobody priced the item. There's no wrong number to catch, because there's no number. It surfaces in the field, after buyout, when the sub who could plausibly own it points out that it wasn't in their scope. By then you're negotiating, not estimating.
The Scope Gap Playbook, built from 200+ GC interviews, tracks where these land: $400K of missed roof cover board on a $50M project, recovered only because the sub made a relational concession. A $45K stone-depth mismatch between civil and architectural drawings on one slab. $10K of mass timber destroyed in a lay-down yard, because no clause required material protection on site.
None of those are counting errors. Every one is an ownership question nobody asked.
The two get conflated because both problems start from the same input, a drawing set, so tools in both categories market themselves on reading drawings.
Does: reads the full project set together, drawings plus specifications plus contracts plus tables, notes and addenda. Scope Agent generates trade-by-trade scope packages where every line traces to the exact page and section it came from. It flags scope that appears in the documents but lands in no package, and it re-runs when an addendum arrives instead of starting over. 97% match accuracy on scope item extraction against our internal validation dataset, where a human estimator on the same exercise came in at 91.3% and took about four days.
Doesn't: quantity takeoff. No measured counts, no linear feet, no cubic yards. We don't produce a priceable quantity set and we're not trying to.
Doesn't: replace your estimator's judgment. The output is a reviewable draft with citations. Someone who knows the job still owns the number.
Need both? Run both. They sit at different points in the workflow and they don't conflict.
Ask what went wrong on your last three change orders.
If the answer is "we counted it wrong," your bottleneck is takeoff and measurement discipline.
If the answer is "we assumed the mechanical sub had it" or "it was in the specs but not in anyone's package" or "the drawings and specs disagreed and nobody caught it," your bottleneck is scope qualification. A better takeoff tool won't touch that.
Most teams we talk to have takeoff reasonably solved and have never systematically addressed the second category, because senior people have always done it from memory. That works until the senior person is on three pursuits at once. The trade-by-trade breakdown is a decent way to pressure-test whether your packages cover the interfaces.
No. Provision does scope qualification: what's in scope, which trade owns it, and what's missing. It doesn't produce measured quantities.
Yes. They solve different problems at different points in the workflow.
Trade-by-trade scope packages, with every line traced to the drawing or spec section it came from. Exports to PDF, Word, and Excel.
Both, together with contracts, tables, notes, and addenda. Reading drawings against specs is where most scope gaps surface.
The review re-runs against the updated set. You don't start over.
General contractors running preconstruction workflows. See how GCs use it, or what it means for subcontractors receiving the packages.
Provision generates trade-by-trade scope packages with citations from your full project set.
See Scope AgentMore Articles
