AI submittal review and construction document control.

Keep Procore or Autodesk Forma Build (formerly Autodesk Build / ACC) as the system of record. Specset adds cited review against the governing spec sections, then returns the review status, summary, and linked review record into Procore or Autodesk Forma Build.

Product data, shop drawings, mix designs, sample records, safety plans, and closeout packages. Each page group in the package generates its own checks, so mixed or unexpected content is still reviewed rather than skipped. Built-in categories also include test and inspection reports, certificates, O&M manuals, and warranties, and custom submittal types are supported.

The marked-up submittal itself: an annotated PDF with findings drawn at the page location, plus a consolidated issue list with citations and a suggested disposition. Your PE or PM reviews, edits, and makes the call.

The conformed contract record: the governing specification sections with addenda and special provisions applied, plus the drawings, including schedule values, details, and notes. Checks run spec-first, drawing-first, and submittal-first so gaps in any direction surface.

See why a chat window over a folder of PDFs is not document control.

Yes. Specset checks the package against each applicable paragraph of the governing section, with addenda and special provisions applied, and against the drawings. It runs spec-first, drawing-first, and submittal-first, cites every finding to the paragraph and the sheet, and flags required information that is absent as Missing Info. Your reviewer makes the call.

Yes. Sync the package in from Procore or Autodesk Forma Build (formerly Autodesk Build / ACC), run the review, and return the status, summary, and linked review record when the decision is ready. The submittal workflow stays where it already lives.

Your reviewer, always. Specset consolidates overlapping findings, challenges each issue with a second AI, and suggests a disposition, but approve, revise and resubmit, and reject decisions belong to the engineer of record.

Minutes for a typical package, and the review covers the full package against every applicable requirement. Teams use it to return a complete first-pass review the same day the submittal arrives.

A general-purpose model can summarize a PDF. Specset checks the full package against the conformed contract record: governing sections with addenda and special provisions applied, plus drawings. It runs checks spec-first, drawing-first, and submittal-first, adversarially verifies findings, and returns an annotated PDF with issues drawn on the pages. Your reviewer still owns the disposition.

Findings are marked on the submitted pages at the location they apply, numbered, and compiled behind a clickable table of contents, the way a project engineer would return a package, including a path for your firm’s stamp. The deliverable is the reviewed submittal, not another dashboard.

Product data, shop drawings, mix designs, sample records, safety plans, and closeout packages. Each page group generates its own checks, so mixed or unexpected content is still reviewed rather than skipped.

Yes. Specset reviews against the conformed record. UFGS, Caltrans including special provisions, WSDOT, FDOT, and other formats already in production are conformed before checks run.

UFGS submittal compliance review

Overlapping findings collapse into one reviewer-ready issue. A second, independently scoped AI tries to disprove each issue before it enters the active queue. Rejected findings stay auditable. Your reviewer confirms, dismisses, edits, or reopens. Reasoned dismissals can carry into later reviews.

Yes. WSDOT, Caltrans with special provisions, FDOT, BNSF and other railroad books, and UFGS are formats already in production. The book is conformed before the checks run.

Caltrans and DOT conformed spec books