> 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/landscape-initiative-maturity/collective-monitoring.md).

# Collective monitoring

The collective monitoring criterion assesses whether a landscape initiative manages a structured monitoring and reporting system that tracks progress toward collective sustainability impact goals. Effective monitoring ensures transparency, accountability, and informed decision-making.

Baseline performance assessments and performance monitoring reassessments (whether conducted through LandScale or another relevant service) establish the landscape's conditions and track changes over time, demonstrating progress toward collective sustainability goals and providing insights to inform adaptive management. To ensure credibility, these assessments are strengthened by validation from local experts. Activity monitoring provides more frequent tracking of progress against the collective action plan.

To assess these aspects, the criterion is divided into three sub-criteria: 

1. [Baseline performance assessment and reporting](/landscape-initiative-maturity/collective-monitoring/baseline-performance-assessment-and-reporting.md).
2. [Performance monitoring and reporting](/landscape-initiative-maturity/collective-monitoring/performance-monitoring-and-reporting.md).
3. [Activity monitoring and reporting](/landscape-initiative-maturity/collective-monitoring/activity-monitoring-and-reporting.md).


---

# 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/landscape-initiative-maturity/collective-monitoring.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.