> 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/plot-risk-assessments.md).

# Plot Risk Assessments

The **Plot Risk Assessments** endpoint enables users to manage risk assessments for individual plots of land that they or their suppliers own. These assessments are used to evaluate compliance in the context of the European Union Deforestation Regulation (EUDR).

Users can update the status of a plot’s risk assessment and include notes throughout the assessment process. All status updates are logged in the plot's risk assessment history.

**Available Status Values**

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

* **NEW**\
  The assessment has been created but no action has been taken yet.
* **UNDER\_REVIEW**\
  The plot is currently under review by the organization.
* **IN\_RISK\_MITIGATION**\
  Risks have been identified and mitigation efforts are ongoing.
* **EUDR\_COMPLIANT**\
  The plot has been assessed as complying with EUDR requirements.
* **EUDR\_NON\_COMPLIANT**\
  The plot has been assessed as not meeting EUDR compliance standards.


---

# 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/plot-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.