> For the complete documentation index, see [llms.txt](https://www.bilancarbone-methode.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-methode.com/english/2-scope-of-the-approach/2.2-perimetre-organisationnel.md).
# 2.2 - Organisational boundary
Source: Pexels
The Bilan CarboneĀ® method is applied here at the scale of an organisation, whose [definition](/english/annexes/glossaire.md#o) includes any company, local authority, association, public establishment, company, society, firm, authority, institution, or a part or combination of the foregoing entities.
The [establishments](/english/annexes/glossaire.md#e), [equipment](/english/annexes/glossaire.md#e) and [installations](/english/annexes/glossaire.md#i) of the organisation constitute the **organisational boundary** to be considered during the Bilan CarboneĀ®. In order to define the organisational boundary, the organisation must map its organisational chart by listing all the buildings, agencies, subsidiaries, clients, suppliers, etc. that gravitate around it.
Establishing the organisational boundary - figure 2.2.
š [*English version*](https://abc-transitionbascarbone.fr/wp-content/uploads/2025/11/Organisational-boundary.png) *of this image.*
Within the framework of a Bilan CarboneĀ® and regardless of the [maturity level](/english/1-scoping-the-approach/1.1-definir-son-niveau-de-maturite-bilan-carbone-r.md) targeted, 100% of the equipment and installations over which the organisation exercises [operational control](/english/annexes/glossaire.md#c), i.e. that it operates and uses, must be included in the organisational boundary. Any other choice must be justified.
> :mag\_right: *This requirement corresponds to the "operational control" approach of the* [*mandatory BEGES-R*](/english/annexes/bibliographie.md#autres-standards-normes-et-reglementations-de-comptabilisation-des-emissions-de-ges)*, and of* [*ISO standard 14064-1: 2018*](/english/annexes/bibliographie.md#autres-standards-normes-et-reglementations-de-comptabilisation-des-emissions-de-ges)*.*
> :mag\_right: *To express the Bilan CarboneĀ® with a so-called "analytical" reading, consistent with* [*analytical carbon accounting*](/english/annexes/bibliographie.md#guides-pratiques)*, the organisational boundary considers or defines the* [*analytical axes*](/english/annexes/glossaire.md#a) *of the organisation.*
{% hint style="info" %}
Within the framework of the Bilan CarboneĀ®, it is possible to restrict the boundary to a part of the organisation, at the scale of a site, a project, a worksite, or an event. The flexibility this generates regarding the boundary may be relevant to adapt to certain needs (decision-making, action management, etc.).
This choice is justified, transparent, and included in the [Deliverables](/english/2-scope-of-the-approach/2-introduction-a-lidentification-des-perimetres.md#livrables-relatifs-a-lidentification-des-perimetres).
{% endhint %}
> :mag\_right: *If the Bilan CarboneĀ® is intended to serve a specific regulatory reporting purpose, the organisational boundary is that of the* [*Legal Entity*](/english/annexes/glossaire.md#p) *subject to the regulation. The declaration of the* [*mandatory BEGES-R*](/english/annexes/bibliographie.md#autres-standards-normes-et-reglementations-de-comptabilisation-des-emissions-de-ges) *must concern the SIREN of the organisation in question. The* [*CSRD*](/english/annexes/bibliographie.md#autres-standards-normes-et-reglementations-de-comptabilisation-des-emissions-de-ges) *sustainability declaration must concern the same reporting company as the financial statements.*
Throughout the rest of this document, the Bilan CarboneĀ® method uses only the term "organisation". It refers to the organisational boundary adopted here (including if it is a part of the organisation or a grouping of organisations); and thus differs from an Individual, Product or Territory [boundary](/english/introduction-to-the-low-carbon-transition/quelle-integration-du-bilan-carbone-r-au-sein-dune-demarche-de-transition-bas-carbone.md#id-1-les-differentes-echelles-de-comptabilite-carbone). Certain [specificities](/english/annexes/annexes/annexe-5-specificites-pour-les-collectivites-et-les-associations.md) apply to local authorities or associations.
{% hint style="warning" %}
Double counting is inherent to the exercise. The emissions for which the organisation is responsible and on which it is dependent overlap with certain dependency and responsibility emissions of another organisation. When consolidating across multiple sites of the same organisation (a so-called multi-site approach), care must be taken to exclude double counting within this consolidation.
{% endhint %}
***
*Do you have a question of understanding?* [*Consult the FAQ*](/english/annexes/faq.md)*. The method is a living document and therefore subject to change (clarifications, additions): find the* [*change log here*](/english/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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://www.bilancarbone-methode.com/english/2-scope-of-the-approach/2.2-perimetre-organisationnel.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.