> 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-overview.md).

# 360 Overview

360 Feedback gives leaders in your organization a confidential, all-around view of how they are perceived at work. A leader (the **ratee**) is rated by the people around them (their manager, peers, direct reports, and themselves) and receives a report that shows how each group sees them, where their strengths are, and where they can develop.

Because 360 Feedback runs inside Compass, the results live alongside your engagement data, with one login and one place to go.

{% hint style="info" %}
**Availability.** 360 Feedback is enabled per organization. If you don't see it, contact your TalentMap consultant.
{% endhint %}

TalentMap runs your 360 for you

360 Feedback is delivered as a **managed service**. Your TalentMap Client Success team sets up and administers the program on your behalf; building the participant list, launching the assessments, and preparing the reports. You and your team take part as raters and ratees, and TalentMap handles the operational work.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FApnWsM5U94jN3taEgvMs%2Fimage.png?alt=media&amp;token=01153076-5b53-49f0-a6ea-a6e75d07bbf3" alt=""><figcaption></figcaption></figure>

## Key terms

<table><thead><tr><th width="183">Term</th><th width="388.9896240234375">What it means</th></tr></thead><tbody><tr><td><strong>Ratee</strong></td><td>The person being assessed - the leader who receives feedback.</td></tr><tr><td><strong>Rater</strong></td><td>A person who provides feedback on a ratee (manager, peer, direct report, or self). A rater receives one email per person they are rating.</td></tr><tr><td><strong>Administration</strong></td><td>One full 360 for one leader. Five administrations means five leaders assessed.</td></tr><tr><td><strong>IDP (Individual Development Plan)</strong></td><td>The development plan a ratee writes from their results. A manual IDP template is included in the report PDF. (This is distinct from Action Planning.)</td></tr></tbody></table>

## What to expect

* **You are invited by email.** Raters receive an invitation with a secure link to complete a short assessment. Raters do not need a Compass account.
* **You give or receive feedback.** Raters complete assessments; ratees later receive a report based on the combined feedback.
* **Reports are released when ready.** When your report is released, you are notified by email and can view it in Compass. A ratee must be a Compass user to view their report.

{% hint style="info" %}
**Your feedback is confidential.** Feedback is always reported at the group level, and comments are never attributed to an individual. Groups too small to protect anonymity are hidden from the report. See Anonymity and Confidentiality in 360.
{% endhint %}

## Where to go next

* If you have been asked to give feedback: Completing a 360 Assessment
* If you are receiving feedback: Viewing and Sharing Your 360 Report
* How your responses are kept confidential: Anonymity and Confidentiality in 360
* Common questions: 360 Feedback FAQ


---

# 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-overview.md?ask=<question>&goal=<user_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.