> 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/360-feedback/360-feedback-faq.md). # 360 Feedback FAQ What is the difference between a rater and a ratee? A **ratee** is the person being assessed; the leader who receives the feedback. A **rater** is a person who provides feedback on a ratee, such as their manager, a peer, a direct report, or the ratee themselves (a self-assessment). ## Who sets up and runs the 360? 360 Feedback is delivered as a **managed service**: TalentMap's Client Success team sets up and administers the 360 on your behalf. You and your colleagues take part as raters and ratees. ## Do raters need a Compass account? No. Raters complete their assessment through a secure link in their invitation email and do not need a Compass account. Ratees (the people being assessed) receive their reports by email. ## Can one person rate more than one ratee? Yes. A person can be asked to rate several ratees. Each assessment is separate, and you receive one invitation email per ratee. ## Who can see an individual rater's responses? No one. Feedback is always combined by rater group, and reports never attribute a score or comment to a named individual. ## Where do I plan my development after seeing my results? The report PDF includes a manual **Individual Development Plan (IDP)** template. Use it to turn your strengths and development areas into goals. The IDP is your own development plan and is separate from Compass Action Planning. ## What is an "administration"? An administration is one full 360 for one leader. If five leaders are assessed, that is five administrations. ## What languages are available? 360 Feedback is available in English. --- # 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/360-feedback/360-feedback-faq.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.