> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/managers-and-leaders/read-your-results/heatmap-report.md).

# Heatmap Report

If you are responsible for multiple groups, you may be provided a heatmap. Multiple groups might be two or more business units, divisions, departments, locations, teams or demographic subgroups (e.g., age, tenure, gender). The following chart describes the basic content of a heatmap report.

Watch: Reading Your Heatmap. Video length: 2m01s. Narrated with an AI voice.

{% embed url="<https://vimeo.com/1242037711>" %}

![](https://2153489382-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXPT9x2nGbXVrpeQoz4Oz%2Fuploads%2FJZSGt7mLNInT5a6jKFDR%2Fmg-img-5.png?alt=media)

A heatmap report is valuable in three specific ways:

1. It provides a very convenient means of looking across your organization to see which parts are generally more or less favourable than the organization as a whole.
2. It allows you to focus on a specific dimension (e.g., compensation, work/life balance, performance management) to see which parts of the organization are most and least favourable.
3. It allows you to focus on the Team Engagement versus Organizational Engagement scores to see which parts of the organization have the most and least engaged teams, as well as which parts are the most and least connected to the organization as a whole.

The scores for each part of the organization represent the difference between the subgroup and the overall organization percent favourable score. Differences that are more favourable than the overall score are highlighted in blue and differences that are less favourable than the overall score are highlighted in orange. It is important to view these differences as more or less favourable than the overall score, rather than as good or bad.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talentmap.com/knowledge-base/managers-and-leaders/read-your-results/heatmap-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.