> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/tradeaware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/tradeaware/using-the-tradeaware-api/api-reference/risk-assessments/supplier-risk-assessments.md).

# Supplier Risk Assessments

The **Supplier Risk Assessments** endpoint allows users to manage risk assessments specifically for suppliers. These assessments help organizations evaluate and track supplier compliance and risk over time.

Users can update the status of a supplier’s risk assessment and add relevant notes during the process. All status changes are recorded in the risk assessment history for traceability.

**Available Status Values**

The following statuses can be assigned to a supplier risk assessment:

* **NEW**\
  The assessment has been created but not yet started.
* **UNDER\_REVIEW**\
  The supplier information is currently being reviewed.
* **READY\_FOR\_ASSESSMENT**\
  The review is complete and the supplier is ready for a formal assessment.
* **CMS\_ASSESSMENT\_REQUESTED**\
  A request has been made for an external risk assessment from our partner, CMS Germany (subject to CMS being engaged).
* **CMS\_ASSESSMENT\_COMPLETED**\
  The external CMS assessment has been completed.
* **IN\_RISK\_MITIGATION**\
  Risks have been identified and mitigation actions are in progress.
* **EUDR\_COMPLIANT**\
  The supplier has been assessed as compliant with EUDR (European Union Deforestation Regulation) standards.
* **EUDR\_NON\_COMPLIANT**\
  The supplier has been assessed as not meeting EUDR compliance requirements.


---

# 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.live-eo.com/tradeaware/using-the-tradeaware-api/api-reference/risk-assessments/supplier-risk-assessments.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.