Aggregated participation rate

The main number in the participation section shows the aggregated participation rate over a length of time set by the account administrator. This length of time is determined by the “Time for all data” setting, which is either three, six, or twelve months. This means that if an employee has participated in one survey during that length of time, they are counted in the participation rate. 

Non-aggregated participation rates

To view the non-aggregated participation rate of each survey, click on the “Expand” icon. These participation rates are not aggregated, meaning that you are able to see exactly how many employees were surveyed on each round and how many employees answered each round. 

Participation rate benchmarks

Benchmark for participation works the same as benchmark for scores and is determined by the context selected in the left menu. When viewing the company scores as a whole, the benchmark is based on the industry or Peakon average, depending on the setting chosen by the administrator. 

If the context is set to a particular segment, the benchmark is based on the company average (or whatever benchmark has been configured for that segment by the administrator). 

Typically as a manager logging into Peakon viewing your team dashboard, the participation rate will be benchmarked against the company average.

Engagement participation

This section on your participation panel relates to the amount of people who have been asked an engagement question within the time for all data window. In this case, the engagement question refers to one of the following questions:

  • Question: How likely is it you would recommend [Company Name] as a place to work?

Additional engagement questions that can be activated:

  • ‘Loyalty’ outcome question: If you were offered the same job at another organisation, how likely is it that you would stay with [Company Name]?
  • ‘Satisfaction’ outcome question: Overall, how satisfied are you working for [Company Name]?
  • ‘Belief’ outcome question: How likely is it you would recommend [Company Name] products or services to friends and family?

Click on the “employees surveyed” icon to reveal the employee list. The list will not state whether an employee has answered the survey or not, it simply lists the employees that have been sent a survey within a specific length of time set by the account admin.

Note: Depending on the engagement question frequency, it could be the case that Peakon shows 100% aggregated overall survey participation, but if one employee has not answered one of the engagement questions it could show "400 answered out of 401 employees surveyed" in the "Engagement participation" box.

Aggregated score accuracy

The aggregated score accuracy indicates whether the scores are more or less accurate when taking into account participation rates. The score accuracy will either be low, medium, or high.

High - Peakon expects that if all employees answered then the score would change by no more than 0.2

Medium - Peakon expects that if all employees answered then the score would change between 0.2 - 0.5

Low - Peakon expects that if all employees answered then the score would change by more than 0.5

It may be the case that you have a low participation rate and high score accuracy. This can happen for larger segments where you would only need a small number of responses to give an accurate score. A good analogy to help illustrate this case are polls for general elections. They are normally done on a very small percentage of the population (< 0.1%), yet are extremely accurate.

The score accuracy is designed to encourage action planning on scores in cases where participation rates are lower. In such situations, the score accuracy is a useful indicator on the reliability of scores for action planning initiatives.

Viewing survey participation in the heat map

It's also possible to view survey participation in the heat map by using the "Participation" toggle. This will show both the aggregated participation and latest survey round participation rates.

Did this answer your question?