> 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/help-and-updates/product-updates/october-27th-2026.md).

# October 27th, 2026

## The Heatmap now explains its colours and numbers

A key above the heatmap now tells you what every cell is compared with and what each colour means, so you can read and present your results without someone explaining them.

![The heatmap with the key open above the grid, compared with Overall](https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FmeL9PMnaZbAWhuJgX43B%2Fheatmap-key-open.png?alt=media)

**What's new:** The key's first sentence names your **Compare To** choice and who it covers, for example everyone in your organization and the number of responses. The rest of the key explains the colours in words: orange is below the comparison, blue is above, white is less than 1 point either way, and darker shades mean bigger gaps, with each shade labelled in points. A previous period is named by its own title, such as 2025. In the percentage view, hover over a cell to see its gap from the comparison. Screen readers read it too.

**Why it matters:** Colour alone does not say what a cell is compared with, or how big a gap is. The key puts that on the page in plain words, so a heatmap can be read and shared without a walkthrough.

**How to use it:** Navigate to **Reports** > **Heatmap**, select a survey and a demographic, and read the key above the grid. Change **Compare To** and the key changes with it. Click **HEATMAP KEY** to close the key to one line for more room. Compass opens it the way you last left it.

Related article: [Heatmap Overview](https://docs.talentmap.com/knowledge-base/reports/compass-reports/heatmap/heatmap-overview.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 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/help-and-updates/product-updates/october-27th-2026.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.
