Centerville debates code enforcement model and considers modern permitting software
Loading...
Summary
Planning and community development staff asked the council for an 0.8 FTE‑equivalent code enforcement resource and proposed a cloud‑based permitting system to replace manual processes; council asked for peer comparisons and more information before deciding on proactive enforcement or a complaint-driven approach.
Centerville’s planning staff told the council at the April 10 budget retreat that growth in permitting, business licensing and land‑use activity is stretching current staff and that two near‑term investments could improve service: (1) a part‑time code enforcement position to handle commercial and operating violations, business licensing compliance, signage and nuisance calls; and (2) cloud‑based permitting and business‑license software to replace paper‑based workflows.
What staff proposed: Community Development proposed a part‑time code enforcement resource (29 hours/week cap presented as a $45,000 fiscal cap) to investigate signage violations, unlicensed businesses, site‑use changes and parking/illicit‑discharge issues. Staff said enforcement could be targeted to commercial corridors (Parrish Lane) while remaining complaint‑responsive in residential neighborhoods at council direction.
Permitting and records modernization: Staff said current building‑permit and business‑licensing workflows are manual and time‑consuming (paper forms, Word documents and email). Staff requested a cloud permitting/business‑licensing product (vendor preferred by staff) with a one‑time implementation fee and annual subscription. An example vendor quoted a $12,000 implementation and roughly $25,000/year subscription; staff proposed an initial FY funding level and recommended funding implementation this year so that online permitting, GIS integration and applicant self‑service can begin before business‑license renewals.
Council reaction and next steps: Council debated the merits of hiring a code enforcement person because of past negative experiences with proactive enforcement. Several council members asked staff to collect peer city experiences, including Syracuse (where a prior code enforcement hire had been controversial) and to provide examples of neighboring cities that use code enforcement successfully. Council asked staff to outline a complaint‑based policy vs. a proactive enforcement policy and to produce RFP language and peer‑city comparisons for both the proposed code enforcement resource and the permitting software. Staff agreed to pursue vendor follow‑up, to seek integration with county systems where possible, and to return with a draft implementation and enforcement policy for council review.
