Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Transportation And Streets topic

No spam. Unsubscribe anytime.

Redmond public works unveils proposed Title 10 and 12 municipal-code updates covering micro‑mobility, traffic control and right‑of‑way rules

5078383 · June 26, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Public Works presented proposed revisions to Redmond Municipal Code Titles 10 and 12 on June 24, clarifying authority for traffic control and right‑of‑way work, adding micro‑mobility rules and new procedures for unpermitted right‑of‑way modifications.

Redmond Public Works presented a study‑session overview June 24 of proposed updates to the Redmond Municipal Code (RMC) Titles 10 and 12, intended to align local rules with current state and federal practices, clarify public‑works responsibilities and to support a future APWA (American Public Works Association) accreditation package.

Paul Cho, Traffic Operations Safety and Engineering manager, said the update consolidates and modernizes traffic control‑device language, clarifies which actions require council approval (for example, setting new speed limits after engineering studies), and adds explicit language about micro‑mobility devices and sidewalk/shared‑use path speeds.

Cho and Patty Bridal (Traffic Operations and Safety Engineering) said Title 10 drafts include a sidewalk speed expectation (staff proposed 5 mph as a pedestrian‑pace guideline) and a 15 mph limit on regional shared‑use paths to align with neighboring jurisdictions. Councilmembers asked about enforceability and potential for disparate enforcement; staff said the draft language can be adjusted to prioritize pedestrians and that enforcement methods require coordination with Police.

Title 12 changes address right‑of‑way restoration, unpermitted modifications, temporary roadway closures and emergency right‑of‑way procedures. Bridal said the code now allows the city to require restoration to “better than original condition” where federal, state or local mandates (for example ADA ramp standards) apply, and adds a process for removing unpermitted work with notification timelines and cost recovery.

Councilmembers raised detailed questions: whether a 5 mph sidewalk speed should remain a fixed number or be replaced by language that requires bicyclists and micro‑mobility users to yield to pedestrians; concern about the “leave unattended child” provision that references children younger than 16 (staff said the change aligns with state law); expansion of allowed parking fee processes (the update removes geographic references so the city can implement parking programs citywide but still requires a council review/approval step); and a change from 24 to 72 hours for unposted vehicle parking limits intended to reduce enforcement on non‑storage, short‑term situations.

No code changes were adopted at the study session. Staff said the updates will be posted for public comment through the city’s “Let’s Connect” portal, and Public Works anticipates packaging all chapters and bringing the consolidated update back to council with targeted stakeholder engagement; staff said they aim to adopt the full code package in Q2 2026.

What’s next: staff will refine language on sidewalk/shared‑use speeds and enforcement, confirm alignment with state statutes on the child‑in‑vehicle provision, add requested clarifications on parking and right‑of‑way timelines, and continue stakeholder outreach before returning to council.