Works Council and AI: Co-determination, BV Template, Two-Meeting Playbook

If you are about to roll out AI in a German company with a Betriebsrat, the legal frame is not optional and not negotiable. The Betriebsverfassungsgesetz (BetrVG) gives the Betriebsrat hard co-determination rights on every AI system that touches employees — § 80 Abs. 3 (right to expert consultation), § 87 Abs. 1 Nr. 6 (co-determination on technical systems that can monitor performance), § 95 Abs. 2a (co-determination on selection criteria when AI is involved in personnel decisions). Skip these and you do not just have a legal problem — you have a rollout that the works council can stop in week three.

This guide is the practical version: which sections of BetrVG apply to which AI use case, what a working framework Betriebsvereinbarung KI looks like, how to brief the Betriebsrat in two meetings instead of six months of stalling, and what the first court ruling on AI co-determination from 2024 actually means for Mittelstand AI rollouts.

Almost every workforce-AI rollout in Germany triggers at least one of three BetrVG paragraphs, and most trigger all three. Knowing which is which lets you write a cleaner Betriebsvereinbarung and run a faster negotiation.

In 2024, the Arbeitsgericht Hamburg issued the first German court ruling on Betriebsrat co-determination at the introduction of generative AI. The headline: ChatGPT used purely on private accounts of employees, without integration into employer systems and without employer instruction, did not trigger mandatory co-determination — because the employer had no technical control over the system. The full ruling and analysis is in Bird & Bird\u2019s coverage.

What that does NOT mean: that AI without explicit employer instruction is co-determination-free. The ruling was narrow. The moment an AI system is provided, integrated, instructed, or paid for by the employer — § 87 Abs. 1 Nr. 6 BetrVG triggers, and a Betriebsvereinbarung is mandatory. The Bitkom Leitfaden Künstliche Intelligenz und Mitbestimmung 2026 is the most up-to-date guidance for the post-2024 landscape.

What that DOES mean for a Mittelstand rollout: shadow AI usage on private operator phones is technically outside co-determination, but the moment you provide a sanctioned, opt-in WhatsApp Business + AI summary system, you are inside co-determination. Which is exactly the right place to be — sanctioned, governed, and signed off, instead of un-sanctioned and untracked.

A working framework Betriebsvereinbarung KI for a Mittelstand setup covers exactly twelve sections. Anything more is over-engineering — anything less and the Betriebsrat will not sign or the employer will leave loopholes that bite later. The structure below is the format used by skill-sprinters and betriebsrat-kanzlei.de, adapted for a 30-to-300-employee Werkzeugbauer.

Most Mittelstand AI rollouts stall not because the Betriebsrat is opposed, but because the employer comes to the first meeting with a finished system and a take-it-or-leave-it framing. The Betriebsrat then exercises § 80 Abs. 3 (bring an external Sachverständigen at the employer\u2019s cost), and the next six months are spent on a technical dispute about a system the Betriebsrat was never consulted on during design.

The two-meeting alternative: meeting one is a 60-minute briefing before any vendor selection. You explain the use cases, the categories of personal data involved, the EU-hosting commitment, the opt-in default, the minimum cell size of 5, and the explicit § 9 ban on performance monitoring. You give them the draft architecture document and the 12-section BV outline. Meeting two, two to three weeks later, is the BV negotiation itself. Most Mittelstand-Betriebsräte sign within meeting two if meeting one was honest. The Sachverständigen budget should be allocated regardless — but it gets used as a sounding board, not as a delay weapon.

A signed Betriebsvereinbarung KI is the precondition, not the destination. After signing, the rollout follows the 90-Tage-Einführung from the AI playbook for family-owned manufacturers: days 0–14 Inhaber-Brief and Werkstatt-briefing (yes, even after the BV — the Betriebsrat speaks for the workforce, but the workforce still needs to hear the Inhaber). Days 15–30 Pulse-Baseline and AI-Readiness-Check. Days 31–45 the first pilot use case (typically shift handover). Then the loops compound.

The BV gets reviewed at month 6 and month 12. By month 12 you usually have a 1–2 page addendum extending the use-case list (Loop 2 knowledge capture, Loop 3 daily KVP pulse) — written together with the Betriebsrat, signed in one short meeting.