What rights the works council has over an AI assistant
Since the Works Council Modernisation Act of 2021, the BetrVG mentions AI by name in sections 80, 90 and 95, though it still has no chapter on the subject. The provision that usually decides the matter for an assistant doesn't mention AI at all. That is section 87(1) no. 6.
Information and consultation, section 90 BetrVG. This one applies whenever there is a works council. You must inform it about planned technical installations, work processes and workflows in good time and with the necessary documents, and since 2021 no. 3 adds "including the use of artificial intelligence". Paragraph 2 has you discuss the measures and their effects on staff early enough for the council's suggestions and concerns to be taken into account in the planning. Section 90 gives the council no veto. What it fixes is timing, and that puts it before the purchase order.
Monitoring technology, section 87(1) no. 6 BetrVG. The works council has co-determination over introducing and using technical devices "designed" to monitor employees' behaviour or performance. The Federal Labour Court reads "designed" as objectively suitable to collect and record information on behaviour or performance, whatever you intend to do with it. That is in paragraph 30 of its decision of 8 March 2022, 1 ABR 20/21, and paragraph 31 treats Office 365 as such a device. An assistant that logs who asked what and when, or whose admin console breaks usage down by person, therefore makes a strong case for co-determination. If that applies, the tool can't go live without the council's consent, and a deadlock goes to the conciliation board, the Einigungsstelle, at either side's request. Its ruling replaces the agreement. Where your own tool stands is a question for your lawyer and the council.
Who you talk to across several sites, section 50(1) BetrVG. The general works council handles matters that affect several establishments and that the individual councils can't settle. In the same decision the court held that for company-wide use of Office 365 with central control. If your assistant runs centrally across sites, establish early which body you are dealing with.
Experts, section 80(3) BetrVG. Budget for an expert from the start, because section 40(1) puts the costs of the council's activity on you. The works council may bring in experts where its work properly requires them, on terms agreed in more detail with you, and since 2021 the statute treats an expert as necessary to the extent the council has to assess the introduction or use of AI. Whether there is an expert is therefore settled, while the person, the scope and the fee still need agreeing. With several tools on the way, it often makes sense to agree on a standing expert for AI matters.
Selection guidelines, section 95(2a) BetrVG. Guidelines on whom you hire, transfer, regrade or dismiss need the works council's consent, and paragraph 2a confirms that nothing changes when AI is used to draw them up. Check this section if your assistant is meant to pre-sort job applications. The council's right to demand such guidelines in the first place exists only in establishments with more than 500 employees.
Usage rules, section 87(1) no. 1 BetrVG. The Hamburg Labour Court looked at ChatGPT guidelines on 16 January 2024, in summary proceedings 24 BVGa 1/24. Section 87(1) no. 1 gives the council a say over order in the workplace and employee conduct there, but Federal Labour Court case law leaves out instructions on how the work itself is done, and the Hamburg court treated the ChatGPT guidelines as instructions of that kind. It found no breach of no. 6 either. The tools weren't installed on company computers, staff reached them in a browser on their own private accounts, and the employer had no access to the data held by the vendor. A group works agreement already covered the browser itself. A company account with an admin console removes that ground, and a single first-instance ruling in summary proceedings is a thin basis to build on anyway.
The order of steps for a company of 20 to 250 people
- Take stock. Start with a list the works council will also get to see later, covering each AI tool already in use and the job it does.
- Understand the tool before you buy it. The tool profile is a single page with the vendor's answers to three questions, each of which you should have them demonstrate: what the admin console records, how long it keeps that data, and whether per-person reporting can be turned off.
- Inform the works council during planning. No order goes out before this meeting, where the council gets the profile, your stock-take and the use you have in mind.
- Settle the expert question. If the council asks for one, agree on the person and the scope early.
- Negotiate the framework and the first annex. The next section covers what goes in. Later tools go through the change procedure, which is why the first one takes longest.
- Pilot with a small group. Agree a time-limited pilot if the framework isn't finished. Section 87(1) no. 6 covers introduction and use, and its text makes no exception for trial runs, so if your tool falls under it, assume the pilot needs the council's consent too. Your lawyer can check if you're unsure. How a measured Copilot pilot works in practice is in the Microsoft 365 Copilot rollout checklist.
- Train and keep a record. Each role gets a short session, and someone keeps the attendance list.
- Roll out and review on the agreed date. Both sides adjust the rules together wherever daily use shows they don't work.
What a works agreement on AI covers
With a framework for the rules that apply to every AI system in the company and an annex for each tool, a new tool only puts a new annex on the table, which is why I suggest that split. A typical agreement covers the following.
- Purpose and scope. The departments and staff covered, the uses the tools are meant for, and anything the agreement expressly does not aim at.
- Tool list with a change procedure. Without a change procedure, every software update reopens the negotiation. So each approved tool sits in an annex with its purpose, the data it handles, its logs and who can access it, and the framework sets out how new tools, or new features in approved ones, join the list. You hand the works council a one-page profile, it has an agreed period for questions and objections, and then the annex is updated.
- No monitoring of performance or behaviour, or clear limits on it. Exceptions such as a security incident go through a separate procedure in which the works council takes part, and the rule itself says in writing that usage data won't be used to assess individuals.
- Data and logs. A minimum group size for statistics keeps any one person from being worked out of the figures, so it's worth writing in. The agreement should also name who holds admin rights and who receives reports, and say what the tool keeps and for how long.
- Training. This item doubles as part of your Article 4 compliance. It sets who receives which introduction before first use, how attendance is recorded, and what happens when features change.
- Review. Six months in is a sensible point for both sides to check whether the rules hold up in practice. Fix the date in the agreement.
- Disputes and escalation. Escalation runs from a named contact on each side to a small joint committee, and only then to the conciliation board.
Expect retraining and the effect on jobs to come up too. Whether they go in this agreement or a separate one is for the two sides to decide.
Nothing copied off the internet will fit your tools and your workplace, or stand in for a lawyer's review, which is why this piece leaves out a template.
What the works council will check in your draft
The council will measure your draft against the statute. Each point here rests on a provision of the BetrVG or the GDPR that you can open and read, and which ones matter depends on the tool. Go through them before the first round and bring your answers.
- Can the agreement rule out analysis of individuals? Section 75(2) BetrVG obliges you and the council alike to protect and promote the free development of each employee's personality. Measure each report your draft permits against that, and take out any that fails.
- Does a person make the final call on decisions about people? Article 22 GDPR gives employees the right not to be subject to a decision based solely on automated processing that produces legal effects for them or similarly significantly affects them. The article allows exceptions, so write in that a human reviews and decides before an AI output has consequences for anyone.
- Could the tool ever touch hiring, transfers or dismissals? If personnel decisions aren't in scope, put that exclusion in writing. A draft that is silent on it will draw the question, because selection guidelines need the council's consent under section 95(1), and paragraph 2a keeps that rule when AI is used to draw them up.
- What happens when a feature ships in an update? The duty to inform in good time under section 90 also covers work processes and uses of AI you plan later. AI features often arrive in ordinary updates, so have the change procedure say that a new feature in an already approved tool triggers a fresh profile.
- Will people need new skills to keep doing their jobs? Assess in advance how far the tool will change the daily work, because section 97(2) BetrVG sets a threshold. Once your measure changes people's work so much that their knowledge and skills no longer suffice for their tasks, the council has co-determination over introducing in-house vocational training, and the conciliation board settles the matter if the two sides cannot agree.
- What survives if one side terminates? Work out which parts rest on a co-determination right before you sign. Section 77(6) keeps a terminated agreement's rules in force only in matters where the conciliation board's ruling can replace agreement between the parties, and only until another arrangement replaces them. Termination itself takes three months' notice under section 77(5) unless you agree otherwise, so decide in the text what becomes of the rest.
If your tool stores no per-person usage data, write exactly that commitment into the annex.
The EU AI Act and data protection, briefly
The AI Act and the GDPR add duties of their own on top of the council's rights, and neither takes any of those rights away.
High-risk AI at work. A drafting assistant or a tool that summarises meeting notes will usually fall outside the high-risk category, and that matters because high-risk systems bring an extra duty. Under Article 26(7) of the AI Act, employers must tell workers' representatives and the employees concerned before putting such a system into service or using it at the workplace. For employment, Annex III's list includes systems that target job adverts, screen applications or evaluate candidates, systems used for promotion or termination decisions, systems that allocate tasks according to individual behaviour, and systems that monitor or evaluate performance. Under the Digital Omnibus, Regulation (EU) 2026/1744, these duties apply from 2 December 2027.
AI literacy under Article 4. Training belongs in the works agreement anyway, which makes Article 4 convenient here. Since that same regulation amended it, the article asks companies for measures that support AI literacy among their staff, without prescribing a level. The European Commission's questions and answers add that no certificate is needed and that organisations can keep an internal record of the training. AI literacy under Article 4 covers the practical side.
Data protection. You need a data processing agreement with the vendor whatever else you sign. Logs and usage statistics are personal data about employees, and Article 88 GDPR together with section 26(4) of the Federal Data Protection Act lets a works agreement regulate how they are processed. That power has a ceiling. On 19 December 2024, in C-65/23, the Court of Justice of the EU held that such an agreement must still meet the GDPR's general requirements and that courts review this in full. A works agreement can't turn unlawful processing into lawful processing.
If there's no works council
You still have duties, just fewer of them. Start with the data processing agreement for the vendor and a short usage policy that says plainly what is and isn't logged. The AI usage policy template has wording to adapt. Article 13 GDPR separately requires telling staff the purposes, legal basis, recipients and retention period of their usage data, and from December 2027, using a high-risk system means informing affected employees in advance. What falls away is co-determination, and with it any works agreement.
That can change. Under section 1(1) BetrVG, staff in any establishment that normally has at least five permanent employees eligible to vote, three of whom are eligible to stand, can elect a works council, and a newly elected one has a say under section 87(1) no. 6 over monitoring technology that is already running. Records kept from day one leave little to catch up on.
When the works council wants AI for its own work
Sometimes the request comes from the council. Minutes pile up, a forty-page draft lands a week before the meeting, and someone suggests an AI assistant to get through it. As the employer, you face four questions.
Do you have to provide it? Section 87 isn't the issue here, section 40 BetrVG is. Paragraph 1 puts the costs of the council's activity on you. Paragraph 2 has you provide rooms, material resources, information and communication technology and office staff, to the extent necessary for meetings, consultation hours and day-to-day business. An AI assistant can fall under that. Expect any disagreement to centre on the word "necessary", and ask for a council resolution that names the task, minute summaries for instance.
Who answers for the data? Under section 79a BetrVG the council must comply with data protection law when it processes personal data, you are the controller for processing done to carry out the council's duties, and both sides support each other in complying. That reaches complaints and dismissal files. The natural home is a company account you have contracted with the vendor, so that such data doesn't land in a private account with no data processing agreement behind it.
What can your IT see? On a company account, the admin console may show what the council asked. Section 79a binds the data protection officer to silence towards you about anything that would reveal how the council forms its views, and says nothing comparable about IT administrators. Agree before starting who holds admin rights over the council's area and whether its history sits apart from everyone else's. I'd go for a dedicated workspace where the tool supports one.
What happens to your secrets? Members may neither disclose nor exploit trade or business secrets that you have expressly marked as confidential, under section 79(1) BetrVG. Whether typing them into an outside tool counts as disclosure is a question the provision leaves open, so raise which documents stay out.
Expect training requests as well. Section 37(6) BetrVG extends release from work without loss of pay to training courses, insofar as they teach knowledge the council's work requires. A member preparing to negotiate an AI agreement is a plausible case.
The next step
Put the first meeting with the council before the purchase order and bring the tool profile. That meeting can then deal with log settings and training. A council that hears about the assistant from the all-staff email starts with whether it can trust you.
If a rollout like this is on your desk, tell me which tool you have in mind. The negotiating stays with you and the legal questions stay with your lawyer. What caadoo takes on, as part of a subscription, is the technical work: the tool profiles, the log settings, the training and the documentation.
Frequently asked questions
Does the works council have to approve an AI tool?
A tool with per-person logs or usage statistics makes a strong case that it does. Section 87(1) no. 6 BetrVG covers technical devices designed to monitor behaviour or performance, and the Federal Labour Court reads "designed" as "objectively suitable", so your intentions don't decide it. Where the right applies, the tool can't go live without the council's consent, and a deadlock goes to the conciliation board at either side's request. Your lawyer and the council settle where your tool stands.
When must we tell the works council about an AI rollout?
Before the purchase order goes out. Section 90 BetrVG gives the council no veto, but the statute sets the timing. You inform the council about planned work processes and workflows, including the use of artificial intelligence, and hand over the necessary documents. You then discuss the plans early enough for its suggestions and concerns to be taken into account. A council that learns about the tool from the all-staff email spends its first meeting on whether it can trust you.
Can the works council bring in an AI expert at our expense?
Yes, and the bill is yours under section 40(1) BetrVG, so budget for it from the start. Section 80(3) BetrVG lets the council bring in experts on terms agreed in more detail with you, where its work properly requires them. Since 2021 the statute treats an expert as necessary to the extent the council has to assess the introduction or use of AI. Whether there is an expert is settled. The person, the scope and the fee still need agreeing.
Do we need a works agreement before rolling out an AI assistant?
If the tool falls under section 87(1) no. 6, you need the council's consent, and I'd put that consent in writing as a works agreement. One framework for every AI system in the company plus an annex per tool works well, because the next tool then means negotiating an annex and nothing more. Have an employment lawyer read the text before anyone signs.
Can the works council use AI for its own work?
It can ask for it. Section 40(2) BetrVG has the employer provide material resources and information and communication technology, to the extent necessary, for the council's meetings, consultation hours and day-to-day business, which can include an AI assistant. The route is a resolution with reasons rather than a licence bought on its own account. Complaints and dismissal files stay off private accounts with no data processing agreement, because section 79a makes the employer the controller when the council processes personal data for its duties.
What if our company has no works council?
Co-determination and works agreements fall away. You still need a data processing agreement with the vendor. Article 13 GDPR requires telling staff the purposes, legal basis, recipients and retention period of their usage data, and from December 2027 a high-risk system means informing affected employees in advance. Staff can elect a council wherever an establishment normally has at least five permanent employees eligible to vote, three of them eligible to stand. A new council has a say over monitoring technology already running.