Washington State’s State Environmental Policy Act, SEPA, is the environmental review law that affects more development projects in Washington than any other state-level regulatory requirement. Unlike the federal National Environmental Policy Act (NEPA), which applies only to federal actions, SEPA applies to most significant private development projects in Washington, and to virtually all multifamily and commercial development above the thresholds that local governments establish as categorical exemptions.
For developers who have built in Texas, Arizona, or Colorado without encountering an equivalent process, SEPA is frequently the most surprising element of Washington’s development regulatory environment. Understanding what SEPA requires, how it affects project timelines, and how SEPA mitigation conditions carry into the construction period is prerequisite knowledge for anyone bringing a Washington development project from concept to shovel.
What SEPA Is and Why It Applies to Private Development
SEPA is a procedural law, it requires government agencies to consider the environmental effects of their decisions before acting, and it gives the public an opportunity to comment on significant environmental impacts. When a private developer seeks a permit from a local government (a building permit, a conditional use permit, a shoreline permit, a subdivision approval), that government’s decision to issue the permit is the “action” that triggers SEPA review.
The practical implication: private development is subject to SEPA through the permits it requires, not because SEPA directly regulates private development. If a project requires a building permit from Seattle, Seattle’s issuance of that permit is subject to SEPA. Seattle reviews the project for environmental impacts, determines whether those impacts are significant, and either issues a Determination of Non-Significance (DNS) or requires further environmental analysis through an Environmental Impact Statement (EIS).
What Triggers Full SEPA Review
Most local governments have adopted SEPA categorical exemptions, classes of projects that are presumed to have no significant adverse environmental impact and that are exempt from full SEPA review. Seattle’s categorical exemption thresholds are lower than most Washington jurisdictions: in Seattle, projects of more than 25 dwelling units or more than 12,000 square feet of commercial floor area require full SEPA review. In smaller cities, exemptions sometimes extend to projects several times that size.
Projects that exceed the categorical exemption thresholds are subject to a SEPA environmental checklist, a detailed questionnaire that asks the applicant to assess the project’s potential impacts on earth, air, water, plants and animals, energy, land use, transportation, utilities, public health, and cultural resources. The lead agency (the jurisdiction processing the primary permit) reviews the checklist, may conduct its own analysis, and issues either a DNS, a Mitigated DNS (MDNS), or requires an EIS.
The DNS vs. MDNS vs. EIS Distinction
Determination of Non-Significance (DNS). The lead agency determines that the project will not have a probable significant adverse environmental impact. The DNS can be appealed by any person who commented during the comment period. Most routine commercial and multifamily projects in established urban areas receive a DNS after a standard comment period.
Mitigated Determination of Non-Significance (MDNS). The lead agency determines that the project could have significant impacts, but that those impacts can be mitigated to a less-than-significant level through specific mitigation measures. The mitigation measures become binding conditions of the SEPA determination, they are not suggestions but requirements that the project must implement.
The MDNS is the most consequential SEPA outcome for project construction management, because the mitigation conditions it establishes carry into the construction period as permit conditions. A project that received an MDNS requiring specific stormwater management, bird-safe glazing, construction hour limitations, or staging restrictions has an obligation to implement those measures during construction. Monitoring programs that don’t track MDNS condition compliance create permit violation exposure that can affect certificate of occupancy.
Environmental Impact Statement (EIS). Required when the lead agency determines the project will have probable significant adverse environmental impacts that cannot be mitigated to non-significance. An EIS is a major undertaking, it requires a detailed analysis of alternatives, impacts, and mitigation measures, takes 12 to 24 months in most cases, and adds substantial cost. Large urban infill projects, projects in environmentally sensitive areas, and projects that generate significant opposition sometimes require EIS preparation.
SEPA Timeline Impact
For developers from Texas or Arizona entering Washington, SEPA is often the first regulatory surprise. A project in Dallas or Phoenix with complete construction documents can be submitted for building permit review and receive a permit in 3 to 6 months. The same project in Seattle requires SEPA review, with a public comment period, potential appeal period, and MDNS or EIS preparation, before the building permit application can even be submitted in some cases, or concurrent with building permit review in others.
The combined effect of SEPA review, design review, and building permit processing can extend a Seattle project’s pre-construction timeline to 18 to 36 months, a carrying cost that must be reflected in development pro formas. Developers who model Seattle entitlement timelines using Texas or Arizona benchmarks will understate the carrying cost by a factor of 3 to 5.
SEPA Conditions and Construction Management
The mitigation conditions established by an MDNS don’t expire when the building permit is issued. They are permit conditions that must be implemented and documented during construction. Construction managers on Washington projects should review the SEPA determination and its conditions as part of project setup, not as background reading but as a compliance checklist that needs to be tracked throughout construction.
Common SEPA construction-period conditions: stormwater management specifications beyond standard code requirements; construction noise limits during specified hours (often more restrictive than general ordinance); construction staging restrictions to protect adjacent resources; species protection measures during construction near habitat areas; and vibration monitoring near historic structures.
Related: Construction Management, Washington State · Multifamily Development, Seattle WA · Owner’s Representative, Washington State · Development Advisory Guide