This disclosure asks an organisation to be clear about which entities, businesses, subsidiaries, joint arrangements or other parts of the group are included in its sustainability report. In practice, the report should make it obvious whether the information covers the whole organisation, only certain legal entities, or a defined subset of operations. The aim is to avoid any ambiguity about the reporting boundary so readers can understand what the reported data and statements do, and do not, cover.
The practical focus is on coverage and consistency: explain the scope used for the report and make sure it matches the way the organisation has chosen to present its sustainability performance. If some parts of the group are left out, or if the report only covers selected sites, regions or entities, that should be stated clearly so users do not assume the figures represent the entire organisation.
This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official GRI source.
A quick mental checklist before you prepare this disclosure — tick each as you settle it.
Key datapoints to prepare
How to prepare it
Request the group entity scope and consolidation notes
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Use your organisation’s own perimeter, consolidation and entity-list terms first, then map them to the sustainability report wording. If your team talks about the group structure, reporting perimeter, legal entities, or consolidation pack, use those terms in the request and in the response.
Please provide the entities included in sustainability reporting and explain the consolidation approach.
Why it fails: This uses framework-style language only and does not tell the owner what practical records to pull. It is too vague on the source list, the comparison point, the period, and the change events that affect the answer.
Please send the current group entity list used for the sustainability pack for [period], plus the matching list used for the group accounts or filed statements, and note any differences, ownership adjustments, acquisitions, disposals, mergers, or topic-specific scope exceptions.
Notes that turn data into a disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
Explain which entities are included in the sustainability reporting boundary, how that boundary was built from the group structure, and whether the same approach was used for all disclosures and material topics.
Clarify what the reported figures represent by linking them to the entities covered, noting any differences from the financial reporting population and any adjustments needed to combine data across the group.
If the reporting population changed, describe whether the movement was driven by acquisitions, disposals or other structural changes, and explain how any change in scope affects comparability with earlier periods.
Preparation tools & forms
Professional preparation tools for GRI 2-2 — free with an LRA Community membership. Register once (it's free) and every download unlocks, together with the Disclosure Library, templates and the LRA AI-assistant.
For each claim, check the evidence
Evidence pack to prepare
Common reporting gaps
Mistakes to avoid when collecting the data
Where judgement is often needed
Illustrative examples
Synthetic, written by LRA — not from a company report, not text from any standard.
We include six entities in our sustainability reporting: the parent company, three wholly owned operating subsidiaries, one joint venture accounted for on a proportionate basis for this report, and one dormant holding entity. Our published financial statements cover five entities; the only difference is the joint venture, which is outside the financial reporting perimeter, while one finance-only special purpose vehicle is excluded from sustainability reporting because it has no operational activity. - For group-level figures, we combine the included entities on a line-by-line basis and remove intra-group balances and transactions; where we do not fully own an entity, we adjust the reported figures to reflect our share and the interests of other owners. - We update the perimeter for acquisitions and disposals from the date control starts or ends, so the reporting set reflects entities added during the year and those sold or closed before period end. - The same consolidation approach is used across the disclosures in this standard, but for material topics we apply topic-specific boundaries where an issue sits outside the reporting perimeter of a particular entity, such as a leased site or a jointly controlled operation.
Illustrative only: shows how to name the reporting perimeter, explain any gap versus the financial perimeter, and describe consolidation choices for ownership, deal activity, and topic-specific boundaries.
Our sustainability reporting covers eight entities: the parent company, four operating subsidiaries, two project companies, and one service entity. Our audited financial statements include seven of those entities; the difference is one project company that is consolidated for sustainability reporting because it carries the main environmental and workforce impacts of the project, but is not included in the statutory accounts perimeter. - We bring the included entities together using full consolidation for controlled businesses and a share-based approach for jointly controlled arrangements; minority holdings are reflected through adjustments so the group totals do not overstate our share. - When businesses are bought or sold, we include them from the date we gain control and stop including them from the date control ends, so the reporting set changes in step with mergers, acquisitions, and disposals. - We use one consolidation method for the disclosures in this standard, but for some material topics we widen the boundary to capture significant impacts in entities we do not fully control, such as major contractors on our project sites.
Illustrative only: shows a second plausible perimeter with a different mix of entities, a different gap to the financial reporting set, and a different way of explaining topic-level boundary choices.
How companies report GRI 2-2 in practice
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Scenarios to work through
A group has a parent company, two wholly owned subsidiaries, and one joint venture that is not fully controlled. The finance team’s year-end pack includes all four entities, but the sustainability team has only drafted content for the parent and the two subsidiaries.
A group bought a business in October and sold another in March. The sustainability data team has used the full-year figures from the acquired business but has left out the sold business entirely because it was not owned at year end.
A group has a 70% owned operating company and a 30% owned associate. The sustainability team has included 100% of the operating company’s emissions and 30% of the associate’s, but no one has written down whether the minority share was adjusted in the process.
A group reports on climate, workforce, and community topics. For climate, it uses one consolidation method across all entities; for workforce data, it uses a different method because one acquired business has incomplete legacy records; and for community spend, it uses a third approach for a joint operation.
Related framework references
How this disclosure maps across the major reporting frameworks.
Questions this page answers
The page says to prepare a reporting entity list, a note on boundary differences, minority interest treatment, transaction boundary changes, the disclosure-specific method, and the topic-level consolidation method. Use that as your starting checklist before you draft anything.
Use it as a working sequence to move from scoping and ownership through to evidence and draft output. The page is designed to help you prepare the disclosure, not just describe it.
The page flags a reporting entity list as a required datapoint to prepare, so you should compile the entities in scope for the disclosure and keep that list consistent with the rest of your boundary notes. The page does not add any extra rules beyond that.
The page tells you to prepare a boundary differences note, so you should record where the disclosure boundary differs from other reporting boundaries and keep that explanation available for review. It is meant to support clarity and assurance readiness.
The page lists minority interest treatment as a datapoint to prepare, so you should document how minority interests are handled in the disclosure and keep that treatment consistent in your working papers. The page does not define the treatment for you.
The page says to prepare transaction boundary changes, so you should note any changes that affect the boundary used for the disclosure and keep a clear record of what changed and when. That helps with traceability and later assurance checks.
The page is set up for practitioners to assign ownership as part of preparation, so the practical approach is to name the data owner, the drafter, and the reviewer early. The page does not prescribe a specific role structure.
The page includes an evidence pack with five items for assurance readiness, so you should assemble those materials alongside the disclosure draft and keep them easy to trace. It is intended to support review, not replace it.
The page says there are four assurance claims to verify, each with a claim, risk and evidence prompt. Use those prompts to check that the disclosure is supported before it goes to review.
The page lists common reporting gaps and mistakes, so it is worth checking your draft against that list before sign-off. In practice, use it as a final quality-control step to catch missing scope notes, weak methodology or incomplete evidence.
The examples are synthetic and are there to show how a finished disclosure might look, including a quantitative table where relevant. Use them as a drafting reference only, and make sure any numbers in your own report are internally consistent.
Get your GRI 2-2 tools — free
Your preparation tools are free for LRA Community members and students. Register once (it's free) and your download starts right away — plus the Disclosure Library, templates and the LRA AI-assistant.
You're in — your download is starting
Your file is downloading now. Your Community Cabinet — with the Disclosure Library, templates and the LRA AI-assistant — is ready too.
Open your Cabinet →