Does a German works council have to approve 360° feedback? What to settle before you roll out

Why the works council comes into play for 360° feedback

A 360° programme collects structured ratings of a leader’s behaviour – from supervisors, peers and direct reports – through a software platform and condenses them into a report. Those three features – a technical system, a questionnaire and an appraisal of behaviour – touch areas in which Germany’s Works Constitution Act (Betriebsverfassungsgesetz, BetrVG) gives the works council (Betriebsrat, the elected employee representation at establishment level) participation rights. That it serves development, not control, does not make the question go away – answer it before the first invitation goes out.

The two provisions that usually matter: § 87(1) no. 6 and § 94 BetrVG

§ 87(1) no. 6 BetrVG gives the works council – “insofar as no statutory or collective-bargaining provision exists” – a co-determination right over the “introduction and use of technical devices intended to monitor the behaviour or performance of employees” (our translation). A 360° platform collects and evaluates ratings of employees’ behaviour. What “intended to” means – and whether a system used for development falls under it – is the question that occupies courts and commentators. We do not answer it here; we note that it is regularly asked.

§ 94 BetrVG is titled “Personnel questionnaires, appraisal principles” (Personalfragebogen, Beurteilungsgrundsätze). Its first paragraph provides that personnel questionnaires require the works council’s consent; if no agreement on their content is reached, a conciliation committee (Einigungsstelle) decides, and its ruling replaces the agreement. The second paragraph extends this to general appraisal principles. Two questions follow: is a rater questionnaire a personnel questionnaire in this sense? And is the competency model behind it – the dimensions against which leadership behaviour is rated – a general appraisal principle?

Both provisions are about the how – content, purpose, limits – not a blanket prohibition; § 94 even names the route if the two sides cannot agree on content. In our experience that route is rarely needed when the programme answers the typical objections from the outset.

Leaders only, development only – does that change anything?

“We assess leaders, not employees” and “This is development, not control” – both objections are relevant; neither settles the question on its own.

Senior managerial employees (leitende Angestellte)

The BetrVG largely excludes senior managerial employees – leitende Angestellte – from its scope. Whether a leader in your programme belongs to that category is decided not by title but by the statutory criteria, for the group actually assessed. In many development programmes, team leads and managers are employees in the sense of the Act – and even in a top-tier-only programme, the raters usually are, and their data is processed too.

Development purpose

A pure development purpose is your strongest argument – and exactly what the works council wants to see in writing. Whether it removes co-determination is a legal question we do not answer. A purpose promised only verbally helps nobody: it belongs in the works agreement, with a ban on use for promotion, pay or dismissal and an access architecture that backs the ban – if HR cannot see individual results, “not for personnel decisions” is more than words. See Can HR see individual 360° results?.

What a works agreement on 360° feedback usually covers

The usual route is a works agreement (Betriebsvereinbarung) – a written agreement between employer and works council, binding on both sides – stand-alone or annexed to a framework agreement on people development or IT systems. In our experience these nine areas appear almost every time:

1. Purpose and purpose limitation. Development of the leader; expressly no performance appraisal, no basis for personnel decisions.
2. Voluntariness. For the leader and the raters: no disadvantage for not taking part, the right to decline. Under § 26(2) BDSG, the voluntariness of an employee’s consent is assessed taking into account the employee’s dependence and the circumstances.
3. Anonymity. From how many responses a group is shown separately, what happens below that, how free text and the usually single supervisor are treated – see Is 360° feedback anonymous?.
4. Access rights. Who sees the report – the leader and the accompanying consultant – and who does not: HR, supervisors, the management board; whether and above which group size aggregated analyses are allowed.
5. Retention and deletion. How long responses and reports are stored and what happens when the leader leaves; specific periods are yours to set with your data-protection officer.
6. Ban on use. No use for promotion, pay, warnings or dismissal; no employer entitlement to the individual report.
7. Data protection. Legal basis, processing agreement, server location, information for data subjects under Art. 13 GDPR, a data protection impact assessment where required – see GDPR and 360° feedback.
8. Evaluation. Pilot phase, evaluation date, criteria, rights to adjust and terminate; a fixed-term agreement with an evaluation clause is easier to sign than an open-ended one.
9. Involvement in changes. What happens if questionnaire, competency model or vendor change, and which documents the works council receives in advance.

A practical sequence: involve early, show the design, offer a pilot

Sequencing can cost or save you months: a works council that learns of a tool already procured negotiates differently from one that helped shape the selection criteria. What has served our programmes well:

1. Inform before vendor selection. Objective, group to be assessed, process, timeline – and ask which points matter most to the council.
2. Show the anonymity design concretely. Not “feedback is anonymous” but: the threshold for showing a group, what happens below it, how free text is displayed, what HR sees – with a sample report and the vendor at the table.
3. Provide the questionnaire and competency model in full. Both language versions, all scales, the open questions.
4. Offer a pilot. A limited cohort, a fixed evaluation date, jointly agreed criteria – it turns a debate about principles into a question of experience.
5. Draft together. The works agreement with data-protection officer and legal department, using the nine areas as the outline.
6. Evaluate after the pilot. Response rates, raters’ experience, benefit as seen by the leaders – and adjust where needed.

What does not work: introducing the tool first and asking afterwards; promising “full anonymity” no system delivers – the leader usually sees who was nominated and who has submitted; the answers are what is protected – and handing over the vendor brochure instead of the questionnaire.

What LEADBeyond 360° brings to these conversations

A works council is right to check whether an agreement’s assurances hold in the system. With LEADBeyond 360°, the points such agreements typically demand are platform properties, not process promises:

• Rater groups are shown separately only once a configurable minimum number of completed responses (default: two) is reached; below that they are folded into “all others”, and values from which an individual answer could be derived are withheld.
• Free text is never attributed to a person and is shown in randomised order; raters can decline a request.
• HR and client admins see progress, completion rates and release status – no individual results, reports or free text. The consulting team sets the anonymity threshold, not HR.
• An organisation-level analysis without names or individual scores exists for HR only for a closed cycle with at least five leaders holding a report and the consulting team’s explicit release.
• Every report is reviewed by a consultant before release; released reports remain immutable. No automated decision-making, no AI processing of free text.
• Hosted in Frankfurt am Main; questionnaire and report in German and English.