> 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-d-transparence-de-la-methodologie-des-sources-et-formation/critere-d.4-mise-a-jour-methodologique-de-loutil.md).

# Criterion D.4 - Methodological update of the tool

The Bilan Carbone® method has evolved and continues to do so in order to offer tools and methods that remain relevant for supporting organisations in managing their GHG emission reductions. This is why the owners of the candidate tool must, first and foremost, "keep their tool alive", meaning they must plan for development and routine updates such as the update of EFs, as well as the updates necessary to maintain alignment with future reference standards and methodologies.

In order to facilitate the use of a platform, it is therefore important to offer a good level of transparency regarding changes to modules and functionalities, so that users can follow and improve their practice by benefiting from the developments made by the tool provider. Carbon accounting tools play a major role in the democratisation of carbon accounting, and to that end some offer highly accessible tools. Tool developments therefore contribute to the growing maturity of users, by avoiding blocking them due to tools that are overly focused on accessibility.

In the same way, it is important to ensure the highest level of transparency regarding the management of updates to the EF databases used and the impact these updates may have on users' assessments. This will in particular prevent the unexpected modification of an assessment's result without its owner being notified.

#### 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 D.4 - Methodological update of the tool</strong></td></tr><tr><td><strong>Question</strong></td><td>Is future development of the candidate tool planned, and in particular the need for periodic updates of EFs or even of the candidate tool's methodology? Are the associated update processes clearly described in the candidate tool's resources? Are users informed of the impacts of these updates on their assessments?</td></tr><tr><td><strong>Answers</strong></td><td><ul><li><mark style="color:green;"><strong>Yes, the candidate tool includes an update history and its EF and tool update processes are clearly explained.</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>Search the user guide, methodological guide and/or manual for paragraphs explaining past (and/or future, if available) developments. Is there a project/development manager for the candidate tool?</p><p>Is it possible to clearly identify a development lead/manager for the candidate tool? Are human resources allocated to the development of the tool?</p><p>Check for the presence of a description of the process for updating the emission factors used, and of how users are impacted.</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-d-transparence-de-la-methodologie-des-sources-et-formation/critere-d.4-mise-a-jour-methodologique-de-loutil.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.