Agency manual
The manual publishes the standard specifications and how the book is organized. On a live project the special provisions and addenda sit in other files, so the amendment is in a different PDF from the paragraph it changes.
A DOT contract is never just the standard specifications. Special provisions amend sections, and addenda land after the set is printed. Specset merges the standard book, the project’s special provisions, and every addendum into one governing text per section, with the source of each paragraph kept, then runs submittal review, RFI checks, bid screening, and design review on that conformed book. Every finding is cited back to the issued page.
Start from the standard specifications the contract names, apply the project’s special provisions to the sections they amend, then apply each addendum in issue order. The result is one governing text per section, and each paragraph should still point to the document it came from.
The standard specifications edition the contract names, the special provisions, every addendum, and the plans. Upload them in whatever shape the owner published them, scans included.
Special provisions replace values, add paragraphs, or delete subsections in the standard book. Specset applies them where the directive language says to, so the amended paragraph sits in the section it changes.
Each addendum is applied in order, with precedence kept, so the latest instruction governs and the history stays visible.
Every paragraph keeps the file it came from. A reviewer clicks through to the issued page.
Drawing revisions stay visible so submittals and RFIs answer against the current set.
Submittal review, RFI checks, bid screening, and design review read the same record.
Caltrans, WSDOT, and FDOT books are already in production, along with BNSF and other railroad and port authority books and scanned legacy manuals. A new agency book is normal onboarding work.
Agency publication details checked October 8, 2026 on each agency’s site.
The manual publishes the standard specifications and how the book is organized. On a live project the special provisions and addenda sit in other files, so the amendment is in a different PDF from the paragraph it changes.
One governing text per section, with special provisions and addenda applied in order and every paragraph traceable to its source. Search and review read what governs now.
Yes. Once the book is conformed, Specset checks shop drawings, product data, and mix designs against the governing section and the plans, and returns an annotated package with each finding cited to the paragraph and the sheet. Your engineer makes the call.
Submittal review →Software that merges the standard specifications, the project’s special provisions, and the addenda into one governing text per section, so search and review read what governs now. Specset does that for Caltrans, WSDOT, FDOT, and other agency books, with a click back to the issued page.
Start from the standard specifications the contract names. Apply each special provision to the section it amends. Apply addenda oldest to newest. Keep the source of every paragraph. Specset does this per section, then runs submittal, RFI, bid, and design reviews on the result.
Yes. Special provisions are merged into the standard sections they amend, with attribution, so reviewers and agents read one governing text per section.
Yes. WSDOT books are a format already in production and are read as issued, with the project’s special provisions and addenda conformed into the governing text.
Yes. FDOT books are a format already in production and are read as issued.
Yes. BNSF and other railroad and port authority books are formats already in production. Packages are reviewed against the conformed book with cited findings, and your reviewer makes the call.
No. Upload the book as the owner issued it. Caltrans, WSDOT, FDOT, and MasterFormat structures are first-class on Specset.
No. Specset prepares cited findings. Licensed reviewers own the decision.
We conform the book, review the package, and you check the citations.