Albion council finalizes priorities for city manager goals, pushes staff for specific timelines

Albion’s City Council spent its July study session refining a consolidated set of goals the council will use to evaluate the city manager, focusing on infrastructure, municipal operations, housing and code enforcement.

The city manager opened the discussion by presenting a seven-area priority list and asking council members to mark subitems as short-term (within six months), midterm (six to 12 months) or long-term (one year or more). "We want to make sure that at least the residents feel like we're moving towards something and improvements within the community," the city manager said, urging achievable targets to inform future performance reviews.

Council members broadly agreed on several short-term items, including finalizing an inventory of sidewalks and pavement needs and creating an initial online citizen service portal. Members said identifying priority corridors and neighborhood fix-it projects is achievable in the near term, but that funding gaps — particularly for sidewalk and utility work — will require midterm planning and capital scheduling.

Staff described the city’s ongoing water meter and replacement work and noted state compliance timelines referenced in the discussion. Officials said the meter program has helped identify potential lead service connections and that the city will replace lead services as they are encountered; staff referenced a phased state-required approach with a long-range compliance horizon (discussion noted a 2041 date for staged obligations).

Council spent substantial time on code enforcement and community cleanup, where staff and the police chief described increased enforcement activity in recent years and outlined the litigation and cost implications of abatement actions. The chief cautioned that enforcement and subsequent court processes can be costly and lengthy, and council directed staff to develop a targeted enforcement strategy that balances housing stability with priority enforcement areas.

On municipal operations, council asked staff to scope a citizen-facing portal and a dashboard of performance metrics. Members recommended the portal and scheduled dashboards be prioritized as short-term deliverables and removed the word "real-time" from the short-term expectations; staff will return with proposed dashboard metrics (examples discussed included revenues, expenditures and work-order status).

Housing and downtown development conversations centered on a handful of projects council members said warrant active support — including proposals on Watson Street and two other developments (Washington Garner and Austin Street). Council and staff emphasized that utility-extension costs and who pays for those utilities remain key barriers, and members asked staff to explore funding options such as assessment districts and grants.

Council supported continuing the use of outside planning consultants (examples cited: McKenna, PCI) to provide objective reviews for planning commission cases and reduce legal risk in special-use and zoning decisions.

No final policy or ordinance was adopted at the study session. Council moved to excuse an absent member near the end of the meeting and called for a voice vote; the transcript records mixed vocal responses and does not show a clear roll-call tally or formal resolution adopting the goals. Staff was directed to return with more detailed implementation schedules, cost estimates and recommended metrics for council review.

What happens next: staff will refine the draft goals into specific, measurable tasks and bring back proposed timelines, funding sources and implementation milestones for council consideration and potential inclusion in the city manager’s evaluation framework.