> For the complete documentation index, see [llms.txt](https://www.bilancarbone-conformite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.bilancarbone-conformite.com/compliance-framework/compliance-referentials/chapitre-c-engagement-a-laction-significative/critere-c.3-caracterisation-des-actions-du-plan-daction.md).

# Criterion C.3 - Characterisation of action plan measures

With the definition of actions to build an operational roadmap for the transition plan, it is necessary to be able to implement project management for the implementation and steering of these actions.

Indeed, if a tool enables the creation of an action plan grouping complete actions and structuring a low-carbon transition strategy, it is necessary that these actions be sufficiently clearly defined to facilitate their implementation.

While this makes it possible to characterise actions and assess their feasibility, the relevant information here also serves the selection of actions to be implemented, by considering for example:

* The emission categories concerned by the action
* The human, technical and financial resources required or available
* The selection and prioritisation criteria for actions, such as reduction potentials, costs, prerequisites, etc.
* The steering of these actions, in particular the teams or persons responsible for the action

{% hint style="info" %}
Tools may draw on the [action sheet template](https://www.bilancarbone-methode.com/5-plan-de-transition/5.2-construction-du-plan-daction#la-definition-des-fiches-actions) proposed by the Bilan Carbone® methodology.
{% endhint %}

#### Criterion

<table data-header-hidden><thead><tr><th width="136"></th><th></th></tr></thead><tbody><tr><td><mark style="color:red;"><strong>Mandatory</strong></mark></td><td><strong>Criterion C.3 - Characterisation of action plan items</strong></td></tr><tr><td><strong>Question</strong></td><td>Does the candidate tool enable the definition of actions that are sufficiently characterised to ensure their success? (lead, linked internal resources, monitoring over time, potential barriers, etc.)</td></tr><tr><td><strong>Answers</strong></td><td><ul><li><mark style="color:green;"><strong>Yes, the characterisation of actions matches the action sheets of the Bilan Carbone® methodology, or is sufficiently close and comprehensive</strong></mark></li><li><mark style="color:red;"><strong>No, the characterisation of actions is not sufficient</strong></mark></li></ul></td></tr><tr><td><strong>Implementation guidance</strong></td><td>Analyse the characterisation of actions possible within the tool. It will be verified whether this characterisation incorporates all the relevant elements of the <a href="https://www.bilancarbone-methode.com/5-plan-de-transition/5.2-construction-du-plan-daction#la-definition-des-fiches-actions">action sheet template</a> proposed by the Bilan Carbone® methodology.</td></tr></tbody></table>


---

# 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://www.bilancarbone-conformite.com/compliance-framework/compliance-referentials/chapitre-c-engagement-a-laction-significative/critere-c.3-caracterisation-des-actions-du-plan-daction.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.