This disclosure asks an organisation to identify which of its operational sites are located in, next to, or otherwise associated with protected areas or other places recognised for high biodiversity value. The focus is on the organisation’s footprint across its operations, not just a few well-known or flagship sites, so the report should reflect the full set of relevant locations it controls or uses.
In practice, the organisation should explain where these sites are, how many there are, and how they relate to the protected or high-value area concerned. The key point is to show the extent of operational exposure to sensitive biodiversity locations, so readers can understand whether the issue is limited to a small number of sites or spread across a wider part of the business.
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 site and biodiversity location 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, land and environmental terms first, then map them to the reporting categories. Ask for the records the operational owner already keeps for site registers, land files, GIS layers, permits or environmental reviews, rather than using framework wording in the first ask.
Please provide the protected-area disclosure data for GRI 304-1, including all sites adjacent to protected areas and all biodiversity-value locations, with the required attributes.
Why it fails: This uses framework language that many operational teams do not use day to day, so it is easy to misread or answer inconsistently. It also does not point the owner to the records they already hold, the internal site terms they use, or the exact site-level details needed to build the extract.
Please send the site register extract for [reporting period] for [business unit / portfolio], covering any sites in or near environmentally sensitive areas. Use your normal site, land and map terms first, then we will map them for reporting. For each site, include the internal site ID, location, ownership or control basis, size, activity type, relationship to the sensitive area, any subsurface land, the sensitive-area description used in your records, and the source file or system.
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 organisation defined a relevant site, and what basis was used to decide whether a place counted as protected or biodiversity-sensitive.
Set out what the figures show about the organisation’s footprint in or near sensitive natural areas, including where those sites are, what kind of operations they host, and how large they are.
If the number or mix of sites changed, note whether this was driven by site openings, closures, changes in control, updated mapping, or a revised view of which locations meet the inclusion criteria.
Preparation tools & forms
Professional preparation tools for GRI 304-1 — 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 would describe the sites we operate, lease or manage that sit in, or next to, protected land or other places recognised for high ecological value. In this example, our portfolio includes 3 operational sites: one 12 ha wind farm in Scotland, 2 km from a designated nature reserve; one 8 ha battery storage site in Wales, partly within a locally important wildlife corridor; and one 5 ha substation in England, adjacent to a protected wetland. We would also note any below-ground land under our control, such as 1.5 ha of underground cable routes beneath the wind farm and 0.4 ha beneath the substation, and explain the relevant conservation feature for each location, including the protected designation or other biodiversity attribute that makes the area sensitive.
Illustrative only: shows how to identify relevant sites, state where they are, describe the operation and site size, and explain both the conservation feature and any formal protection status without using a tabular format.
*Synthetic illustration only.* Our group would report the facilities we own and manage that are inside, beside, or close to areas valued for biodiversity. In this example, we have 2 operational sites: a 20 ha processing plant in northern Italy, 500 m from a protected riverbank habitat, and a 6 ha packaging depot in southern Spain, partly overlapping a high-value coastal dune area. We would also disclose the underground land we manage, such as 2.0 ha of buried service corridors at the plant and 0.2 ha of drainage works at the depot, together with the ecological feature that defines each area and whether it carries a formal protected listing.
Illustrative only: shows how a reporter can combine site location, operational footprint, below-ground land, proximity or overlap with sensitive habitat, and the reason the area is considered important for biodiversity.
How companies report GRI 304-1
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Scenarios to work through
A logistics depot sits 300 metres from a wetland reserve boundary, and the company also leases a small underground cable corridor beneath the same plot. The site team is unsure whether the reserve’s status and the depot’s exact position need to be captured together.
A quarry is partly on land owned by the business and partly on land it leases from a third party. The boundary touches a conservation area, but the operations team has only mapped the surface footprint so far.
A processing plant is not inside a protected area, but it is next to a habitat recognised locally for high biodiversity value. The environmental manager has the habitat name and the plant size, but not the legal protection category.
A manufacturing site is managed by the company under a long-term contract, and a small underground service tunnel extends beyond the fenced boundary. The site is 1.8 hectares and sits beside a bird nesting area outside any formal reserve.
Related framework references
How this disclosure maps across the major reporting frameworks.
Questions this page answers
Start with the plain-language explainer, then work through the step-by-step preparation section and the datapoints to prepare. The page also gives narrative starters and a draft GRI content-index line to help turn the collected data into a first draft.
The page says to prepare eight datapoints: protected site footprint, site location, underground land rights, area relationship, operation type, site area size, biodiversity attribute, and protection status. Use those as your minimum data checklist before drafting.
Use the page’s preparation section and datapoints to decide which sites and land relationships are in scope, then capture the site-level details needed for the disclosure. The page is designed to help you define the reporting boundary before you write the narrative.
The page does not assign roles, but it is set up for a sustainability or ESG manager, HR or data owner, and assurance reviewer to use together. In practice, ownership should sit with whoever can confirm the site data, evidence, and final draft are complete.
The page includes an evidence pack with five items to support assurance readiness. Use it alongside the six assurance claims to verify that the claim, risk, and evidence are aligned before review.
The page lists common reporting gaps and mistakes to help you avoid weak or incomplete disclosures. A practical use is to check your draft against those gaps before you finalise the evidence pack and narrative.
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 card as a quick reference while drafting.
Yes, as a drafting aid only: the page includes synthetic illustrative examples and a quantitative table to show how a disclosure can be structured. Keep the numbers internally consistent and replace the example content with your own site data.
The draft-output section gives visualisation ideas, narrative starters, and a GRI content-index line. Use those to convert the prepared datapoints into a short explanation of what was reported and where the supporting information sits.
Start with the six assurance claims and verify each one against the stated risk and evidence. Then check the evidence pack and the common reporting gaps to see whether the draft is supportable and complete.
The page says the closest ESRS correspondence is ESRS E4 (Biodiversity and Ecosystems), so the same site data may be reusable for that work. It does not say the requirements are identical, so you would still need to check the ESRS reporting needs separately.
Get your GRI 304-1 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 →