TruaceTracing the truth around AIMonday, July 13, 2026
TRV-2026-0156Certified recordPeer-reviewed

They Think AI Can Do More Than It Actually Can: Practices, Challenges, & Opportunities of AI-Supported Reporting In Local Journalism

Declining newspaper revenues prompt local newsrooms to adopt automation to maintain efficiency and keep the community informed. However, current research provides a limited understanding of how local journalists work with digital data and which newsroom processes would benefit most from AI-supported (data) reporting. To bridge this gap, we conducted 21 semi-structured interviews with local journalists in Germany. Our study investigates how local journalists use data and AI (RQ1); the challenges they encounter wh…

Science · The Trace — both readings · certified 2026-07-13 · v1 · article view · machine-readable

Current reading — gain

Local journalists in Germany reported willingness to use AI-supported tools to process data and discover stories to help maintain efficiency.

Current reading — problem

Local journalists in Germany do not fully leverage AI to support data-related reporting work, linked to limited awareness of what AI can do.

What this doesn’t fix

Findings are bounded by a small qualitative sample of 21 local journalists in Germany and by limited existing research on local data practices, which constrains generalizability.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0156, v1: “They Think AI Can Do More Than It Actually Can: Practices, Challenges, & Opportunities of AI-Supported Reporting In Local Journalism.” Truvace, 2026-07-13. /record/TRV-2026-0156 (accessed at citation time). sha256 a5b2621a7a34e14d

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1a5b2621a7a34

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0156 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.