IT framework works agreement
An IT framework works agreement bundles co-determination over company IT into one set of rules – with common standards and a process for new systems, instead of negotiating every tool separately. This guide neutrally explains content and benefits and the role of the conciliation committee.
Why a framework agreement?
Almost every IT system is subject to co-determination as a technical installation (Section 87(1) no. 6 BetrVG). Negotiating every system individually ties up a great deal of time on both sides. A framework agreement sets common principles and a standard level of protection and defines an orderly process for adopting new systems. This creates speed, transparency and planning certainty for employers and works councils alike.
Typical content
- Scope and covered system classes
- Principles on purpose limitation, data protection and log evaluation
- Process for adopting new systems (notification, assessment, deadlines)
- A common standard level of protection
- Access and role concepts
- Escalation and dispute-resolution path (up to the conciliation committee)
- Regular review and updating
If no agreement is reached
Disputes can arise over the framework agreement itself – or over adopting a specific system. As chair, I structure the process so that a balanced, practical set of rules emerges that carries both sides and eases day-to-day operations.
Briefly answered
It sets common principles and a standard level of protection for company IT and defines a process by which new systems are reviewed and adopted – instead of negotiating every tool separately.
No, it structures it. For particularly intrusive systems, supplementary individual rules remain common; but the framework agreement creates speed and planning certainty for both sides.
Related guides: Microsoft 365 · Video surveillance · all guides
A conciliation committee on an IT framework agreement?
As a neutral chair I guide the parties to a durable, future-proof set of rules – across Germany.