> 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/referentiels-de-conformite/chapitre-e-communication-et-positionnement.md).

# Chapitre E : Communication et positionnement

Au-delà de la conformité aux éléments qui caractérise une démarche Bilan Carbone®, l’audit cherchera également à analyser la communication, les prises de positions et les messages passés au sein des outils-candidats ainsi que sur leurs sites web, blogs, réseaux sociaux voire articles de presse parlant de l’outil.

Ces enjeux de communication sont essentiels pour assurer la mobilisation de toutes les parties prenantes dans une transition pertinente et pérenne. C’est pourquoi il convient que ces derniers soient en accord avec les avis d’experts sur la transition bas carbone. Plus particulièrement, il sera analysé les messages passés sur la comptabilité carbone (enjeux, objectifs, etc.), sur la neutralité carbone ainsi que sur la place de la compensation carbone dans le panel d’action à disposition des organisations.


---

# 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/referentiels-de-conformite/chapitre-e-communication-et-positionnement.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.