> 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-30th-2026.md).

# October 30th, 2026

## Every dash on the Heatmap now says why

When a heatmap cell has no score or no gap to show, hover over its dash to read why, so you can answer the question when someone asks instead of guessing.

![A dash in a dashed box compared with 2024, its tip reading Not in 2024: the 2024 results don't include this group](https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FqQZ6ftRuOJmH6RKeHvEt%2Fwi188-dash-tip-1280.png?alt=media)

**What's new:** Every dash now gives its reason in its tip, in plain words, for example that the previous period's results don't include the group, or that too few people in the group answered a question. Screen readers read the same reason, and reasons show in English, French, or Spanish, whichever language you use Compass in. A dash, or a score with nothing to compare it with in the percentage view, sits in a dashed box so it never looks like "less than 1 point", and the key ends with a **Nothing to compare** entry. When a comparison scores 0% favourable on a question, each group now shows its score and its gap instead of a column of dashes. Compared with a previous period, a group with no scored answers in this survey now shows a dash on screen and in Excel and PowerPoint exports, instead of a negative change, and its dimension's change is worked out from the other questions.

**Why it matters:** A dash used to give no reason, so it could be read as "no change" and nobody could say why a number was missing. Now the heatmap answers that itself, and a missing number never looks like a result.

**How to use it:** Navigate to **Reports** > **Heatmap**, select a survey and a demographic, and hover over any dash or boxed score to read its reason. If a group or question you expected is missing from a previous period comparison, a Site Admin can check how it is mapped on the survey's **Previous Period** page.

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-30th-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.
