The AI that reads your project, not just your documents.
Every workflow on Specset stands on the same two layers: a governing record that holds the whole project, cross-referenced, and agents that do the work on top, citing that record for every claim they make.
One governing record, cross-referenced.
The project manual, the sheet set, addenda, submittals, and RFI answers are parsed into a single linked record. Not a folder of PDFs with search on top: a structure that knows what references what, and what governs what.
2.2 PERFORMANCE. Units shall meet the scheduled airflow and filter efficiency at the listed external static pressure.
Provide filter racks sized for the scheduled MERV 13 final filters. Addendum 2
Include the manufacturer start-up report before final acceptance. Addendum 3
Spec sections keep their hierarchy and schedules keep their rows. Drawings are read as geometry: measurements, symbols, and clearances, not OCR text. Caltrans, WSDOT, FDOT, and MasterFormat structures are first-class.
Section references, callouts, and schedule rows link into a graph that spans the sheet set. Follow a reference and the record opens the governing paragraph, on the page it lives on.
Addenda, special provisions, and RFI answers stack in precedence order with a full audit trail. The record always answers with what governs now, and shows you what it superseded.
Agents that check their own work.
Reviews run as fan-outs over the record: one agent per spec section, one per sheet, so coverage is structural, not sampled. Then an adversarial pass tries to break every finding before you see it.
Structural, not sampled.
Every run publishes its ledger: which sections, which sheets, which pages were read. Sampled search never claims completeness on a Specset project. Coverage scans do, across document sets up to 20,000 pages.
A second agent tries to break it.
Every finding faces an independently scoped verifier whose only job is to disprove it against the plans and specs. What survives arrives verified. What does not is archived with the reasoning.
Your judgment outranks the AI's.
Accept, dismiss, or annotate any finding. The record keeps both sides of that call, so six months later you can see not just what the AI said, but what your team decided.
Trust, but verify.
A finding cannot be written into the record without citing what governs it: the spec paragraph, the schedule value, the RFI answer. Uncited claims are rejected at write time. Checking the AI takes one click, not an afternoon.
Filter requirement conflicts with the schedule.
Section 23 73 00 §2.2 requires MERV 13 filters. The mechanical schedule lists MERV 8 for AHU-1.
Feeder schedule calls for cable no section specifies.
Sheet E-101 calls for a cable type that no section in the Division 26 package specifies.
Submitted product deviates from the approved basis.
The submittal shows a two-fan configuration. The requirement calls for N+1 redundancy at design airflow.
Every citation opens the governing paragraph, on the page it lives on
Built to fit the process you already run.
Teach Specset your firm's checklists, QA programs, and review criteria as skills, then run them with a slash command. Outputs land in your formats: the Excel log your PMs live in, your proposal template, your closeout forms.
- Your QA checklist becomes a review pass with the same coverage guarantee
- Your division-of-work rules become how findings get routed
- Your exports come back in the templates your clients already expect
Reviews and answers reach your team in the tools the project already runs on. No rip-and-replace.
One platform. Every review runs on it.
The record and the agents are the same under every workflow. Pick the one your week needs.
Bid-time screening
The risk screen that reads the whole package before you price it.
→PreconDesign quality review
A full review across the spec book and sheet set, before the errors reach the field.
→BuildSubmittal review
Every submittal checked against the section that governs it, deviations flagged with citations.
→BuildPlan comparison
What changed between revisions, sheet by sheet, with every delta linked to what it touches.
→Every phaseAsk the record
Questions answered from the governing record, cited to the paragraph.
→Close outO&M handoff
The closeout record becomes the operations record: assets, warranties, and maintenance plans.
→Watch it read your project.
Book a demo and we'll run it on your documents. Or start a self-serve pilot: upload a package and get a design review back in hours, not months.