Beyond the note-taker: What city managers should demand from meeting intelligence

SDI Productions via Getty Images
COMMENTARY | General AI tools and note-takers fall short of what is required to act on decisions made. Several key questions help separate a note-taker from meeting intelligence.
When a governing body gives direction in a public meeting, the city manager is responsible for what happens next. They dispatch staff, commit budgets and set deadlines based on what the record says the body decided.
When that record is thin or contested, the manager is the one exposed. "Council directed us to proceed" meets "No, we asked you to bring it back first."
Resolving such disputes takes real time and effort. Someone has to replay imperfect audio, straining to make out who actually said what. A vague or contested record offers no protection, and the costs land squarely on the manager's desk.
What follows is a guide to understanding where those costs actually live, why general-purpose AI tools fall short of what public sector meetings require, and what a city manager should demand from any solution before committing to it.
The Labor Cost is Enterprise-Wide
It is tempting to treat documentation as the clerk's burden alone, but in practice it is spread across the whole organization.
Planning and zoning, code enforcement and other quasi-judicial bodies require records precise enough to survive appeal. Advisory boards, committees and project meetings each generate their own minutes, captured by staff whose actual jobs are something else.
The hours and the costs behind them are substantial, and largely invisible because they sit buried in dozens of individual workloads. And when experienced staff leave, the conventions behind those records walk out the door with them.
That is the number a manager should be able to cite: the aggregate staff time consumed capturing, drafting, reviewing and re-litigating meeting records across every body the organization supports. Trimming that load even modestly returns professional time to higher-value work and shortens the gap between a decision and its execution.
A Note-Taker is Not Enough
The consumer transcription and summary tools that took off during the remote work era produce a readable recap, but nothing more. They cannot tell a motion from a discussion, recognize when a vote has been taken, attribute a statement to the right official in a crowded chamber, or organize output around a formal agenda.
A summary captures the gist. A record captures what was officially decided, by whom, and how. That is what holds up when a decision is challenged.
What local governments need is a tool built around the structure of a public meeting. It should follow the agenda, identify motions and their movers and seconders, log how each member voted, flag direction given to staff, and attribute remarks accurately.
It should also do it the same way every time, giving clerks a uniform, structured first draft regardless of who takes the notes or how complex the meeting gets.
Match the Minutes Standard and Don’t Over-Capture
More documentation is not automatically better, and a manager should be wary of any tool that assumes it is. Most bodies deliberately keep summary or action minutes rather than verbatim transcripts, both to stay focused on decisions and to avoid creating a discoverable record where none is required.
A tool that captures everything by default can expand a jurisdiction’s public-records and retention exposure instead of reducing its workload.
The better approach is configurable. Good meeting intelligence lets a jurisdiction match its own adopted minutes standard — action minutes for one body, fuller detail for another, verbatim only where law or local policy demands it — and apply the right retention treatment to each.
The goal is the correct record produced quickly, not the maximum record.
Building the Business Case
For a manager weighing an investment in better meeting documentation against competing budget requests, the case rests on three returns.
First, recovered labor: staff hours redirected from transcription and reconstruction to review and oversight.
Second, speed: draft minutes delivered in hours rather than days, easing public-records turnaround and transparency obligations.
Third, risk reduction: a defensible, consistently formatted record that protects staff when direction is disputed and holds up when a quasi-judicial decision is appealed.
Each of these gains can be quantified in hours saved, turnaround time, or legal exposure avoided, and defended in a budget request But those numbers have to come from somewhere.
City managers should undertake a focused pilot, one standing committee and one recurring project meeting, to produce real figures on all three before any broader commitment.
How to Evaluate Your Tool
The city manager rarely makes the decision alone. Technology teams increasingly lead the evaluation, scrutinizing security, permissions, governance, and deployment. So it’s worth bringing IT in early and treating its review as part of the decision, not a formality after it.
When evaluating various AI meeting tools, it’s important to ask some key questions to separate meeting intelligence from dressed-up note-takers:
- Was it built to produce agenda-based, decision-focused minutes, or just a summary?
- Can it match our adopted minutes standard for each body, rather than forcing one format on all of them?
- How does it identify and attribute speakers in a full room, so a known official is recognized reliably rather than guessed at from seating or context?
- Where does the data reside, and how does the solution fit within the organization's security, governance, and records-management requirements?
- Can retention and access controls mirror our existing records policy?
- Does it integrate with the systems we already run?
The right answers point to a tool that understands a public meeting is not a conference call. The wrong ones point to software that will leave the manager exactly where they started, accountable for executing decisions no one can quite confirm.
Ayelet Levi is a senior product manager at voice AI provider AudioCodes, with more than two decades of experience spanning product management, software development, and technology leadership. In her role, she helps shape AI-powered voice solutions for organizations worldwide.




