Every estimating tool that reads drawings has to answer one question before it answers any other: where does the machine stop and the contractor start. Most tools answer it by accident, discovering the boundary through the first few jobs that go wrong. AsBuilt answers it as a design rule, written down before the first line of the takeoff engine:
Scope and quantity are extracted. A price is never invented.
That sentence is the shortest description of the product. This article is the long one.
What it reads
A drawing set lands and the clock starts. AsBuilt reads that set, native or scanned, for scope and quantity, trade by trade, and cites every extraction back to the sheet it came from. Sheets photographed on site from a phone feed the same pipeline, because the version of a drawing that matters is often the one on the table, not the one in the email.
Alongside the takeoff runs drawing and spec conflict detection. Per the estimators the system is built for, the number-one source of estimating errors is not arithmetic. It is two documents that quietly disagree: a detail on a sheet that the specification contradicts, discovered on site three months after somebody priced one of them. The system flags the conflict before bid day, cited by sheet, while it is still a question rather than a change order.
Neither of these is the judgment a contractor gets paid for. Both of them stand between the estimator and the number.
What it refuses
It does not price the work.
This is a limitation the way a load rating is a limitation: deliberately chosen, and the reason the thing can be trusted. Three arguments hold it in place.
A quantity is checkable. A price is not.
An extracted quantity carries a citation: this count came from this sheet, at this detail. An estimator can verify it in seconds by opening the sheet, and disprove it just as fast. It is a claim about a document that the document can settle.
A unit price is a claim about the world: this crew, this market, this month, this subcontractor's backlog, this building's loading dock and freight elevator schedule. There is no sheet to open. A generated price cannot be checked; it can only be trusted or overridden, and a number that can only be trusted is a number nobody should have to trust.
The pricing is the contractor's judgment, and their liability
A general contractor's margin lives in knowing which subs are hungry this quarter, which scope always runs over, and what a difficult site costs that a drawing does not show. That knowledge is the business. A system that generated prices would be substituting its ignorance for the estimator's expertise on exactly the axis where the expertise is worth the most, and the contractor, not the software, signs the bid.
There is a failure mode particular to generated numbers, too: they are anchoring. A plausible price on a screen is very hard to argue with under bid-day pressure, and the number that gets submitted is more often adjusted from the machine's guess than reasoned from the job. Refusing to produce the number keeps the judgment where the liability is.
Wrong in one direction loses the job; wrong in the other loses money
Estimating has an asymmetry no general-purpose model handles well. Price high and the bid is dead: no feedback, no learning, just a loss. Price low and you win the job and lose money on it for a year. Both failures are expensive and only one of them is visible at the time. This is not a domain where a confident approximation is better than an honest gap.
The same rule, applied everywhere else
The takeoff engine is not the only place the rule shows up. It is the house rule, and the other engines obey it.
- Compliance dates are computed, not estimated. Where a job touches prevailing wage or public funding, certified payroll cadence and lien-filing deadlines are each computed from the statute they come from and cited by section. A deadline is a fact with a source, so it gets one. And for a contractor whose work does not touch public funding, the whole engine switches off cleanly rather than producing requirements that do not apply. An unnecessary compliance warning trains people to ignore the necessary ones.
- An RFI log never guesses who is holding the answer. The submittal log carries a backward pass to the architect's due date; the request log tracks the actual holder. "Probably with the architect" is not a status.
- AIA billing tracks what has been earned, against the schedule of values, on the standard G702 and G703 forms, not what has been billed, which is a different number and the one that causes arguments.
- COI Watch tracks certificates to their expiry dates and reminds before an expired certificate becomes an exposure on an active site. A date, from a document.
- Every signature carries a certificate (who, when, from where) because a signature without provenance is a picture of a signature.
Read that list and the pattern is consistent: the system does the work that is mechanical, citable and boring, and hands back everything that requires judgment, with the source attached so the judgment can be made quickly.
Why citation is the actual feature
The temptation with any document-reading system is to measure it on coverage: how much it extracted, how fast. The better measure is how long it takes an estimator to audit what it extracted.
A takeoff with no citations has to be re-done to be trusted, which means it saved nothing. A takeoff where every quantity names its sheet can be spot-checked in minutes and accepted or corrected line by line. Citation is what converts an output into something a professional can put their name on, and putting their name on it is the entire transaction.
Where it runs
The first deployment is live at Integral Construction of NY, a certified MBE general contractor building corporate interiors. Estimating, purchasing and billing are in daily use, shaped in direct conversation with the principal and the estimator who run the bids rather than from a spec sheet. Integral's own work is private, so the compliance engine sits unused there, on by default for the next contractor whose jobs touch prevailing wage.
The full system is on the AsBuilt page: estimating, purchasing, AIA billing, submittals and RFIs, e-signature, and a separate complete desk for the estimator so purchasing never bottlenecks on one screen.
The system reads the drawings. The pricing stays yours.