TNFD Reporting Checklist and Free LEAP Deliverables Pack

Early TNFD teams often collect useful information in workshop slides, emails and external spreadsheets that cannot support a public report. A deliverables pack creates a common structure for cross-functional teams and technical reviewers. It also prevents the reporting team from writing claims that the assessment work did not actually support.

The pack contains seven core tools. The scoping sheet sets the reporting boundary and project assumptions. The location register records assets, activities, geographies, ecosystems and priority-location criteria. The dependency and impact register captures the organisation’s interface with ecosystem services and pressures on nature.

The risk and opportunity register converts dependencies and impacts into business consequences, responses and residual risk. The metrics matrix links metrics to DIROs, methods, boundaries and data quality. The evidence register creates traceability between claims and records. The disclosure checklist maps outputs to the TNFD pillars, general requirements and limitation wording.

Scoping comes before LEAP and prevents the project from becoming too broad or too vague. Locate is supported primarily by the location register. Evaluate is supported by the dependency and impact register. Assess is supported by the risk and opportunity register. Prepare is supported by the metrics matrix, evidence register and disclosure checklist.

The workflow should be iterative. A new risk may reveal a missing dependency; a metric may reveal a location gap; a reviewer may ask for a stronger evidence source. The controlled adjustment log captures these changes so that the published report is consistent with the underlying assessment.

Figure 1. TNFD Checklist to Evidence Workflow. Branded LRA visual; illustrative, not an official TNFD diagram.

The scoping sheet should name the reporting entity, business units, geographies, direct operations, value-chain areas, reporting period, TNFD objective, materiality lens and known exclusions. It should also identify the project owner, reviewers and decision gates.

The most important field is not the list of included activities; it is the reason for inclusion or exclusion. A value-chain tier may be excluded because it is out of scope for year one, because no data are available, because it was screened and judged not material, or because it will be addressed under another framework. Those are different conclusions and should not be blended.

Each register should be maintained as a controlled working document. Rows should have unique IDs, owners, source references, review status and links to related rows. For example, a dependency in the dependency and impact register should link to one or more locations and one or more risk or opportunity records.

The evidence register is the release gate. Before publication, every significant claim should have at least one evidence record and a review status. Where evidence is incomplete, the disclosure should use limitation wording rather than silently presenting a complete answer.

Figure 2. TNFD LEAP Deliverables Pack Architecture. Branded LRA visual; use with the article caption and source note.

The pack does not write the report automatically. It gives the reporting team a defensible basis for drafting. A strong drafting sequence is: confirm scope, summarise governance, describe priority locations, explain DIRO pathways, present metrics and limitations, map to TNFD recommended disclosures, and add an expansion roadmap.

The pack should be archived with the report version. Next year, the team should roll forward the registers, update evidence, close resolved gaps and document changes in scope, methods and claims.