> 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-admin/results/benchmarks.md).
# Benchmarks
To add Benchmark data to your survey, please follow these steps:
1. From the Compass dashboard, click **Surveys**. **Please Note**: the **Surveys** option is only available to your organizations Compass administrator(s).
2. Click on the title of the survey you would like add benchmark data to.
3. Click **Benchmarks** in the left column.
4. Click **AutoMap** then **Continue**. Automap will do its best to match items to TalentMap's benchmarked items. Click the **Expand All** icon in the top right to open the list of all items to see if the survey is mapped correctly.
5. Items that have not been mapped will appear with a red background. To manually map an item, click the pencil icon to the right, then choose the correct item from the dimension dropdown list and click **OK**.
6. To remove a benchmark mapping, click the pencil, then click **Clear Mapping** and **OK**.
Benchmark data will appear in Snapshot and Dashboard reports.
> **Ranked choice items are not benchmarked.** Ranked choice questions do not appear on the benchmark survey page or in the benchmark builder.
---
# 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-admin/results/benchmarks.md?ask=&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.
