Citizen Portal
Sign In

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

Get email alerts on the Public Works topic

No spam. Unsubscribe anytime.

Council considers letting city engineer authorize variances to engineering standards; public comment supports staff flexibility

5415261 · July 18, 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

Council considered amending city code so the city engineer (and staff) can grant variances to engineering standards without a council vote. Proponents argued it speeds development and corrects technical problems; council members asked to preserve a process for controversial or precedent-setting variances to return to the council.

Cedar City staff asked the council on July 16 to amend ordinance language requiring engineering standards to be adopted by ordinance and to allow the city engineer to authorize variances to those engineering standards so routine project-level exceptions do not need a council vote.

Why it matters: Engineering standards govern how public improvements are designed and constructed. Allowing the city engineer to grant variances for site-specific or technical issues can shorten project timelines, but council members emphasized the importance of retaining a public review path for issues that would change city-wide expectations.

What was proposed: The revised language would clarify that engineering standards define commonly encountered design requirements, but cannot anticipate every site condition. When circumstances arise that standards do not clearly address, the design engineer and the city engineer would exercise professional judgment and, where appropriate, authorize a variance.

Council discussion: Several council members said they support delegating routine variances to staff to avoid project delays. Council members asked that the ordinance retain clear appeal steps and the option for staff to bring difficult or precedent-setting variances to council. Staff confirmed appeals would go to the city manager and, if necessary, the council would see matters that trigger substantive policy questions.

Public comment: Phil Schmidt (city council staff) spoke in support of the change and gave technical examples where staff-level variance authority would be useful — for example, valve-box details and meter-lid sizes — but he also urged the council to resist developer pressure to weaken construction specs that produce long-term maintenance problems.

Outcome: Council directed staff to place the ordinance change on the action agenda for a future meeting (two-week timeline was discussed). Staff said changes to engineering standards themselves would still return to council through the formal ordinance process when needed.

Ending: Council asked staff to draft language that preserves staff-level variance authority for routine, technical matters while ensuring major or precedent-setting changes are returned to the council for policy review.