TNFD Assurance Readiness: Evidence, Controls and Greenwashing Risks

Figure 1. Define the assurance subject matter.

TNFD is a voluntary risk-management and disclosure framework. “Assure our TNFD report” is not a sufficiently precise engagement description because a report can include recommendations, entity methodologies, forward-looking models, estimates, external datasets and claims that require different procedures. Assurance readiness should begin before drafting the assurance statement.

ISSA 5000 is a framework-neutral sustainability assurance standard designed for sustainability information across topics and frameworks. It supports limited and reasonable assurance. It does not make TNFD assurance compulsory; it provides a professional framework where assurance is undertaken.

DIRO process. Evidence that dependencies, impacts, risks and opportunities were identified, prioritised and approved using the stated process.

Locations. Coordinates, site/portfolio populations, sensitive-location definitions, spatial methods and validation.

Models and tools. Versions, inputs, assumptions, limitations, overlays, overrides and change approval.

Metrics. Definitions, units, populations, calculations, estimates, reconciliations and changes.

Targets. Baseline, scope, period, dependencies, progress and revisions; activity is not automatically outcome.

Claims. “Nature positive”, “restored”, “no impact”, “net gain”, “aligned” and “verified” need precise support.

Governance and connections. Board oversight, risk integration, financial effects and cross-report consistency require operating evidence.

A strong file retains the activity and location population, tool versions, evidence considered, stakeholder inputs, decision criteria, challenge records, exclusions and approvals. Where an issue was screened out, the file explains whether it was absent, not significant, outside the boundary or insufficiently evidenced. Geospatial evidence records coordinate source, geometry, dataset version, join method, buffer rationale, resolution, false-positive risks and local validation.

Each metric needs a controlled definition, boundary, unit, population, formula, source lineage, estimate method, reconciliation, owner, reviewer and prior-period treatment. Each target needs a baseline, target period, approval, dependencies, planned actions, progress calculation and explanation of adverse performance. Models require purpose, owner, version, input controls, sensitivity, validation, management overlays and approved use.

A correct activity metric can support a misleading claim if the boundary is omitted, a pilot is described as portfolio-wide performance, avoided harm is called restoration, or a screening score is presented as measured impact. A claim ledger should link each sensitive statement to its definition, boundary, period, method, evidence, limitation and approval.

Weeks 1-2. Define subject matter, criteria, boundary, intended level and exclusions.

Weeks 2-4. Map every disclosure and high-risk claim to evidence, owner, method, control and report location.

Weeks 4-7. Reperform calculations, trace locations, review models, test baselines and challenge claims.

Weeks 7-9. Correct errors, narrow unsupported claims and document estimates and limitations.

Weeks 10-12. Lock versions, obtain management representations, complete governance approval and prepare provider access.

An asset manager proposes to describe a thematic fund as “nature positive” because most holdings pass a biodiversity-screening threshold and several investees have restoration projects. A readiness review finds that the threshold measures exposure, not net outcomes; the portfolio boundary excludes some instruments; restoration data covers only a few holdings; and negative impacts are not assessed. The manager changes the wording to describe screening, engagement and allocation, reports coverage and limitations, and postpones the outcome claim.

Scope drift. The report, evidence matrix and assurance wording describe different populations.

Uncontrolled location file. Coordinates changed after screening without change history or re-performance.

Screenshot as evidence. Inputs, version, settings and transformations are unavailable.

Target without baseline control. The baseline changed but progress and comparatives did not.

Policy described as performance. The narrative implies effectiveness without outcome evidence.

Ambiguous “verified”. Internal review is presented as external assurance.

Figure 2. Show five claim gates.

Prerequisite: TNFD Explained - Recommendations, LEAP, DIROs and how to start.

Apply next: TNFD LEAP Approach - a step-by-step guide.

Evidence: Geospatial Data for TNFD - coordinates, maps, data quality and confidentiality.

Advanced: TNFD metrics, targets and the limits of composite biodiversity scores.