Good evening.

I would like to call to order the Shoreline Planning Meeting.

What's happening over there, Andrew?

All right.

Good evening.

Oops.

I would like to call the order the Shoreline Planning Commission meeting of Thursday, November 6th, 2025.

Carla, will you call roll?

Yes.

Chair Brinson.

I am here.

Commissioner Cabe.

Here.

Commissioner Fry.

Present.

Commissioner Hadley.

Here.

Commissioner Lai.

Here.

Thank you.

Vice Chair Mosier.

Yeah.

And Commissioner Povick is absent with notice.

Thank you.

Excellent.

Thank you.

Approval of the agenda.

Thumbs up.

All right.

And approval of the meeting minutes from October 16th.

Excellent.

Also approved.

Now, is there any public general public comment?

Not related to our public hearing.

Nothing, uh nothing tonight.

Excellent, thank you.

Moving on.

Tonight's public hearing is on the environmentally critical areas code update.

The purpose for this hearing is to obtain public testimony and for the commission to develop a recommendation to forward to the city council on this topic.

Public comments are limited to three minutes per person testifying.

When the clerk calls your name for either in-person or remote comment, please state your name and city of residence for the record before you begin.

The process for the public hearing is as follows.

First, the city will present its staff report, and then the commission will be given an opportunity to ask clarifying questions.

Individuals will be given an opportunity to testify.

After all the testimony has been received, the commission will begin deliberation and may ask questions of the staff or individuals who testified.

The commission will then vote and close the public hearing.

I now wish to open the public hearing.

All right, good evening, Commissioners.

Let's see, make sure I can be heard.

My name is Elise Keim.

I am the planning manager here for the City of Shoreline with a brief staff presentation on the Critical Areas Code update for the public hearing.

What I have in store for you during this presentation is a recap of why we're updating our critical areas code, a summary of the process to date, summarizing some amendments that have uh occurred since we were last together in early October discussing this topic, go over the uh development code amendment criteria, and then uh move on to Commission questions, testimony, and then discussion and a recommendation if Commission so uh deems it appropriate.

So, first up, why are we updating our critical areas code?

Uh cities in Washington State are required to have a uh development code that protects environmentally critical areas.

This is a requirement of the Growth Management Act, and cities are required to periodically review and update their critical areas codes so that they are incorporating best available science.

When we did our analysis of our current critical areas code, which was last uh updated in 2015, what we found is the gap was related to uh best available science for protection of streams and stream ecosystems.

DFW, Washington State Department of Fish and Wildlife, excuse me, uh published updated guidance on best available science for how to protect stream ecosystems with the concept uh focused on riparian management zones, these areas around streams.

So, uh with that in mind, our goals for this update process have really been focused on updating the code to be uh incorporating best available science with really a focus on riparian management zones, as that was the big topic that had changed since our last update in 2015, and the goals of the code were to make sure that we uphold our environmental protection standards while still maintaining that flexibility for existing development.

Additional goals included to reorganize and consolidate the code so that it was easier to understand for both review staff and applicants.

The process to date, uh we have met several times in this forum uh with um planning commission going over uh these uh uh introductions to the best available science, different approaches, and uh reviewing draft code language.