Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Development topic
No spam. Unsubscribe anytime.
Council debates shift of traffic‑control costs to developers as LDSO revisions aim to lower housing costs
Summary
Staff proposed shifting the city’s annual sign/striping costs to developers and tightening street/paving and sidewalk standards as part of Land Development & Subdivision Ordinance updates aimed at reducing housing development costs. Council asked staff to return with cost breakdowns and safeguards.
City planning and operations staff on March 17 advanced a package of proposed Land Development & Subdivision Ordinance (LDSO) changes designed to lower development costs and help housing affordability — and floated a separate proposal to shift the city’s recurring cost for traffic control devices, signs and striping to developers.
Senior planner Austin Reed described recommended LDSO edits to simplify standards and reduce typical new‑street paving widths (for example, standardizing new local street paving widths and clarifying where sidewalks are required). Reed said the committee that drafted the changes sought consistency and fewer surprise variance requests.
Director of operations Patrick Frerich then proposed a separate, operational change: require developers to pay the estimated and installed cost of traffic‑control devices (stop signs, street name signs, pavement markings and, where applicable, signalized intersections). Frerich said the city would retain installation and maintenance responsibility but recover material, labor and an administrative fee from developers; staff estimated the current annual cost to the general fund at roughly $8,000 and said a typical sign installation could be under $300 per location.
Council members raised a range of concerns: fairness to small developers, the risk of raising housing costs, the administrative burden of requiring traffic impact studies and engineering for small subdivisions, and the possibility that shifting costs would simply change which taxpayers ultimately bear them. Several members asked staff to analyze the net effect on development costs and long‑term maintenance liabilities, and to explore whether the city engineer or in‑house staff could perform some studies to reduce outside consultant costs charged to developers.
Council also asked staff to build safeguards, such as defining when a full traffic impact analysis is required and how to treat signalized intersections or large commercial projects differently from small residential plats. The council did not vote on the proposal; members directed staff to return with more detailed cost breakdowns, developer input and options that limit unintended consequences.
