Use hierarchy and downline views

Attributes slice the org sideways. Hierarchy slices it the way it actually runs — by who reports to whom. Drill into any manager’s branch and see the PSindex® picture for exactly the people under them.

Before you start

• You need the admin role.
• Your participant file must include reporting relationships, configured as a hierarchy. Without one, the hierarchy controls don’t appear. See Set up attributes and hierarchies.

Drill into a branch

1. Open the survey’s Results.
2. Navigate the hierarchy to the manager you care about. The heatmap now scores only participants in that branch.
3. Keep drilling to go deeper, or step back up to widen the lens.

Choose the downline depth

With a branch selected, the downline control sets how far below the manager to include:

• Direct Reports Only — just the people who report straight to this manager. The cleanest read on one team.
• Direct Reports + N Levels — the manager’s reports plus everyone the chosen number of levels beneath them. Use this for a director’s or VP’s whole organization.

Depth changes the population, so it changes the scores. A VP’s directs may be thriving while the levels below them are not — checking both is the entire point of this view.

Confidentiality still applies

Branches with fewer responses than the survey’s response-count threshold (default 3) are hidden, exactly as in the flat heatmap. A frontline manager with two respondents won’t produce a score. Widen the depth or move up a level to get a reportable population. See Read the heatmap.

Use it well

Downline views make results personal — this is a named leader’s organization, not an anonymous cut. Share a branch view with that leader as the start of their own work, not as a scoreboard. Zone breakdowns and deltas behave the same here as everywhere else in the heatmap.