Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Development Code topic
No spam. Unsubscribe anytime.
Staff previews Redmond development‑code amendments; public hearing set for Feb. 10
Summary
City staff briefed the City Council on proposed development‑code text amendments covering urban forestry, irrigation schedules, cemetery rules, backflow prevention and system‑development‑charge procedures, and said a public hearing is scheduled for Feb. 10 with adoption possible about a month later.
Get email alerts on the Development Code topic
No spam. Unsubscribe anytime.
City of Redmond staff presented proposed text amendments to the city’s development code and told the City Council they will take the proposal to a public hearing on Feb. 10.
Staff member (S1), who opened the briefing, said the package bundles several changes: urban‑forestry clearance rules, updates to the irrigation schedule, tweaks to backflow‑prevention and cross‑connection requirements, clarifications to cemetery regulations, and more precise procedures for assessing system development charges (SDCs). “Here we are today to with the actual text amendments in front of us,” the staff member said, and added, “we are making it a public hearing on February 10.”
The staff summary said the irrigation watering window was adjusted after council feedback: the previously proposed 7 p.m.–7 a.m. window was changed to allow watering through 9 a.m. to accommodate additional input. On trees, the amendments clarify a 14‑foot clearance above roadways and alleys so maintenance and equipment may pass without damaging trees.
Staff described outreach conducted for the package, naming local stakeholders and a direct email to about 500 active permit applicants. The staff member said the city will accept public comment at the Feb. 10 council meeting; if the council adopts the amendments there, staff expects the code changes to take effect roughly a month afterward.
Councilors asked staff to prepare clear outreach materials for residents who may be unsure how to comply — especially older residents who may attempt unsafe ladder work — and staff agreed to include arborist contact information in those materials. The briefing closed with staff inviting council direction and questions ahead of the public hearing.
The council did not take a formal vote on the code text at the briefing; the public hearing on Feb. 10 is the next scheduled procedural step.
