Introduce team feedback together.

Clarify participation rights before getting started

Review participation rights in light of your questions, the technical capabilities and the intended use.

Whether participation rights apply, and which ones, depends on the specific implementation, questions and use of the results. Technical systems for monitoring behaviour or performance may fall under section 87(1)(6) BetrVG . Calling an application team feedback does not settle this question. Its technical usage capabilities must also be assessed.

For personnel questionnaires and assessment principles, section 94 BetrVG must also be considered. Different participation rules may apply in public or church institutions. This page offers guidance; it does not replace a review of your specific use.

Insight into morale rather than performance appraisal

EngageBeat does not collect performance data or enable performance appraisals of individuals, teams or their leaders.

EngageBeat collects subjective views on collaboration and the topics asked about. The index and topic trends are not metrics for work output, productivity or leadership quality. Performance capability may be an aim of your improvement measures; this feedback does not measure it.

This applies to the intended use as team feedback. Custom questions must also stay within this scope. Feedback must not be used to derive assessments of individuals, teams or their leaders. Free text and additional knowledge may nevertheless allow inferences; the protection and participation issues below therefore remain relevant.

A shared purpose

A clearly agreed purpose limits which questions you ask and how you use feedback.

Record which issues you want to discuss together, such as collaboration, guidance or working conditions. Agree who selects questions, who may view results and how the team leader discusses them with the team. Do not use feedback to attribute individual responses, rank employees or appraise individual performance.

With EngageBeat Fokus, too, new questions and topic packs should fit the agreed purpose. Switching to AI adoption or transformation is a reason to review the purpose, information and existing agreements again.

Discuss the protection model realistically

Protection thresholds limit access; they do not replace an open discussion of possible identification.

EngageBeat does not store names, email addresses, employee IDs or IP addresses in response records. Results and comments are shown to authorised team owners only after the week closes and with at least five valid responses per question. Participant access does not include a results overview.

Organisation-wide reporting is available at no extra charge for 3 or more teams in EngageBeat Team, EngageBeat Fokus and EngageBeat Enterprise and is set up optionally. It requires its own permissions. Authorised company admins or organisation leaders arrange inclusion from the following Monday; team owners are informed. Separate consent from team owners is not required. After the week closes, it shows aggregate values from at least three eligible teams, each with five valid responses per question; additional protection rules apply. Comments and individual team values are excluded. Include this additional analysis purpose and the information given to participants in your discussions.

This is not an unrestricted guarantee of anonymity. Free text, small groups and contextual knowledge may allow individuals to be identified. With shared access, five responses are not technical proof of five different people’s identities. These limitations should be discussed with the team and employee representatives. Read more under Confidentiality.

Agree before the first survey

Record in advance how participation, access, retention and later changes will be governed.

• Purpose, permitted questions, teams involved and survey frequency.
• Voluntary participation with no disadvantages for non-participation, and clear information for all employees.
• Authorised users, handling comments and limits on sharing results.
• Retention, deletion, backups and procedures for groups that are too small.
• Data protection roles, required data processing arrangements and contacts for questions or complaints.
• Procedures for new custom questions, changes in use and ending the surveys.

Record the outcome in an agreement suitable for your organisation. Where consent from or an agreement with employee representatives is required, it must be in place before the relevant introduction or use.

Data protection remains a separate responsibility

Employee participation and data protection each require a clear basis for your specific use.

A conversation with the works council does not replace clarification of the legal basis under data protection law. Voluntary participation also does not automatically mean that valid data protection consent has been obtained. For employees, the relationship of dependency must be considered in particular; section 26 BDSG contains specific requirements on this.

Clarify with those responsible for data protection which legal basis, information and contracts your use requires. The privacy policy for this website does not replace your organisation’s employee information or any required data processing agreement.

Including during the 28-day trial

A free trial using real employee data also requires rules agreed in advance.

A free trial using real employee data requires the same clearly agreed framework. For an initial introduction, use the product demo on the home page with fictional sample data. Then agree the EngageBeat Team trial with the relevant people in your organisation.

Make introduction and participation easy to understand

Give those responsible and the participants clear information before the first survey starts.

Are you coordinating the introduction in your organisation? The page for HR brings together coordination, information and handling results. The explanation for employees describes, from a participant’s perspective, which data is stored, who sees results and where identification may still be possible. You can share it with the team before the first survey.

Frequently asked questions about introduction

Resolve outstanding questions together before approving use with employees.

Is EngageBeat right for your team?

Choose the right starting point and resolve your questions before the trial.

Choose EngageBeat Team for everyday teamwork or EngageBeat Fokus for custom questions and change initiatives.