Environmental Document Quality Control Checklist

(CEC, PCE, ER, EA)

Project ID:

Project Name:

Project Termini:

The purpose of this checklist is to;

Establish quality environmental document benchmarks that must be attained and certified by the environmental document preparer

Assist the environmental document reviewer in ensuring quality environmental document benchmarks are met and the environmental document is ready for signature

Use of this checklist;

The environmental document preparer shall perform a review of the finished document in its entirety and certify document quality by checking each quality benchmark before transmitting the document, along with this checklist, to the Region Project Manager (or Region Environmental Coordinator (REC) if prepared internally) for review and approval

The WisDOT Region may determine if the project manager should review the environmental document and use this checklist as part of the environmental document approval process

As a minimum, the REC shall use this checklist as part of their review of and comment on the environmental document

The REC shall certify environmental document quality by checking each quality benchmark prior to approval of the environmental document and transmittal to the Environmental Process and Documentation Section or Federal Highway Administration if applicable

The final checklist shall be placed in the project file with the signed environmental document and uploaded to the Region’s Regional Document Library portion of the EPDS SharePoint site

PROJECT MANAGER PREPARER	REGION REC	EPDS REVIEWER	Quality Benchmark	Guidance
☐	☐	☐	☐	Latest version of environmental document form is used	The current environmental document forms can be located on the WisDOT internet page: https://wisconsindot.gov/Pages/doing-bus/eng-consultants/cnslt-rsrces/environment/formsandtools.aspx.
☐	☐	☐	☐	All abbreviations, acronyms and terminology defined appropriately	Write out abbreviations the first time they are used in the document. Define technical terms. ERs/EAs should include a list of abbreviations and acronyms.
☐	☐	☐	☐	Correct highway abbreviations used	The following are the acceptable highway abbreviations per the WisDOT Style Guide: I-43, US 10, WIS 29, County DK
☐	☐	☐	☐	Document written in “plain English”	Avoid highly technical writing. The audience for the document includes the general public.
☐	☐	☐	☐	No errors in consistency	Cross check values (e.g. acreages, costs) throughout text and tables.
☐	☐	☐	☐	Appropriate level of detail in the document	The level of detail within the document should be appropriate for the type of environmental documentation and scope of the project.
☐	☐	☐	☐	No question left blank	Do not leave questions blank. Write “not applicable” or “N/A”.
☐	☐	☐	☐	Appropriate graphics and maps included	Graphics and maps should be inserted in text or added as attachments and referenced in the document text.
☐	☐	☐	☐	Avoided the use of words like “shall”, “will” and “must”	Be careful about making definitive statements that may not be true. For example, avoid statements like, “The project will increase the potential for economic growth”, unless that truly is a purpose for the project.
☐	☐	☐	☐	Accuracy and approximation consistent	If you have a high degree of accuracy in a number, then that degree of accuracy for that number should be used consistently. Additionally, if you cite a number to the tenth, the number should probably not be referred to as “approximate”.
☐	☐	☐	☐	The project has logical termini	- Project end points should be rational for both a transportation improvement action and a review of the environmental impacts. - Project termini typically should not end at geographic boundaries (e.g. county lines, rivers). Typically, they should continue to the nearest state or federal roadway or major local road. (See FHWA Guidance on the Development of Logical Project Termini https://www.environment.fhwa.dot.gov/legislation/nepa/guidance_project_termini.aspx)
☐	☐	☐	☐	Project segmentation has not occurred	A project must be able to function on its own without further construction of an adjoining segment (independent utility and significance) and should not restrict consideration of alternatives for other reasonably foreseeable transportation projects.
☐	☐	☐	☐	All statements are supported with proof	Statements made throughout the document should be substantiated with proof and should adequately describe the reasons for a factual conclusion or for a decision on a particular issue.
☐	☐	☐	☐	The proposed action is not described in the purpose and need section	For ERs and EAs, discussion of the preferred alternative should be reserved for Question 8. In CECs and PCEs, purpose and need are discussed before the proposed action.
☐	☐	☐	☐	There is tangible support for purpose and need	Both sections should be substantiated with actual numbers (e.g. capacity with design year volumes, deteriorating pavement with pavement distress index, bridge deficiencies with bridges inspection ratings) and should provide a comparison to statewide averages or thresholds for action.
☐	☐	☐	☐	The need section does not mistakenly describe economic development as a need	Generally, the need for a transportation project is to service economic growth caused by other planned development or conditions, rather than to induce economic growth. Statements like this may require an indirect and cumulative impacts analysis.
☐	☐	☐	☐	The term “Preferred Alternative” is used properly for Asset Management Program projects	- If the Asset Management scope certification process or preliminary engineering for a non-Asset Management project has resulted in a preferred alternative, the term “WisDOT Preferred Alternative” should be used. - Other alternatives considered and eliminated from consideration must be described. - The WisDOT Preferred Alternative needs to be clearly identified in any tables.
☐	☐	☐	☐	An assumption is not made that the build alternative is a foregone conclusion	Use a phase like, “If a build alternative is selected,” as a lead-in to comments you include as part of the environmental document, particularly when discussing project schedule.
☐	☐	☐	☐	Detour routes descriptions are included when applicable	When the project will include a detour, the detour route(s) and any necessary maintenance or improvements to those route(s), should be included in the description of the preferred alternative.
☐	☐	☐	☐	Proper identification of a public involvement meeting vs. a public hearing	- Public involvement meetings (PIM) are informal meetings intended to disseminate proposed project information and to provide others an opportunity to voice their views about a project, alternatives, impacts or proposed mitigation. - Public hearings are legally-noticed meetings to solicit oral and written comments about a project, alternatives, impacts or proposed mitigation.
☐	☐	☐	☐	All substantive public comments provided about the project are included and resolution of those comments is explained	- Include a summary of reasons why people were for or against (don’t sugarcoat it). If members of the public make wrong or purposefully false statements, you may tactfully state that too. - Actual names of people making comments should not be included as part of the document. - Explain how WisDOT will (or plans to) answer the concerns people expressed.
☐	☐	☐	☐	The correct factor sheets are used as needed	If sufficient detail can be provided in the Environmental Factors Matrix, then a factor sheet is often not needed.
☐	☐	☐	☐	All required agency coordination is included in the document	Be sure all required agency coordination is completed to the appropriate level for the draft and final document. For example, coordination with BOA is required if the project would change the horizontal or vertical alignment of a transportation facility located within 5 miles (8.05 km) of a public use or military airport.
☐	☐	☐	☐	All agency comments, and commitments, resulting from those comments are included as part of the environmental document	Agency comments should be summarized in the body of the document and explained in more detail on applicable factor sheets. Summaries should indicate which comments resulted in environmental commitments. If any agency’s comment or requested commitment is dismissed from consideration, an explanation as to why WisDOT will not be complying with the request must be included in the document also.
☐	☐	☐	☐	Environmental commitments and sufficient commitment detail are part of the Environmental Commitments matrix	Non-standard project mitigation measures, including methods of operation, agreed upon as part of agency coordination or through discussions with other entities such as a local unit of government, must be included on the Environmental Commitments page of the environmental document. Remember to include who, what, when and where on the commitments matrix to support fulfillment of the commitment.
☐	☐	☐	☐	Agency correspondence and supporting project data are current	Agency correspondence should be updated if more than 3 years have lapsed since the last correspondence or if the project scope/impacts have changed. The validity of supporting data such as traffic volumes should also be considered based on when the data was gathered or processed.
☐	☐	☐	☐	Section 106 documentation is complete to the appropriate level for the environmental document type	- The Section 106 process must be completed (e.g. signed MOA) and included in the final document as an attachment. If on the screening list, include the appropriate .pdf page(s). - The Tribal notification letter and distribution list should be included in the document's attachments. Tribal correspondence should be updated if more than 5 years have lapsed or if the project scope/impacts have changed.
☐	☐	☐	☐	Document attachments are in the correct place and referenced appropriately	- Attachments should be placed after the CEC, PCE, ER, EA Template and factor sheets, not throughout the document. - If the document is an ER or an EA, the list of attachments should be included in the table of contents - If the document is a CEC, the list of attachments should be included in Question XI - If the document is a PCE, a separate list of attachments should be included. - Reference to attachments should be in the document and should be double checked for accuracy, particularly after any updates or changes are made.

Preparer Comments:
Preparer Name (Print)	Date
Project Manager Comments:
Project Manager Name (Print)	Date
REC Comments:
REC Name (Print)	Date
EPDS Comments:
EPDS Liaison Name (Print)	Date