What it
actually produced.
Not a screenshot of a dashboard. Three artifacts the system made against real construction documents, including one it decided was not worth showing anybody. Project, building and trade names are removed. Everything else is exactly what came out.
The hard part was never finding things. It was not reporting the normal ones.
A conflict, with both sheets quoted.
Read from a nineteen sheet architectural bid set. Every full height partition on the job is drawn one way in the legend and specified another way in the partition schedule. Two subcontractors pricing this set can price two different walls, and neither is wrong.
A-100 · legend
FULL HEIGHT GYPSUM PARTITION, TYPICAL FOR ALL PARTITIONS: NEW 3-1/2" THICK 18 GAUGE METAL STUD AT 16" O.C., 5/8" GYP BD BOTH SIDES OF WALL
A-601 · schedule
PARTITION TYPE #2 FULL HEIGHT PARTITION: 5-5/8" METAL STUDS AT 16" O.C., ONE LAYER 5/8" GYP BD ONE SIDE AND (2) LAYERS 5/8" GYP BD THE OTHER SIDE
It does not decide which is right. It names both sheets, quotes both, and stops. The estimator opens the two sheets and settles it in a minute, which is a minute rather than a change order.
Raised on both readings of the set · architectural
A conflict it threw away, and why.
The same reader found two different editions of the same code cited on one sprinkler set. It did not report it. The reason is a sentence a client said out loud, and it is stored against the rule so that anyone who deletes the rule has to argue with a person.
SP-001 · general note
AUTOMATIC SPRINKLER SYSTEM SHALL COMPLY WITH SEC. 903 & APPENDIX Q OF NYC BUILDING CODE & NFPA 13-2016
SP-002 · design criteria
AREA COVERAGE PER SPRINKLER SHALL BE IN ACCORDANCE WITH 2013 NFPA STANDARD NO. 13.
Set aside, because
Multiple code citations on one set are normal practice, not a contradiction. Estimating lead, on an earlier run: “This just means that trades have to follow code requirements. That’s normal.”The first time this reader was pointed at a live set it produced three findings and not one of them was real. Every rule that screens a finding out carries the client line that put it there. That is why the list above is short, and why it gets opened.
Suppressed automatically · fire protection
The line a purchase order carries.
A subcontractor prices a job, an addendum lands, and later they say their number never included it. The fix is not a better email. It is one line above the signature, so the acknowledgement is part of what they signed.
Addenda incorporated:
Addendum 1, issued 12 June 2026
Addendum 2, issued 6 July 2026
This purchase order includes the addenda listed above. The subcontractor’s price is understood to incorporate them.
Eight purchase orders went out on one job before this line existed. It costs nothing, it is printed from the addenda already on the job record rather than typed, and it turns the most common dispute in buyout into a document somebody signed.
Printed on the purchase order, above the rider
Why this page is hard to copy.
Specimen 01 needs a system that can read a drawing set. Specimen 03 is a decision anybody could make tomorrow, and almost nobody has. Specimen 02 needs something rarer: a client who told us our findings were worthless, and a rule written down in their words so it stays that way.
A competitor can build the first and copy the third by Friday. The second is a year of being told no by people who run jobs, and it is the only reason the list an estimator opens is short enough to open.
Specimens are real output from live readings, with project, building and trade names removed. Nothing on this page is illustrative.