Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Transportation Safety topic
No spam. Unsubscribe anytime.
Redmond staff outline draft Safer Streets action plan, set targets to cut severe crashes 50% by 2030
Summary
Redmond City Council received a staff presentation Tuesday evening on a draft Safer Streets action plan that proposes to reduce fatal and severe‑injury (FSI) crashes by 50% by 2030 and to achieve zero FSI crashes by 2035.
Get email alerts on the Transportation Safety topic
No spam. Unsubscribe anytime.
Redmond City Council received a staff presentation Tuesday evening on a draft Safer Streets action plan that proposes to reduce fatal and severe‑injury (FSI) crashes by 50% by 2030 and to achieve zero FSI crashes by 2035.
Deputy Director Sarah V. Allen, Planning and Community Development, introduced the item and said staff are seeking council feedback before a Jan. 28 study session and an anticipated plan adoption in March or April. "Tonight staff will provide a status update on the progress of Redmond's Safer Streets action plan," Allen said.
The draft plan uses a safe‑systems approach endorsed by U.S. Department of Transportation and the Federal Highway Administration and adds a sixth pillar — land use — to emphasize locating destinations close to people to reduce exposure. "This draft plan is really centered on this approach," Transportation Planning Manager Michael Hintz said, noting the plan was developed with input from planning, police, fire, public works and parks.
Key strategies described in the presentation include: - Updating the city traffic signal manual (last revised in 2002) to add practices such as pedestrian scrambles, leading pedestrian intervals and selective no‑right‑turn‑on‑red signs where appropriate. - Pursuing a speed study to identify where simple sign changes suffice vs. where design changes are needed, and considering lowering local street limits to 20 mph in particular cases. - Piloting speed safety cameras focused on school zones, parks and other areas with vulnerable users; staff said the automated enforcement program is anticipated to be in place for the 2025–26 school year and would include equity measures such as a warning system for first offenses and reduced fines for demonstrated hardship. Staff said revenue would be directed back into roadway safety programs. - Defining and reinforcing pedestrian priority zones (the city currently has three defined zones, with downtown the only signed zone) and using design tools such as reduced street widths, raised crossings and adaptive signals to prioritize pedestrians. - Institutionalizing complete streets through a checklist used in project development, revising street standards and coordinating with the fire department on emergency response compatibility. - Expanding school‑focused programs, including participation in King County’s SchoolPool program funded by the Move Ahead Washington legislation, and pursuing rapid, low‑cost demonstration projects that can be evaluated and made permanent if successful. - Establishing a post‑crash response team composed of first responders, planners and engineers to review every fatal or serious injury crash, document contributing factors and identify engineering or operational changes. - Increasing traffic‑related data collection, including camera data, first responder and hospital reports, and pedestrian/bicycle counts, and presenting progress through tools such as an online dashboard and annual reports.
The presentation also flagged emerging technology options such as intelligent speed assistance for fleet vehicles and SmartSigns (an infrared pilot in King and Pierce counties) that detect behaviors like phone use or seat belt nonuse; staff said Redmond will monitor pilots before proposing local deployment.
Council members pressed staff on several implementation details. Council Vice President Forsyth asked for more information on the plan’s land‑use pillar and requested that a council member liaison sit on the proposed post‑crash response team. Forsyth said she wanted "to hear how that goes" and suggested council representation on the team. Council Member Fields asked for timeline detail distinguishing near‑term actions from longer‑term projects and raised concern about city vehicles blocking bike lanes in some photos used in the presentation; Fields asked for a policy to prevent that practice.
Council Member Anderson sought clarification of the term "first responders;" staff said the term generally refers to police, fire and emergency medical services in the crash‑review context. Council Member Salahuddin asked whether the FSI reduction target accounts for impacts from natural disasters; staff said the target focuses on traffic‑related injuries and offered to follow up.
Staff asked for feedback at the Jan. 28 study session and said they will return to seek approval to apply for federal Safe Streets for All funding in the May–summer time frame.
Why it matters: the plan frames near‑term engineering, enforcement and education steps to reduce risk to pedestrians, bicyclists and other vulnerable users, and positions the city to compete for federal and state safety grants that could fund infrastructure changes.
Looking ahead: staff will present more detail at a Jan. 28 study session that also will include police on automated enforcement policy, and will return later this spring to seek formal adoption and grant‑application authority.

