Works council and innovation tools: what to clarify before you start
The pilot is ready, the first workshop is booked, the licence is paid. Then the works council writes: please stop the tool, nobody talked to us. This checklist shows what to clarify beforehand, so the works council co-signs your plan instead of stopping it.
Why the works council has a say
In Germany the works council (Betriebsrat) has a co-determination right on the introduction and use of technical systems that are suitable for monitoring the behaviour or performance of employees (section 87 paragraph 1 number 6 BetrVG). The decisive word is "suitable". Intent does not matter; it is enough that the system could.
A tool that records who said what, counts talk time and attaches contributions to individuals can qualify. The usual instrument is a company agreement (Betriebsvereinbarung) or a short addendum to an existing framework agreement on IT systems. With an existing framework agreement it often comes down to a two-page annex.
Involving the works council early takes weeks. Being stopped after the first workshop takes months and costs trust. Whether your tool is subject to co-determination is a question for your data protection officer or legal department; this checklist prepares that conversation, it does not replace it. Austria has its own rules for the Betriebsrat and Spain for the comité de empresa; this piece describes the German situation.
What to clarify before the conversation
- What the tool captures and what it does not. Write it down in one sentence: text, no audio recording. Say whether names are attached to contributions and whether that is optional. What it does not capture matters to the works council as much as what it does.
- Who can see what. Say who opens which workshop space. In tools like IdeaHone a space is either open to the organisation or private, and a private space stays closed even to admins; agree which default you use. No management dashboard of individuals. If the tool offers such views, say they are switched off.
- What is never evaluated. Talk time per person is not a performance figure and is not analysed. Scores apply to ideas, never to people. This point usually decides the conversation, so put it first.
- Retention and deletion. Name a period in months, not "as long as necessary". Say who deletes, whether deletion is automatic and what happens to exports.
- Voluntariness. Nobody has to create a voice profile. Anyone who declines takes part as normal, and their contributions appear without a name. Declining has no consequences, and that is in writing.
- Hosting and the data processing agreement. Where is the data stored, in which country, with which provider, and is there a data processing agreement? Your data protection officer should already know.
- Pilot scope and review date. Two teams, three months, then a joint review with the works council. A pilot with a fixed review date is easier to sign than an open-ended rollout.
- The one-page description. Summarise points 1 to 7 on one page, in your own words, without vendor terminology. It is your conversation document and later the annex to the agreement.
Five sentences that usually settle it: "The tool documents workshop results. It stores text, no audio. It evaluates ideas, never people. Names are attached only with the person's consent. Data is deleted after twelve months." Insert your own period.
Invite a works council member to the first pilot workshop as a participant, not as an observer. Someone who has entered and scored ideas knows what the tool does without taking your word for it.
What costs you the works council's trust
- Presenting the vendor's slides. The works council wants to know what you will do with the tool, not everything the manufacturer can do. Sales slides raise exactly the concerns you want to settle.
- Keeping quiet about disabled features. If the tool could measure talk time and you have switched that off, say so unprompted. If it comes out later, it looks like concealment.
- Starting the pilot "quietly". A pilot without information is a rollout without co-determination. That is precisely what triggers the stop.
- Treating the works council as an obstacle. The works council is a co-signer. An agreement it supports protects you too when someone later asks why contributions carry names.
Setting up the capture itself is covered in Workshop transcription and GDPR and Who said what.
Never lose an idea between sessions
IdeaHone follows every idea from first mention to decision, across all your workshops and teams.
Does the works council have to agree to an innovation tool?
If it is suitable for monitoring the behaviour or performance of employees, the works council in Germany has a co-determination right under section 87 paragraph 1 number 6 BetrVG. Whether that applies to your tool depends on what it captures and who can access it; clarify it with your data protection officer before the pilot.
Is a workshop transcript a performance record?
It can become one if contributions are attributed to people, talk time is counted and the data is analysed. A transcript that only records results, with optional names and no evaluation of people, is far less sensitive. What counts is what is technically possible and what has been agreed.
What should a company agreement for a capture tool contain?
Purpose, data captured, access rights, a ban on performance and behaviour monitoring, deletion periods, voluntariness of voice profiles, hosting and data processing, and the pilot scope with a review date. In short: the eight points of this checklist, in contract form.
