Measure engagement with a mix of instruments: a periodic census survey for breadth, short pulses for trend, one-to-ones and focus groups for explanation, plus behavioural signals such as attrition and absenteeism that corroborate what people report. Response rate and genuine anonymity decide whether the data is honest. Segment by team and tenure; an organisation-wide average hides almost everything.
Four instruments do most of the work, and each answers a different question. A census survey, run to the whole organisation on a slow cadence, gives breadth and lets you compare teams on identical items. A short pulse, run far more often on a handful of items, gives movement between census runs. One-to-ones give a manager the texture behind a team's numbers. Focus groups, facilitated by someone the participants do not report to, explain a result nobody can interpret from the data alone. Software built for [employee engagement](/employee-engagement-software) mostly automates distribution, reminders and aggregation; it does not decide which instrument fits the question you are asking, and that decision stays with you.
Everything downstream depends on whether people answered honestly, and both conditions are fragile. A low response rate does not merely weaken the sample, it biases it, because the people who stayed silent are rarely a random slice. Anonymity has to be real and it has to be believed: if a free-text box can be traced by writing style, or a group is small enough that a demographic filter identifies one person, employees will write what is safe. Publish the minimum group size below which results are never shown, say plainly who sees raw responses, and hold to it. One breach of that promise poisons every survey you run afterwards.
Self-report is worth checking against behaviour, because the two diverge in useful ways. Resignations among people you wanted to keep, absence patterns, leave building up unused, overtime concentrated on a few names, internal transfer requests and participation in optional work all say something about how people feel about being there. None of them is engagement, and each has innocent explanations, so treat them as corroboration rather than proof. Where the survey says one thing and the behaviour says another, that gap is the interesting finding. Pulling those signals together usually means the [people analytics side of your HR stack](/hr-analytics-software), since the data sits in attendance, leave and the employee record rather than in the survey tool.
A single headline figure is the least useful output of the whole exercise, because engagement is rarely uniform and the average conceals the variance that matters. Cut by team, by manager, by tenure band, by location and by function, and the picture usually resolves into a small number of places where something is genuinely wrong and a majority where little has changed. Tenure cuts are particularly revealing: a dip concentrated among people in their first year points at onboarding or at how the role was described during hiring, not at the company. Segment first, then decide where to spend attention, rather than launching a company-wide initiative in response to a number that describes nobody.
Cadence is a resourcing decision, not a best practice. Every survey creates an obligation to read the results, feed them back and do something visible, and that work is far larger than the work of sending it. Pick a rhythm you can service: a slower census you genuinely act on beats a frequent pulse nobody reads. Anchor the timing to the calendar the business already runs on, so results arrive before planning and budget decisions rather than after them. If you skip a scheduled run, say why. Silence reads as the programme quietly dying, and restarting it later costs more credibility than the pause saved.
Measuring without visible action is worse than not measuring, because it teaches people that answering is pointless and the next round's data gets quieter and more polite. The remedy is unglamorous: within a short window, publish what was heard, name the two or three things being changed, name the things that will not change and say why, and give each item an owner. Refusing something honestly costs far less credibility than a vague promise to look into it. Reporting back also has to reach team level, because a company-wide email about company-wide themes does not answer the question one specific team raised.
Published averages for engagement scores vary by industry, by region, and by how the survey was administered, so figures from different populations are not comparable and no external number can tell you whether yours is good. Compare against your own previous result on the same items, with the same instrument, distributed the same way, and read the direction of travel. Where you change the questions or the provider, say so and treat the series as broken rather than pretending it continues. The comparisons that do work are internal: this team against that one, this tenure band against the rest, this period against the last, all measured identically.
Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. If this answer described something you want to run properly, the ATS is where it lives.
Free for 1 user · No credit card · Talk to a real hiring expert
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo · Talk to sales · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
