Review the GSP that governs.
A WSDOT General Special Provision is dated standard language that modifies the Standard Specifications for the projects that include it. In the contract, those special provisions outrank the book and the plans. Specset merges the provision that was actually inserted, including fill-ins, region provisions, and project provisions, then reviews the plans and the submittal against that text.
How do you review WSDOT General Special Provisions?
Review WSDOT General Special Provisions by reading the dated provisions the contract inserts, including fill-ins, as the revisions incorporated between yearly Standard Specifications books, using the instructions for use on the WSDOT General Special Provisions page.
What a General Special Provision is.
A GSP is the standardized amendment WSDOT uses between yearly editions of the Standard Specifications. The contract copy is that language plus the project's fill-ins.
WSDOT publishes the Standard Specifications every year. Revisions that have to land between those books are incorporated into contracts through the General Special Provisions. As checked October 2026, the GSP page states that the 2027 Standard Specifications apply to WSDOT projects advertised on or after September 14, 2026. The same page indexes the active GSPs by division, from Division 1 General Requirements through Division 9 Materials, and publishes interim GSP updates that come out after the annual package. It also publishes local-agency GSPs.
As checked October 2026, the master compilation is the combined GSP document. Its introduction says the contract is constructed in accordance with the 2027 Standard Specifications, then distinguishes three kinds of special provisions. A General Special Provision is marked with the date it was last updated. It is standardized language used on applicable projects in Washington. After that date, the only difference from one project to another is variable project data, inserted as a fill-in.
A Region Special Provision is marked with a region or division abbreviation and the date it was last updated. The compilation lists Eastern (ER), North Central (NCR), Northwest (NWR), Olympic (OR), South Central (SCR), Southwest (SWR), and Washington State Ferries (WSF). It is standardized language for that region, again with fill-ins as the project difference. A project specific special provision is marked with six asterisks instead of a date. The compilation says these provisions normally appear only in the contract they were developed for.
How a GSP layers on the Standard Specifications.
The Standard Specifications are the base. The special provisions in the contract modify them, and they outrank the book.
Division 1 of the Standard Specifications defines special provisions as supplemental specifications and modifications to the Standard Specifications that apply to an individual project. A GSP is one of those special provisions when the contract includes it. The statewide library is not, by itself, a contract part.
The amendments are written as directives against a section. In the master compilation, one option says Section 1-02.1, including its title, is deleted and replaced, and the April 2, 2018 option replaces that section with "Vacant." Another says Section 5-04.2(2), under Hot Mix Asphalt, is supplemented, and the added sentence leaves the project value as a fill-in. Delete-and-replace removes the book language. Supplement leaves the book language and adds to it. Which one governs depends on the directive in the contract, not on a guess from the section title.
Section 1-04.2 of the Standard Specifications says the parts of the contract complement each other, and that a requirement in one part binds as if stated in all of them. When the parts are inconsistent, the order of precedence, highest first, is addenda, the Proposal Form, special provisions, contract plans, the Standard Specifications, and Standard Plans. Figured dimensions govern over scaled dimensions on the contract plans, working drawings, and Standard Plans.
That order stops where work is required by one part and omitted from another. Section 1-04.2 says the work required in one part must be furnished even if the other parts do not mention it. A referenced code, rule, specification, or standard means the version in effect on the bid advertisement date, unless the contract states otherwise or law requires a different reading. Ambiguities and disputes over interpreting the contract go to the Engineer, as provided in Section 1-05.1. That section lists interpretation of the plans and specifications among the Engineer's decisions, and it sends a timely written protest to Section 1-04.5.
Where a WSDOT review goes wrong.
Each of these is a misread of the special provisions or of Section 1-04.2, not a preference about how to mark up a set.
- 01
Reading the Standard Specifications without the special provisions
Special provisions are modifications of that book for one project, and Section 1-04.2 ranks them above both the Standard Specifications and the contract plans. Addenda rank above the special provisions.
- 02
Applying the latest statewide library instead of this contract
A GSP is dated standardized language. The contract contains the GSPs that were inserted, with that project's fill-ins. Interim updates published after advertisement are not in the contract unless the contract includes them.
- 03
Treating a silent GSP as a deleted requirement
Section 1-04.2 says the order of precedence does not apply when one part requires work that another part omits. The work required in one part must still be furnished.
- 04
Missing region and project specific provisions
The special provisions hold three types. A region provision is marked with a region abbreviation and a date. A project specific provision is marked with six asterisks and normally appears only in that contract. A statewide GSP index will not contain it.
- 05
Ignoring the fill-in
From one project to the next, the standardized GSP sentence stays the same. The project data inserted as a fill-in is the part that changes. The statewide sentence without that insert is not the contract.
- 06
Letting a plan dimension outrank a special provision
Contract plans rank below special provisions. Figured dimensions govern over scaled dimensions on the plans, the working drawings, and the Standard Plans. That rule does not lift a drawing over the special provisions.
- 07
Using a newer code than the advertisement date
Unless the special provisions say otherwise, or law requires it, a referenced code, rule, specification, or standard is the one in effect on the bid advertisement date. The GSP's own update date is not that date.
How Specset reviews GSPs against plans and submittals.
The merge uses the provisions in the contract, including the fill-ins. Plans and submittals are checked against that text.
Specset takes the set as issued: the Standard Specifications edition the contract names, the special provisions that were inserted, addenda, plans, and submittals. General, region, and project specific provisions are all special provisions. A fill-in is part of the provision, not a blank to ignore. Conforming applies those amendments into one governing text per section, with the file each paragraph came from still attached. Conforming happens before design review or submittal review starts. That is the conformed DOT book described on UFGS and DOT specs, and the same merge spec intelligence runs when the amendment says to delete, replace, or supplement a section. Addenda outrank the special provisions, so an addendum that was issued has to be in the set that gets conformed.
Design quality review compares that conformed text with the sheets. Conflicts, missing information, and constructability risks come back cited to the paragraph or the sheet. The reviewer confirms, downgrades, or dismisses each finding. Section 1-04.2 still ranks contract plans below the special provisions, so a sheet that repeats the unamended book is the conflict, not the governing text.
Submittal review checks the package against the conformed sections and the current drawings. Checks run spec-first, drawing-first, and submittal-first. The package comes back annotated. Specset does not replace the Engineer. Section 1-05.1 gives the Engineer the decision on interpretation of the plans and specifications, and a written protest is handled under Section 1-04.5. Specset also does not replace the reviewer who owns the stamp. The Proposal Form also outranks the special provisions. Specset's review cites the conformed specification and the drawings. A higher-ranking Proposal Form entry is still a contract part the reviewer applies.
Official WSDOT sources.
Format, ranking, and edition claims on this page come from these publications.
- General Special Provisions
Annual Standard Specifications, the 2027 book for projects advertised on or after September 14, 2026, GSP indexes by division, interim updates, and local-agency GSPs. As checked October 2026.
- GSP master compilation, as checked October 2026
How general, region, and project specific provisions are marked, what a fill-in is, and sample amend-or-supplement directives.
- Standard Specifications, Division 1
Definition of special provisions, and Section 1-04.2 coordination of the contract documents.
What teams ask about WSDOT General Special Provisions.
01What is a WSDOT General Special Provision?
A GSP is standardized language used on applicable projects in Washington, designated with the date it was last updated. From one project to another, the only difference after that date is project data inserted as a fill-in. Revisions that have to land between yearly Standard Specifications books are incorporated into contracts through the GSPs.
02How does a GSP layer on the Standard Specifications?
Special provisions are supplemental specifications and modifications to the Standard Specifications for an individual project. As checked October 2026, the GSP compilation introduces the contract as constructed in accordance with the 2027 Standard Specifications, then amends sections with directives such as deleted and replaced, or supplemented. The 2027 book applies to WSDOT projects advertised on or after September 14, 2026.
03What is the order of precedence on a WSDOT contract?
Section 1-04.2 ranks an inconsistency, highest first: addenda, Proposal Form, special provisions, contract plans, Standard Specifications, Standard Plans. That order does not apply when one part requires work another part omits. The required work must still be furnished. Figured dimensions govern over scaled dimensions. Ambiguities go to the Engineer under Section 1-05.1, which includes interpretation of the plans and specifications, and a written protest is handled under Section 1-04.5. A Proposal Form that outranks the special provisions is still a contract part the reviewer has to apply.
04What is the difference between a GSP, a region provision, and a project specific provision?
The special provisions include all three. A GSP carries a date and is statewide standard language plus fill-ins. A region provision carries a region abbreviation and a date: Eastern, North Central, Northwest, Olympic, South Central, Southwest, or Washington State Ferries. A project specific provision is marked with six asterisks and normally appears only in the contract it was written for.
05How do you review WSDOT General Special Provisions?
Review WSDOT General Special Provisions by reading the dated provisions the contract inserts, including fill-ins, as the revisions incorporated between yearly Standard Specifications books, using the instructions for use on the WSDOT General Special Provisions page.
06How does Specset review WSDOT GSPs against plans and submittals?
Specset ingests the Standard Specifications edition the contract names, the special provisions that were inserted (general, region, and project specific, including fill-ins), addenda, plans, and submittals as issued. It merges those amendments into one governing text per section before review starts. Design quality review compares that text with the sheets. Submittal review checks the package against the conformed sections and the current drawings. Findings cite the paragraph or the sheet. The reviewer still owns the stamp.
UFGS and DOT specsSpec intelligenceDesign quality reviewSubmittal review
Other agents that start from the same record.
FDOT provisions
Review FDOT supplemental specifications and special provisions against the Standard Specifications, plans, and submittals. Those provisions merge into the sections they amend.
BNSF specifications
Review BNSF engineering specifications against the project special provisions, plans, and submittals. Project provisions merge into the sections they amend.
Non-MasterFormat specs
Review a specification book that is not organized as MasterFormat. The parser follows the headings and section numbers in the uploaded file.
Send the book and the special provisions.
Bring the Standard Specifications edition the contract names, and the general, region, and project specific provisions that were inserted, fill-ins included. Specset conforms the section. You check the citation before anything goes back on the project letterhead.