Score or Trend? How to Compare Engagement Results Correctly

The first question most people ask when they receive an engagement survey report is: "What was our score?" The second follows quickly: "What changed since last year?" And the third often comes from leadership: "How do we compare to similar companies?"

These three questions look at the same result from three different angles, and the difference between them is rarely clear. In meetings, score and trend get used interchangeably, and the benchmark is read as a standalone report card. Yet the same result can tell a completely different story depending on which measure you look at.

In this article we explain what score, trend and benchmark each answer, when each can mislead, and how to read the three together. It is a framework that complements our articles on comparing engagement survey results year over year and employee engagement benchmarks; see those for the technical detail.

Three measures, three different questions

Each measure's blind spot is another's strength. A score does not show change; a trend does not show level; a benchmark does not show your own organization's dynamics. A result can only be read completely when all three are considered together.

Score: A starting point, but not the whole story

A score shows the current level of a statement or index on a 0–100 scale. It is the fastest way to tell at first glance whether a result is good, average or weak. Using a score alone carries three risks:

• Absolute thresholds are arbitrary. Rules like "above 75 is good, below 60 is bad" ignore the scale and the nature of the statement. Some statements (fair pay perception, for example) naturally score lower than others. It is more meaningful to read a score alongside the same statement's past results or a suitable benchmark.
• A single number hides the distribution. Two groups with the same score can have very different answer distributions: in one, most people are moderately engaged; in the other, one group is highly engaged and another has disengaged. Trusting the average without seeing the distribution is misleading. We explain how the favorable rate is calculated and why it should be reported alongside in what is a favorable score.
• A high score breeds comfort. A high-scoring unit is considered "fine" and drops off the agenda. If the score in that unit starts to fall, someone looking only at the score will not be the first to notice.

Trend: Direction and momentum

A trend shows how a score moves over time. The difference between two measurements is only a difference; three or more measurements form a trend. A trend is the most direct way to see whether your actions are working: if the score rises in an area you prioritized, your steps are paying off.

But trends have their own traps:

• Not every difference is real. In small groups, a change of a few points is often chance. Which differences count as meaningful depends on group size; see sample size and margin of error for details.
• A trend requires comparable measurements. A trend built on measurements where the statement, scale, scope or calculation changed is misleading. We cover what disrupts a trend in comparing results year over year.
• Rising at high scores is hard. Raising a score by 3 points at 85 can be much harder than at 55. Evaluate a rising trend with its starting level in mind.
• Recovering from low scores is easy. In a unit starting from a very low point, the first year's rise may be a rebound rather than a lasting improvement. That rise needs to be confirmed by later measurements.

Benchmark: Provides context, does not pass judgment

A benchmark relates your result to similar organizations or to other groups inside your own. We explain why benchmarks are needed and their types in employee engagement benchmarks. What matters here is that a benchmark is context, not a verdict:

• The comparison group matters. Industry, workforce profile, size and country all directly affect the comparison. Being "above" or "below" an unsuitable comparison group does not reflect your real situation.
• Scale and calculation must match. Values produced with different scales or calculation methods cannot be compared.
• A benchmark does not show direction. You cannot tell an organization slightly above the benchmark with a falling trend from one slightly below it with a rising trend by looking at the benchmark alone.
• Internal comparisons should not be used for rankings. Ranking units or managers by score rewards chance differences in small teams and creates pressure before the next survey.

Same result, different stories: Four scenarios

When you combine score and trend, four basic pictures emerge. Each calls for different action.

The value of this table is that a manager who looks only at the score would read the second scenario as "all is well". Likewise, someone looking only at the trend might call a unit in the third scenario "successful" despite its still-low score. Seeing both together makes it much easier to set the right priority.

Example

Consider the results of three units (sample data):

Looking at score alone, A is the best unit. Looking at the benchmark alone, A is above and B is well below, so B looks "problematic". Add the trend and the picture changes: a 5-point drop in A (if the group is large enough) is an early warning, while B is recovering by 9 points and its actions may be working. C is stable and close to the benchmark; to set priorities there, you need to go down to the statement level.

A practical order for reading all three

1. Look at the score first. What is the overall level? Which statements are high and which low? What does the distribution look like?
2. Then look at the trend. Is the previous measurement comparable? Is the change meaningful for the group size? Where possible, look at three or more measurements together.
3. Then look at the benchmark. Is the comparison group suitable? Are the scale and calculation the same? Does the benchmark change how you read the trend? For example, if the whole sector is also declining, the decline in your organization is interpreted differently.
4. Focus on the areas where action was taken. Has anything changed in the areas you prioritized last year? This is where the results have a real "story".
5. Validate with open-ended comments. Comments often explain the reason behind a numerical change or difference. We cover the general steps of analysis in our guide how to analyze employee survey results.

When setting priorities, alongside the score you should also look at which statement actually drives engagement. Key driver analysis is the strongest tool for that.

Define score and direction together when setting targets

The comparison approach also affects how you set targets. A single score threshold ("all units should rise above 75") looks fair, but it does not mean the same thing to units starting from different points.

• Set a "maintain" goal for high-scoring units. Expecting continuous increases from an already strong unit is unrealistic and creates needless pressure.
• Set an "improve" goal for low-scoring units. Define the target relative to the unit's own starting point instead of a score threshold.
• Set a direction and a date. A goal like "in the next survey, scores in the priority area should rise beyond the margin of error" expresses both the direction and that the change must be meaningful.
• Do not tie targets to managers' individual performance. In small teams, scores and changes are open to chance fluctuations; it is fairer to define goals through actions and processes.

Show all three side by side in reporting

A good engagement report shows the score, the change and the benchmark together next to each result:

• Show score, change and benchmark on the same row. The reader sees all three perspectives at once.
• Mark only meaningful changes. Put up or down arrows only on differences that pass the threshold; show the others as "no change".
• State the number of responses. The reader can judge for themselves how reliable a difference is.
• Define the benchmark group. State in the report who the benchmark is made up of and when it was collected.
• Break the trend line where needed. Do not show a trend for results where the statement, scale or scope changed, and note why.

Common mistakes

• Using score in place of trend: Saying "our score is high, so we're doing well" lets you miss a falling trend.
• Drawing conclusions from a single year's change: A one-year jump or drop can be chance or a composition effect.
• Reading the benchmark as a report card: Saying "we're below" or "we're above" without questioning the suitability of the comparison group is misleading.
• Presenting the three separately: Showing score, trend and benchmark on different slides in different meetings keeps the whole from being seen.
• Dropping high-scoring units from the agenda: When a decline starts in these units, it becomes hard to notice.
• Giving low-scoring units the same target: Setting the same score target for units starting from different points is unfair.

Conclusion

Score shows today, trend shows the trajectory and the benchmark shows context. Reading an engagement result from all three angles prevents both false alarms and real risks going unnoticed. In your next results meeting, instead of only asking "what's the score?", ask these three questions together: Where are we? Where are we heading? Where do we stand relative to similar organizations? The answers will help you set priorities far more accurately.

Frequently asked questions