North Ogden staff propose proactive code‑enforcement procedures; council agrees to empower department heads and consider a CSO in budget

City staff presented a sweeping recommendation to change how North Ogden enforces municipal codes, proposing a shift from a largely complaint‑driven system toward targeted, staff‑led proactive enforcement for life‑safety and other high‑priority cases, and asking the council to consider adding at least one community service officer (CSO) in the coming budget.

Planning Director Scott Hess told the council the city is currently "a reactive code enforcement city" and described a multi‑department proposal that would repurpose an existing permitting and case management system (iWork) to accept proactive code complaints and coordinate work across planning, building, business licensing and police. He said staff also proposes aligning initial administrative letters from permitting departments with the formal code‑enforcement notice process to reduce delays between a first notice and formal enforcement steps.

Hess and police staff said continuing or expanded proactive enforcement would require more staff time. "The real impact to this is that there's a budget impact," Hess said, and recommended adding at least one CSO (and noted more would be useful if the city wants major proactive efforts). Police and planning data presented to the council showed rising CSO call volume year‑over‑year; staff said two CSOs currently handle a broad range of duties including animal control, evidence maintenance, vacation checks and code work.

Council members repeatedly emphasized a triage approach: pursue life‑and‑fire‑safety issues proactively, but avoid using limited enforcement resources on every minor code violation. Several council members signaled support for giving department heads authority to initiate enforcement when safety issues are evident. Mayor and multiple councilmembers said they will expect consistent and documented application of rules and asked staff to return with recommended priorities and budget figures during the upcoming budget process.

Staff also asked council whether fine schedules and code timelines should be moved from ordinance text into a more flexible administrative fee schedule so staff can adjust enforcement timelines and fines without revising the ordinance in every case. Council asked staff to propose legislative clarifications for instances where the city code is inconsistent (for example, a land‑use reference to a 25‑foot setback versus an apparent 75‑foot standard elsewhere). Hess proposed synchronizing title 11 (land‑use) and title 14 (city code) language during the planning commission process.

Outcome: The council gave staff direction to proceed: department heads may pursue proactive enforcement for life‑safety and egregious violations; staff will return with a recommended CSO request for the fiscal‑year budget; and planning staff will draft ordinance corrections to resolve internal inconsistencies.