> 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.7-livrables-bilan-carbone-r.md).

# Criterion B.7 - Bilan Carbone® deliverables

The formalisation of the deliverables of a Bilan Carbone® approach, like the organisation of a dedicated time for reporting, helps to centralise all the information and data from the assessment. This makes it possible to move forward in the process and to facilitate the implementation of the identified work areas, for the reduction of GHG emissions as well as for the continuous improvement of the approach.

Bilan Carbone® deliverables also serve to communicate with stakeholders, both internal and external, to share information with an appropriate level of transparency or to highlight the efforts and progress made.

Thus, at each stage of the Bilan Carbone® process, deliverables must be compiled according to the targeted level of maturity. Compliant tools must be able to support a Standard Bilan Carbone® approach at each stage: scoping, boundaries, engagement, accounting and transition plan. The list of deliverables is available at [criterion T2](https://www.bilancarbone-methode.com/6-synthese-et-restitution/6.1-restitution-du-bilan-carbone-r#niveau-standard-critere-t2) of the Bilan Carbone® method.

#### 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 B.7 - Bilan Carbone® Deliverables</strong></td></tr><tr><td><strong>Question</strong></td><td>Does the candidate tool allow the centralisation of the deliverables compiled in a Bilan Carbone®?</td></tr><tr><td><strong>Answers</strong></td><td><ul><li><mark style="color:green;"><strong>Yes, all deliverables can be centralised within the tool</strong></mark></li><li><mark style="color:green;"><strong>Yes, all deliverables are available or importable, but without centralisation</strong></mark></li><li><mark style="color:green;"><strong>Yes, the tool allows at minimum the import or creation of a flow mapping and the production of a summary of engagement actions carried out.</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 the deliverables and possible exports in the candidate tool, in particular whether:</p><ul><li>The tool allows the creation or import of a flow mapping</li><li>The tool allows the editing of a summary of engagement actions carried out</li><li>The tool allows the entry of information required for the other deliverables of the Bilan Carbone® method, particularly during the scoping and boundaries phase, which is less commonly accessible in a carbon accounting tool.</li><li>The tool allows the centralisation of Bilan Carbone® deliverables</li></ul></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 dynamically by asking a question.

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

```
GET https://www.bilancarbone-conformite.com/compliance-framework/compliance-referentials/chapitre-b-accompagnement-de-la-demarche-carbone/critere-b.7-livrables-bilan-carbone-r.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.