UFGS tailoring and editing.
The designer selects sections, resolves brackets and fill-ins, and edits the guide specification with government spec-writing tools. UFGS tailoring at design produces the project book.
Specset checks federal construction submittals, shop drawings, product data, and drawings against the conformed UFGS sections and returns findings cited to the paragraph and the sheet. The book is conformed first: brackets already resolved at design, agency supplements, addenda, and amendments merged into one governing text per section. Specset also conforms Caltrans, WSDOT, FDOT, and railroad books the same way. Your reviewer still owns the stamp.
UFGS compliance review checks what the contractor submitted against what the tailored UFGS book requires. Specset does that check on construction-phase packages: each submittal is read against the governing UFGS section, Section 01 33 00 Submittal Procedures, and the current drawings, and every finding cites the paragraph or sheet it came from.
UFGS are written jointly by USACE, NAVFAC, and AFCEC for military construction, published on WBDG, and updated quarterly. On a project, the designer tailors the guide specifications, resolves the brackets, and issues the book. The contractor then builds submittals against that issued book. Specset starts there: it conforms the issued sections with agency supplements and addenda, then reviews the packages against them.
Federal tenants run in CUI mode, which keeps model calls inside the Assured Workloads boundary and turns off the Procore and Autodesk integrations.
The designer selects sections, resolves brackets and fill-ins, and edits the guide specification with government spec-writing tools. UFGS tailoring at design produces the project book.
Specset reads the issued, conformed book and checks shop drawings, product data, and drawings against it. Findings are cited, consolidated, challenged by a second AI, and returned on the marked-up package for the reviewer’s call.
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. UFGS tailoring at design happens before construction. Specset reviews the construction-phase package against that tailored, conformed result. It picks up after tailoring.
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.
UFGS Section 01 33 00 Submittal Procedures sorts every submittal by a Submittal Description (SD) number. Each technical section lists the submittals it requires under those numbers, and a "G" marks the ones that need Government approval.
Submittals marked "G" (or "S" for sustainability reporting) go to the Government for approval. The rest are approved by the contractor’s quality control system. The guide specification notes that the submittal register is created from the project specification files at the end of design. Specset reviews each package against the section that called for it, so a product data sheet is checked against the same paragraphs the reviewer will hold it to.
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.
A state DOT job is the standard specifications plus the project’s special provisions and addenda. Conformed spec book software merges them into one governing text per section before anyone reviews a submittal or prices a bid. Specset does that for Caltrans, WSDOT, FDOT, and other agency books.
Caltrans and DOT conformed specification book software →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 →It is a construction-phase check of submittals against the tailored, conformed UFGS book. Specset reads each package, including shop drawings, product data, and drawings, against the governing UFGS section, Section 01 33 00 Submittal Procedures, and the current sheets, and cites every finding to the paragraph or page. It does not replace agency review or the engineer of record.
UFGS tailoring at design is done with government spec-writing tools: the designer selects sections, resolves brackets, and edits the guide specification into the project book. Specset picks up after tailoring and reviews construction packages against the tailored, conformed project book.
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.
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.
They are the Submittal Description numbers defined in UFGS Section 01 33 00 Submittal Procedures: SD-01 Preconstruction Submittals, SD-02 Shop Drawings, SD-03 Product Data, SD-04 Samples, SD-05 Design Data, SD-06 Test Reports, SD-07 Certificates, SD-08 Manufacturer’s Instructions, SD-09 Manufacturer’s Field Reports, SD-10 Operation and Maintenance Data, and SD-11 Closeout Submittals. Items marked "G" need Government approval. Specset reviews each package against the section that requires it.
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.
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.
Filed FedRAMP 20x Class A application, under review; Marketplace listing FR2631258135, Initial Implementation; pursuing Class C.
Bring the book as published. Specset conforms it, and you check the citations before anything goes back on the project letterhead.