> 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/managers-and-leaders/read-your-results/survey-participation.md). # Survey Participation Before reviewing your survey scores, it is important to consider the percentage of employees who responded to the survey. The goal of the survey administration is to hear from as many employees as possible. The higher the participation rate, the less room there is for questions about how those who did not respond might have impacted the results. A healthy level of participation is 60 percent or better. This allows you to have confidence that you have heard from more than not. If your participation is low (e.g., less than 50 percent), you can still review your results. However, you should exercise some caution about placing too much confidence in the representativeness of the results. When participation is low, it might be prudent to conduct some post-survey focus groups to further validate the results - i.e., to discuss the results with employees to determine if the results, despite low participation, still ring true with your employees. --- # 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/managers-and-leaders/read-your-results/survey-participation.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.