More than 620 organisations have committed to TNFD-aligned reporting. Most are discovering the same thing: the framework is harder to operationalise than it looks.
The problems are not usually the software itself. They are the assumptions organisations bring into implementation. Specifically around their own data, LEAP requirements, and what "TNFD-aligned" means under scrutiny.
This article breaks down the four most common failure points, and what teams can do differently.
Failure 1: Treating the data problem as external when it is mostly internal
The most common belief among organisations starting TNFD implementation is that they cannot proceed because the biodiversity data does not exist. This is largely a myth.
The TNFD's own co-chair has been direct on this point: the most pressing data gaps are typically inside the organisation, not outside it. The first constraint for most teams is knowing exactly where their direct operations are located and where their suppliers are interfacing with nature. Asset location data, specifically basic facility coordinates, is often the first bottleneck, particularly for financial institutions trying to assess financed portfolios.
Among LEAP pilot testers and those working to meet CSRD reporting requirements, the most pressing data gaps are most often inside their own organisation, not outside it. The gap is specifically around knowing where direct operations are located and where suppliers are interfacing with nature.
External nature data does have gaps, particularly for metrics on ecosystem condition and species extinction risk. Companies report difficulties assessing species extinction risk, ecosystem condition, and invasive species. Market data also remains fragmented, with Bloomberg, Goldman Sachs, and Net Purpose all tracking nature metrics differently. But this is separate from the internal data problem, and solving it first will not unblock an organisation that cannot geocode its own asset base.
What to do instead: Before evaluating any TNFD compliance software, audit your internal data. Can you produce a list of direct operational sites with GPS coordinates? Can you map your top 50 suppliers by spend and approximate location? If the answer to either is no, start there. Software cannot fix an internal data gap. It can only expose it.
Failure 2: Running LEAP as a linear checklist rather than an iterative assessment
Organisations that approach the LEAP approach as a one-time sequential exercise (locate, evaluate, assess, prepare) consistently produce shallow assessments that do not hold up to scrutiny.
EY's pilot testing of the TNFD framework across 70 financial institutions in Asia-Pacific found that key stumbling blocks included conducting LEAP at scale, the lack of spatial data for assets and ecosystem interaction data, and challenges in defining boundaries and aggregating results of the assessment.
The specific failure mode is scope definition. Teams often set the boundary of their LEAP assessment too narrowly, typically limited to Tier 1 suppliers and direct operations, and too early in the process, before they have enough information to know where the material risks actually sit. The result is an assessment that is technically complete but practically useless: it misses the risks that matter.
The TNFD is explicit that LEAP is iterative. A first-pass materiality screen should inform where to deepen the analysis. Most software implementations fail here because they are configured to produce a single output rather than support progressive refinement across assessment cycles.
What to do instead: Run a rapid hotspot screen first, using sector-level biodiversity sensitivity data, before committing to a full LEAP assessment. Let the hotspot results drive scope decisions. Then configure your software to support a staged approach: sector materiality first, then portfolio-level analysis, then site-level granularity for the highest-exposure assets.
Failure 3: Mapping nature risk without geospatial data
This is the most technically significant failure point, and the one most likely to produce disclosures that cannot survive external scrutiny.
Nature risk is inherently location-specific. A real estate asset in a water-stressed basin carries fundamentally different exposure than one in a region with abundant freshwater, even within the same sector and country. Software that assigns risk based on sector codes or national averages cannot distinguish between the two.
Nature-related disclosures require granular, spatially explicit data that is not easily captured through traditional reporting methods. The TNFD's LEAP approach depends on access to precise geospatial data across direct operations and value chains.
The problem compounds in supply chains. For most businesses, the greatest risks and impacts are hidden in Scope 3 supply chains. Tier 2 and Tier 3 supplier locations are rarely disclosed. Teams that rely on sector-level proxies for supply chain nature risk produce assessments that look complete in a dashboard but would not withstand a question from an informed investor about methodology.
The minimum geospatial requirement for a credible TNFD disclosure is: site-level assessment for direct operations and highest-spend suppliers, using authoritative datasets (WDPA for protected areas, IUCN for biodiversity, WRI Aqueduct for water risk), with clear documentation of where proxies were used and why.
What to do instead: Evaluate your TNFD compliance software specifically on its geospatial capability. Can it run an assessment from a latitude and longitude coordinate against real biodiversity datasets? If the platform's primary output is a sector-level score, treat it as a screening tool: useful for prioritisation, not sufficient for disclosure.
Failure 4: Materiality misalignment between ESG and finance teams
The final failure point is organisational rather than technical, but software choices either compound it or help resolve it.
TNFD requires organisations to assess material nature-related risks and opportunities, which means translating ecological exposure into financial impact language. This is where ESG and finance teams consistently diverge. ESG teams are comfortable with biodiversity metrics and ecosystem service dependencies. Finance teams want revenue-at-risk figures, asset impairment probabilities, and time-horizon-specific scenarios. Both perspectives are correct, and neither is sufficient alone.
Governance and risk management disclosures are relatively strong in early TNFD reports, reflecting areas where organisations find it easiest to integrate nature into existing frameworks. However, metrics, targets, and scenario analysis remain underdeveloped, highlighting the challenge of translating ambition into measurable performance.
The software failure that follows from this is choosing a platform that only one team can use. If the TNFD compliance software lives exclusively in the sustainability function and produces outputs that the risk committee cannot interpret, the implementation has failed, even if the disclosures are technically accurate.
What to do instead: Require your software to support both audiences. ESG teams need the LEAP workflow and ecological data. Finance teams need financial quantification of nature-related risks, ideally expressed in the same language as other risk categories in the enterprise risk register. Platforms that bridge this translation exist, though they are rare. If a vendor cannot demonstrate how their output connects to financial materiality thresholds during a demo, keep looking.
The pattern across all four failures
Looking at these failure points together, a pattern emerges. Organisations that struggle with TNFD compliance software implementation are almost always using tools designed for a different problem: climate disclosure, general ESG reporting, or regulatory compliance management, and trying to adapt them to nature risk assessment.
Most companies adapting TNFD rely on climate governance frameworks but lack nature-specific expertise. Many ESG teams are skilled in carbon accounting and TCFD alignment but underprepared for nature risk analysis.
Nature risk is not a harder version of climate risk. It is a different type of risk assessment entirely. It is location-specific, ecologically complex, and requires data integration that general ESG platforms were not architected to handle. The organisations getting this right are the ones that recognised this distinction early and chose tools built specifically for the problem.
Frequently asked questions
Why do companies struggle with TNFD compliance software?
The most common reasons are internal data gaps (missing asset location data), software that was built for climate or general ESG disclosure rather than nature risk specifically, and a disconnect between ecological outputs and financial materiality language. Technology is rarely the primary problem. Governance, internal data quality, and methodology understanding are more fundamental constraints.
What makes mapping nature risks hard without dedicated TNFD software?
Nature risk is inherently location-specific. The same sector exposure varies enormously depending on where an asset operates. Without geospatial capability that integrates authoritative biodiversity datasets (IUCN, WDPA, GBIF), risk mapping defaults to sector averages, which cannot produce credible TNFD disclosures. Manual GIS analysis is an alternative but takes months and does not scale across large portfolios.
How do biodiversity assessment platforms simplify TNFD materiality analysis?
Purpose-built platforms pre-integrate the scientific datasets that TNFD requires, automate the geospatial intersection of asset locations with biodiversity and ecosystem data, and provide structured workflows for each LEAP phase. This reduces a multi-month manual process to weeks. The more important simplification is methodological: good platforms guide teams through double materiality in a structured way, rather than leaving ESG teams to build the framework from scratch.
What is the best TNFD reporting platform for complex supply chains?
For complex supply chain assessment, the critical capabilities are: the ability to ingest supplier lists and assign nature risk at the entity or asset level, sector-level risk profiles for suppliers where precise location data is unavailable, and multi-tier supply chain support beyond Tier 1. Platforms that only assess direct operations are inadequate for organisations where material nature risk sits in upstream supply chains.
What are the leading nature risk mapping tools for TNFD alignment?
The most credible tools integrate IUCN Red List, WDPA protected area data, GBIF species occurrence data, ENCORE for dependency and impact mapping, and WRI Aqueduct for water risk. Platform quality varies significantly. The key differentiator is whether geospatial assessment is run at the site level against real datasets, or whether the output is a sector-level average dressed up as a location-specific score.
NatureRisk is built for TNFD and ESRS E4 from the ground up, covering the full LEAP workflow from geospatial asset mapping to boardroom-ready disclosure. Book a demo
