> 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.5-presentation-et-analyse-des-resultats.md).

# Criterion B.5 - Presentation and analysis of results

The way results are presented is equally important for compliance with the spirit of the Bilan Carbone® methodology. Indeed, it is important that users can visualize the emission categories and sub-categories for organization-focused tools, as well as the most emitting equipment and life cycle phases for project- or product-focused tools.

This should make it possible to identify and implement reduction actions that are relevant to each organization's emission profile. This level of granularity in the presentation of results is also fundamental to the reporting phase of the Bilan Carbone® process (cf. [criterion B.12](/compliance-framework/compliance-referentials/chapitre-b-accompagnement-de-la-demarche-carbone/critere-b.12-restitution-finale-et-conclusion-de-la-demarche.md))

It is therefore important to allow a good capacity for adaptation in the display of results in order to enable the finest possible analysis of each emission profile. In this sense, it is also important to be able to distinguish between emissions under responsibility and emissions under dependency.

#### 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.5 - Presentation and Analysis of Results</strong></td></tr><tr><td><strong>Question</strong></td><td>Does the candidate tool allow results to be analysed with sufficient granularity to enable action that is consistent with the emission profile?</td></tr><tr><td><strong>Answers</strong></td><td><ul><li><mark style="color:green;"><strong>Yes - The tool enables a detailed analysis of the organisation's emission profile, by category, sub-category and emission source, and the tool allows results to be visualised with and without dependency emissions</strong></mark></li><li><mark style="color:green;"><strong>Yes - The tool enables a sufficiently detailed analysis of the organisation's emission profile by highlighting significant emissions</strong></mark></li><li><mark style="color:red;"><strong>No - The tool does not allow a sufficiently relevant analysis of the organisation's emissions</strong></mark></li></ul></td></tr><tr><td><strong>Implementation guidance</strong></td><td><p>Analyse the presentation of results in the candidate tool and ensure that different levels of reading are possible.</p><p>Check whether the tool allows dependency emissions to be included or excluded from the display of results.</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 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.5-presentation-et-analyse-des-resultats.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.