Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Council Staff Processes topic

No spam. Unsubscribe anytime.

Cambridge staff to publish tracker and explore centralized constituent-service routing after council push

Cambridge City Council · January 27, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Following council concerns about unanswered policy orders and duplicated constituent requests, city staff committed to publish a public "in-process" tracker in early February and to study centralized routing or 311-like options to reduce duplication and improve responsiveness.

City officials told the Cambridge City Council on Jan. 27 that they had cleared much of a backlog of awaiting policy-order reports and plan to make ongoing work more visible to councilors and the public.

"When I started, there were 90 awaiting reports sitting that hadn't been responded to," the city manager said, describing a prior backlog. He reported the administration had significantly reduced the number of outstanding policy orders over the last term and had responded to nearly all items that remained. "We responded to almost every single one of those," he said, and city staff pledged to finish responses on the remaining items that were passed late in the year.

Councilors and staff then discussed how to track items after a response is filed, noting cases where an awaiting report's response indicated further work but the item then disappears from public tracking, leaving councilors and residents uncertain about status. Councilor Sabrina Wheeler and others asked for an "in-process" status that would follow an item after an initial report and show subsequent steps and timelines.

City staff (represented by the city manager and Matt Nelson of the manager's office) said an internal tracker exists and that the administration would consider a public-facing version. Staff offered a provisional timeline of "early February" for an updated public status tool and monthly or quarterly updates.

Councilors also raised constituent-service issues: multiple councilors forwarding the same email to different departments often produced duplicate department responses or gaps in accountability. Deputy city staff suggested clarifying best practices (who should be copied to ensure a single staff contact sees an issue) and exploring centralized intake options (a stronger ClickFix implementation or a 311-style service). The city manager said staff would return with recommendations and committed to working with committee chairs to align priorities and reporting expectations.

The council recorded a roll-call vote to close public comment and recessed; both procedural votes passed unanimously. Councilors said they expected the staff follow-ups on the tracker and constituent-service proposals to be shared with the council and posted publicly.