The rollout goes fine in the US. Fine in the UK. Then it reaches the German subsidiary, and someone from the works council asks for the Betriebsvereinbarung. There isn't one. The rollout stops there — sometimes for a quarter, occasionally permanently.
This happens often enough to be predictable, and it is entirely avoidable. The problem is that co-determination has no equivalent in US or UK employment law, so it rarely appears on a procurement checklist written by someone who has only deployed in those two places.
Co-determination is not consultation
The distinction matters more than any other point in this piece.
Consultation means you tell people, listen, and then decide. Co-determination means the works council's agreement is a condition of the thing happening at all. Under Section 87(1) No. 6 of the German Works Constitution Act (BetrVG), the works council has a co-determination right over the introduction and use of technical devices designed to monitor the behaviour or performance of employees.
If you deploy without agreement, the deployment is not merely irregular. The works council can move to stop it, and in practice this is one of the more reliably enforced provisions in German employment law. Nobody is bluffing.
The trigger is capability, not intention
Here is where buyers from other jurisdictions consistently misjudge the scope. The instinctive reading of "devices designed to monitor" is that it applies to surveillance products — so a capacity analytics tool, or a helpdesk system, or a CRM should fall outside it.
German courts have read it far more widely than that. The Federal Labour Court has held that neither an intention to monitor nor any actual evaluation of the data is required. What matters is whether the system is objectively capable of collecting or storing behaviour or performance data about identifiable employees.
That sweeps in a great deal of ordinary software. Ticketing systems that timestamp who closed what. CRMs that log call activity. Productivity dashboards, obviously. Anything with a per-user audit log, potentially.
The practical implication is not that every tool needs a separate agreement — many German employers run framework agreements covering categories of system. It is that you should assume your monitoring or analytics tool is in scope, because arguing it is not is a fight you will probably lose and will certainly lose slowly.
What a Betriebsvereinbarung actually settles
The works agreement is the vehicle. It is negotiated, written down, and binding on both sides — and it is genuinely useful, because it converts every vague question about the tool into a settled answer.
A monitoring agreement typically fixes:
- What is collected, specifically, at the level of data categories rather than marketing language.
- What is explicitly not collected. This clause does a lot of work, and it is where an honest product specification pays off.
- Who can see what, including whether individual-level views exist at all and who may open them.
- Aggregation thresholds — the minimum group size before a manager view will render.
- Retention periods, and the mechanics of deletion rather than a promise of it.
- Prohibited uses. Most agreements bar the data from performance management and disciplinary proceedings outright.
- Change control: what happens when the vendor ships a new feature. This is the clause people forget and then badly need.
The rest of Europe, briefly
Works council rights are not uniform, and the differences are substantive rather than procedural.
Netherlands. Genuinely close to Germany in effect. Article 27 of the Works Councils Act gives the ondernemingsraad a consent right over decisions to introduce, change or abolish arrangements for monitoring the presence, behaviour or performance of employees. That is a real veto, and the Dutch data protection authority is clear that works council involvement is part of doing this lawfully. Note that it covers changes too — reconfiguring an existing tool can require going back.
Austria. Works agreement required for measures affecting human dignity, which is read to cover monitoring systems. Treat it as consent territory.
France. The CSE must be informed and consulted before you deploy technology that permits control of employee activity, under Article L.2312-38 of the Labour Code. This is consultation, not veto — but skipping it has a sharp consequence: French courts have treated data gathered from an unconsulted monitoring system as inadmissible in disciplinary proceedings. Which means the tool you bought to support a dismissal cannot support the dismissal.
Belgium has a collective agreement framework covering monitoring of electronic communications with information obligations to employee representatives.
Nordics and elsewhere vary from co-determination-flavoured negotiation duties to lighter information rights.
Two practical rules follow. First, do not generalise from one country to the region — the gap between a Dutch consent right and a Belgian information duty is the gap between a nine-month project and a two-week one. Second, check whether your entity structure actually triggers these obligations at all; thresholds and council existence vary, and plenty of smaller subsidiaries have no council.
None of this replaces GDPR. Works council agreement and lawful processing are separate requirements, and you need both — the GDPR monitoring checklist covers the data protection half, and the UK/ICO guide covers the post-Brexit position, which has no co-determination equivalent.
How to run the process without losing two quarters
Having watched this go badly and well, the difference is almost always sequencing.
- Find out whether a council exists before you shortlist, not after you sign. This is a two-email question and it changes the buying criteria.
- Bring the council in during evaluation, not at deployment. A council presented with a signed contract and a go-live date reasonably concludes the consultation is theatre, and responds accordingly. A council asked which of three tools they would find acceptable is a different conversation entirely.
- Propose the narrow configuration first. Every optional collection feature you leave enabled "in case we need it later" is a clause to negotiate. Turn them off, agree the narrow version, and revisit if a real need appears.
- Bring a data map, not a datasheet. Councils ask what fields exist, where they are stored, who can query them, and what the deletion path is. Vendor marketing does not answer those. Ask your vendor for the field-level answer before the first meeting.
- Expect to concede aggregation thresholds and prohibited uses. These are the standard asks, and they are reasonable. If conceding them makes the tool useless to you, that is worth knowing early — it usually means you were buying it for performance management while describing it as capacity planning.
- Write the pilot into the agreement. A time-limited trial with agreed review is far easier to get signed than an open-ended rollout, and it gives both sides evidence instead of predictions.
What makes a tool easy to get agreed
Some products get through this process in weeks and some never get through at all, and the pattern is not subtle.
Easy: metadata rather than content. Aggregate views that work without opening an individual record. Collection that is genuinely off rather than disabled-by-policy. Employees able to see their own data. Configurable retention. A vendor who will state plainly what the product cannot do.
Hard: screen recording, keystroke capture, anything with a blended per-person score, and — this one comes up constantly — features the vendor markets as flagship capabilities that you insist you will never enable. A council reasonably asks why you bought a product whose main selling point you have promised not to use. The ethical monitoring principles are, not coincidentally, close to what a council will ask for unprompted.
Where ProdView fits
Most of what a works agreement negotiates, ProdView settles by construction: activity and app metadata only, never screen content or keystrokes, screenshots optional and off by default, employees on the same dashboard as their manager, configurable retention, SOC 2 Type II. That makes the "what is explicitly not collected" clause short and verifiable rather than a promise about restraint.
When not to pick us: you have a regulatory mandate for session recording or DLP. Those needs are real in some sectors, and a UAM tool is the honest answer — but expect the negotiation to be substantially longer, and scope it to the seats that genuinely require it. Our monitoring policy template is a reasonable starting draft for the plain-language annex a council will want alongside the agreement.
Try before you commit
Three seats are free forever, which is enough to run a demonstration for a works council against a real tenant rather than a slide. Model the payback with the ROI calculator if you need the business case in the same meeting.
General information about European works council frameworks as of August 2026, not legal advice. Requirements differ by country and by the structure of your entity — take local advice before deploying.