Engagement analytics by driver, team and segment

Ask the same questions on the cadence you choose, and every answer rolls up into scores you can read by theme, by department and by how long people have been with you.

Engagement analytics by driver, team and segment

Survey results

Agreement score, sentiment and eNPS in one view

Open a running survey and the headline numbers are already there — who answered, how they rated, and how the answers spread.

  • Agreement score

    One figure for the whole survey: the share of people who rated favourably.

  • Overall sentiment

  • eNPS

preview

Engagement drivers

The themes your questions roll up into

Tag questions with a theme — recognition, workload, management — and they stop being separate rows. They become one score you can follow, compare between teams and open up to read what people wrote underneath it.

  • A driver library shared by every survey

    Named once for the whole company, so the same theme means the same thing in March and in November.

  • How a driver is scored

  • The comments behind a score

preview

Engagement analytics by team and segment

Compare teams, locations and tenure side by side

Choose how the rows are grouped and the whole survey re-reads itself that way — response rate, every driver and its average rating, one row per group.

Nine ready-made groupings

Nine ready-made groupings

Departments, locations, divisions, positions, work type, gender, age and tenure, plus your own segments. One dropdown, nothing to set up first.

Segments you define yourself

Segments you define yourself

Combine location, department and division into a named group — for the teams your org chart does not draw. A person can sit in several.

One filter, every tab

One filter, every tab

Narrow to a team once, and the scores, the comments and the headline charts all follow.

The anonymity threshold

One number decides how small a group can get before its results stop being shown — and you are the one who sets it.

A threshold set on the survey itself

Set when you build the survey, five by default: the fewest distinct people a figure needs before it is shown.

A threshold set on the survey itself

Testing of every slice, not the survey as a whole

Every chart, question, score-grid group and the comment list is checked against the threshold on its own.

Testing of every slice, not the survey as a whole

The same rule when you narrow the view

Filter to one department or tenure band, and what is left is re-tested. A slice below the threshold reads not enough data.

The same rule when you narrow the view

Comments with a date and no author

On an anonymous survey a comment shows its answer and date, not its author. Breakdowns still work: department, location and tenure are stored on the answer.

Comments with a date and no author

More in Pulse

The rest of the survey module

Company-wide surveys are one half of Pulse. The other half asks one person at a time, at the moment it matters.

Lifecycle surveys

A form sent by a workflow when someone reaches a stage — onboarding, exit, the moments between — read person by person or pooled per question.

Learn more
Lifecycle surveys

Frequently asked questions

How small can a team be before its results are hidden?

What does a manager see, and what does HR see?

Can an answer be traced back to a person?

Can we run the same survey every quarter?

Can we compare this survey with the last one?

Do we have to set drivers up before the first survey?

See what your people would tell you

Run one engagement survey with drivers, segments and a threshold of your own. An implementation manager sets it up with you.