Nobody Watches the Four-Hour Council Meeting: Turn Public Meetings Into an Accurate Five-Minute Audio Recap (2026)

1. The gap: decisions nobody hears about

There are roughly 90,000 local governments in the United States, according to Northeastern University professor Beth Noveck, and "almost none of them have meaningful public-facing AI tools" (The Renovator, June 2026). The same article notes that only 9% of Americans under 30 follow local news very closely, citing Pew. As local newsrooms have shrunk, there's often nobody left whose job is to sit through the meeting and tell residents what happened. We covered the news-desert side of this in our hyperlocal audio briefing guide. This post is narrower: the meeting recap itself.

Audio fits the problem. People who won't watch a four-hour stream or read a sixty-page agenda packet will listen to five minutes while driving or cooking. One citizen project already publishes AI-voiced recaps of a city's council and planning board meetings for residents who "only have 10 minutes a week" (Saratoga Civic Pulse).

The audience is the person who would care if they knew: the parent whose school's boundary is changing, the renter on the street being rezoned, the homeowner whose dues are going up.

2. How AI meeting recaps go wrong

The early tools are instructive. A reporter testing one recap app described the result as "hollow": an AI voice reading a summary "with no sense of how individual council members voted and why", and the developer acknowledged it "has occasionally gotten budget numbers wrong" (The Renovator). Town clerks report AI transcription mishearing local terms, including one board that spent time teaching a system that "abutters" were neighbouring property owners, not butter (Concord Monitor).

The two-host conversational format popular in AI podcast tools deserves a direct warning. It's engaging for study notes. For a recap of a contested vote it's the wrong choice, because a conversation needs opinions, and opinions are exactly what a neutral recap must not have.

3. The format: one narrator, four parts, five minutes

Use a single, calm narrator voice and the same structure every time. Consistency is part of what makes residents trust it.

1. Decided (about 2 minutes). Each action item: what it was, the motion as worded, the result, and the roll-call vote by name. "The motion to approve the revised parking ordinance passed four to three. Voting yes: [names]. Voting no: [names]."
2. Discussed, not decided (about 1 minute). Items that were presented, debated, tabled or sent back to committee, with what happens next.
3. Coming up (about 1 minute). Next meeting date, public hearings, comment deadlines and anything on the next agenda that residents might want to speak to.
4. How to take part (30 seconds). How to comment, where to find the full video, agenda packet and official minutes.

Open with one sentence that names the body, the date and the fact that this is a summary: "This is a five-minute summary of the Riverside City Council meeting of October 1st. It is not the official record." Close the same way every week.

What to leave out: adjectives about the debate ("heated", "lengthy"), characterisations of members' motives, and anything you'd need to justify with "it seemed like". If a debate was long, say how long. If it was contested, the vote shows it.

4. The verification pass

This is the step that separates a useful recap from a liability. Budget fifteen to thirty minutes per meeting.

Then listen to the rendered audio once, all the way through, with the checklist in front of you. Text-to-speech can turn a correct "$4.2M" or "Ordinance 2026-14" into something wrong aloud. Write numbers out the way they should be spoken; our numbers normalisation guide covers the patterns. Add local street names and members' names to your pronunciation list once and reuse it.

Keep a short timestamp list alongside the recap, one per item, linking to the point in the official video. It lets anyone check you, which is the point.

5. Public comment and private residents

Public comment is on the record, but a recap is a different medium. A resident who spoke for two minutes at a meeting didn't agree to have their name in a weekly audio programme heard by the whole town. Our recommendation:

• Summarise public comment by topic and count: "Eleven residents spoke about the proposed bike lane; seven opposed, four in favour."
• Don't name private residents. Named officials, staff and organisations speaking in an official capacity are fine.
• Don't quote or paraphrase individual comments in a way that makes the speaker identifiable.
• Never generate a synthetic version of a resident's voice. If you use clips at all, use officials' on-the-record statements, and only if your policy allows it.

6. Production workflow

1. Get the inputs: the agenda and packet, the clerk's action list or draft minutes if available, and the meeting transcript or video.
2. Draft the script in the four-part structure, using AI to summarise the transcript, but filling in votes and motion wording from the official record rather than from the summary.
3. Run the verification pass (section 4).
4. Render with one consistent narrator voice. Keep the same voice every week; residents learn to recognise it.
5. Listen once against the checklist.
6. Publish with a transcript, the timestamp list and links to the official video and minutes.
7. Aim for 24 to 48 hours after the meeting. Fast enough to be useful, slow enough to verify.

Clerks are already using AI for the minutes themselves. The town clerk of Long View, North Carolina told Smart Cities Dive she went from four to eight hours of minutes work per meeting to about 30 to 60 minutes (Smart Cities Dive). The recap should sit downstream of that work, not replace it. If your clerk already produces an action list, the recap is mostly a script-and-render job. If you're recording meetings yourself, our guide to turning recorded meetings into episodes covers the audio side.

7. Disclosure, corrections and the official record

• Say it's AI-assisted. One line at the end: "This summary was prepared with AI tools and reviewed by [office or person]." Noveck's point in the Renovator piece is the right one: disclosure tells people to go and check the original source.
• Say it's not the minutes. Approved minutes remain the official record. The recap is a guide to it.
• Publish corrections. If you get something wrong, re-render the corrected recap, note the correction at the top of the show notes and in the next episode. AI narration makes a corrected re-render cheap, so there's no excuse to leave an error up.
• If you're the public body, check whether your communications policy, records rules or open-meeting law say anything about official summaries. If you're a volunteer, make clear you're independent.

8. Accessibility and reach

Publish the transcript with every episode. It's searchable, it serves residents who are deaf or hard of hearing, and public bodies have accessibility obligations for web content; our ADA Title II guide covers the US timeline. If a significant share of residents speak another language, a second-language version of the same verified script reaches people the English-language minutes never did. Our school district language-access guide explains why audio often works better than translated text for those families.

Distribution: put it where residents already are. A podcast feed, the city or district website, the newsletter, a phone line for residents without smartphones, and a short clip of the "Decided" section for social media.

9. FAQ

It can draft a summary quickly, but it makes mistakes with numbers, names and votes. Treat the AI output as a first draft and verify votes, motions and figures against the official record before publishing.

No. Conversational formats add reactions and opinions, which read as bias when the subject is a contested vote. Use one neutral narrator and a fixed structure.

About five minutes for a typical meeting: two minutes on decisions with votes, one on items discussed but not decided, one on what's coming up, and thirty seconds on how to take part.

No. Approved minutes are the official record. Say so in every recap and link to them.

We recommend not. Summarise comments by topic and count, and name only officials, staff and organisations speaking in an official capacity.

Yes. The same four-part structure works for any body that votes: school boards, planning commissions, HOAs and nonprofit boards. For private bodies like HOAs, check your governing documents on what can be shared outside the membership.