Carbondale council seeks clearer staff–council communications, proposes newsletters and study sessions

Carbondale councilmembers opened a broad discussion about how elected officials and staff communicate information, manage projects and notify the public — a conversation prompted in part by the high turnout on the camping-ordinance item.

Council member Colombo (S3) urged staff to surface project-level information earlier in a project’s timeline and recommended combining weekly timeline updates with vertical, project-specific documentation so council members can review both the current status and the history behind proposals. ‘‘We should know sort of the steps that are happening so that we can make a better informed decision when it does come to us,’’ Colombo said.

Several council members asked for more comprehensive weekly or monthly reports that include department-level detail and upcoming decisions, not just retrospective summaries. Council member Lowes (S5) suggested periodic study sessions or informal retreats where council and staff can discuss complex items without the constraints of a standard council meeting. The idea of a volunteer-host registry and a community newsletter also received support from council and members of the public.

City manager and staff responded that they take the requests seriously but cautioned about legal constraints (Open Meetings Act) and staff bandwidth. The city manager (S13) and Community Development Manager John Lindsay (S27) said they would work to improve the balance between useful transparency and operational feasibility and promised incremental improvements to weekly updates and better public-notification tools.

Council asked staff to develop options for improved reporting, including a public-facing newsletter or expanded push-notification signups, more consistent monthly department updates, and the logistics for occasional study sessions. Staff also noted the need to preserve confidentiality where legally required and to avoid creating excessive reporting burdens that would reduce time for core operations.

The discussion closed with council consensus to cancel one May meeting (May 12) and to pursue a single meeting on May 24; staff were asked to return with specific proposals on reporting formats and outreach mechanisms.