Short answer
The answer, before the reasoning
GRI and TNFD can be supported by a substantially shared nature evidence base, especially for activities, value-chain exposure, locations, direct drivers of biodiversity loss, ecosystem condition, ecosystem services, policies, actions and targets. They do not, however, answer the same reporting question.
GRI centres on an organisation’s significant impacts on biodiversity and people. TNFD covers nature-related dependencies, impacts, risks and opportunities and asks how these issues affect governance, strategy, risk and impact management, metrics and targets. A combined project is efficient when it reuses evidence but preserves separate materiality tests, decision records and framework-specific disclosures.
ANSWER | EXPLAIN | APPLY | EVIDENCE | CONNECT | PUBLISH
Article map
This Knowledge Card gives a direct answer, explains the technical logic, shows how to apply it, identifies the evidence needed, and provides a controlled publishing package. Requirements, recommendations, implementation practice and expert interpretation are kept distinct.
In practice
| Stage | What the reader will get |
|---|---|
| 1 | Direct answer and why it matters |
| 2 | Technical explanation and distinctions |
| 3 | Practical method, mapping and examples |
| 4 | Common mistakes, myth correction and reviewer checklist |
| 5 | Related standards, source status and update triggers |
| 6 | Editorial, SEO, visual and CMS package |
Why the connection matters
Nature teams are often asked to prepare a GRI biodiversity disclosure, a TNFD-aligned report, lender responses and internal risk analysis from the same small pool of location and supplier data. If each request is treated as a separate project, teams repeatedly collect coordinates, land-use information, water dependencies, ecosystem condition data and policy evidence. If the projects are merged too aggressively, the organisation may imply that impact significance under GRI is identical to nature-related risk materiality under TNFD.
The practical solution is neither duplication nor equivalence. It is controlled interoperability: establish a common evidence architecture, document the GRI impact conclusion, document the TNFD dependency–impact–risk–opportunity pathway, and disclose the residual differences. This approach also improves internal decision-making because impact owners, risk owners, finance and nature specialists work from a reconciled view of activities and locations.
The joint GRI–TNFD interoperability mapping published in 2024 identifies extensive alignment. It also makes clear why mapping must be applied with judgement: all GRI 101 disclosures are reflected in the TNFD recommendations, but some TNFD requirements concern the identification and assessment of risks and opportunities rather than impact reporting alone.
In practice
Quick orientation
| Question | Practical answer |
|---|---|
| Can one location register support both? | Usually yes. Coordinates, activity type, ecosystem context and proximity to sensitive areas are highly reusable, provided precision, boundary and data-quality limitations are retained. |
| Does a complete GRI 101 disclosure automatically complete TNFD? | No. TNFD-specific work can still be needed on dependencies, risk and opportunity pathways, financial effects, time horizons, resilience and integration into risk management. |
| Must an organisation use LEAP to disclose under TNFD? | TNFD presents LEAP as optional guidance. Organisations may use an equivalent existing assessment process, but LEAP is a useful completeness check. |
| Is GRI 101 only about sites? | No. It addresses impacts in operations and the supply chain, including products and services with the most significant biodiversity impacts and location-specific information. |
| What is the central control? | Keep one evidence pool, but maintain distinct GRI and TNFD conclusions, responsible owners, approvals and disclosure gap logs. |
In practice
The source-grounded relationship
| Layer | What it means in practice |
|---|---|
| GRI requirement | Where biodiversity is a material topic, the organisation applies the relevant GRI 101 disclosures and reports how it manages the topic. GRI 101 includes disclosures on impact identification, locations, direct drivers, changes to the state of biodiversity and ecosystem services. |
| TNFD recommendation | TNFD provides 14 recommended disclosures organised around Governance, Strategy, Risk and impact management, and Metrics and targets, supported by general requirements. |
| TNFD guidance | LEAP — Locate, Evaluate, Assess and Prepare — is an optional, flexible and iterative assessment approach. It can be used as guidance or as a checklist against an existing process. |
| Interoperability guidance | The joint GRI–TNFD mapping supports controlled reuse and identifies strong alignment, but it is not a declaration that every criterion, materiality decision or disclosure is equivalent. |
| LRA implementation practice | Create a shared location-and-nature evidence model, then add a two-column decision trail: GRI impact significance and TNFD DIRO materiality, including residual data and disclosure gaps. |
1. Start with the different reporting objectives
GRI asks the organisation to report on its most significant impacts on the economy, environment and people, including human rights. In the biodiversity context, the core question is how the organisation’s activities, products, services and business relationships affect biodiversity, where those effects occur, how significant they are, and how the organisation manages them.
TNFD uses the connected language of dependencies, impacts, risks and opportunities — often shortened to DIROs. A dependency exists where the organisation relies on ecosystem services, such as water regulation, soil quality, pollination or flood protection. An impact is a change in the state of nature caused, contributed to or directly linked through the organisation’s activities and relationships. Risks and opportunities arise when dependencies and impacts interact with the organisation’s strategy, operations, markets, financing, reputation, regulation or other value drivers.
In practice
| Dimension | GRI-centred question | TNFD-centred question |
|---|---|---|
| Impact | Which biodiversity impacts are most significant, and how are they managed and reported? | Which impacts are material within the organisation’s chosen materiality approach, and how do they connect to strategy and risk management? |
| Dependency | Relevant when it helps explain the impact pathway, ecosystem services or management response. | A core assessment dimension: what ecosystem services does the organisation rely on, how critical are they and can they be substituted? |
| Risk | May be useful context but is not the basis for determining GRI material topics. | A core output: physical, transition and systemic nature-related risks, their time horizons and management. |
| Opportunity | May be reported as part of management actions or positive impacts where relevant. | A core output: opportunities associated with products, services, resource efficiency, restoration, financing or strategic positioning. |
| Primary users | Broad stakeholders seeking accountability for impacts. | Capital providers and other stakeholders using nature-related information for decision-making, depending on the reporting approach. |
2. What GRI 101 contributes to a TNFD evidence base
GRI 101: Biodiversity 2024 provides a particularly useful foundation because it moves biodiversity reporting towards activity-, value-chain- and location-specific evidence. Its disclosures can populate significant parts of a TNFD assessment, provided the organisation does not stop at the impact disclosure.
The joint mapping also reduces terminology friction. GRI 101 uses TNFD definitions for ecologically sensitive areas and refers to the Locate and Evaluate phases of LEAP. This does not make the standards identical; it makes it easier to use consistent location and ecosystem evidence.
Figure 1. A shared evidence pool can support two different reporting lenses. Reuse must preserve framework-specific materiality and disclosure decisions.
In practice
| GRI 101 disclosure | Reusable evidence | Residual TNFD work |
|---|---|---|
| 101-4 Identification of biodiversity impacts | Sites, products and services in the supply chain associated with the most significant actual and potential impacts; methods, assumptions, evidence and limitations. | Dependency pathways; risk and opportunity pathways; materiality test used for TNFD; financial effects and time horizons where applicable. |
| 101-5 Locations with biodiversity impacts | Precise site locations and information on proximity to ecologically sensitive areas; location characteristics and affected ecosystems. | TNFD priority or material location criteria; aggregation logic; risk exposure and strategic implications by geography. |
| 101-6 Direct drivers of biodiversity loss | Land and sea use change, exploitation of natural resources, climate change, pollution and invasive alien species, as applicable. | Translation of drivers into dependency and impact pathways, risk metrics, opportunity analysis and management integration. |
| 101-7 Changes to the state of biodiversity | Ecosystem extent and condition, species information and methods used to measure or estimate change. | Risk thresholds, resilience implications, scenarios, time horizons and business consequences where relevant. |
| 101-8 Ecosystem services | Ecosystem services affected or relied upon and beneficiaries affected by changes. | Criticality and substitutability of dependencies; transmission into operational, market, financing or strategic risk. |
| 101-1 to 101-3 Management disclosures | Policies, commitments, actions, targets and management of impacts. | TNFD governance, strategy, risk-management integration, resilience and opportunity disclosures beyond impact management. |
3. Why location-specific analysis is the bridge
Nature-related issues are highly location-dependent. A water-intensive plant may have modest effects in one catchment and severe effects in another. A supplier’s land conversion may intersect a Key Biodiversity Area even when the same commodity is sourced elsewhere without the same ecological sensitivity. Organisation-level totals can therefore obscure both significant impacts and business dependencies.
A combined location register should normally connect each site, supplier area or product-sourcing geography to: the activity conducted; geographic coordinates or an appropriate spatial boundary; ecosystem type and condition; proximity to ecologically sensitive areas; direct drivers; affected communities and other beneficiaries; ecosystem services relied upon; data source and date; confidence and limitations; and the GRI and TNFD decisions supported by the record.
In practice
| Location field | Why it matters for GRI | Why it matters for TNFD |
|---|---|---|
| Coordinates / polygon | Supports identification and disclosure of locations associated with significant impacts. | Supports Locate analysis, priority locations and concentration of exposure. |
| Activity and output | Connects the impact to the organisation’s operation, product, service or business relationship. | Supports dependency and risk pathways and sector-specific metrics. |
| Ecosystem condition | Helps assess the state of biodiversity and significance of change. | Supports dependency criticality, physical risk and resilience analysis. |
| Sensitive-area proximity | Supports GRI 101-5 and contextualises severity. | Supports priority-location criteria and heightened due-diligence attention. |
| People and beneficiaries | Shows who may be affected by changes to ecosystem services. | Supports social consequences, stakeholder analysis and transition risk. |
| Evidence confidence | Makes assumptions and limitations transparent. | Supports risk-model governance and the reliability of strategic conclusions. |
4. A combined workflow for nature teams
A single project can support both systems when it is designed around shared evidence and separate decisions. The sequence below is LRA implementation practice, not a mandatory process prescribed by either framework.
1. Set the governance and user needs. Confirm whether the output is a GRI report, a TNFD-aligned disclosure, internal risk analysis, lender response or a combined package. Assign impact, risk, finance, nature-data and approval roles.
2. Define the organisational and value-chain scope. Map activities, products, services, sites, suppliers and downstream relationships, including relevant time horizons.
3. Locate nature interfaces. Build the site and sourcing register, identify ecosystems and sensitive areas, and record data precision and limitations.
4. Evaluate dependencies and impacts. Identify ecosystem services relied upon, direct drivers, changes to nature, affected people and plausible impact pathways.
5. Apply the GRI significance test. Assess actual and potential impacts, determine the material topic and document the evidence, stakeholder input, thresholds and governance approval.
6. Translate dependencies and impacts into TNFD risks and opportunities. Identify transmission channels, existing controls, time horizons, scenarios and potential financial effects where relevant.
7. Prepare framework-specific outputs. Draft GRI 101 disclosures and TNFD recommended disclosures, then maintain a residual-gap register rather than using a one-to-one substitution assumption.
8. Reconcile, approve and monitor. Test consistency across statements, metrics and locations; retain the evidence trail; and update the assessment as conditions or data change.
Figure 2. A practical combined workflow. LEAP can guide the Locate, Evaluate, Assess and Prepare work, while GRI and TNFD conclusions remain separately controlled.
5. Where data can be reused — and where it cannot
Reuse is strongest at the factual and evidence level. It becomes weaker as the organisation moves from evidence to judgement and from judgement to a reporting conclusion. The same coordinate is usually the same coordinate; the same habitat-condition model can often be reused; the materiality conclusion and disclosure consequence may still differ.
In practice
| Information object | Reuse potential | Required control |
|---|---|---|
| Site and supplier location data | High | Retain precision, reporting boundary, date, source, geospatial method and confidentiality restrictions. |
| Activity, production and sourcing data | High | Reconcile units and period; link the activity to both impact and dependency pathways. |
| Direct-driver metrics | High to medium | Check whether the metric satisfies both GRI disclosure detail and TNFD metric definitions. |
| Ecosystem condition and species data | Medium to high | Preserve methodology, baseline, model uncertainty and spatial resolution. |
| Stakeholder and community evidence | Medium | Protect confidentiality; distinguish impact evidence from financial-risk assumptions. |
| Materiality conclusion | Low | Apply and document the relevant framework’s criteria and user needs separately. |
| Narrative disclosure | Low to medium | Draft for the specific disclosure; do not copy a GRI impact statement into a TNFD risk section without translation. |
6. Where the users’ information needs diverge
A broad stakeholder may want to understand the organisation’s accountability for ecosystem degradation and effects on local communities. A lender or investor may additionally ask how loss of water regulation, pollination or regulatory access could affect production, costs, asset values or strategy. The underlying story is connected, but the emphasis and evidence are not identical.
GRI normally needs a clear account of the significant impact, its location or value-chain connection, the organisation’s involvement and management response.
TNFD normally needs the dependency–impact–risk–opportunity chain, including governance, strategy, risk-management integration, metrics and targets, and material locations.
Impact evidence should not be reduced to a financial-risk proxy. Severe harm can be significant even where financial consequences are uncertain or long term.
Financial estimates should not be presented as ecological facts. Assumptions, models, time horizons and uncertainty need their own evidence and review.
A combined report should tell readers which materiality approach has been applied and avoid using “aligned” or “complete” claims without a disclosure-by-disclosure check.
In practice
Hypothetical case: ingredient sourcing and a wetland-adjacent site
| Element | Illustrative case |
|---|---|
| Organisation | A food ingredients group operates a processing site near a wetland and purchases cocoa through several tiers of suppliers in two countries. |
| Available evidence | Site coordinates, water abstraction, effluent data, habitat surveys, supplier-origin information for 70% of cocoa volume, community interviews and commodity-level deforestation risk data. |
| GRI impact conclusion | The site’s water and effluent pathway and selected cocoa-sourcing areas are assessed for significant actual and potential biodiversity impacts. The organisation identifies location-specific impacts and reports relevant GRI 101 disclosures, including data gaps for untraced cocoa. |
| TNFD dependency analysis | The processing site depends on freshwater supply and local water regulation; cocoa sourcing depends on soil fertility, rainfall regulation and ecosystem resilience. Criticality and substitutability are assessed. |
| TNFD risk / opportunity analysis | Potential risks include water restrictions, supplier disruption, compliance costs and loss of market access. Opportunities include supplier landscape programmes, water-efficiency investment and more resilient sourcing. |
| Shared evidence | Location register, water data, habitat condition, supplier-origin records, stakeholder evidence, direct-driver metrics and management actions. |
| Separate decisions | GRI material-topic approval and TNFD risk/opportunity materiality, time horizons, scenario assumptions and strategic implications are documented independently. |
| Limitations and next step | Supplier traceability is incomplete and ecosystem-condition data are uneven. The group discloses limitations, prioritises high-risk origins and expands geospatial and supplier verification. |
In practice
Illustrative combined basis-of-preparation wording
| Annotation | Why it matters |
|---|---|
| Common evidence register | Explains the reuse architecture without claiming one process produces identical conclusions. |
| Separate assessment purposes | Makes the GRI impact lens and TNFD DIRO lens visible to readers. |
| Evidence categories | Shows what supports the assessment rather than relying on generic “data analysis” language. |
| Coverage limitation | Quantifies the gap and explains the proxy used. |
| Improvement action | Connects uncertainty to a controlled next step. |
In practice
Weak versus stronger interoperability wording
| Weak wording / approach | Why it is weak | Stronger direction |
|---|---|---|
| “Our GRI 101 report is fully TNFD compliant.” | Neither framework provides a general shortcut by which completion of one automatically establishes full completion of the other. | “GRI 101 data were mapped to the TNFD recommendations; residual gaps on dependencies, risks, opportunities and financial effects were assessed separately.” |
| “The same materiality assessment was used for both.” | The statement hides potentially different criteria, users, time horizons and outputs. | Describe common inputs, then state the separate impact and DIRO tests and approval records. |
| “All sites were assessed for nature risk.” | No location method, spatial precision, priority criteria or limitation is given. | Specify the sites and value-chain areas screened, criteria, datasets, exclusions and how priority locations were selected. |
| “LEAP was completed, therefore TNFD is satisfied.” | LEAP is guidance and does not itself prove that all recommended disclosures are complete. | Use LEAP as an assessment trail and maintain a separate disclosure checklist against the 14 recommendations and general requirements. |
In practice
Common mistakes and corrections
| Mistake | Risk | Correction |
|---|---|---|
| Treating interoperability as equivalence | Creates an overclaim and can conceal missing TNFD risk, opportunity or strategy information. | Use a disclosure-by-disclosure mapping and maintain a residual-gap register. |
| Starting with organisation-wide totals | Masks location-specific impacts, dependencies and exposure. | Build the site, supplier and sourcing-location register first. |
| Ignoring dependencies | A strong GRI impact assessment may still leave the organisation unable to explain nature-related operational or strategic risk. | Identify ecosystem services, criticality, substitutability and transmission channels. |
| Using one undifferentiated materiality score | Averaging impact and financial factors can suppress severe impacts or exaggerate weak risk links. | Apply separate criteria and preserve the underlying evidence and rationale. |
| Treating LEAP as mandatory or mechanically linear | May create unnecessary process burden and false certainty. | Use LEAP flexibly and iteratively, or explain the equivalent assessment process used. |
| Publishing sensitive coordinates without review | Can create biodiversity, community, security or confidentiality risk. | Apply a controlled publication rule: precise internal data, proportionate public aggregation and documented justification. |
| No owner for residual gaps | Shared data are collected, but unresolved TNFD or GRI requirements remain unaddressed. | Assign each gap, deadline, evidence source and reviewer in the mapping register. |
Rule
Myth: “Once we have reported all relevant GRI 101 disclosures, our TNFD work is complete.”
Reality: GRI 101 supplies highly reusable impact and location evidence, and the joint mapping shows strong alignment. TNFD can still require additional analysis and disclosure on dependencies, risks, opportunities, financial effects, time horizons, resilience, strategy and risk-management integration. Why the confusion arises: The misconception arises because the same nature data appear in both systems and GRI 101 deliberately aligns terminology and location concepts with TNFD. Shared data do not remove framework-specific judgement or disclosure requirements.
Readiness
Reviewer checklist
- Have we stated the GRI and TNFD reporting objectives separately?
- Does the scope cover operations, relevant products and services, and material parts of the value chain?
- Can each reported location be traced to coordinates or an appropriate spatial boundary, activity, ecosystem context and data date?
- Have we identified both impacts on ecosystem services and dependencies on those services?
- Are actual and potential impacts assessed under the GRI significance logic?
- Are TNFD risks and opportunities linked to dependencies and impacts through explicit transmission pathways?
- Have we documented the materiality approach, time horizons and financial-effect assumptions used for TNFD?
- Does the mapping register identify reusable data, transformed data and residual gaps?
- Are sensitive location and stakeholder data protected while the public disclosure remains useful?
- Have impact, risk, finance, nature-data and governance reviewers approved the relevant conclusions?
- Does the final disclosure avoid unsupported claims of equivalence, compliance or completeness?
- Are update triggers defined for incidents, ecosystem change, supplier-location changes, new data and framework revisions?
In practice
Related standards and next steps
| Relationship | Reference | Practical use |
|---|---|---|
| Direct | GRI 101: Biodiversity 2024 | Primary disclosures on biodiversity impacts, locations, drivers, ecosystem state and services. |
| Supporting | GRI 3: Material Topics 2021 | Determining significant impacts and material topics. |
| Comparison / interoperability | TNFD Recommendations v1.0 | Nature-related governance, strategy, risk and impact management, metrics and targets. |
| Implementation | TNFD LEAP guidance | Optional Locate, Evaluate, Assess and Prepare approach for nature-related assessment. |
| Interoperability | GRI–TNFD interoperability mapping, 2024 | Disclosure-level alignment and residual differences. |
| Next step | GRI 101 location-specific evidence guide | Build a site and supply-chain location-data register. |
| Advanced | Nature dependencies, risk pathways and financial effects | Translate ecosystem services into risk, opportunity and strategy analysis. |
In this GRI–TNFD workflow, a priority location is a site or value-chain area selected for focused analysis because its activities, ecosystem context, dependencies, impacts or exposure meet the organisation’s stated priority criteria. Selection should consider location-specific evidence, including proximity to ecologically sensitive areas, and record the datasets, spatial precision, exclusions and limitations used.
Questions
Questions people ask
Does GRI 101 satisfy TNFD?
Reality: GRI 101 supplies highly reusable impact and location evidence, and the joint mapping shows strong alignment. TNFD can still require additional analysis and disclosure on dependencies, risks, opportunities, financial effects, time horizons, resilience, strategy and risk-management integration.
Is LEAP mandatory?
A single project can support both systems when it is designed around shared evidence and separate decisions. The sequence below is LRA implementation practice, not a mandatory process prescribed by either framework.
What nature data can be reused?
GRI and TNFD can be supported by a substantially shared nature evidence base, especially for activities, value-chain exposure, locations, direct drivers of biodiversity loss, ecosystem condition, ecosystem services, policies, actions and targets. They do not, however, answer the same reporting question.
How do GRI impacts differ from TNFD risks?
GRI centres on an organisation’s significant impacts on biodiversity and people. TNFD covers nature-related dependencies, impacts, risks and opportunities and asks how these issues affect governance, strategy, risk and impact management, metrics and targets.
What is a priority location?
In this GRI–TNFD workflow, a priority location is a site or value-chain area selected for focused analysis because its activities, ecosystem context, dependencies, impacts or exposure meet the organisation’s stated priority criteria. Selection should consider location-specific evidence, including proximity to ecologically sensitive areas, and record the datasets, spatial precision, exclusions and limitations used.
Take it with you
The checklists as a working spreadsheet
Every checklist and table on this page, with empty status, owner and evidence columns for your team to fill in and keep.
✓ Knowledge Hub AI Assistant · Human-in-the-loop
Ask about this guide
It answers from this page, and reaches into the linked disclosure cards when your question is about the standard itself. Your first two answers are free without signing in.
Go deeper · GRI
Certified GRI Standards Training
This page settles one disclosure. The GRI Standards Certified Training — two live days, taken as a bundle with an ESRS course — walks the whole cycle: material topics, datapoints, evidence, the Content Index and assurance readiness, with exercises on your own data.
Available as two live training days online or on-site in London, bundled with an ESRS course.
