> 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/step-5-analyze-interpret-and-report/compass-reports/prepare-reports-for-senior-leadership.md).

# Prepare Reports for Senior Leadership

Once the survey data is ready for reporting, one of the most important milestones is to pass along filtered reports to Senior Leadership. The below series of videos are intended to guide you through how to potentially prepare reports for this audience so that they can make the most of their data. 

The three pillar reports often shared with leaders are:

1. **Snapshot:** Best for visualizing all surveys scores in one report along with key driver analysis.
2. **Heatmap:** Best for senior leaders who wish to view comparison data for the groups they support.
3. **Comments:** Best for providing direct insights into what employees are experiencing and feeling.

Other reports like [Insights](/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/insights.md) or [AI Comment Analysis](/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/comments/ai-comment-analysis.md) are more often used once your organization is ready to start making meaningful change with focus groups and action planning. 

### Snapshot Report | 7m 06s

{% embed url="<https://vimeo.com/1050042661?share=copy#t=0>" %}

### Heatmap Report | 3m 08s

{% embed url="<https://vimeo.com/1050044443?share=copy#t=0>" %}

### Comments Report | 4m 23s

{% embed url="<https://vimeo.com/1050045613?share=copy#t=0>" %}

### Bulk Report Prep | 1m 46s

{% embed url="<https://vimeo.com/1050044946?share=copy#t=0>" %}


---

# 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/step-5-analyze-interpret-and-report/compass-reports/prepare-reports-for-senior-leadership.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.