> 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/comments/faq/how-should-disclosure-of-employee-comments-be-handled.md). # How should disclosure of employee comments be handled? TalentMap recommends as much transparency as possible. The ideal is to share all comments “as is” but very few management teams have the fortitude. Full buy-in is needed from your CEO for this approach. For most organizations, the following seems to work: * All members of the senior team see all comments * Directors see all comments that fall in their respective portfolios The challenge is how or whether to disclose comments to managers. #### **Is the manager’s group large enough to protect anonymity?** It’s human nature to try to guess who said what. Typically, comments are NOT to be shared when a manager has fewer than 25 direct reports. #### **Is it possible to share comments without causing too much upset?** Some managers are sophisticated and can put “hurtful” comments in proper context, but there are many less able to do so, and they’ll struggle with negative comments. A way to bridge these issues is to provide managers with a random or representative sample of comments from the larger department or division. In other words, all managers in a given department get the same set of comments. This approach gives managers exposure to the tone and nature of verbatim comments, which can be very direct and personal. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.talentmap.com/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/comments/faq/how-should-disclosure-of-employee-comments-be-handled.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.