Federal and state jobs do not arrive as a tidy MasterFormat PDF. Specset takes UFGS, Caltrans special provisions, WSDOT, FDOT, railroad and port authority books, and scanned manuals as issued, merges amendments into one governing section text, and runs design, bid, and submittal agents on that record. Every finding is cited back to the page.
Specset checks shop drawings, product data, and drawings against the conformed UFGS sections (brackets resolved, project amendments applied) and returns cited findings. That check does not replace agency review or the engineer of record.
On USACE and NAVFAC work, the review reads UFGS submittal procedures after the project book is conformed. SpecsIntact-style tailoring and editing happen at design. Specset reviews the construction-phase package against that tailored, conformed result. It works alongside SpecsIntact and does not replace it.
UFGS is the Unified Facilities Guide Specifications. On a real job the guide spec is not the whole contract. Agency supplements sit beside UFGS sections. Addenda land after the set is printed. Special provisions amend paragraphs deep in the book.
Checking a submittal against UFGS means checking it against the governing section. Base language, supplements, and addenda merge into one text. Every paragraph keeps the file it came from. The package (product data, shop drawings, samples) is then reviewed against that text and the current sheets. Findings come back cited to the paragraph or the page.
The Specset Cloud Platform service description names UFGS compliance checking. The platform flags potential issues and returns cited answers drawn from the customer’s own project documents. That check does not replace agency review or the engineer of record. Licensed reviewers still own the stamp.
Special provisions amend paragraphs deep in the standard book. Addenda land after the set is printed. A keyword search, or a chat over the wrong revision, misses what actually governs. Non-standard is the standard. Conforming happens before screening or review starts.
Specs, drawings, addenda, and special provisions, in whatever shape the owner published them. No template reformatting required to start.
The base section and its amendments are applied oldest to newest, as the directive language is written: replace this value, add this paragraph, delete that subsection. The result is one governing text per section, with attributions and precedence. Every paragraph keeps the file it came from. Click through to the issued page.
Drawing revisions stay visible so RFIs and submittals answer against the current set.
Design quality review, bid screening, submittal log and review, and closeout read that same record. Conforming happens before screening or review starts.
The manual tells you the standard book. The project tells you what amended it. Conformed software is the merge of those two before anyone reviews a submittal or prices a bid.
Caltrans, FDOT, and WSDOT manuals publish the standard specifications and how the book is organized. On a live project they are not the whole contract. Special provisions, addenda, and the project manual sit beside the standard sections. Reading them as separate PDFs leaves the amendment in a different file from the paragraph it changes.
Conformed software merges the base book, the special provisions, and the addenda into one governing text per section before screening or review starts. Caltrans special provisions are merged into the standard sections they amend. WSDOT and FDOT books are read as issued. Search and review then run on what governs now, with a click back to the issued page.
A new format is normal work. Upload the book as issued.
General contractors, construction managers, design teams, and owners working from UFGS or a state DOT set.
Bidding and building federal and state work. The book arrives with special provisions and addenda already in force. Review runs on the governing section, not on a search of the wrong revision.
Issuing milestone sets against UFGS or DOT specs. Design quality review reads the same conformed record the team will build from.
Approving sets and inheriting closeout on public programs. Findings stay cited to the paragraph or the sheet.
Yes. A submittal is checked against the conformed UFGS section and the current sheets. Each finding cites the governing paragraph or page. Specset does not replace the reviewer who owns the stamp.
Design quality review, bid screening, and closeout read that same conformed record on federal and public programs.
Federal solutions →Specset checks shop drawings, product data, and drawings against the conformed UFGS sections (brackets resolved, project amendments applied) and returns cited findings. That check does not replace agency review or the engineer of record. On USACE and NAVFAC work, the review reads UFGS submittal procedures after the project book is conformed.
It is UFGS compliance review. SpecsIntact-style tailoring and editing happen at design, when the guide specification is edited and brackets are resolved. Specset reviews construction-phase packages, including shop drawings, product data, drawings, and RFIs, against that tailored, conformed result. It works alongside SpecsIntact and does not replace it.
UFGS is the Unified Facilities Guide Specifications. Teams check a submittal against the governing section: base UFGS language, agency supplements, and addenda merged into one text, then the package reviewed against that text and the current sheets. Findings are cited back to the paragraph or page. Specset flags issues from the customer’s project documents. It does not replace agency review or the engineer of record.
Upload the base book, special provisions, addenda, and drawings as the owner issued them. Conforming applies those amendments oldest to newest into one governing text per section, with attribution and precedence. Every paragraph keeps the file it came from. Drawing revisions stay visible. Design review, bid screening, submittal review, and closeout then read that record. Conforming happens before screening or review starts.
Agency manuals publish the standard specifications. They do not apply a project’s special provisions and addenda into one governing section. Conformed software does that merge, so search and review read what governs now, with a path back to the issued page. Caltrans, including special provisions merged into standard sections, plus WSDOT and FDOT, are formats already in production. A new format is normal work.
Yes. Special provisions are merged into the standard sections they amend, with attribution, so agents and searchers read one governing text per section.
No. Specset flags issues and returns cited findings from the customer’s project documents for licensed reviewers. Agency and engineer-of-record judgment remain with the humans who own the stamp. The FedRAMP public service description uses the same boundary: the platform flags potential issues and returns cited answers drawn from the customer’s own project documents.
No. Caltrans, WSDOT, FDOT, and MasterFormat structures are first-class on the Specset platform. Upload the owner’s format.
Yes. Specset reviews submittals against the conformed UFGS sections and the current drawings, with a citation on each finding. Design quality review, bid screening, and closeout read that same record. Specset does not replace the reviewer who owns the stamp.
Specset is pursuing FedRAMP 20x Class A certification (FedRAMP Marketplace listing FR2631258135, Initial Implementation). The Class A application was filed in September 2026 and is under review. No class has been granted.
Bring the book as published. Specset conforms it, and you check the citations before anything goes back on the project letterhead.