How to involve the works council early, transparently, and collaboratively when introducing tools like Can Do.
🧑⚖️ Involving the Works Council During a Software Rollout – What Needs to Be Considered?
When introducing new software for multi-project management, resource planning, or portfolio management such as Can Do, many companies ask: When and how must the works council be involved?
The answer is clear: early and purposefully — because a successful rollout depends not only on technology, but also on the proper handling of co-determination rights.
✅ When Must the Works Council Be Involved?
According to Section 87 (1) of the German Works Constitution Act (BetrVG), the works council has co-determination rights whenever the new software affects areas such as:
-
Performance and behavior monitoring: If the software makes data visible about working hours, workloads, or project activities of individual employees — even indirectly via reports or dashboards.
-
Work organization: If task distribution, responsibilities, or team structures are affected by the new software.
-
Working time regulations: For example, through automated planning or approval processes that impact work schedules.
-
Implementation of technical systems: The introduction itself falls under co-determination if the software significantly affects the work environment.
-
Training and qualification: If employees need to be trained to use the software and this affects their working time.
Rule of thumb: Whenever employees are directly or indirectly impacted by the new system, the works council must be involved.
⏱️ When Is the Right Time?
The earlier, the better. The works council should be involved not just shortly before go-live, but already during the planning phase. This brings clear advantages:
-
Legal certainty: Co-determination rights are respected early, and potential conflicts are avoided.
-
Company-wide acceptance: The works council acts as a multiplier and can address concerns or questions from the workforce at an early stage.
-
Faster rollout: Delays caused by late adjustments or negotiations are minimized.
At the latest, the works council should be informed and involved when vendors are being compared or pilot projects are being discussed — ideally even earlier, during the requirements definition phase.
🤝 Best Practices for Collaboration
-
Open communication: Provide early insight into the goals, functionality, and intended use of the software.
-
Transparency in data protection: Clearly explain which data will be collected — and which will not.
-
Joint workshops: Bring together the works council, IT, HR, and project leads.
-
Include in training: The works council should be aware of training content — or help shape it.
Conclusion
Involving the works council is not a barrier — it's a success factor for your software rollout. A transparent and collaborative approach ensures that not only the system works, but that the people who use it are fully onboard.
💬 Our Offer: Direct Dialogue with Your Works Council
We are happy to support you in involving the works council early and transparently.
On request, we can present our solution directly to the council, answer open questions, and jointly lay the foundation for a trust-based introduction.