ESRS E4 and TNFD screen the same locations, but one is EU law and one is voluntary.
If your company reports under the EU’s sustainability rules, biodiversity is no longer optional. ESRS E4 (the European Sustainability Reporting Standard on Biodiversity and Ecosystems) is the mandatory nature standard under the Corporate Sustainability Reporting Directive, the EU law that requires large companies to report on sustainability. The Taskforce on Nature-related Financial Disclosures (TNFD) is the voluntary framework most teams reach for to actually do the work. TNFD is the recommended method; ESRS E4 is the legal requirement.
The useful news for a reporting team is that these two are not separate projects. The EU standard names TNFD’s assessment method as a tool you may use, and both turn on the same question: where are your sites, and are they in or near protected or otherwise sensitive areas. So the location work you do for one produces evidence for the other.
But the fit is not total, and the places it stops matter. This piece walks three things: where the method and the location screen line up, where the two frameworks define “sensitive” differently, and what a reporter actually does with the overlap.
- On TNFD vs ESRS E4: ESRS E4 is EU law under the CSRD, and TNFD is the voluntary method most teams use to do the work. The EU standard even names TNFD’s LEAP approach as a tool you may use.
- The two ask almost the same location question, but their materiality tests differ: ESRS E4 requires double materiality, while TNFD runs from a financial baseline and treats impact reporting as optional.
- The catch is the word “sensitive.” E4’s biodiversity-sensitive areas are a narrower list of designations, a subset of TNFD’s broader five-criteria set.
- The payoff: one asset-level location screen produces evidence for both, as long as you respect where the two definitions of “sensitive” part ways. It is the location spine, not the whole E4 assessment.
One is EU law, the other is voluntary, and E4 names TNFD’s method
The starting difference is legal force. ESRS E4 is binding. It is Annex 1 to Commission Delegated Regulation (EU) 2023/2772 and applies to financial years from 1 January 2024. TNFD is a voluntary, market-led framework. A company chooses to use it; no regulator requires it.
Despite that, the EU standard points to TNFD’s method by name. TNFD built the LEAP approach (Locate, Evaluate, Assess, Prepare), a four-step way to find and assess nature-related issues. The joint EFRAG-TNFD correspondence document, published by the two bodies together in June 2024, states that “the LEAP approach is mentioned in the ESRS as a tool that organisations may consider using when conducting a materiality assessment on environmental subtopics (other than climate change)”. In plain terms: the EU standard tells you that you may use TNFD’s method to work out what is material to report. The Application Requirements of the four environmental ESRS say so directly, and LEAP “has been specifically designed to be consistent with the impact materiality lens used in the ESRS and the financial materiality lens used by both the ISSB and the ESRS”. In plain terms: TNFD built its method to slot into the EU’s test, not to compete with it.
One version note, because it changes over the next reporting cycles. The text above is the 2023 standard, which is the one in force. There is a later EFRAG draft, dated November 2025, that feeds a revision of the ESRS mandated by the “Omnibus” simplification law (Directive (EU) 2026/470, targeting financial year 2027). That draft is not yet adopted. It moves the LEAP reference out of the topical E4 text and into the general standard, ESRS 1, where LEAP is kept as a non-mandatory reference that EFRAG retained, in its own words, “to ensure interoperability with TNFD”. In plain terms: the EU cut a lot in the simplification, but it deliberately kept the bridge to TNFD. For a report you file today, use the 2023 text; the direction of travel keeps the TNFD tie either way.
| Dimension | TNFD | ESRS E4 |
|---|---|---|
| Legal force | Voluntary, market-led | Mandatory, EU law under the CSRD |
| Materiality | Financial baseline; accommodates double materiality | Double materiality required (financial and impact) |
| “Sensitive” definition | Five functional criteria | A narrower designation list (a subset of TNFD’s) |
| Scope | Own operations plus value chain | Own operations; value-chain sites voluntary |
| Method | The LEAP approach | Names LEAP as an optional tool you may use |
The materiality tests differ, and the screen sits inside both
“Materiality” is the test a framework uses to decide what is worth reporting. The two frameworks apply different tests, and this is the real divergence.
ESRS uses double materiality. ESRS 1, the general standard, “defines the concept of double materiality as the basis for sustainability disclosures,” with “two dimensions: financial materiality and impact materiality”. In plain terms: an EU reporter has to consider both how nature affects the business and how the business affects nature. TNFD runs from a different baseline. It asks preparers to report “consistent with meeting the material information needs of capital providers as a baseline, consistent with the ISSB and the TCFD,” and treats the impact lens as an add-on preparers use “should they need or choose to do so”. The correspondence document puts it plainly: TNFD “accommodates use of a double materiality approach” but, “rather than prescribing a particular approach to materiality,” it “enables the use of different materiality approaches”. In plain terms: TNFD’s default is the financial question; ESRS requires both.
That difference could make E4 sound like a bigger, separate exercise. Here is the part that keeps the location work shared. Whatever the materiality outcome, a company still has to find its sites near sensitive areas in order to decide whether biodiversity is material at all. The site screen is part of the identification process (in ESRS terms, the IRO-1 process for identifying impacts, risks, dependencies and opportunities) that you must run to reach a materiality conclusion. In plain terms: even though the specific line-item disclosure is only required if biodiversity turns out to be material, the location screen that gets you to that answer is not optional. TNFD says the same thing from its side: it “strongly recommends, irrespective of the approach to materiality taken by the report preparer, the identification and assessment of all four types of nature-related issues”. Both frameworks make you locate first.
(One caution for anyone carrying habits over from climate reporting: the “rebuttable presumption” that forces a detailed explanation if you claim climate is not material is specific to the climate standard, ESRS E1. E4 does not carry it.)
Both ask the same location question, but E4’s “sensitive areas” is the narrower set
This is where the frameworks converge, and where they quietly diverge. Getting both right is the point of the piece.
The convergence is the method and the screen. TNFD’s LEAP starts with Locate: “locate your interface with nature,” working through your operations and value chain to find, in step L4, which sites are “in ecologically sensitive locations”. ESRS E4 has the same localisation step in its Application Requirement AR 7, which is why the two map cleanly at that level. At the disclosure level, TNFD’s Strategy Disclosure D, which asks a company to “disclose the locations of assets and/or activities… that meet the criteria for priority locations”, corresponds in the joint mapping to ESRS 2 IRO-1 (ESRS E2, E3, E4). On the E4 side that lands on two disclosures: the material-sites disclosure (SBM-3, paragraph 16(a)), which asks for a list of material sites and the biodiversity-sensitive areas they affect; and the identification-process disclosure (IRO-1, paragraphs 17 and 19), which includes the “in or near” screen. Same locate-your-sites question, asked by both.
The divergence is in the word “sensitive,” and the correspondence document is explicit about it. TNFD’s “sensitive locations” is a broad, five-part functional set: areas important for biodiversity; areas of high ecosystem integrity; areas of rapid decline in ecosystem integrity; areas of high physical water risks; and areas important for ecosystem-service provision, including benefits to Indigenous Peoples, Local Communities and stakeholders. ESRS defines “biodiversity-sensitive areas” more narrowly, as a specific list of designations: the Natura 2000 network, UNESCO World Heritage sites, Key Biodiversity Areas, and other protected areas. The joint document states the relationship directly: ESRS “use a different definition of sensitive areas with respect to TNFD, which corresponds to a subset of the TNFD’s definition (for what relates to ‘Areas important for biodiversity’)”. In plain terms: E4’s protected-area list is one slice of TNFD’s wider set, not the whole thing.
Two more differences sit alongside it, both named in the mapping. TNFD’s “priority locations” bundles material and sensitive locations together; ESRS asks instead for a list of “material sites”. And TNFD asks you to look across your upstream and downstream value chain, while ESRS requires the list for your own operations, treating value-chain sites as voluntary. So the overlap is real but bounded: same method, same core protected-area screen, different breadth and different scope.
The same screening data answers both
This is the practical payoff. The location question is answered with location data, and one asset-level screen produces evidence usable on both sides.
Continuuiti’s Biodiversity and Land Use / Land Cover (LULC) analysis runs on a site’s coordinates and returns exactly the location facts both frameworks ask for. Here is how the screen maps onto the criteria, and where it stops.
| Criterion (TNFD / the E4 protected-area limb) | What the location screen provides | Bound |
|---|---|---|
| Areas important for biodiversity / E4 “biodiversity-sensitive areas” | Protected-area proximity from the World Database on Protected Areas (WDPA): inside, within 20 km, or none nearby, with the site’s protection category | Global protected-area layer. No distinct Key Biodiversity Area, UNESCO World Heritage, Natura 2000, or species layer |
| High ecosystem integrity | RESOLVE Ecoregions context and conservation priority | Ecological context, not an intactness score |
| Rapid decline in ecosystem integrity | Hansen Global Forest Change deforestation and LULC land-cover change | A proxy via tree-cover and land-cover loss, not a full integrity measure |
| High physical water risks | Basin-level water stress from WRI Aqueduct | Screening-level, basin scale |
| Ecosystem-service provision (IPLC) | Not a native output | Needs stakeholder and field assessment; in ESRS the people and rights side maps primarily to the social standard S3, though E4’s own identification process references community consultation |
The WDPA is the global register of protected areas; RESOLVE divides the world into 846 ecoregions; Hansen Global Forest Change tracks annual tree-cover loss; WRI Aqueduct is the World Resources Institute’s water-risk dataset. Because only one of the five criteria needs to be met for a location to count as sensitive under TNFD, a screen that answers four of them settles most sites quickly. The screen also feeds the E4 metric side: TNFD’s spatial-footprint and ecosystem-change metrics correspond to E4-5 paragraph 38, and ESRS says preparers “can use the TNFD metrics, if relevant”.
Free Nature Risk Report
Screen your supplier locations for nature and deforestation risk
Free land-cover change, deforestation exposure, and protected-area proximity for any site. No call required.
Where the shared screen stops
A location screen is a location screen. It is worth being exact about the four things it does not do, because E4 asks for all of them.
First, impact causation, not just proximity. E4’s sensitive-area datapoint asks whether activities “negatively affect these areas by leading to the deterioration of natural habitats”. That is a judgment about whether your activity harms the area. A proximity flag and a land-cover-change layer are evidence toward that judgment, not the judgment itself. This is also where the two frameworks point in different directions: E4’s sensitive-area datapoints are framed on your impact on the area (E4’s wider identification process also assesses dependencies, but the site datapoints themselves are impact-worded), while our screen and TNFD’s Locate step are about where you sit and what you depend on. The location data is shared; the conclusion each framework draws from it is not the same.
Second, the named designation sets. We screen protected-area proximity globally through WDPA, which is the largest limb of the E4 definition (“other protected areas”). We do not hold separate Key Biodiversity Area, UNESCO World Heritage, or Natura 2000 layers. Natura 2000 in particular is an EU-specific designation; WDPA catalogs many such sites as protected areas, but our screen is not a designation-complete Natura 2000 or KBA check. State the global protected-area coverage with confidence; confirm the named EU designations separately.
Third, ecosystem condition and dependency. Our screen measures the extent of nature and a site’s proximity to it, not the condition of an ecosystem or the value of the ecosystem services a business depends on. Those are the deeper Evaluate questions.
Fourth, the metrics beyond location. E4 also asks for anticipated financial effects and for land-degradation and soil-sealing metrics. Those are downstream of a location screen, not produced by one.
So the bounded position: the screen is the data spine for the Locate step and the location side of both frameworks. It is strongest on the protected-area and land-cover criteria, and it is not the whole E4 assessment.
What a reporter does with both
The workflow that falls out of this is straightforward. Run one asset-level location screen across your sites. Use the output as shared evidence: it answers TNFD’s priority-location question and feeds ESRS E4’s identification of material sites in or near biodiversity-sensitive areas, from the same coordinates, hectares and maps. Then route each framework to its own treatment. Under E4, the sites feed the double-materiality assessment and the E4 disclosures once biodiversity is material. Under TNFD, the same sites feed Strategy Disclosure D and the risk assessment, where you ask how a dependency or impact at that location could affect the business.
You do the location work once. Because the EU standard names TNFD’s method and shares its core screen, the same evidence carries into a voluntary TNFD report and a mandatory E4 filing, as long as you respect where the two definitions of “sensitive” part ways.
For the mechanics behind this, the TNFD framework overview covers the four pillars and where materiality lands, and the LEAP approach walkthrough covers Locate and Evaluate in detail. The companion piece on TNFD and GRI 101 covers the impact-reporting neighbour. For the deforestation and land-use screening behind the criteria above, see the related EUDR, TNFD and EUDR, and land use and land cover coverage.
Frequently asked questions
Does ESRS E4 replace TNFD, or the other way round?
Neither. ESRS E4 is the mandatory EU requirement; TNFD is a voluntary method many companies use to meet it. The EU standard names TNFD’s LEAP approach as a tool you may use for your materiality assessment, and the two bodies published a joint mapping showing all 14 TNFD recommended disclosures are addressed by the ESRS.
If I use TNFD or LEAP, have I satisfied ESRS E4?
Not automatically. LEAP is a method the ESRS says you may use; E4 is the legal disclosure requirement. LEAP helps you locate sites and identify what is material, but E4 also asks for impact conclusions, specific metrics and financial effects that a location method alone does not produce.
Is ESRS E4’s ‘biodiversity-sensitive areas’ the same as TNFD’s sensitive locations?
No. E4’s definition is a narrower list of designations: the Natura 2000 network, UNESCO World Heritage sites, Key Biodiversity Areas, and other protected areas. The joint EFRAG-TNFD mapping describes it as a subset of TNFD’s broader five-criteria set. A TNFD sensitive location may not be an E4 biodiversity-sensitive area, and vice versa.
Do you screen Natura 2000 sites?
We screen protected-area proximity globally through the World Database on Protected Areas, which includes many Natura 2000 sites as protected-area records. We do not run a separate, designation-complete Natura 2000 layer, so a Natura 2000-specific check should be confirmed separately.
Can I do the location work once for both TNFD and ESRS E4?
Yes, for the location side. One asset-level screen answers TNFD’s priority-location question and feeds ESRS E4’s identification of material sites in or near biodiversity-sensitive areas, from the same coordinates and maps. You then route each framework to its own treatment, and confirm the named EU designations and impact conclusions E4 asks for beyond the screen.
