> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/hub/headcount-heatmap-chart.md).

# Headcount Heatmap Chart

The Headcount Heatmap shows workforce distribution across two dimensions simultaneously — revealing structural depth and patterns that are invisible in single-dimension views.

## What It Shows

* **X-axis (columns):** Primary grouping — Department, KLT Area, Location, Job Function
* **Y-axis (rows):** Hierarchical dimension — Layers (most useful), Pay Grade, Level
* **Cell color intensity:** Darker = more headcount in that intersection
* **Cell values:** Exact headcount numbers

**Recommended setup:** X-axis = Department (or KLT Area), Y-axis = Layers.

## How to Read It

**Layer depth** — Count how many rows have data per column — this is how many layers that department has. Consistent depth across departments indicates standardized structure; outlier columns indicate structural variation.

**Concentration points** — Dense cells show where most people are. Small populations at high layers (e.g., 2 people in Layer 9) are potential efficiency flags — are those senior positions adding value?

**Structural anomalies to flag:**

* One department with 9+ layers when others have 6 — why so many?
* Very small populations (1–3 people) at high layer numbers
* Missing middle layers (structural gaps)
* Highly inconsistent patterns across comparable departments

**Healthy patterns** — 5–6 consistent layers across departments, concentration in middle layers (3–5), minimal populations at extreme layers.

## Common Use Cases

**Analyze chain length:** Set Departments × Layers, count rows per column, identify which departments have unusually long reporting chains, investigate why.

**Compare business units:** Look for departments with different patterns from peers; consistent patterns = standardized structure; variation warrants investigation.

**Pre/post-reorg comparison:** View heatmap in Main Org (current state), screenshot, then open the scenario to see how proposed changes reduce layers or redistribute headcount.

## Interactive Features

**Show table** — Click to reveal position-level breakdown for any cell (who is in that layer-department combination). Also exportable.

**Filters** — Apply filters to focus on specific layers only (e.g., Layers 1–4 for leadership analysis) or specific departments.

**Export** — PNG for presentations, PowerPoint for editable charts, CSV for quantitative analysis in Excel.

## Troubleshooting

| Problem                          | Solution                                                                                  |
| -------------------------------- | ----------------------------------------------------------------------------------------- |
| Chart looks empty                | Check filters; verify X/Y axes are configured; confirm recent data upload                 |
| Too many layers showing          | May be legitimate or a data issue; filter to Layers 1–6 to reduce noise                   |
| Numbers don't match expectations | Check scope filters; verify access permissions; confirm effective date range in scenarios |

## Related Resources

* [Layers and Spans of Control Chart](/hub/layers-spans-chart.md)
* [Headcount Distribution Chart](/hub/headcount-distribution-chart.md)
* [Hub Overview](/hub/overview.md)
* [Planning a Reorganization](/reference-guides/overview/planning-reorganization.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agentnoon.com/hub/headcount-heatmap-chart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.