> 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-goals-and-actions/collective-action-plan.md).

# Collective action plan

A well-defined collective action plan is essential for translating sustainability goals into concrete steps and ensuring long-term impact. This sub-criterion evaluates whether stakeholders have agreed on a multi-year action plan that outlines clear strategies for achieving sustainability goals and whether there is a structured process in place to review and update the plan regularly.

{% hint style="success" %}
Good practice considerations for a collective action plan include:

* Addressing systemic issues by focusing on long-term solutions that can be embedded in local governance. 
* Considering diverse land uses and commodities within the landscape. 
* Outlining strategies and actions that align with defined milestones and advance progress toward sustainability goals. 
* Being publicly available and agreed upon by participating stakeholders to ensure broad support. 
* Being updated regularly to reflect progress, funding availability, and changing conditions. 
* Including a finance or funding strategy to support implementation. 
  {% endhint %}

## Requirements and validation criteria

To assess whether a landscape initiative has a well-defined collective action plan, LandScale requests specific information via tailored questions. Submitted materials are used to evaluate and validate the extent to which the collective action plan sub-criterion is met. 

<table><thead><tr><th width="195">Requirements</th><th>Validation criteria</th></tr></thead><tbody><tr><td>Collective action plan.</td><td><p>Documentation of the initiative's multi-year action plan is uploaded, including evidence that it has been agreed to by participating stakeholders and aligns with the collective sustainability goals and associated milestones. The action plan should:</p><ul><li>Clearly define available resources (e.g., funding, technical support). </li><li>Include at least one action per sustainability goal. </li><li>Address diverse land-use types and/or commodities. </li><li>Be agreed upon by multiple stakeholders. </li><li>Be publicly available.</li><li>Have been updated within the last five years. </li></ul><p>Include an indication of the time period covered by the action plan.</p></td></tr><tr><td>Action plan review and update process.</td><td><p>A clear description of the process for reviewing and updating the action plan over time is provided, including:</p><ul><li>The stakeholders responsible for the review process.</li><li>The frequency of reviews.</li></ul></td></tr></tbody></table>

Once validation is complete, the collective action plan 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.landscale.org/landscape-initiative-maturity/collective-goals-and-actions/collective-action-plan.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.