CSRD and ESRS reporting.

What the framework asks for

The Corporate Sustainability Reporting Directive requires in-scope companies to report against the European Sustainability Reporting Standards, in a defined format, subject to assurance, as part of the management report rather than as a separate document. The practical consequence is that sustainability information sits inside the same reporting infrastructure as the financial statements and is held to a comparable standard.

Scope, timing, and the detail of the requirements have been revised since the directive was introduced. Any engagement begins by confirming what currently applies to your organization, in your jurisdictions, on your timeline.

Double materiality assessment

The double materiality assessment determines what you actually have to report, which makes it the highest-leverage piece of the whole exercise. Done well, it narrows the scope to what matters and produces a defensible record of why everything else was excluded. Done poorly, it either balloons the reporting burden or leaves a gap that an assurance provider will find.

Both directions are assessed: impact materiality, meaning the organization's effects on people and the environment, and financial materiality, meaning the sustainability matters that affect the organization's own position and performance. A topic that is material in either direction is in scope.

• Value chain mapping, upstream and downstream, to establish where impacts actually sit
• Stakeholder identification and engagement, documented as evidence rather than as a workshop summary
• Impact, risk, and opportunity identification against the ESRS topical structure
• Scoring methodology with defined thresholds, applied consistently and written down
• Governance of the conclusions, including how the assessment was reviewed and approved
• A documented audit trail, since the assessment itself is subject to assurance

Gap analysis and data architecture

Once materiality determines the datapoints, the question becomes whether the organization can produce them. Usually the answer is partially. The gap analysis compares required disclosures against what currently exists, and separates the gaps that are a data collection problem from those that are a methodology problem or a governance problem, because the remediation differs.

The architecture work that follows is the part that determines whether year two is easier than year one: naming an owner for each datapoint, defining the source system or collection route, setting the calculation methodology, and establishing the review and approval path. Sustainability data typically arrives from operations, HR, procurement, and facilities, most of whom have never produced reportable information before, so the process design matters more than the technology.

Preparing the sustainability statement

The statement itself needs to be assembled, tagged, and reviewed alongside the rest of the management report. Practically that means linked data rather than copied numbers, a review workflow with real sign-off, and consistency between the narrative and the metrics. This is where a reporting platform earns its cost, particularly for groups producing the statement in multiple languages or across multiple entities.

Assurance readiness

CSRD disclosures are subject to assurance, which means an external party will ask how each number was produced and expect documentary evidence rather than explanation. Readiness is built during the process: methodology documented as it is decided, sources retained as they are collected, review evidenced as it happens. Reconstructing that after the fact is significantly more expensive than building it in.