Works Council and AI Introduction: Plan Co-determination Early

In Germany, the works council has co-determination rights in almost every AI introduction, and section 90 BetrVG requires the employer to inform it at the planning stage, before the tool is selected. Involving it only once the pilot is running costs weeks of coordination that a few early meetings could have settled. For executive management, co-determination is therefore a planning matter with a fixed place in the project plan.
Why involvement is a delivery topic
An AI application is only introduced once the business functions use it in their daily work, and that depends on questions management and the works council answer together: which data the system processes, who can see how individuals use it, and how tasks change. As long as these remain open, managers hesitate and employees use the tool cautiously.
The planning rule follows directly. An initiative whose framework has been agreed with the employee representatives can be scheduled; one without that agreement carries an open item that falls due shortly before rollout, when delays are most expensive. In legal terms, the employer may not introduce an application subject to co-determination without the works council's agreement, and the works council can obtain a court order to stop its use. Involvement therefore belongs in the project plan like any other dependency, with a date, a named owner and a defined result. How this step fits into the full sequence of an introduction is set out in the article From pilot to scale.
This article provides an overview and does not constitute legal advice.
When is AI subject to co-determination?
AI is subject to co-determination as soon as the company provides it and the application generates data that allow conclusions about the behavior or performance of individual employees. That applies to almost every application licensed across a company. Four provisions of the German Works Constitution Act (BetrVG) are decisive for AI initiatives:
- Section 87(1) no. 6 BetrVG: the works council co-determines whenever a technical system is capable of monitoring the behavior or performance of employees. The Federal Labor Court treats objective capability as sufficient; no intention to monitor is required.
- Section 90 BetrVG: the employer must inform the works council in good time when planning technical installations and working procedures, and discuss the effects with it, explicitly including the use of AI.
- Section 80(3) BetrVG: where the works council has to assess the introduction or use of AI, calling in an expert adviser is deemed necessary.
- Section 95(2a) BetrVG: selection guidelines for hiring, transfers and dismissals remain subject to co-determination even when AI drafts or applies them.
In addition, the rules on order in the establishment (section 87(1) no. 1) apply when the company sets usage rules for AI, and the provisions on vocational training (sections 96 to 98) apply once tasks change so far that existing skills no longer suffice. In companies with more than 20 employees entitled to vote, the introduction of fundamentally new working methods can also constitute an operational change under section 111. That is the case for AI applications that restructure entire workflows, and it triggers negotiations on a reconciliation of interests.
The lower boundary is equally clear. A German labor court ruled in 2024 that employees using a publicly available language model through private accounts in the browser does not trigger co-determination under section 87(1) no. 6, because no usage data reach the employer. For project planning, every AI application that the company provides and whose use it can log is therefore a topic for involvement. Microsoft Copilot and comparable integrated assistants fall clearly on the co-determined side; the details are in Introducing Microsoft Copilot.
A single yes means involvement is planned as a fixed step. A yes to the fifth question adds the obligations of the EU AI Act: deployers of a high-risk system in the workplace must inform workers' representatives and the affected employees before putting it into service. The classification is explained in High-risk AI under the AI Act.
Which questions does the works council ask?
The works council asks the same five questions in almost every meeting, and presenting written answers shortens the coordination considerably:
- Which personal data does the application process?
- Which logs are created, and who has access to them?
- For which purposes may evaluations be used, and for which may they not?
- What training do employees receive?
- How do tasks and responsibilities change?
The core of most negotiations is the third question. Works councils accept AI applications far more quickly when monitoring the performance and behavior of individuals is explicitly excluded and evaluations are only aggregated above a defined group size. The commitment costs little, because the business case rests on process metrics.
A process model in four steps
- Describe the use case. A short description records purpose, user groups, data types and logging. It is the shared basis for all further steps and fulfills the duty to inform under section 90.
- Agree the framework before selection. Management and the works council clarify which limits should apply, for example for the evaluation of individual performance. Vendors are then assessed against known requirements, and the selection does not have to be reopened later.
- Run the pilot within the agreed framework. A defined group and a fixed duration provide experience on which both sides can base the later arrangement. Many companies secure the pilot with a time-limited informal agreement.
- Fix the arrangement for routine operation. The findings from the pilot feed into a binding agreement, usually a works agreement.
How long does coordination with the works council take?
With good preparation, you should plan two to four months from the first meeting to a signed works agreement. The lower end applies to an application with a clearly limited user group, a complete short description and an existing framework agreement on IT systems. The upper end applies to company-wide assistants with access to email, documents and calendars, because logging and access rights need more detailed rules there. An expert review adds its own duration. This period belongs in the plan from the start.
For project control, involvement is treated like a technical milestone: a named contact such as the product owner, fixed meeting dates in the plan, and the same status information the steering committee receives. Enablement of employees runs in parallel; the approach is described in Change management for AI introductions.
What happens if management and the works council cannot agree?
If no agreement is reached on a matter subject to co-determination, the conciliation board decides, and its ruling replaces the agreement between employer and works council (sections 87(2) and 76 BetrVG). The board consists of an equal number of members from each side and an impartial chair, who is appointed by the labor court in case of dispute. The works council can therefore delay an AI introduction, but in these matters it cannot prevent it permanently.
For planning purposes, the conciliation board is still the least favorable route: the application may not be introduced until the ruling, and the employer covers the costs. Companies that agree the framework before vendor selection and exclude individual evaluations rarely need it.
How Niehues Consulting plans introductions with involvement
Niehues Consulting guides AI initiatives using the Niehues Delivery Model in three phases: Understand, Build, Introduce. Three of its review questions matter for works council involvement. In the Understand phase the question is: who decides, who delivers, who uses? The answer goes into the short description, which serves as notification under section 90 and as the basis for the first meeting. In the Build phase the model asks which roles, decision paths and interfaces operations require. Here, prototypes prove the value in the real workflow and run within the agreed framework from the start. In the Introduce phase the question is whether users are enabled and processes adapted before the works agreement secures routine operation.
Delivery management provides the control: involvement is a work package with a date and a named contact, and it appears in the status report like any other deliverable. For managing directors and heads of department, this results in a timeline that contains the agreements instead of waiting for them. The entry point is the free initial consultation of 30 minutes.
Frequently asked questions
Does the works council have to approve AI?
Yes, for any AI application that the company provides and whose use can be attributed to individual employees, the employer needs the works council's consent. The basis is section 87(1) no. 6 BetrVG, under which objective capability to monitor is sufficient. Without agreement, the conciliation board decides.
When must the works council be involved in an AI introduction?
Under section 90 BetrVG, the works council must be informed at the planning stage, before a vendor is selected. The information must come early enough for its proposals to be taken into account in the planning. A short description of the use case fulfills this duty and serves as the basis for further discussions.
Which section of the German Works Constitution Act covers AI?
The BetrVG names AI explicitly in three places: section 80(3) on expert advisers, section 90(1) no. 3 on information during planning, and section 95(2a) on selection guidelines. The central co-determination right follows from section 87(1) no. 6 on technical systems capable of monitoring behavior or performance. That provision does not mention AI explicitly, but covers it through the capability to monitor.
Can the works council bring in an expert adviser on AI?
Yes, under section 80(3) BetrVG an expert adviser is deemed necessary when the works council has to assess the introduction or use of AI. The details, such as the person, scope and fee, are agreed with the employer, who pays the costs. Where several AI applications are planned, a standing expert adviser is worthwhile, and the Act expressly permits one.
Is ChatGPT subject to co-determination in a German company?
ChatGPT is subject to co-determination as soon as the company provides a corporate account through which usage data reach the employer. Where the company only permits use through private accounts in the browser, a labor court has denied co-determination under section 87(1) no. 6. Rules on use itself, such as which data may be entered, remain co-determined as a matter of order in the establishment.
What happens if the works council blocks the AI introduction?
If the works council withholds consent, either side can call the conciliation board, whose ruling replaces the missing agreement. Until then the application may not be introduced. A permanent block is therefore ruled out; a delay of several months remains the realistic risk.
How long do negotiations with the works council on AI take?
With good preparation, plan two to four months to a signed works agreement. An existing framework agreement leads to the lower end, company-wide assistants with access to email and documents to the upper end.
Does every AI application need its own works agreement?
No, a framework agreement on AI can cover several applications and is supplemented with annexes for individual tools. A separate agreement is worthwhile for applications that contribute to personnel decisions or restructure entire workflows.
Let’s talk about your initiative.
In 30 minutes we clarify where your organization stands and which step will pay off most now.
Request a consultation30 minutes · free · no obligation



