> 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-reports/reporting-faq/what-is-the-purpose-of-the-neutral-option.md). # What is the purpose of the neutral option? The neutral category provides an option for the participant who truly does not have an opinion on a question so that they are not forced to respond positively or negatively. If you do not include a neutral option, you are forcing employees to make a choice, when in reality there are times when people have no opinion. Without a neutral rating, the tendency is for people to choose the more positive rating, and accordingly, it will falsely skew results towards favorable. Research confirms that you should not use an even-numbered rating scale (e.g. 4-point or 6-point). TalentMap uses the five-point likert scale, the most common scale in attitudinal research because a five-point scale is widely considered to represent the "natural" number of opinion plateaus or levels. --- # 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-reports/reporting-faq/what-is-the-purpose-of-the-neutral-option.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.