Introduce pulse surveys with clear ground rules

An additional rhythm, not a replacement for conversations

Annual surveys provide a broader picture, employee reviews consider individual circumstances, and exit interviews explore experiences when people leave. The weekly check-in does not replace any of these formats. It adds a regular picture of mood from everyday team life.

EngageBeat asks two to four questions per week: the fixed index question and one to three rotating questions. The team index and topic trends remain separate. Over several weeks, you can observe whether a topic needs attention and whether the team perceives an agreed change differently. A shift is a signal, not a diagnosis or an automatically generated recommendation for action.

Agree in advance which questions will be addressed at team level and when a wider obstacle should be escalated to HR.

Coordinate with the works council and data protection team before starting

Clarify the purpose, participating teams, permitted questions and how results will be handled before sending the first invitation. Involve those responsible for data protection and any employee representation early. Even a free trial using real employee data needs this framework. The product demo with sample data is available for an initial introduction.

The ‘Co-determination’ page provides a structured list of points to agree before rollout, along with further guidance. It is not a ready-made works agreement. The pilot guide adds an invitation template, success criteria and a discussion guide. Adapt participant information and delivery to your specific agreement. The sales website's privacy policy replaces neither your employee information nor the data processing agreement.

Clearly document who is responsible, who may see results and where employees can take their questions. Clarify voluntary participation and how non-participation is handled, as well as retention and deletion. The appropriate legal basis under data protection law for your use must be checked with the people responsible. The technical minimum threshold alone does not answer that question.

Points to agree and further guidance

Pilot guide as a PDF

What feedback can tell you — and what it cannot

Recurring feedback can indicate which topics deserve a closer look within a team. If perceived clarity falls, for example, that is a reason to review priorities and responsibilities. If a topic score rises after a change, you can discuss with the team whether that change is experienced as helpful. The trend supports a joint review but does not prove a causal relationship.

Authorised team owners see team results and comments after the week closes and once there are five valid responses per question. Organisation-level reporting is available at no extra cost from 3 teams in EngageBeat Team, EngageBeat Fokus and EngageBeat Enterprise, and is set up optionally. If three teams begin on the first shared start date, you can also try organisation-level reporting during the trial. Separately authorised organisation access can show HR aggregated values: for each question, at least three teams must have released results, each with at least five valid responses, subject to additional protection rules. Comments and individual team values remain hidden there. Authorised company admins or organisation leads set up inclusion from the following Monday; team owners are informed. Participant access shows no results; an HR role alone does not grant access rights.

EngageBeat does not provide individual analysis, performance assessment or rankings of people. A response cannot reliably reveal an individual's attitude or intention to change employer. Response records contain no names or email addresses. Comments and contextual knowledge may still allow individuals to be identified, so an absolute anonymity guarantee would be inaccurate. With shared access, five valid responses are also not technical proof that five different people responded.

Understand the protection model

EngageBeat Fokus for AI adoption and transformation

With EngageBeat Fokus, you can use your own questions on a scale from one to five and explore question sets on AI adoption or transformation. This lets you repeatedly ask about specific perceptions during a change process: Is the direction clear? Is enough support available? Can new ways of working be used in everyday work? Choose a small number of questions whose answers can genuinely inform a decision or action.

Team owners can review questions as drafts, activate them or pause them. Changes start a new question version and take effect no earlier than the following week. Custom topic trends remain separate from the fixed team index. This prevents the general index question from being mixed with a project's changing priorities. For new topics, also check whether the purpose, participant information and existing internal agreements still apply.

AI adoption refers here to the subject of the questions. It does not mean your responses are analysed by AI. Nor does the question set measure individual abilities or replace the evaluation of a change project. The Fokus demo shows custom questions, versions and separate trends using fictional data, so you can understand how it works before booking.

Support transformation with team feedback

Sample questions and access to the Fokus demo

Follow changes using your own questions

An AI adoption example shows whether AI is perceived as helpful for suitable day-to-day tasks. The trend relates to an unchanged question version and remains separate from the fixed team index. It is not an assessment of individual employees.

Data control: specify location, access and deletion

EngageBeat runs on a netcup server in Nuremberg. The contact mailbox uses IONOS Mail Basic without an AI assistant. This does not constitute a blanket promise that all communication and certificate data is processed exclusively in Germany. Separate privacy notices and the agreed data processing rules apply to the web app. Optional appointment booking leads to Calendly and is a separate contact channel.

Team owners can choose 13, 26, 52 or 104 completed weeks for retaining responses and weekly records; the current week is added. Retention must be deliberately configured. Displaying twelve weeks is not a deletion period. Question versions and plan decisions are retained until the team is deleted. Choose a period that matches your actual purpose and communicate it before participation.

Backups need a separate deletion and recovery process. Downloaded files and results shared internally must also be covered by your rules; deletion within the application does not automatically remove those copies. The agreed period for retrieval and return of data after the contract ends is 30 days.

Hosting and retention

Web app privacy notice

Plan a start that remains manageable in everyday work

Choose a suitable team and someone to take responsibility. Clarify the documents, inform participants and agree a suitable weekly rhythm. Once the start is approved, team owners share the prepared participant access and invitation text themselves. Email recipients and automatic reminders are optional and are configured only when sending has been deliberately activated. Team owners review released results and organise the review of agreed actions. The short participation time is not the full support workload.

For a team of at least five people, you can try EngageBeat Team or EngageBeat Fokus free for 28 days. The 28 days begin when the first survey opens. Setup and preparation do not count towards the trial. Afterwards, your selected plan continues as a paid subscription unless you cancel beforehand. The responsible person receives a reminder seven and two days before charges begin. You can also prepare multiple teams directly. Up to three teams take part in the trial on the first shared start date; further teams start after an explicit paid booking. An individual quote is required for eleven or more teams, or personal support.

Trial start, weekly close and what follows

Questions before getting started