When a works council AI agreement is mandatory
Many HR teams start with AI without involving the works council (Betriebsrat, the elected employee representation in German companies), because "it only produces a text draft". That is a mistake with consequences. What matters is not what the tool is meant to do, but what it could do. A system that sorts applications, suggests wording for reference letters or summarises performance data is, under the settled case law of the Federal Labour Court, a technical device suited to monitoring employees. That triggers Section 87 (1) no. 6 of the Works Constitution Act (BetrVG), and the works council has an enforceable co-determination right. If it is bypassed, the works council can stop the use of the tool through an injunction, and everything created with it up to that point stands on shaky legal ground.
Three questions to test whether your case is subject to co-determination:
If all three apply, you need the agreement before the tool goes live. A shortcut through an AI policy issued by the employer alone does not replace the agreement, but it can be the first step. More under An AI policy for HR teams, the legal basis in detail under Co-determination and AI under German law.
The process in four steps
A works council agreement that holds is created with the works council, not for it. The difference shows in the sequence: whoever walks into the first meeting with a finished draft negotiates every paragraph afterwards. Whoever starts with a joint assessment has the works council on their side from step two.
Together with the works council: which HR routines should get AI, which deliberately should not. The result is a list, not a slide deck.
Per use case: data basis, depth of intervention, classification under the EU AI Act, role of the data protection officer.
The text of the agreement based on the list. Permitted cases, prohibited cases, control rights, objection, termination.
A time-limited test phase with a fixed review date. Only then does the agreement become open-ended.
What belongs in a works council AI agreement
The outline is similar for most agreements. The content differs considerably depending on the tools and the works council. These eight points must be settled in every case:
- ScopeWhich systems, which departments, which employee groups are covered.
- Permitted use casesAn exhaustive list, no catch-all clause. New cases need an addendum.
- Explicitly prohibited use casesAutomated rejection, emotion recognition, performance ranking without human review.
- Data basis and retentionWhich data may go in, where it is stored, when it is deleted.
- Human final decisionEvery people decision is made by a human. The tool prepares.
- Works council control rightsAccess to logs, usage statistics, changes to prompts and models.
- Training and informationWho is trained before using the tool, and how employees are informed.
- Term, review, terminationTime-limited test phase, fixed review date, notice period and continued effect after termination.
Where the works council typically objects
Four points come up in almost every negotiation. Whoever prepares a solid answer for each of them beforehand shortens the process by weeks. First, the retention of applicant data: the works council wants to know whether rejected applications stay in the AI tool. The answer that holds: deletion after the statutory period, automated, with evidence. Second, the traceability of pre-selections: why was an application marked as a match? Only a tool that shows criteria helps here, not one that shows only a result. Third, the right of individual employees to object to their data being run through a model. That can be solved if the routine also works without AI, just more slowly. Fourth, the role of the data protection officer: the works council expects the agreement to be endorsed by them, otherwise it counts as one-sided.
A fifth point comes up less often but costs the most time when it does: the question of whether the tool's vendor draws training data from your inputs. Settle that with the vendor contract before the first meeting, not during it. For Microsoft Copilot, ChatGPT Enterprise and Claude for Work the answer is contractually fixed. For free consumer versions it is not.
How long it realistically takes
Nobody signs a works council AI agreement in three weeks, and anyone who promises that has not negotiated one yet. The timeline depends on how often the works council meets, on the number of use cases, and on whether a framework IT agreement already exists that the AI agreement can attach to. Without groundwork, two to four months is realistic. With an existing IT framework agreement it goes faster.
Three mistakes that double the process
Starting with the tool instead of the use case. An agreement about "Microsoft Copilot" is out of date at the first update. An agreement about "drafting job ads with a language model" still holds when the tool changes.
Skipping the test phase. Without a time-limited test, the works council negotiates every sentence as if it applied forever. With a review date after three months, agreement comes more easily, because both sides know it can be adjusted.
Informing the workforce only after the signature. The agreement also governs how employees are informed. Whoever does that late ends up explaining themselves to employees who already know about the tool from the grapevine.
Works council agreements and AI rollouts delivered with the works council Roles in corporate groups, mid-sized companies and scale-ups. More about me
Outline of a works council AI agreement with sample wording
The full structure of the eight points above, with wording suggestions drawn from negotiated agreements, as a Word file you can work on directly with your works council. Not legal advice, but a starting point that saves weeks.
Frequently asked questions
Is an employer-issued AI policy enough instead of a works council agreement?
No, if the three criteria above apply. A policy is one-sided and does not replace the co-determination right. It can, however, be the first step to clarify expectations before negotiating. More under An AI policy for HR teams.
What if we have no works council?
Then co-determination does not apply, but data protection and the EU AI Act still do. An AI policy with the same eight points is the right route, and it protects you if a works council is elected later.
Does this also apply to Microsoft Copilot in Outlook and Word?
Yes, as soon as Copilot accesses HR data. Many companies have rolled out Copilot without regulating its use in HR. That is exactly a typical trigger for a retrospective agreement.
What does support for this process cost?
Part of every interim or fractional engagement, or a standalone project with a clear end. Terms on the first call. To AI for HR teams.
Does the agreement need adjusting because of the EU AI Act?
If use cases are classified as high-risk, such as candidate selection, documentation and registration duties are added. The agreement should reference the AI register. Details under The EU AI Act for HR.
Who signs at the end?
Employer and works council, usually the managing director and the works council chair. The data protection officer does not co-sign but should have seen the agreement beforehand, otherwise the objection arrives after the signature.