> 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-4-deploy-employee-survey/monitor-response-rates.md).
# Monitor Response Rates
To monitor, filter and export live survey response rates or view historical rates, please follow these steps.
1. Login to [Compass](https://compass.talentmap.com/), click **Reports** then **Response Rate**.
2. Select a survey in the dropdown near the top left of the screen.
3. On the left side of the screen, you will see the option to display responses based on demographic information.
4. You can add multiple layers by clicking the + icon to breakdown demographic data.
5. To view the breakdown of multiple demographics, click the dropdown next to a demographic field or click the open / collapse orange icons below overall response rate.
6. Filter response rates to generate reports for specific demographic groups by clicking Filters in the top right. Available data will be displayed in the center column where you can choose demographics. Once a field is selected, you will see the available filter options in the right column. Check box(s), then click OK.\
\
**Note:** you can select multiple filters by clicking the **+** button again, then select **AND / OR.**
7. Export to Excel by clicking export in the top right corner. Add a title to the file, then click Export. Note: the export file is timestamped using UTC time. For more information on UTC timezone conversion, please view this [LINK](https://www.utctime.net/utc-time-zone-converter).
---
# 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-4-deploy-employee-survey/monitor-response-rates.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.
.png?alt=media&token=444be4d8-f0bf-4c73-a9dc-b76f7fd427cb)
.png?alt=media&token=ca044d65-cffa-4178-b97d-6dc87201f73b)
.png?alt=media&token=6d93ce2a-fdee-45fd-842b-46f8de044999)