Rolling Out Copilot in Germany: What the Works Council Will Ask
Bottom line: a Copilot works council conversation is not optional in Germany. If a Copilot rollout touches a German entity, the works council, the Betriebsrat, has a real seat at the table under section 87 BetrVG, Germany's co-determination law. The standard way through it is a Betriebsvereinbarung, a written works agreement, signed before rollout starts, not after.
I plan international Copilot rollouts for a living, and Germany is the one country where a plan built somewhere else always needs a second look before it lands there too. Not because German employees resist AI. Because German law gives the works council an actual vote on exactly the kind of technology Copilot is.
Why the works council gets involved
Works council co-determination under section 87 BetrVG applies to Copilot because Copilot is monitoring-capable technology, and it changes how people do their work. Both of those are standard co-determination territory in Germany, long before AI showed up on anyone's radar.
Section 87 gives German works councils the right to negotiate over technical systems that are capable of monitoring employee conduct or performance, whether or not monitoring was ever the intent. Copilot logs usage. That is enough to put it inside this territory, the same way earlier rollouts of email archiving or time-tracking software were.
One disclaimer, stated plainly, once: this page is not legal advice. It describes the pattern I see across rollouts that touch German entities and multinational teams. Your own employment lawyer gets the final word on your specific case.
6 questions to expect
If you are the one presenting Copilot to the Betriebsrat in English, with the German-speaking members reading a translated summary, these are the 6 questions to prepare for. A Copilot works council conversation, in my experience, clusters around 6 themes: monitoring, personal data, training, scope of use, evaluation, and what happens to people who opt out. That is my own framing of the section 87 territory, built from what actually comes up in these conversations. Treat it as a planning guide, not a quoted legal checklist.
01Monitoring of performance and behaviour
Can Copilot log what someone asked it, how often, or how well they used it? If the answer is yes in any form, expect this question before rollout, not after. A system that is technically capable of monitoring conduct or performance needs a works agreement, whether monitoring was ever the point or not.
02Personal data
What personal data does Copilot touch, and where does it actually live? Email content, calendar entries, anything that reads like a performance record. Works councils want a plain answer here, not a data processing addendum nobody has read.
03Training
What training do people get before they are expected to use it, and is it required or optional? A rollout that skips training reads, to a works council, like a rollout that has not thought through the employee side at all.
04Scope of use
Which teams, which apps, which tasks. "Copilot across the organisation" invites far more scrutiny than a specific plan with named departments and named use cases.
05Evaluation
How will the organisation judge whether this worked, and who sees those numbers? If the evaluation criteria could double as an individual performance review, that is usually where the negotiation gets stuck.
06What happens to people who opt out
Is using Copilot mandatory, and if someone declines, what changes for them? A clear, written answer here tends to close the whole negotiation faster than anything else on this list.
The Betriebsvereinbarung, in plain terms
A Copilot Betriebsvereinbarung, the written works agreement between employer and works council, is standard practice before rollout in Germany. It is not spelled out word for word in the Act itself. It is how German employers typically handle their section 87 obligations, and skipping it is what turns a routine rollout into a stalled one.
What actually goes into it: what Copilot can and cannot see, how long any logs are kept, who can access them, what training looks like, and what opting out really means in practice (on paper it is usually allowed, in practice almost nobody uses it, and that gap is worth asking about directly rather than assuming the policy speaks for itself). None of that is exotic. It is the same 6 themes from the section above, written down and signed by both sides.
Timing matters more than most rollout teams expect. A works agreement negotiated after licences are already assigned puts the works council in the position of saying no to something already live, which is a worse conversation for everyone involved. Starting the conversation before procurement finishes avoids nearly all the friction I have seen.
Where training fits before rollout
Training is one of the 6 questions for a reason. A works council that sees a real training plan treats it very differently from a rollout that promises training "at some point" (and I have never once seen a works council accept "at some point" as an answer).
If your German rollout needs live, English-language training scheduled for European working hours, that is what I run. See Copilot training for European companies for the formats and prices.
Data residency questions tend to come up in the same breath as works council questions, and for good reason. The Copilot, GDPR and EU data residency page covers where Copilot data actually sits, and what changed with Flex Routing earlier this year.
Questions I get about Copilot and German works councils
Does the works council need to approve Copilot in Germany?
In practice, yes, in the form of a Betriebsvereinbarung negotiated before rollout. Section 87 BetrVG gives the works council co-determination rights over monitoring-capable technology, and Copilot fits that description. Skipping this step is the most common reason a German rollout stalls before it even starts.
What is a Betriebsvereinbarung, and do we need one before rollout?
A written works agreement between the employer and the works council. It is standard practice, not a fixed legal template, before rolling out Copilot to a German entity, and it covers what the tool can see, what gets logged, and what training and opt-out look like.
What will the works council ask about Copilot?
In every Copilot works council conversation I have sat in on, 6 themes come up almost every time: monitoring, personal data, training, scope of use, evaluation and opt-out. That is my own framing of the section 87 territory, not a quoted checklist.
Does section 87 BetrVG apply to Copilot specifically?
Copilot is not named in the law, obviously. It applies to any technology capable of monitoring employee conduct or performance, and Copilot's usage logging fits that description. This is the standard reading, not a Copilot-specific rule.
What should be in place before rollout in Germany?
A Betriebsvereinbarung, a clear scope (which teams, apps, tasks), a training plan with real dates, and a plain answer on what happens to anyone who opts out. Get those 4 in writing and the works council conversation moves fast.
Want training scheduled before the works council conversation, not after?
An intro call is the fastest way to work out what a German rollout looks like for your organisation, live online, in English, in your timezone.