- Supports the lane structure because ESRS reporting is based on material impacts, risks, opportunities, disclosure requirements, and datapoints.
"Disclosure Requirement consists of one or more distinct datapoints"
A practical workflow for preparing evidence behind the CSRD sustainability statement before assurance review.
Use it to connect each ESRS disclosure to scope evidence, materiality rationale, data ownership, control support, estimate logic, and digital-tagging checks.
Structured answer sets in this page tree.
Cited legal and guidance references.
Under the CSRD framework, sustainability information prepared under ESRS is subject to assurance and published with the related assurance report. The evidence pack should therefore be built as a reporting file: every material topic, omitted topic, metric, policy, action, target, estimate, and digital tag needs a traceable owner and support.
Open the evidence pack by identifying the reporting undertaking, whether the file supports an individual sustainability statement, a consolidated sustainability statement, or a third-country sustainability report, and which management-report or annual-financial-report process will publish it.
Then record the assurance provider route for the jurisdiction: statutory auditor, audit firm, or independent assurance services provider where the Member State allows one. Keep this separate from ordinary independent review because the CSRD assurance opinion addresses compliance of the sustainability reporting with the Directive, ESRS, the undertaking's process to identify reported information, digital mark-up, and Article 8 Taxonomy reporting where relevant.
Organise the pack around conclusions, not around teams. A reviewer should be able to open a material topic or datapoint and see why it is in the sustainability statement, where the data came from, what control checked it, and how the final wording or number was approved.
Use the same structure for omitted topics. ESRS lets undertakings omit non-material topical disclosures, with special explanation expectations for climate change. The evidence file should preserve the materiality assessment result, the inputs considered, and the reason the omission is supportable.
Use this workflow to organise ESRS disclosure evidence, materiality judgements, data controls, value-chain estimates, and digital-tagging checks before the assurance request list arrives.
Assurance delays usually come from judgement-heavy areas: double materiality thresholds, group and value-chain boundaries, estimates where direct value-chain data is not available, omissions, restatements, and public wording that is broader than the underlying evidence.
For each judgement, keep the short conclusion next to the basis. The pack should show the evidence considered, alternatives rejected, how consistency was checked across entities or business units, and whether the conclusion changes a disclosure, metric, target, or omission.
Do not leave digital tagging until after the sustainability statement is drafted. CSRD implementation materials describe digital format and mark-up as part of the reporting and assurance context, so the evidence pack should preserve how each reported ESRS item maps to the sustainability statement text, table, metric, and tag candidate.
For narrative disclosures, keep enough context for the tag reviewer to identify the exact passage being tagged. For metrics and semi-narrative items, keep the unit, period, consolidation boundary, dimensional breakdown, and any calculation support together with the final wording.
The final workflow step is a readiness review, not a legal sign-off. The review should test whether an assurance provider can trace every selected disclosure from ESRS requirement to management judgement, source data, control evidence, approved statement text, and digital-tagging review.
Keep the close-out record concise: open items, waived items, management judgements, late changes, control exceptions, and the owner for post-publication improvements. That record helps avoid rebuilding the same evidence trail in the next reporting cycle.
"Disclosure Requirement consists of one or more distinct datapoints"
"data gap analysis or data collection exercise"
"supporting narrative open text"
"compliance with the requirement to mark up sustainability reporting"
"Compatible with Any Suitable Reporting Framework/Standard"