> 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/readme.md).

# Foreword

Compliance framework for the Bilan Carbone® method

**This document presents the compliance framework for carbon accounting tools with the Bilan Carbone® method.** It details the framework, objectives, and process of the compliance procedure. The reference framework is structured in a tree format and is accompanied by a blank evaluation grid, enabling in particular the completion of self-assessments by tool developers.

In addition to the assessment of carbon reports, this guide also presents a control guide for the requirements of the ESRS E1 standard of the CSRD, which does not provide an official output, but allows compliance with its requirements to be verified prior to the annual audit.

The guide is designed both to support auditors in their assessments and to enable tool developer candidates to prepare for their compliance process.

This guide was published on [**03/02/2026**](/compliance-framework/readme/historique-et-suivi-des-modifications.md)**.**


---

# 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/readme.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.