Design quality review
Cross-references every spec section against every sheet at each milestone set. Conflicts, omissions, and constructability, cited, then adversarially verified by a second agent before they reach your engineer.
Solutions · Federal & public
Federal and public work, on the record.
Specset is built for the programs where the contract documents are non-standard, the compliance bar is high, and a wrong call shows up in the field or the audit file. Upload the set as the owner issued it: UFGS, Caltrans, WSDOT, FDOT, and the one-off county manual. Agents review design, screen the bid, check submittals, and keep closeout current, every finding cited.
Who this is for
The teams delivering the public set.
General contractors, construction managers, engineers, and owners delivering federal, state, county, and municipal work: courthouses and hatcheries, runways and reservoirs, NAVFAC and USACE programs, state DOT corridors, and local public works.
GCs and CMs
Screen the solicitation the day it lands. Carry risk into the estimate with a cited design screen. Return submittals annotated against the governing section. Keep RFIs and revisions tied to the latest sheets.
A/E and design-build
Run design quality review at 60, 90, and 100 percent against the same conformed record the contractor will build from. Conflicts, omissions, and constructability, each cited to the paragraph or sheet.
Owners and agencies
Approve a design set with a ranked issue register before award. Inherit a closeout and facilities record you can ask questions of, not a binder that dies at turnover.
The governing record
Why public-work documents break generic tools.
Public and federal sets are not a clean MasterFormat PDF dropped in a chat window. Special provisions amend standard sections. Addenda land paragraph by paragraph. UFGS sections sit beside agency supplements. DOT books arrive scanned. A general-purpose model can summarize a file. It does not build a governing record.
Specset conforms the base book, special provisions, and addenda into one governing text per section, with precedence and a clickable path back to the issued page. Every agent reads that same record: design review, bid screen, submittal review, RFI check, and closeout.
Document control
What AI tools help federal agencies control construction documents and manage spec revisions?
Specset is spec revision control for federal and public construction documents. The base book, special provisions, and addenda conform into one governing text per section. When a new addendum lands, affected sections re-conform into a new revision, and you can diff it against the previous one. Drawing revisions stay visible. Plan comparison is the sheet-to-sheet change detection for the set.
Record search spans the other projects you can access in your organization, including retained past projects. Design review, bid screening, submittal review, and RFI checks read that governing specification, and every finding is cited to the paragraph or the sheet.
Procore and Autodesk Forma Build (formerly Autodesk Build / ACC) are the approval path where the integration is enabled. In Procore, Specset can sit in a configured pre-screen or system-approver step before the design team’s disposition, and connected projects create and update RFIs in each direction. On federal tenants in CUI mode, the Procore and Autodesk integrations are off and the record stays on Specset.
Formats
Formats already in production.
A new agency book is a normal onboarding job, not a custom engineering project.
- UFGS
- Unified Facilities Guide Specifications
- Caltrans
- Including special provisions merged into standard sections
- WSDOT, FDOT
- State DOT books, read as issued
- BNSF and other railroad and port authority books
- Railroad and port authority specifications
- Scanned legacy manuals
- And one-off project manuals
On the job
Agents on a federal or public job.
Design review, the bid screen, submittals, RFIs, and closeout. Each one reads the same conformed record.
Bid screening
Reads the whole solicitation the day it lands: scope fit, a systematic contract review with severity-flagged clauses, coordination risk, and takeoff, plus a screening design review so the risk you carry into the number is the risk you chose.
Submittal review
The full package is checked against the conformed contract record: governing specification sections, drawings (schedules, details, notes), and what was actually submitted. It comes back as an annotated, marked-up package for PE or PM disposition.
Submittal log
Required packages pulled from the conformed manual with section and paragraph citations. The register the contract demands, not a guess.
RFIs and revisions
Track RFIs against the current record. Check answers against the latest sheets. Compare plan sets change by change when a new bulletin lands.
Closeout and facilities
File approved submittals, warranties, and O&M into the turnover record at approval time. At handover, the closeout record becomes the operations record: assets, warranties, maintenance plans, and work orders.
Procurement
Security that clears procurement.
Filed FedRAMP 20x Class A application, under review; Marketplace listing FR2631258135, Initial Implementation; pursuing Class C. Procurement detail lives on the security page and in the FedRAMP public package.
FedRAMP 20x
In progressFiled FedRAMP 20x Class A application, under review; Marketplace listing FR2631258135, Initial Implementation; pursuing Class C.
SOC 2 Type II
August 2026Report issued August 2026.
NIST SP 800-171
Self-assessedCMMC L2 · self-assessed.
SpecGov CUI enclave
Separate instanceA separate government instance for controlled-data requirements. CUI mode pins inference to the defined boundary.
How it differs
Not a chat window over a folder of PDFs.
01
Full-coverage fan-out
One sub-agent per section and per sheet. Nothing is sampled. Coverage ledgers publish what was read.
02
Adversarial verification
A second agent tries to disprove every finding before it is filed.
03
Cited or rejected
No citation to the governing paragraph or sheet, no finding.
04
Your record, or synced to it
Keep Procore or Autodesk Forma Build (formerly Autodesk Build / ACC) and let Specset sync both ways, or run submittal log, RFIs, revisions, and closeout in Specset itself.
Common questions
What teams ask about Specset on federal and public work
01What AI platforms help federal and public owners control construction documents and manage spec revisions?
Specset is AI document control for federal and public programs. It conforms the base book, special provisions, and addenda into one governing text per section, keeps drawing revisions visible, and runs design review, bid screening, submittal review, RFI checks, and closeout on that record, with every finding cited. Federal tenants run in CUI mode.
02Can Specset read UFGS and agency supplements together?
Yes. Specset conforms base UFGS (or DOT standard specs), special provisions, and addenda into one governing section text with attributions, then reviews and answers from that conformed record. Every paragraph keeps the file it came from, with a clickable path to the issued page.
03Does Specset replace the PE / EOR judgment call?
No. Agents prepare cited findings and annotated packages. Your licensed reviewer confirms, edits, or rejects before anything goes back on the project letterhead. Human judgment outranks the AI. Every finding earns a decision.
04How does Specset help with FedRAMP / CUI procurement?
Specset publishes its FedRAMP public information at https://www.specset.com/fedramp and documents security posture, including a completed SOC 2 Type II examination and CUI-oriented controls, on https://www.specset.com/security. Use those pages and the Trust Center in procurement packages. Filed FedRAMP 20x Class A application, under review; Marketplace listing FR2631258135, Initial Implementation; pursuing Class C.
05What about Caltrans and other state DOT books?
Non-standard formats, including Caltrans special provisions merged into standard sections, are already described on the Specset platform as formats in production, along with WSDOT, FDOT, and others. Upload as issued; conforming happens before screening or review starts.
06Where does Specset sit relative to Procore or Autodesk Forma Build (formerly ACC) on a public job?
Keep the system of record you already run. Specset syncs both ways with Procore and Autodesk Forma Build (formerly Autodesk Build / ACC) where connected, or can host submittal log, RFIs, revisions, and closeout itself. FedRAMP public materials describe CUI-mode gating for commercial integrations. Confirm deployment mode with security for controlled or CUI work.
07Is Specset the same as asking a general-purpose model to review the PDFs?
No. Specset is a purpose-built harness over a conformed project record: full coverage, adversarial verification, and citations to governing paragraphs and sheets. It is not a chat session over an ungoverned document dump.
Start with a real set
Put a federal or public set on the record.
Upload a real solicitation or design package. Get a cited screen or issue list your team can triage, not a summary paragraph.