> 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/comments-report.md). # Comments Report Depending on the size of your group and your organization’s policy about distributing the written comments employees provide when completing the survey, you may have access to a comments report. The comments report is particularly valuable for getting an initial understanding of what employees are thinking about regarding each specific topic in the survey. When reviewing the comments report for your area, it is very important to keep a few things in mind: * First, try to avoid playing the “who said what” game. In other words, don’t try to guess which of your employees made specific comments. Instead, try to identify broad themes that communicate a message about how employees feel and suggestions they are making about how situations or issues can be improved. It is possible that some comments are rather harsh. * Try to control your emotions and how you react to these comments. Some employees can be less than diplomatic when they write a comment. Looking past any harsh words, ask yourself whether there is an important message that is being conveyed that perhaps is consistent with other comments that are more tactfully written. --- # 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/comments-report.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.