Employee surveys: what must the works council clarify?

Early coordination makes it possible to design questions and reporting together before technical or organisational decisions are final. Presenting a finished questionnaire only after the tool has been set up makes changes unnecessarily difficult. Important questions about the purpose and employee protection may also remain unanswered.

Information rights and co-determination are not the same thing. The works council must receive timely and comprehensive information so it can fulfil its statutory duties; the legal starting point is section 80(2) of the German Works Constitution Act. Which additional consent or agreement is required depends on the particular matter.

In practice, coordination therefore starts with a description of the project: Which decision should the survey support? Who will take part? What will be collected? Who will see which results? A product presentation alone rarely answers these questions adequately.

Section 94 BetrVG governs works council consent to personnel questionnaires and also contains a provision on general assessment principles. This does not mean that every question put to a team automatically falls into the same category. What needs to be checked is which personal information will be collected and how it will be used.

A survey about processes may require a different assessment from a procedure that systematically records individual characteristics or personal ratings. Questions about identifiable managers also deserve attention. Anonymity for respondents does not necessarily mean that nobody is the subject of an analysis involving personal data.

The complete wording matters for a joint review. A topic heading such as 'Collaboration' is not enough if very different statements could appear beneath it. Include response options, optional comments and additional questions about the area of work too. This allows the actual process to be assessed.

Section 87(1), no. 6 BetrVG concerns technical systems for monitoring behaviour or performance. Under the case law, the system's objective capability is important to this distinction; a stated intention not to monitor anyone does not automatically exclude co-determination. This is explained, for example, in BAG decision 1 ABR 16/23.

The assessment must therefore go beyond the visible interface. Personal identifiers, timestamps, logs, access permissions and exports may be relevant. Also ask which links to other information are possible and whether later settings could change the scope of analysis.

A short questionnaire is not automatically unproblematic simply because it takes little time to complete. Conversely, the word 'software' alone does not determine the assessment. Describe functions and use precisely enough to allow a factual legal review.

Voluntary participation and effective protection against attribution are important features. They do not replace a full assessment of all participation rights. It is also necessary to clarify whom answers refer to and whether technical data or particular analyses make attribution possible.

In 1 ABR 13/17, Germany's Federal Labour Court considered changes to a group-wide employee survey. The decision concerned a specific process and existing arrangements. It cannot be reduced to the simple rule that every voluntary survey is exempt from co-determination.

The practical consequence for planning is to avoid relying on a single label. Explain how voluntary participation works, which results are produced and whether individual employees or managers could be identifiable. The article on anonymity in employee surveys explores this point further.

Depending on the design, other questions under German works constitution law may arise. These might include rules on workplace conduct or a connection to health protection measures. The relevant provisions also appear in section 87 BetrVG; their conditions must be checked individually.

A general question about workload does not automatically turn a team check-in into a complete occupational risk assessment. It should not be presented as a substitute for one either. A survey may also lead to an organisational measure later on, which in turn requires a separate assessment.

Separate agreement on the survey process from decisions about subsequent changes. Agreement with the questionnaire does not automatically mean approval of every measure derived from it. Record which decisions are already covered and which require further coordination.

Data protection and works council involvement address different questions. An agreement with the works council does not automatically replace every data protection assessment. Conversely, a lawful basis for data processing does not remove possible co-determination rights. Both perspectives belong in preparation.

Where employees' personal data is processed, section 26 BDSG, among other provisions, must be considered. If consent is relied on, the provision specifically requires consideration of voluntariness in the employment relationship. A general checkbox on a form is therefore not a complete answer for every situation.

In practice, those responsible, data protection officers and the relevant employee representatives should all work from the same description of the process. If each receives a different summary, inconsistencies can easily go unnoticed. Document open questions and changes clearly.

Prepare a clear description of the process. Include its purpose, intended participants, questionnaire, frequency and planned use of results. Add an account of which data is generated at each step and who can access it.

Show sample reports, rather than just input screens. These make it clear whether small subgroups, individual comments or exports are planned. Also explain what happens if participation is insufficient and whether authorised people may change settings themselves.

Finally, describe retention, deletion, backups and communication to employees. This does not require a polished sales document. A clear, verifiable description with open points marked is more helpful than general assurances such as 'data protection compliant' or 'fully anonymous'.

A practical list of topics includes purpose limitation, prohibited uses, access permissions, reporting limits and comment handling. Rules for changes to questions, new analyses and additional features are useful too. The legally appropriate form of agreement needs separate clarification.

Avoid contradictions between the agreement and the interface. If subgroups are to be excluded, it should not be easy to reconstruct them through an export. If results should be released only at a particular time, the process must reflect that.

Think about operation after launch too. Who answers questions? Who checks permissions? How are errors reported? An agreement becomes more useful when it is clear how to apply it in everyday work. It should cover more than a single launch date.

A trial can help test clarity and effort. It is not, however, a general exemption from participation rights. The purpose, scope of data, permissions and further use of results should be described in advance even for a trial.

Start within the agreed scope. If new questions or additional groups are to be added during the trial, check whether that change is covered by the previous coordination. 'We are only trying something briefly' should not justify a gradual expansion.

The pages on co-determination and confidentiality provide product information for preparation. For the practical methodology, see pulse surveys in small teams.

EngageBeat publicly describes reporting, permissions and limitations. Use this information for your specific preparation and clarify outstanding requirements before use. Ask about your intended process.

This article provides general guidance and is not legal advice. Responsibility, existing agreements and the specific arrangements require expert assessment in each case.