Short answer
The answer, before the reasoning
The most common TNFD reporting mistakes are not usually typographical; they are logic failures. Reports become weak when they copy climate disclosure processes without location specificity, describe “nature risk” generically, skip dependencies and impacts, rely on tool scores as conclusions, use universal buffers or composite footprints without explanation, omit material value-chain interfaces, or make unsupported “nature-positive” claims.
The fix is to rebuild each disclosure from a traceable chain: activity and location, dependency or impact, change in nature, business consequence, metric, control, limitation and next action.
Quick orientation
Quick orientation
- Applies to
- Report preparers, reviewers, consultants, assurance-readiness teams and organisations improving early TNFD drafts.
- Primary decision
- Which weaknesses should be fixed before publication, and how to evidence the correction.
- Key sources
- TNFD Recommendations; TNFD Disclosure Recommendations page; LEAP approach; Getting Started guidance; TNFD Status Report.
- Common confusion
- A software output, heatmap or footprint can support judgement, but it does not replace DIRO logic or disclosure evidence.
Why this question matters
Nature disclosure is newer than climate disclosure for many reporting teams, so mistakes often come from reusing familiar templates. TNFD deliberately aligns with the four-pillar structure of TCFD and ISSB-style reporting, but nature-related assessment needs additional features: priority locations, dependencies and impacts, ecosystem-service logic, stakeholder engagement and value-chain granularity. A report that ignores these features may look tidy but provide little decision-useful information.
Mistake 1: copying climate processes without adapting for nature
Climate reporting processes are a useful starting point for governance, risk management, controls and report production. They are not a complete nature process. Nature-related issues are often more location-specific, more dependent on ecosystems and value chains, and more exposed to stakeholder and rights considerations.
The fix is to reuse climate-reporting infrastructure only where it fits: committee calendars, data controls, internal sign-off, risk taxonomies and scenario governance. Then add nature-specific capabilities: location register, ecosystem-service dependencies, impact drivers, priority-location criteria, stakeholder engagement evidence and nature metrics.
Mistake 2: generic nature risk
A statement such as “nature loss could affect our operations” rarely helps users. It does not identify the activity, location, ecosystem service, pressure, pathway, consequence or response. Generic nature risk is often a symptom that the team has not completed the Locate and Evaluate logic before drafting.
The fix is to write from the interface with nature. For example, a beverage company may depend on groundwater availability and water quality in specific catchments; a construction materials company may affect habitats through quarrying and land disturbance; a bank may have exposures to borrowers whose revenues depend on land conversion-sensitive commodities.
Figure 1. TNFD DIRO Logic Chain QA. Branded LRA visual; illustrative, not an official TNFD diagram.
Mistake 3: missing dependencies and impacts
Some reports jump straight to risks and opportunities because that feels closest to financial reporting. TNFD is built around dependencies, impacts, risks and opportunities. Dependencies and impacts are not optional decoration; they explain why a risk or opportunity exists.
A good reviewer test is: if the risk were challenged, could the organisation explain which dependency or impact created the pathway? If not, the risk disclosure is probably too weak.
Mistake 4: tool-score reliance
Tools such as sector maps, biodiversity datasets, location-screening tools and footprints can be valuable. The mistake is to treat the score as the conclusion. A tool may indicate potential exposure, but the organisation must still test its own activities, locations, controls, data quality, operational facts and materiality.
The correction record should show which tools were used, what they were used for, their limitations, which internal evidence confirmed or challenged the results, and who approved the final judgement.
Figure 2. TNFD Mistakes Diagnostic Map. Branded LRA visual; use with the article caption and source note.
Mistake 5: universal buffers and composite footprints
Universal radius buffers can be useful for a first screen, but they may overstate or understate nature interfaces depending on species, water basins, migration corridors, pollution pathways and ecosystem connectivity. Composite biodiversity footprints can also hide which pressure, ecosystem or location drives the result.
The fix is not to abandon screening. It is to label screening as screening, disaggregate results where needed, and move material claims to evidence appropriate to the decision being made.
Mistake 6: incomplete value chain and unsupported nature-positive claims
Nature-related issues may be concentrated upstream or downstream rather than in direct operations. A report that covers office energy and owned facilities but ignores high-impact sourcing, financed exposures or product use may miss the main nature interface.
Unsupported “nature-positive” claims create particular risk. Such claims need clear scope, baseline, action, outcome evidence, time horizon, uncertainties, limits and avoidance of implying global nature recovery from local activities.
In practice
Practical implementation steps
| Step | Action | Owner / input — Output / control |
|---|---|---|
| 1 | Run a DIRO traceability test | Technical reviewer — Every risk/opportunity links to dependency/impact, location, evidence and owner. |
| 2 | Review location basis | Operations + geospatial owner — Priority-location criteria, maps and data-quality flags. |
| 3 | Separate screening from conclusion | Sustainability analytics — Tool outputs labelled as inputs, not final materiality decisions. |
| 4 | Challenge value-chain exclusions | Procurement, sales, investment or underwriting owners — Boundary memo distinguishing immaterial, not assessed and unavailable data. |
| 5 | Control claims | Legal + reporting owner — Nature-positive and alignment claims approved with evidence trail. |
Hypothetical scenario
Illustrative scenario - not model compliance wording
A mining group drafts a nature section saying all sites were screened with a global biodiversity tool and no material nature risks were identified. Review finds that one quarry is near a sensitive river system, water abstraction data were not checked, rehabilitation obligations were omitted and local community concerns were not reviewed. The corrected disclosure explains the screening tool as an input, adds site-level assessment, identifies a water-dependency and habitat-impact pathway, and states the remaining data limitations.
Illustrative only. It shows how the decision is made, not wording that can be copied or relied on.
In practice
Common mistakes and fixes
| Mistake | Why it matters | Fix |
|---|---|---|
| Climate-copying | Same structure but no nature-specific location or dependency/impact content | Add location register, ecosystem services and impact drivers. |
| No impacts/dependencies | Risk statements appear without causal pathway | Build DIRO register before drafting narrative. |
| Tool-score reliance | Heatmap score used as if it were materiality decision | Document tool role, limitation, internal evidence and review judgement. |
| Universal buffers | Same radius applied across all ecological questions | Use buffers as screening only and refine for relevant ecological pathway. |
| Composite footprints | Single number hides pressure or location drivers | Disaggregate where decision-useful and disclose limitations. |
| Unsupported nature-positive claim | Positive language without baseline or outcome evidence | Use factual action wording unless outcome evidence supports the claim. |
In practice
Myth versus reality
| Type | Text |
|---|---|
| Myth | If we have a biodiversity footprint, we have a TNFD disclosure. |
| Reality | A footprint can be one input. TNFD disclosure also needs scope, locations, DIRO logic, governance, risk management, metrics, targets and limitations. |
| Practical consequence | Do not publish the metric without explaining what it covers, what it excludes and how it informs decisions. |
Readiness
Reader checklist
- Does each nature risk name an activity and location?
- Does each risk/opportunity link to a dependency or impact?
- Are screening tools labelled as inputs, not conclusions?
- Are value-chain exclusions classified as immaterial, unavailable or not yet assessed?
- Are nature-positive claims supported by baseline and outcome evidence?
In practice
Related standards, indicators and next reading
| Related material | Relationship |
|---|---|
| TNFD DIROs Explained | Internal Knowledge Hub link candidate; final URL to be set in CMS. |
| TNFD LEAP Approach | Internal Knowledge Hub link candidate; final URL to be set in CMS. |
| TNFD Gap Assessment | Internal Knowledge Hub link candidate; final URL to be set in CMS. |
| Phased TNFD Adoption | Internal Knowledge Hub link candidate; final URL to be set in CMS. |
| TNFD Reporting Checklist | Internal Knowledge Hub link candidate; final URL to be set in CMS. |
Sources
Primary sources
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.
✓ LRA 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 · TNFD
ESG Reporting Full Stack
There is no standalone LRA course for this framework yet. The Full Stack programme covers the reporting system it sits in — materiality, data, drafting and assurance — with exercises on your own data.
Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.
