Citizen Portal
Sign In

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

Get email alerts on the Development Manual Transparency topic

No spam. Unsubscribe anytime.

Council adopts development policies manual; members seek clearer disclosure of future code changes

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

Council approved a resolution adopting the City of Central Development Policies and Standards Manual but members pressed staff to clearly mark any provisions moved from the Unified Development Code to the manual and to require council ratification of future manual changes.

The City Council voted June 10 to adopt the City of Central Development Policies and Standards Manual and discussed how the manual will relate to the Unified Development Code and future amendments.

Council member LaVeyne moved to approve the resolution adopting the manual and Council member Meyer seconded. The council then discussed whether material moved from the city’s ordinances into the manual could be changed administratively without returning to council. Several council members sought assurances that ordinance provisions would not disappear without formal action. One council member said, “I want it to be clearly depicted … what is no longer in Munic[ode] and what will now only be found in this policy,” and asked for a list showing deletions and the planned replacements.

Staff replied that adoption of the manual does not immediately remove provisions from the formal code, and they said that items referenced in the manual will remain in the code until the city completes future ordinance amendments. Staff committed to adding a front‑page note to the manual explaining that any changes to the policies will be ratified by council resolution and to produce a staff report that documents which provisions will be moved from ordinance to manual in later codified text amendments.

Council members asked for transparency measures: one asked that the manual state on its first page that changes to the manual require council approval, and another requested that the staff report identify specific items shifted from code into policy language. Staff said they will provide that crosswalk in future text‑amendment packets. The resolution adopted the manual on a roll call vote; staff listed future text amendments that will formally move certain items (for example, landscape standards) from ordinance language into referenced policy guidance with council oversight.

Council emphasized that the UDC itself will not be changed by this single resolution and that any future deletions or code changes must follow the ordinance process. Staff said the policy manual is intended to improve clarity and a single place for technical standards while preserving council authority over code changes.