This disclosure asks an organisation to explain whether, and how, its activities have changed the condition of biodiversity in the places where it operates or influences nature. The focus is on reporting the actual change observed or reasonably linked to the organisation, rather than simply describing policies, intentions, or general environmental commitments.
In practice, the organisation should look across the parts of its business that can affect biodiversity and consider the full range of relevant sites and activities, not only a few showcase locations. The report should make clear where the changes are happening, what kind of biodiversity state has changed, and whether the organisation is covering its main operational footprint or only selected assets.
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 site biodiversity change data from EHS / site teams
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Use your organisation’s own site, land, habitat, ecology, or environmental management terms first, then map them to the reporting disclosure. Keep the request in the language your EHS, estates, or site teams already use, rather than using framework labels in the first instance.
Please provide the biodiversity disclosure data for the reporting period.
Why it fails: This is too broad and uses framework language without telling the owner which sites, which measures, or which supporting notes are needed. It is hard to action, hard to trace back to source records, and likely to trigger a partial or inconsistent response.
Please send the site-level extract for the locations your team ranks as having the biggest biodiversity impact, for [period]. For each site, include the habitat or ecosystem type, the base-year area in hectares, the base-year condition, the current condition, and a short note on the method, assumptions, and source records used. Please use your normal site and ecology terms, then add a simple mapping note if needed.
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 sites were included, how the affected habitats were identified, what counts as the starting-year baseline, and the standards, methods and assumptions used to compile the figures.
Set out what the site ranking, habitat type, area in hectares and condition ratings are intended to show, so readers can understand the scale, location and state of the affected ecosystems.
Describe any notable movement in habitat condition between the baseline year and the current period, and note the operational, environmental or data-related reasons behind those changes.
Preparation tools & forms
Professional preparation tools for GRI 101-7 — 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.
*Synthetic illustration only.* We identified the two locations where our operations are most likely to affect nature: our coastal ingredients site and our inland packaging plant. For the base year, the first site sat within **120 ha** of **coastal wetland**, recorded as **fair** condition; by the current period, the same area was assessed as **slightly improved** after drainage controls and habitat buffers were put in place. - The second site covered **85 ha** of **mixed farmland edge**, starting from **moderate** condition in the base year and moving to **moderate-to-good** in the current period. - We compiled the figures using site boundary maps, field surveys, and a simple condition scoring method applied consistently across both periods; where exact ecological boundaries were not available, we used the operational land parcel as the proxy and kept the same assumptions year on year.
This example shows how a reporter can name the main locations driving nature impact, describe the habitat type and area at the starting point, compare condition then and now, and explain the method used to build the numbers.
*Synthetic illustration only.* Our two most significant nature-sensitive locations are the upland turbine cluster and the river-crossing cable corridor. In the base year, the turbine cluster occupied **240 ha** of **heathland and rough grassland**, assessed as **good**; in the current reporting period, it remained **good** after ongoing access management and seasonal restoration work. - The cable corridor covered **36 ha** of **riparian woodland and riverbank habitat** in the base year, with a **poor-to-fair** condition rating then and a **fair** rating now. - We prepared the data from GIS site footprints, ecological walkovers, and a condition rubric aligned to our internal biodiversity procedure; the area totals reflect the full operational footprint, while the condition ratings reflect the habitat within that footprint that we could inspect directly.
This example demonstrates a second plausible sector using different sites and habitat types, while still giving the starting area, the starting and current condition, and a clear note on the data sources and assumptions.
How companies report GRI 101-7
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Scenarios to work through
A manufacturing group has three sites near sensitive habitats, but only one factory has the clearest link to habitat change this year. The team has base-year habitat notes for that factory, plus a current-year field survey showing the area and condition have shifted.
A utility company has mapped a wetland area as 18.4 ha in the base year, but the latest survey shows 17.9 ha after a boundary correction. The preparer is unsure whether to replace the earlier figure or keep the original base-year number.
A food producer uses satellite imagery, consultant surveys, and internal site walkovers to compile the biodiversity note. The methods do not all line up perfectly, and the team has also made a few judgement calls about habitat boundaries and condition scoring.
A mining group has one site where land disturbance is obvious, but another site has a smaller footprint and a more sensitive habitat. The reporting team is debating whether to list both sites or only the one with the largest area change.
Related framework references
How this disclosure maps across the major reporting frameworks.
Questions this page answers
The page says to prepare six datapoints: key biodiversity sites, affected ecosystem type, base-year ecosystem area, base-year condition, current ecosystem condition, and compilation notes. Use those as the starting checklist before you draft anything.
The page’s plain-language explainer and step-by-step preparation section are the place to start, and the key biodiversity sites datapoint is the main scoping input. The guidance is meant to help you decide what to include and document that choice in the compilation notes.
The page includes compilation notes as one of the required datapoints to prepare, so use them to record how the figures and descriptions were assembled. That helps make the disclosure easier to review and explain later.
The page is aimed at sustainability/ESG managers, HR or data owners, and assurance reviewers, so ownership should sit with the person or team that can gather the site and ecosystem data and keep the evidence together. The page does not assign a single mandatory owner, so you need to set that internally.
The page says there is an evidence pack with five items for assurance readiness, and it also lists six assurance claims to verify using claim, risk, and evidence. Use those materials to build a file that shows where each datapoint came from and how it was checked.
The page includes a section on common reporting gaps and mistakes, so it is designed to help you spot issues before you finalise the draft. A practical use is to compare your own draft against that list and fix any missing or inconsistent datapoints.
The Download Centre includes a Prep & Assurance workbook in .xlsx format and a printable Library Card in .pdf format. Use the workbook to organise the preparation and assurance checks, and the PDF if you want a quick reference copy.
Yes — the page has a draft-output section with visualisation ideas, narrative starters, and a GRI content-index line. That gives you a practical route from the prepared datapoints to a first draft.
The page includes synthetic illustrative example disclosures, including a quantitative table, to show how the disclosure might look. You should use it as a model for structure and presentation, not as real company data.
Yes — the page notes a closest correspondence with ESRS E4 (Biodiversity and Ecosystems). You can reuse the underlying data across both, but the page does not say the reporting requirements are identical.
Get your GRI 101-7 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 →