At 4:00 a.m., while the sports desk is still empty, an agent is reading last night’s box scores.

It works through every finished game on the slate, breaks down what decided each one, and, by 5:00 a.m., has filed a recap for every game plus a preview of what’s ahead that night.

A note lands in Slack: Drafts are ready. The agent doesn’t predict winners, and, if a starting pitcher hasn’t been announced yet, it says so instead of guessing. By the time the desk opens, the box score grind is done. An editor picks up the work that needs human review and editorial decision-making.

I work at Brightspot, and that overnight scene is a composite drawn from publishing use cases that we’re helping to engineer on behalf of our customer base.

The workflow isn’t unusual. It’s also a better answer to “what should agentic AI actually do in my newsroom” than most AI headlines I read these days, which often seem more about diagnosing the problem than fixing it.

Much of the coverage of agentic AI in media goes big: multi-agent research systems, AI co-hosts for audio content, tools for deep data analysis.

All real. All worth watching.

But publishing teams getting real results out of this technology aren’t necessarily chasing the moonshot use case. They’re pointing agents at the work that’s about repetition: The grind that eats the first 60 minutes of every shift and doesn’t need an editorial call, but just their time.

A quick definition, since the term gets thrown around loosely: An AI agent isn’t a chatbot with extra steps. It combines three things:

1. Reasoning: breaking a goal into steps.
2. Tool use: connecting to the systems that actually run a newsroom through a connector standard called model context protocol (MCP).
3. Autonomy: working through those steps and correcting itself without someone babysitting each one.

A chatbot answers a question. An agent does the job and hands you the result. An agent in an existing workflow also combines logic and consistency for assured, governed outputs.

Here’s what that looks like once it’s pointed at the repetitive stuff:

• A global wire service runs an agent that reads incoming stories across beats and validates them against source material, retires what’s gone stale, and combines related pieces into one coherent package before a second layer figures out which piece a specific reader actually wants next.
• A large editorial team runs its agentic workflow automation as a review step before anything reaches a human. It catches broken links, leftover placeholder text, brand violations, and even the contextual errors that spellcheck misses (like “there” for “their”). Every fix comes back as a tracked edit with a reason attached. The editor still decides what is published.
• A European broadcast group chains a dozen small agents into one production line: transcribing interviews, tagging images, drafting headlines in-house style, checking SEO meta-data, flagging old photo galleries for a refresh. None of these tasks is worth building a dedicated system for on its own. Chained together, they clear a dozen manual steps from every article’s path to publish, whether or not anyone remembers to kick them off.
• A regulatory intelligence publisher points an agent at dozens of government feeds and subscription alerts. It reads new postings, weighs them against criteria the editorial team sets in advance, and, for anything that clears the bar, drafts a pitch and assignment directly in the content management system (CMS). The editor doesn’t start from a raw filing. They start from a pitch with the source material attached and a note on why it got flagged.
• A multi-market broadcaster keeps translated editions in sync. An update to the source article used to mean someone noticing, translating, and republishing — three separate manual steps that were skipped more often than anyone wanted to admit. Now a correction made once shows up as a review item in every regional queue the same day.

Let’s call it what it is: An agent going through the daily checklist steps we all have in our heads, our notepads, or an established order of operations. Just faster, and it happens every single time.

None of it works, though, without the part that typically doesn’t make it to the live demos: the permissioning system.

An agent that can publish is a risk. An agent that can only do what the person who set it up is allowed to do is a tool. That’s the distinction that creates the confidence for the system to exist. If a human editor can’t publish without approval, neither should the agent acting under them.

A regulated publisher’s correction workflow is the sharpest version of this. Recalling a piece used to mean an editor remembering multiple separate steps, in the right order: Select the recall flag, clear the body, update the title, add the legalese, exclude it from search, apply the tag.

Miss one, and the correction doesn’t fully do its job.

Now an agent loops through all the steps the moment someone selects “recall,” the same way every time, whether it’s their first correction or their 100th. Nothing about that removes the editor. It just means the editor’s memory isn’t the last line of defense anymore.

Automation tools integrate agents that inherit a newsroom’s existing roles and approval chain, not a parallel set of rules nobody agreed to. The editor on the sports desk isn’t writing 15 recaps at dawn. They’re deciding what leads, what’s too sensitive to automate, what the agent’s draft missed, the trade rumour, the player whose September is quietly falling apart.

Those calls were always the actual job. The checklist just isn’t taking up the morning anymore.

Banner image: Adobe stock image by Long.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .