The Works Council AI Notification Packet — BetrVG, WOR, CSE, and the EU AI Act overlay

The single biggest cause of EU AI deployment slippage in 2025 was not technical and was not regulatory in the AI Act sense. It was works-council notification conducted late. A deployment that engages the works council at vendor-shortlist landing typically completes in 6–9 months. A deployment that engages the works council at rollout typically completes in 12–18 months, and the shape of the rollout is determined by what the works council can be persuaded to accept rather than what the business originally wanted.

This packet is the early-engagement materials for three EU jurisdictions plus the EU AI Act overlay. It is sized for the actual conversation that needs to happen, which is 90 minutes long, attended by the project lead, HR lead, IT lead, and works-council representatives, and produces a written acknowledgement that the deployment can proceed (or a list of conditions that the deployment must meet first).

Three jurisdictions, one underlying logic

The legal frames in Germany, the Netherlands, and France are different in detail and substantially the same in intent. Each requires the employer to notify the employee representatives before introducing technical equipment that monitors or evaluates employee work activity. The AI question that triggers each frame is the same: does this system capture, process, or analyse work activity by an identifiable employee? If yes, the notification obligation is active.

The packet does not argue with the legal frames. It assumes you are deploying within them and provides the materials to do so efficiently.

Section 1: Pre-notification preparation

Before the conversation with the works council, the project team needs four documents ready. Skipping any of them moves the conversation backward into a documentation request rather than forward into a deployment decision.

1. System characterisation: what the AI system does, who built it, what the foundation model is, what the deployment use case is, and what categories of employee data flow through it. The first two pages of the AI DPIA template (RES-002) cover this.
2. Risk classification: EU AI Act Annex III mapping, GDPR Article 22 mapping, and the case-law citations relevant to the specific use case (employment Annex III point 4 if hiring/firing/performance is touched, education Annex III point 3 if training is touched, etc.).
3. Mitigation summary: the technical, organisational, and contractual measures from section 4 of the DPIA, presented as bullets the works-council reps can absorb in 10 minutes.
4. Reversibility statement: what happens if the works council asks the deployment to be paused or rolled back. The honest answer to this question is the foundation of trust in the conversation.

The packet provides a template for each. The materials are written for a non-technical audience without dumbing down the substance.

Section 2: Germany — BetrVG §87(1) point 6

The Bundesarbeitsgericht has consistently interpreted §87(1) point 6 broadly: any technical equipment that captures, processes, or analyses employee work activity triggers the co-determination right, regardless of whether monitoring is the primary purpose. Microsoft 365 Copilot, Notion AI, ClickUp AI, Asana AI, and most agentic AI tools meeting employees in their daily work meet this definition.

The German packet contains:

1. Notification letter to the Betriebsrat, written for the §87(1) point 6 standard. Cites the system, the use case, the data categories, the foundation model, the vendor, the contract reference, and the proposed deployment timeline.
2. Betriebsvereinbarung draft (works council agreement), covering: deployment scope, employee opt-out where applicable, monitoring and evaluation boundaries (what the system may NOT be used for, e.g., individual performance ranking), audit log access for the Betriebsrat, review cadence, termination conditions.
3. Pilot framework: a 60–90 day pilot at one team with documented success criteria and a Betriebsrat-attended review at the end. The pilot is the de-risking mechanism that makes the broader Betriebsvereinbarung possible.
4. Q&A reference on the Bundesarbeitsgericht broad interpretation, with the leading cases cited for the situations Betriebsrat questions tend to land on.

The early-engagement workflow that compresses Mittelstand AI timeline from 12–18 months to 6–9 months is documented in detail in OPS-049, the operators-register piece on Mittelstand AI deployment.

Section 3: Netherlands — WOR Article 27

The Wet op de Ondernemingsraden Article 27 requires the employer to seek the consent of the Ondernemingsraad before introducing or modifying systems that process personal data of employees. The Sociaal-Economische Raad guidance from 2024 explicitly extends this to AI systems that process employee work product. The Autoriteit Persoonsgegevens framework from 2025 mirrors the position.

The Dutch packet contains:

