This disclosure asks an organisation to report the metrics it uses to show how its activities are affecting biodiversity over time. In practice, that means explaining the measures it tracks, the period covered, and the main changes observed, so readers can understand whether biodiversity conditions are improving, worsening, or staying broadly stable as a result of the organisation’s actions and impacts.
The practical focus is on whether the reporting covers the organisation’s full footprint or only selected locations, such as flagship sites or areas with the most significant impacts. It should be clear how representative the metrics are, what parts of the business they include, and where there are gaps or limitations in coverage, so users can judge the reliability and scope of the information.
This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official EFRAG 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 Operations
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Use your organisation’s own site, asset, project and environmental monitoring terms first, then map them to the reporting labels. Keep the request in the language your operations, environment or land teams already use, rather than using framework wording.
Please provide the ESRS E4:E4-5 biodiversity change metrics, including sites affected, geographic locations, area names, area types, activities, impact types, ecosystem condition, species indicators, drivers of change, primary data, remote sensing, baseline, monitoring frequency, time series, aggregation level, grouping logic, land degradation and threatened species flags.
Why it fails: It uses framework labels as the ask, which can be hard for operational teams to interpret and may not match how the data is stored. It also reads like a checklist of reporting terms rather than a practical request for the records, evidence and source fields the owner can actually pull together.
Please send the biodiversity change records for [reporting period] for the sites and project areas you manage. For each one, include the site name, location, area class, activity underway, what changed, why it changed, any species or habitat notes, the monitoring source, whether the data came from field work or imagery, the baseline, the monitoring cadence, the dates in the series, and any flags you use for degraded land or threatened species. Attach the supporting files or links and use your team’s own terminology where that is clearer.
Notes that turn data into a disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
State how the reporter defined the affected locations, the area categories used, the activity and impact groupings, the indicators selected for ecosystems and species, the drivers considered, and whether each figure was built from direct source data or other inputs.
Explain what the figures say about where the business is affecting nature, which kinds of operations are linked to those effects, and how the condition of habitats, species and ecosystem services is changing in the places covered.
If any measure moves materially, link the change to shifts in the underlying drivers, the mix of activities, the condition of the sites, or differences in the data used, and note whether the movement reflects a real change or a change in coverage or method.
Preparation tools & forms
Professional preparation tools for E4-5 — 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 summarise the main nature-related pressures linked to our own operations and nearby supply-chain sites, using a mix of field checks and external habitat records. - Sites touched: 3 production or storage sites in Spain, Poland and Brazil; 2 of these are inside or next to sensitive nature areas. - Named areas: Doñana National Park buffer zone (protected area), Biebrza Valley bird area (key biodiversity area), and Cerrado remnant grassland (high conservation value area). - Main activities and effects: water abstraction, wastewater discharge and land clearing; the effects shown are habitat loss, disturbance and reduced water quality. - Measured outcomes: 42 ha of habitat affected; habitat quality index fell from 0.78 to 0.71; 4 indicator species were tracked, with 2 showing decline. Main change drivers were land conversion, altered water flow and pollution; species status was assessed as stable for 1, declining for 2 and unknown for 1. Ecosystem size/quality changed by -6% in the mapped area, and two ecosystem services were assessed as weakened (pollination and flood buffering). - Data basis: primary field data were used for all three sites, supported by satellite imagery and local surveys.
This synthetic example shows how a reporter can describe the sites, the nature areas involved, the business activities causing pressure, and the observed ecological effects in plain language. It also shows how to include change drivers, species and ecosystem condition, and whether the assessment relied on primary data.
We report the nature-related effects of our wind and grid works by site, using site surveys, camera traps and habitat mapping. - Sites touched: 4 project sites in Scotland, Romania and South Africa; 3 are close to or partly within sensitive nature areas. - Named areas: Cairngorms edge peatland (protected area), Danube floodplain wet meadow (key biodiversity area), and Eastern Cape coastal thicket (important biodiversity site). - Main activities and effects: turbine installation, access-road building and cable trenching; the effects recorded were vegetation removal, soil disturbance and bird collision risk. - Measured outcomes: 18 ha of habitat affected; 12 ha temporarily disturbed and 6 ha permanently converted; vegetation cover in the survey plots moved from 64% to 58%. We tracked 5 species indicators, with 3 showing lower abundance and 2 remaining broadly unchanged. The main change drivers were ground disturbance, fragmentation and collision risk; species condition was judged as 3 declining and 2 stable. Ecosystem size/quality changed by -9% in the mapped footprint, and three ecosystem services were assessed as reduced: carbon storage, water regulation and recreation. - Data basis: primary data were used for all four sites, with no reliance on secondary estimates for the headline figures.
This synthetic example shows a different sector using the same disclosure logic: identify the affected sites and nature areas, explain the activities and the type of pressure created, then quantify the ecological effects. It also demonstrates how to present species and ecosystem findings, plus whether the figures came from primary data.
How companies report E4-5 in practice
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Scenarios to work through
A forestry group has three managed blocks in one reporting year: two are inside a designated nature site and one is outside it. The sustainability team has site maps, the local area names, and notes that harvesting, road maintenance, and drainage work took place in different blocks.
A mining business tracks habitat condition around one site using field surveys, drone imagery, and a baseline taken two years ago. The team also has a separate species survey showing fewer nesting pairs of a bird that is considered sensitive in the area.
A food producer monitors land around a supplier cluster every quarter, but only has full field data for one year and satellite checks for the earlier periods. The team wants to present one combined figure for the whole cluster because the sites are close together and managed under one contract.
An infrastructure company has a project corridor that crosses degraded grassland and passes near a habitat known to support a threatened animal. The team is unsure whether to mention land degradation and threatened species separately because the same project caused both concerns.
Related framework references
How this disclosure maps across the major reporting frameworks.
Questions this page answers
Start with the page’s plain-language explainer and the datapoints to prepare, then work through the step-by-step preparation section. The page is designed to help you collect the right site, ecosystem, species, trend and methodology information before you draft.
The page lists affected sites, location details, area name, area classification, relevant activities, impact type, impact measures, ecosystem status, species measures, change drivers, species condition, habitat change, nature services, and the reporting level/grouping rule. Use that list as your starting point for scoping the disclosure.
The page includes a reporting level and grouping rule datapoint, so the practical task is to define how you will roll up site information before drafting. Use the step-by-step preparation section to keep the scope consistent across the affected sites you include.
The page has an evidence pack with five items and also lists six assurance claims to verify using claim, risk and evidence. Build your file so each key datapoint can be traced back to supporting records and the assurance claims can be checked quickly.
The Download Centre provides a Prep & Assurance workbook in .xlsx format and a printable Library Card in .pdf format. Use the workbook to organise the datapoints and evidence, and the Library Card as a quick reference while you prepare the draft.
The page includes a section on common reporting gaps and mistakes, so use that as a checklist before you finalise anything. It is especially useful for catching missing site details, weak evidence, or inconsistent treatment of trends and measures.
The page has a draft-output section with visualisation ideas, narrative starters and a content-index line. Use those prompts to turn your collected datapoints into a clear draft rather than starting from a blank page.
The page includes synthetic illustrative example disclosures, including a quantitative table, to show how the disclosure can look in practice. Treat it as a formatting and structuring aid only, and keep any real reporting internally consistent with your own data.
Those are all listed datapoints on the page, so you should decide and document how each site is evidenced and how often it is monitored. The page’s preparation section and evidence pack are the places to align those choices before drafting.
The page has a ‘From company reports’ table that links to real published reports at the pages where the topic is disclosed. Use it to see how others present similar information, but keep your own draft based on the page’s datapoints and examples.
Get your E4-5 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 →