> 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/your-managed-survey/step-6-discuss-clarify-and-plan/talentmap-survey-results-presentations/talentmap-report-faq/whats-the-difference-between-a-preview-and-a-final-executive-presentation.md).

# What’s the difference between a preview and a final executive presentation?

**HR Preview:** Your Executive Consultant / Organizational Psychologist will first present the executive slide deck to your survey team for review and feedback. This preview session provides an opportunity to discuss the findings, ask questions, and ensure the presentation is appropriately tailored for your Executive Leadership team.

**Executive Presentation:** Two to three business days after the HR Preview, your Executive Consultant / Organizational Psychologist will present the survey findings to your Executive Team. This presentation is designed to:

* Provide an organization-wide overview of the survey results.
* Help Executive Leaders understand how the various survey findings connect and what they mean in the broader organizational context.
* Highlight key organizational strengths as well as opportunities for improvement and future action.

Both presentations are highly interactive, with ample opportunity for discussion and questions. These conversations help ensure a clear understanding of the results and support informed decision-making and effective action planning.


---

# 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/your-managed-survey/step-6-discuss-clarify-and-plan/talentmap-survey-results-presentations/talentmap-report-faq/whats-the-difference-between-a-preview-and-a-final-executive-presentation.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.