> 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/completing-a-360-assessment.md).
# Completing a 360 Assessment
If someone has asked for your feedback as part of a 360 program, you will be invited to complete a short assessment about them. This article explains how.
{% hint style="info" %}
**You do not need a Compass account to complete an assessment.** You can open the survey straight from the link in your invitation email.
{% endhint %}
## Open your assessment
You can start your assessment by clicking the link in your **assessment invitation** email
If you have been asked to rate more than one person (each is called a **ratee**), you receive a separate invitation email for each. There is no single combined email.
## Answer the questions
The assessment shows only the questions that apply to your relationship with the person you are rating, for example, a peer and a direct report may see different sections. You do not need to do anything to set this up; it is handled for you.
Answer the questions and submit. Your progress is saved automatically as you go, so you can close the survey and come back later it will resume where you left off.
{% hint style="info" %}
**Rating more than one person?** Each person you rate is a separate assessment. Complete them one at a time. If you are a Compass user, each finished assessment moves to the **Completed** section of My Tasks with the date you completed it.
{% endhint %}
## Your feedback stays confidential
Your individual responses are never shown to the person you are rating or to their administrator. Feedback is combined with others in the same relationship group and reported at the group level, and comments are never attributed to you by name. See Anonymity and Confidentiality in 360.
---
# 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/completing-a-360-assessment.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.
