This disclosure asks an organisation to explain the greenhouse gas removals it can credibly point to across its value chain, rather than only within its own direct operations. In practice, the focus is on whether removals are being identified, measured and reported in a way that reflects the organisation’s wider business activities and relationships, not just a few selected projects or flagship sites.
The practical question is how complete and consistent the reporting is across the value chain. An organisation should make clear what removals are included, where they occur, and whether the coverage is broad enough to give a fair picture of the organisation’s overall position, rather than a narrow view based on isolated examples.
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 information to prepare
How to prepare it
Request removals and supporting evidence from carbon accounting
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Use your organisation’s own terms first, then map them to the reporting label. For example, if your team talks about carbon capture, sequestration, offsets, sinks, nature-based projects, or removals credits, keep those internal terms in the request and only translate them later for reporting. Adapt the wording to your own systems, project names, and approval process, and check the official source before sign-off.
Please provide the GHG removals disclosure data for the value chain, including the total Scope 1 removals, storage pool quality criteria, intended use, impacts on people and the environment, and the standards, methodologies, assumptions, and calculation tools used.
Why it fails: It uses framework language that many operational teams do not use day to day, so the owner may not know which records to pull. It also bundles several ideas without pointing to the source system, internal project names, or the exact files needed to evidence the figures and narrative.
Please send the removals pack for [period] from [system/project]. Include the total amount recorded, the project or activity type, how each type was checked for quality, what the business says the removals are for, any notes on people or environmental effects, and the method note, assumptions, and calculation file. Use your team’s own terms, then we will map them for reporting.
Notes that turn data into a disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
State the basis used to measure and calculate the removals, including the methods, assumptions, and tools applied, and explain how each storage pool was checked against the relevant quality criteria.
Explain what the reported total means in practice by linking the amount removed to the storage pools involved, the planned use of the removals, and the main effects on people and nature.
If the figures changed materially, describe whether the movement came from changes in storage pool mix, assessment outcomes, intended use, or the calculation approach and assumptions used.
Preparation tools & forms
Professional preparation tools for GRI 102-9 — 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 report 1,250 tCO2e of removals from our own land-based operations this year, all from one storage pool: 1,250 tCO2e in managed woodland, where we apply our internal site-selection and monitoring checks to confirm permanence, leakage control, and traceability. The removals are intended to support our near-term emissions reduction plan and to balance a small share of residual operational emissions, while we also note the wider effects of the activity on people and the environment: no material harm was identified for workers, nearby communities, or Indigenous Peoples, and our habitat surveys found a net positive effect on biodiversity. We used a mix of field measurements, remote sensing, and carbon-accounting software, together with our own assumptions on growth rates, mortality, and discounting, to calculate the figure.
Illustrative only: shows how to describe the amount removed, the storage type and quality checks, what the removals are for, and the main social and environmental effects, plus the methods and tools used.
During the reporting year, we recorded 420 tCO2e of removals linked to our own Scope 1 activities, split across two storage pools: 300 tCO2e in biochar-amended soils and 120 tCO2e in a mineralised aggregate store, with each pool assessed against our quality checks for durability, monitoring frequency, and evidence of long-term containment. We plan to use these removals to offset a portion of residual process emissions and to support our transition plan, and we reviewed the wider consequences for people and nature: the work created no identified adverse effect on workers, local communities, or Indigenous Peoples, while biodiversity impacts were limited to short-term disturbance at one site and were managed through restoration actions. Our calculation relied on site sampling, supplier records, emission factors, and spreadsheet-based models, with assumptions on moisture content, conversion rates, and loss allowances.
Illustrative only: shows a second plausible reporter with different storage pools and a different mix of intended use, impacts, and calculation approach.
How companies report GRI 102-9 in practice
Examples of full and partial reporting practice. These are evidence-led reviews, not exact disclosure templates to copy.

Scenarios to work through
Your team has measured 12,400 tCO2e of carbon removals from supplier-led land projects linked to your operations. Some of those removals are still in a temporary storage stage, and the sustainability draft currently gives only the total figure.
A forestry supplier says its project stores carbon in two pools: living biomass and harvested wood products. The project manager has different evidence for each pool, but the draft report currently uses one generic sentence for both.
Your company plans to use 8,000 tCO2e of removals from a restoration project to support a future net-zero claim, but the project team has not agreed whether the removals are for internal balancing, external claims, or another purpose. The draft report also omits any discussion of local land-use effects.
A draft prepared by the technical team says the removals were calculated using a proprietary model, but it does not say which assumptions were built into the model or which checks were used to test the result. The same draft also mentions possible effects on nearby communities and habitat, but only in a footnote.
Relevant GRI requirements and related disclosures
Available framework references and nearby disclosures relevant to preparing this requirement.
Questions this page answers
Use the page’s plain-language explainer and the step-by-step ‘how to prepare’ section to turn the disclosure into a working plan. Start by identifying the datapoints to prepare, then build the evidence pack and draft output from there.
The page says to prepare six datapoints: Scope 1 removals total, storage quality criteria, removal use plan, direct impact summary, people impact detail, nature impact detail, and calculation basis. Treat these as the core inputs for the disclosure and check that each one is supported by evidence.
The page is aimed at sustainability/ESG managers, HR or data owners, and assurance reviewers, so ownership should sit with the people who can evidence the datapoints and explain the methodology. Use the step-by-step preparation section to assign responsibilities before drafting.
The page includes an evidence pack with five items for assurance readiness. Build it around the datapoints, the calculation basis, and the supporting records needed to show how the figures and impact statements were prepared.
The page says there are six assurance claims to verify, each with a claim, risk, and evidence angle. Use them to test whether the disclosure is complete, consistent, and backed by documents before it goes to review.
The page lists common reporting gaps and mistakes so you can check for missing datapoints, weak methodology, or unsupported narrative. Use that list as a pre-submission quality check against your draft and evidence pack.
The Download Centre includes a Prep & Assurance workbook in .xlsx format. Use it to organise the datapoints, evidence, and assurance checks before turning the information into a draft disclosure.
The Download Centre also includes a printable Library Card in .pdf format. It is there as a practical companion to the page content, so you can keep the disclosure requirements, datapoints, and checks in one place while preparing the draft.
Yes. The page includes synthetic illustrative example disclosures, including a quantitative table, which you can use as a model for structure and level of detail, not as a real-world template.
The draft-output section gives visualisation ideas, narrative starters, and a GRI content-index line. Use those prompts to convert your prepared data and evidence into a first draft that is easy to review and trace back to source records.
Get your GRI 102-9 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 →