> 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-b-accompagnement-de-la-demarche-carbone/critere-b.8-fresque-du-bilan-carbone-r.md).

# Criterion B.8 - Fresque du Bilan Carbone®

To make a Bilan Carbone® approach as useful as possible, it is possible to rely on related tools that may be relevant during the various stages of the process. It is common to use internal tools, for example to facilitate data collection.

To go further, particularly during the Stakeholder Engagement phase — which is essential for the proper involvement and skills development of the employees of an organisation carrying out a Bilan Carbone® — the project leader can also turn to external tools, the best known being the Fresque formats, initiated by the Fresque du Climat in 2015.

In 2021, Mathieu Rubi developed the "Fresque Carbone GRDF" to meet a need: to present the Bilan Carbone® in a simple way and encourage employee action. Following the positive feedback from this innovation, the management of [GRDF](/compliance-framework/annexes/bibliographie.md#grdf) decided to roll out the workshop to all employees as part of its corporate project. In 4 months, more than 10,000 employees were made aware of the Bilan Carbone® and the company's main decarbonisation actions.

After the success of this first rollout, ABC, as the organisation responsible for the Bilan Carbone® method, decided to develop a version adaptable to all organisations that have carried out a Bilan Carbone®. To this end, ABC entered into a partnership with [FAB'Action](/compliance-framework/annexes/bibliographie.md#fabaction), a company created by Mathieu Rubi, to develop this initiative called the Fresque du Bilan Carbone®.

#### Criterion

<table data-header-hidden><thead><tr><th width="136"></th><th></th></tr></thead><tbody><tr><td><mark style="color:green;"><strong>Optional</strong></mark></td><td><strong>Criterion B.8 - Fresque du Bilan Carbone®</strong></td></tr><tr><td><strong>Question</strong></td><td>Does the candidate tool make it possible to facilitate the creation of a Fresque du Bilan Carbone® for its users?</td></tr><tr><td><strong>Answers</strong></td><td><ul><li><mark style="color:green;"><strong>Yes</strong></mark></li><li><mark style="color:green;"><strong>Yes, the tool facilitates the creation of an educational presentation of the emission profile and the transition plan</strong></mark></li><li><mark style="color:red;"><strong>No</strong></mark></li></ul></td></tr><tr><td><strong>Implementation guidance</strong></td><td><p>Check whether the tool seeks to offer reporting formats that allow for an educational and participatory presentation of the emission profile, broken down into (3) major emission categories and (5) sub-categories of emissions.</p><p>Check whether the tool seeks to offer reporting formats that allow for an educational and participatory presentation of the actions in the transition plan, by linking them to a specific sub-category.</p></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-b-accompagnement-de-la-demarche-carbone/critere-b.8-fresque-du-bilan-carbone-r.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.