> For the complete documentation index, see [llms.txt](https://docs.landscale.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.landscale.org/assessment-guidelines/additional-resources/human-rights-assessment-guidelines.md).

# Human rights assessment guidelines

Human rights violations often extend beyond individual projects, plantations, and concession boundaries. Their causes and consequences relate to complex interactions involving multiple levels of government, diverse sectors, and a wide array of stakeholders. Therefore, assessing human rights at the landscape scale is a useful contribution to managing sustainability across larger geographic and governance areas.

Historically, human rights assessments have either been broad risk evaluations at the national level or in-depth, context-specific studies at the project, plantation, supply chain, or community level. These approaches, while valuable, often lack scalability and replicability. LandScale’s landscape-level human rights assessment is a pioneering step towards bridging this gap. However, it is not exhaustive and should not replace the obligations of companies, governments, and other stakeholders to undertake smaller-scale human rights assessments. Instead, it offers a complementary perspective, helping to identify systemic human rights issues, their root causes, and the enabling conditions required to address them effectively.

Download our Human Rights Assessment Guidelines below:

{% file src="/files/E6nDbcY7HRNV85kbbarv" %}


---

# 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.landscale.org/assessment-guidelines/additional-resources/human-rights-assessment-guidelines.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.
