City staff outline development code maintenance package, public hearing set for Feb. 18

Scott Siegel, Community Development Director, used a Feb. 3 work session to walk the City Council through the city’s proposed development-code maintenance amendments, identified in the packet as a legislative matter and referenced as “ordinance 20 25 20 or 2933.” Siegel said the package is intended primarily as code maintenance: clarifications, formatting fixes and alignment with state law rather than a rewrite of the zoning code.

“Code maintenance is intended to clarify and improve predictability and efficiency in the permit process through corrections, definitions, formatting changes, and in some cases revisions to existing regulations to maintain compliance with state and federal law,” Siegel said.

Key elements: Siegel described several categories of changes: - Definitions and building-code alignment: the draft aligns planning definitions for exempt residential accessory structures with changes in the building code (example: accessory structures under certain size/height thresholds). - Appeals and process clarifications: revisions clarify which appeals go to which body (Historic Preservation Commission vs. Planning Commission) and set filing deadlines (14 days for certain middle‑housing land division appeals). - State-law alignment: updates to notices and timelines (for example, Department of Land Conservation and Development notice timing) to match state statutory requirements such as Measure 56–type noticing. - Parking and a new study option: the draft reorganizes parking standards into a single table and proposes a discretionary parking-study procedure that would allow applicants to justify alternative parking requirements based on evidence; such requests would be subject to Type 2 review and public notice. - Permit timelines and extensions: staff proposed lengthening validity periods for many land-use approvals (e.g., from 1 year to 2 years for certain approvals) and permitting limited extensions where code standards have not changed.

Siegel said the package is organized with an annotated exhibit (Exhibit A1A) and an index in the staff report to help reviewers find specific changes. He recommended the council treat the meeting as an opportunity to become familiar with the material and asked whether the council wanted staff to dive further into particular items before the Feb. 18 public hearing.

Council questions focused on the accessory-structure exemption height change, permitting timelines and whether proposed changes are mandatory under state law or discretionary. Siegel said some items simply align the city code with recent building-code or state-law changes; others are discretionary policy choices intended to improve customer service.

Next steps: Siegel said the public hearing on the ordinance is scheduled for Feb. 18 and invited councilors to submit questions by email before that session. Planning Commission has recommended approval of the package; councilors asked staff to return with clarifications as needed during the hearing process.

Ending: The council did not vote on the ordinance at the work session; staff will present the ordinance for public testimony and council action at the Feb. 18 public hearing.