1. Adviesaanvraag (advice request) to the Ondernemingsraad. Cites the system, use case, data categories, foundation model, vendor, deployment timeline, and the GDPR Article 6 lawful basis being relied upon.
2. Toestemming-vraag (consent request) where the system processes personal data of employees, specifying the processing purposes and the boundaries on those purposes.
3. OR convenant draft (works council agreement), parallel to the German Betriebsvereinbarung but reflecting the Dutch consent-rather-than-co-determination posture: deployment scope, opt-out mechanisms, monitoring boundaries, audit access, review cadence.
4. Q&A reference on the Sociaal-Economische Raad 2024 guidance and the Autoriteit Persoonsgegevens 2025 framework, with the leading rulings cited.

The Dutch posture differs from the German in one practical respect: the Ondernemingsraad’s role is advisory plus consent-on-data-processing, where the Betriebsrat’s role is co-determination on the technical equipment itself. The packet documents the difference so the project team does not over-prepare for the wrong frame.

Section 4: France — Comité Social et Économique consultation

The Code du travail Article L2312-8 requires CSE consultation on the introduction of new technologies that have consequences for employees. The 2024 doctrine on AI is consistent that AI deployments meeting employees in their work surface trigger the consultation requirement.

The French packet contains:

1. Convocation au CSE (CSE meeting convocation) with the agenda item on AI deployment.
2. Note d’information (information note) covering the system, use case, data categories, foundation model, vendor, GDPR + EU AI Act posture, and deployment timeline.
3. Procès-verbal template (meeting minutes template) capturing the CSE’s avis (opinion) on the deployment.
4. Délais de consultation (consultation timeline) reference: the legal minimum periods for the CSE to render its opinion, and the practical timeline that French case law treats as good-faith engagement.

The French packet also addresses the data-protection-officer consultation that runs in parallel with the CSE consultation under French data protection law.

Section 5: EU AI Act Article 26(7) overlay

EU AI Act Article 26(7) adds, from 2 August 2026, a deployer obligation to inform workers and their representatives before putting a high-risk AI system into service that will be used to make decisions about them or affect them. This obligation runs in parallel with the national works-council frames; it does not replace them.

The overlay packet contains:

1. Article 26(7) notification template specific to the EU AI Act obligation. Designed to be appended to the national notification (Betriebsrat, Ondernemingsraad, CSE) so a single document satisfies both frames.
2. High-risk classification statement anchored to the Annex III category that triggers Article 26 obligations for the specific deployment.
3. Worker information note in plain language, suitable for distribution to all affected employees, covering: what the system does, what data it uses, what decisions it influences, and what rights employees have to seek human review of those decisions.
4. Recordkeeping template for the Article 26 documentation that the supervisory authority may request.

Section 6: Multi-jurisdiction deployment workflow

For deployments crossing multiple EU jurisdictions, the packet includes a workflow that runs the notifications in parallel rather than sequentially. The workflow assumes the systems are identical across jurisdictions and the variations are in the legal posture, not the technical scope.

The workflow:

1. Project team prepares the four pre-notification documents (section 1).
2. Project team drafts the per-jurisdiction notifications using sections 2–4 as starting points.
3. Project team reviews with local HR and local legal counsel for each jurisdiction.
4. Project team requests parallel notification meetings, all within a four-week window.
5. Project team consolidates the per-jurisdiction outcomes (German Betriebsvereinbarung, Dutch convenant, French avis) into a single deployment-go decision document.
6. Project team executes the Article 26(7) notification (section 5) once the national notifications are complete.

The parallel workflow assumes the company has three local works councils to engage. For companies with European Works Council representation in addition to local councils, the EWC is engaged at step 1 (pre-notification preparation) so the local councils are not surprised by the EWC having a different position.

Section 7: What this packet does not do

The packet does not argue that AI deployments should bypass works-council engagement. It does not provide language for minimising what the system does or what it captures. It does not suggest withholding the foundation model name or the vendor identity. The publication’s editorial position is that early, complete engagement with works councils produces faster deployments with more durable agreements; the packet is built to that thesis, and tools used against that thesis will produce predictable failure.

Versioning and review

This packet is on a 90-day review cycle. Section 5 (Article 26(7) overlay) will be revised after the first wave of EU AI Act enforcement actions in late 2026, when supervisory authority interpretations of the Article 26(7) notification standard become observable. Sections 2, 3, and 4 will be revised when the first cross-jurisdictional case law on AI deployment notification clarifies how the BetrVG broad interpretation, the Dutch consent posture, and the French CSE consultation interact in practice.

Spotted a missing template, an out-of-date legal citation, or a workflow that does not survive contact with your jurisdictional reality? The corrections policy applies.