Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Constituent Services topic
No spam. Unsubscribe anytime.
Council members debate formalizing a process to track and respond to resident complaints
Summary
Council members spent the bulk of the meeting debating whether to create a centralized, low-burden system (for example a SharePoint spreadsheet with departmental tabs and simple metadata) so complaints are tracked, trended and routed to the right bureau manager; no formal policy was adopted and staff was asked to consider options.
A council member said they returned from vacation to find several constituent emails and asked the council to clarify how resident complaints should be logged and who is responsible for responding. "I would like to discuss or just understand the process for responding to these complaints," the council member said, asking who responds and how council and the mayor are informed.
Another council member recommended a simple centralized tracker — "a spreadsheet, something as simple as that," — that would allow the council and staff to see trends and ensure issues do not "slip through the cracks." That member suggested departmental tabs and limited fields (type of complaint, date received) to avoid a heavy administrative burden.
Speakers also emphasized the importance of allowing council members to keep a personal touch when constituents contact them directly while still ensuring staff follow-up. "Typically I'll just send it to the general manager and he'll copy me in on what he's doing," one member said, describing the current practice of routing constituent concerns through bureau managers.
An engineer on the call recommended capturing a few key performance indicators so the city can spot trends — for example, the number of waste-management complaints in a month — rather than recording every minor call. Council members agreed the tool should be lightweight and able to show whether complaints are decreasing over time.
The meeting did not produce a formal vote or adopted policy. Staff was asked to consider options for a centralized tracking approach and report back, with suggestions including a SharePoint-hosted spreadsheet with simple pull-down categories and a date stamp to minimize free-text entry.
The discussion concluded with council members and staff agreeing on the tradeoff between useful transparency and overburdening department staff; no implementation timeline was specified during the meeting.
