The Works Council Has a Say: Why Software Rollouts in Germany Stall — and How Vendors Prepare

Many SaaS vendors experience the same surprise in their first German enterprise deal: the contract is signed, the budget approved, the champion enthusiastic — and then the rollout stops for months. The reason is rarely technical. It is the works council, which under German law has a genuine right of co-determination over the introduction of most business software.

For vendors from markets without statutory employee representation, this is easily misread as internal politics. It is not. It is a legal requirement: where a works council exists, the employer may not lawfully introduce the system without an agreement. Vendors who understand the mechanism and prepare for it shorten time-to-value dramatically — and win deals that competitors lose in implementation.

The Legal Mechanism

Section 87(1) no. 6 of the Works Constitution Act (BetrVG) gives the works council a right of co-determination over the introduction and use of technical systems “intended” to monitor employees' behaviour or performance. The Federal Labour Court reads this broadly: it is enough that a system is objectively capable of monitoring — the employer's intention is irrelevant. Any software that logs user activity, timestamps actions, or produces user-level reports is therefore typically covered. In practice, that is almost all business software.

• No agreement, no rollout: the works council can seek an injunction against introducing or using a system without its consent. If the parties cannot agree, a conciliation committee decides.
• Early information duty: the employer must inform and consult the works council when planning new technical systems — including AI applications — before decisions are final.
• Experts at the employer's cost: the works council can call in external experts; where artificial intelligence is involved, the law deems such expert support necessary.
• Group-wide rollouts: for systems introduced across a group, the competent body can be the group works council — which changes who you ultimately negotiate with.

The Data Protection Layer

Works agreements often serve as the legal basis for processing employee data in the new system. The Court of Justice of the European Union has made clear that such agreements must fully meet the GDPR's requirements and are subject to judicial review — a German employee-data clause similar to other national provisions has also come under scrutiny. The consequence for vendors: customers need precise documentation of which personal data your system processes, for which purpose, and how long — otherwise neither the works agreement nor the data protection impact assessment can be drafted.

“

In Germany, the contract signature is the midpoint of the sales cycle, not the end. The second half is negotiated with the works council.

What Vendors Can Prepare

1. 01A works council pack in German: a plain-language description of the system, data flows, and all logged user data.
2. 02A role and permission concept showing who can see which user-level data — and a configuration option to switch off performance analytics.
3. 03A deletion and retention concept per data category, aligned with the customer's DPIA.
4. 04Model clauses for a works agreement that your existing customers have accepted — the most valuable document you can bring.
5. 05For AI features: documentation of model purpose, inputs, human oversight, and the absence of automated personnel decisions.
6. 06Realistic planning: build weeks or months for co-determination into the implementation timeline and the customer's business case.

Austria and Switzerland

Austria has a comparable, in parts stricter regime: control measures and technical systems that affect human dignity require the works council's consent, and systems processing personnel data need an agreement or a decision of the conciliation board. Where no works council exists, individual employee consent can be required. Switzerland has no co-determination right of this kind, but labour law prohibits systems designed to monitor employees' behaviour — making transparent, purpose-limited configuration relevant there too.

Conclusion

Works council co-determination is not an obstacle to be escalated but a step to be prepared. Vendors who arrive with documentation, configurable monitoring, and proven works agreement clauses turn a months-long stall into a predictable project phase. Aegiron Capital Group helps SaaS companies prepare their German go-to-market for this reality; legal advice comes from the employment law firm you engage.