> 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-6-discuss-clarify-and-plan/talentmap-survey-results-presentations/hr-preview-of-survey-results.md).

# HR Preview of Survey Results

Five business days after the survey closes, you will be able to schedule a 60–90-minute online preview and discussion of the survey findings with our Executive Consultant / Organizational Psychologist. This session provides an opportunity to review the preliminary results, discuss key insights, and address any questions before the formal presentation to your Executive Leadership team.

This collaborative review allows the survey team sufficient time to interpret the findings, refine their understanding of the results, and identify priority discussion points, ensuring the formal presentation is focused, meaningful, and aligned with your organization's needs.


---

# 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-6-discuss-clarify-and-plan/talentmap-survey-results-presentations/hr-preview-of-survey-results.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.