Understanding how benchmarks are applied on different views

The context has an impact on all of the data contained within the dashboard, including all engagement and driver scores, comments, and even the benchmarks used. This article will explain how the benchmark adapts to the context view. It will contain:

• How it works
• Administrator's point of view
• Manager or senior leader's point of view
• Exception: Segment specific benchmark

How it works

The context switcher is located in the top left-hand corner of the Peakon dashboard, and allows users who have access to multiple datasets to switch between them. You can think of the context switcher as an all-round filter to all survey data.

The areas segment's scores are benchmarked against depends on how the segment is viewed. The below table contains the general rules the system follows for benchmark selection:

Note: Customers using True Benchmark can click on The True Benchmark detail to view the slide-out panel that informs them of the benchmark source. Use this if you are unsure where the benchmark is coming from.

Administrator's point of view

An administrator sets their context to company level, and views the Marketing department (8.0). Since Marketing is a sub-segment of the company, this score is benchmarked against the overall company score (7.4).

The administrator then sets their context to London, and views the Marketing department segment. The engagement score for Marketing has now changed (7.9), since now they are viewing the scores of Marketing employees in London only.

Additionally the score is now benchmarked against the London average engagement score, instead of the company wide engagement score.

Manager or senior leader's point of view

The majority of managers and senior leaders have access to one or two segments, depending on whether their direct reports are also people managers. 

When a manager has their context set to their own team, the segment is benchmarked against the engagement score of the company.

However, when they view a sub-segment, for example the tenure segment 2 years - 5 years after starting, this segment is benchmarked to her overall team score. This is because they are only viewing the portion of this segment that is within their own team. 

The same overall logic applies to users who manage multiple segments, not just their own direct reports or all reports.

Exception: Segment specific benchmark

Customers can set a segment specific benchmark to a high-level segment (eg. a specific entity) and propagate that benchmark preference to the segments hierarchically linked to the high-level segment.

In such instances, when viewing in the context of that segment, the segment specific benchmark is applied. To learn more, see About benchmarking and how it works.