> 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.9-prise-en-compte-et-suivi-des-bugs-calculatoires-et-methodologiques.md).

# Criterion B.9 - Handling and tracking of calculation and methodological bugs

The use of the candidate tool by users can sometimes highlight errors/bugs leading to inconsistencies in the final results. It is therefore necessary to allow these users to report the information. It is also necessary to track and work towards correcting these errors.

Thus, tools will be expected to have an accessible and transparent bug reporting process, which notably implies having easy contact with the product team, or at a minimum a competent person within the tool's publisher.

#### 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.9 - Handling and tracking of calculation and methodological bugs</strong></td></tr><tr><td><strong>Question</strong></td><td>Is there an internal procedure for tracking calculation bugs and their associated corrections?</td></tr><tr><td><strong>Answers</strong></td><td><ul><li><mark style="color:green;"><strong>Yes, the procedure is detailed in the tool's resources or upon request</strong></mark></li><li><mark style="color:green;"><strong>Yes in part (correction only, no tracking), but the tool publisher's team can be easily contacted</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 bug reporting or methodological question reporting is facilitated</p><p>Check whether there is information accessible to users on the persons and/or departments to contact in case of issues (email, phone, etc.)</p><p>Verify whether there is a project/development manager for the candidate tool</p><p>Check whether an internal procedure exists for tracking calculation bugs</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.9-prise-en-compte-et-suivi-des-bugs-calculatoires-et-methodologiques.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.