Leader-based reports give managers in your organization access to the survey results relevant to their teams. By giving your leaders access to their results, you can help them to understand where to focus and how to take action within their teams.

Leader-based reports are currently only available on attributed Engagement surveys. To use this feature, you need to create a valid hierarchy for your organization based on manager email addresses.

Once you have created a valid hierarchy, you can choose leader-based report sharing when distributing the results of your survey. To create a report, on the report sharing page, select Create filtered report and choose the Leaders option.

From the drop-down, select the level of the hierarchy for which you want to create reports. Level 0 is the top of the hierarchy (generally the company CEO), level 1 are the people who report into the CEO, and so on, down the full reporting line. You can ‘preview levels’ to see the names and email-address of employees at each level who will receive the reports.

You can choose between including only the managers' direct reports (the people who they manage) or the full reporting line (their direct and indirect reports, all the way down the manager hierarchy). All selected leaders will be assigned report viewer status automatically. Before you publish the reports (and send out invitations), you can remove individuals if required.

For reports with responses from the full reporting line, you can also optionally enable access to reports of managers below them in the hierarchy. Select View responses from the full reporting line to enable the drill-down feature.

When this option is enabled, leaders will be able to select those via the Select Leader drop-down filter in their report.

Click Create draft to finish setting up the report shells.

When you’re ready to share reports, you can add report viewers and owners and publish the report to notify them.

A "not yet reportable" report has a sufficient number of participants to eventually meet the reporting group minimum, but not enough responses have been submitted yet to display data.

While a viewer can be assigned and will receive a notification when the report is published, they won't see any data until the number of submitted responses meets the minimum threshold. Once that happens, the data will automatically become visible to them.
​

In contrast, an "unreportable" report never had enough participants included to be reportable in the first place. The number of participants in the report is below the reporting group minimum, making it impossible to generate a valid report. For this reason, viewers cannot be assigned to these reports, and nobody will be notified of them when published.

When using a full reporting line leader-based report with drill-down enabled, there may be cases where a leader meets the required number of indirect reports but has too few direct reports, based on your confidentiality settings.

In these cases, a removal rule may be applied to exclude certain responses from the report. This helps protect anonymity and ensures no individual can be identified by drilling down to different leaders in the reporting line.

We recommend watching the short video below for a detailed explanation of how this rule works, including a few examples.
​

Leader-based reports are unavailable for Unattributed, Onboard/Exit, or Individual/Leadership 360 surveys. If the option isn't showing for eligible surveys, please ensure your hierarchy is validated, each survey participant has a Manager Email or ID assigned in their user profile, and the hierarchy demographic is selected in the survey configuration. Still not working? Reply with "Ask a Person" in a support conversation to speak with a Product Support Specialist.

When basic or strong protections are selected, we may remove certain responses to protect identities. You can usually see where responses were removed by clicking into a factor on your insights page and scrolling down to the bottom of the page to view the demographic spread graph. Usually, if responses have been removed due to confidentiality, you will see a blue banner above the demographic spread graph.

If fewer than 10% of responses are removed, the banner won’t appear. However, you can still hover over the "n=" score to identify which responses were removed. Always check the demographic spread graph for details.

Additionally, if a leader has fewer reports than the required minimum, their report won’t be created.

A potential workaround is to create two versions of your report: one with drill-down enabled and one without. This allows you to maintain confidentiality while still accessing more comprehensive data where possible.

The confidentiality banner appears in a leader-based report when more than 10% of responses have been removed to protect participant confidentiality. This ensures that report viewers can’t identify individual responses, especially in smaller groups. For example, if one response is removed from a group of 20 participants (which is 5%), the banner won’t appear. But if 10% or more of the responses are removed, the banner will show to highlight the data discrepancy.

You can also spot removed responses by comparing the participation rate with the "n=" information for each question. If the "n=" is smaller than expected, it likely means responses were removed.

The participation report shows how many participants submitted responses from different demographic groups, without revealing specific answers. This data is displayed, as it only counts submissions, not individual responses. Confidentiality protections are stronger in other parts of your reports page such as insights and questions as this shows actual response data.

In leader-based reports with drill-down enabled, some responses are hidden to protect confidentiality and prevent identification. The Heatmap doesn’t show warnings about these removed responses. However, if you apply the same demographic filter in the Insights page, a blue banner will appear to indicate that responses were removed for confidentiality.

This issue usually occurs if the hierarchy demographic isn’t selected as a survey demographic.

Here’s how to fix it:

Still need help? Just reply with "Ask a Person" in a support conversation to speak with a Product Support Specialist.

💬 Need help? Just reply with "Ask a Person" in a Support Conversation to speak with a Product Support Specialist.