> 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/multi-stakeholder-governance/coordination-of-actions-and-monitoring.md).

# Coordination of actions and monitoring

For a landscape initiative to achieve meaningful impact, activities and monitoring efforts must be well coordinated. This sub-criterion examines whether the initiative has mechanisms in place to align actions among stakeholders, track progress, and ensure that interventions are implemented effectively within the landscape.

{% hint style="info" %}
The [governance and decision-making](/landscape-initiative-maturity/multi-stakeholder-governance/governance-and-decision-making.md) sub-criterion is related to, but distinct from, the coordination of actions and monitoring sub-criterion. Governance focuses on the structures, representation, and processes that guide decision-making and accountability, while coordination focuses on how actions and monitoring efforts are aligned, implemented, and tracked across stakeholders. While governance systems may include coordination mechanisms, each sub-criterion assesses a different functional dimension, with some potential for overlap.
{% endhint %}

## Requirements and validation criteria

To assess whether a landscape initiative's governance structure has mechanisms in place for the coordination of actions and monitoring, LandScale requests specific information via tailored questions. Submitted materials are used to evaluate and validate the extent to which the coordination of actions and monitoring sub-criterion is met. 

<table><thead><tr><th width="231">Requirements</th><th>Validation criteria</th></tr></thead><tbody><tr><td>Coordination of actions and monitoring.</td><td><p>A clear description or relevant documentation (e.g., Terms of Reference, organigram of governance structure, Memorandum of Understanding, or partnership agreements outlining coordination responsibilities) of how coordination is structured is provided. It should cover:</p><ul><li>The stakeholders involved in coordination.</li><li>The main activities being coordinated.</li><li>The approach to monitoring and tracking progress.</li></ul></td></tr><tr><td>Coordinating body.</td><td>If applicable, confirmation and supporting evidence that the initiative has a dedicated coordinating body responsible for these functions. Examples of coordinating bodies include a secretariat, technical working group, or center of excellence.</td></tr></tbody></table>

Once validation is complete, the coordination of actions and monitoring sub-criterion on the wheel at the top of the initiative's profile will be filled to reflect the assigned maturity level, with validated information visible throughout the profile unless it is set to private.


---

# 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/multi-stakeholder-governance/coordination-of-actions-and-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.