- Supports ESRS 2 disclosure mapping for IRO-1, IRO-2, and SBM-3 after the materiality assessment.
"Disclosure Requirements in ESRS covered"
A source-grounded workflow for running an ESRS double materiality assessment across impacts, risks, opportunities, stakeholders, and the value chain.
Use it to structure the IRO register, materiality scoring, governance review, disclosure mapping, and evidence pack for assurance.
Structured answer sets in this page tree.
Cited legal and guidance references.
Under ESRS, the sustainability statement starts with a assessment. The undertaking identifies material impacts, risks, and opportunities from the impact-materiality and financial-materiality perspectives, including relevant upstream and downstream value-chain connections. ESRS sets criteria but no universal threshold or mandatory process. This workflow is an implementation method for sustainability, finance, risk, legal, procurement, and internal audit teams, not an official form.
Start by defining the reporting undertaking, consolidation perimeter, business model, geographies, activities, products, services, and value-chain segments that the assessment will cover. ESRS value-chain information is not a request to document every supplier or customer; it is a requirement to include material upstream and downstream information where it is needed to understand material impacts, risks, and opportunities.
Create a source register before scoring begins. It should include ESRS 1 and ESRS 2 references, the EFRAG materiality and value-chain guidance used by the team, previous sustainability assessments, due diligence outputs, enterprise risk materials, stakeholder engagement evidence, and any sector or country data used for value-chain estimates.
Build the candidate IRO list from the undertaking's actual business context, not from a generic topic checklist. Use ESRS sustainability matters, prior assessments, due diligence findings, enterprise risk registers, incidents, complaints, workforce and community engagement, supplier information, customer-use information, regulatory changes, and sector/geography exposure to identify where IROs may arise.
For value-chain IROs, record where the matter may arise: own operations, upstream suppliers, materials and services, distribution, customer use, end-of-life, financing, or other business relationships. If primary value-chain data is unavailable after reasonable effort, ESRS allows estimates based on reasonable and supportable information available without undue cost or effort. Record the proxies, sector averages, indirect sources, assumptions, accuracy limits, and planned accuracy improvements.
Score each candidate matter for impact materiality and financial materiality before consolidating the result. A matter can be material from the impact perspective, the financial perspective, or both. Treat the two dimensions as connected but not interchangeable.
For impact materiality, assess negative impacts by severity and, for potential negative impacts, likelihood. Severity is based on scale, scope, and irremediable character; for a potential negative human-rights impact, severity takes precedence over likelihood. For financial materiality, record likelihood and potential magnitude of effects on development, financial position, financial performance, cash flows, access to finance, or cost of capital. Thresholds may be qualitative, quantitative, or mixed, but the undertaking must set and explain them from the ESRS criteria and its facts.
Before governance approval, run a challenge session on the IRO register. Test whether the assessment reflects the undertaking's activities, business relationships, affected stakeholders, geographies, and products rather than only the easiest data sources.
Challenge questions should focus on completeness and supportability: which affected stakeholder groups were considered, how existing engagement or due-diligence processes informed the assessment, which credible proxies or scientific sources were used, which value-chain estimates rely on sector averages, and whether missing data could change the conclusion. ESRS does not require direct engagement with every stakeholder for every matter.
Use the workflow to connect ESRS source requirements, IRO scoring, stakeholder evidence, value-chain assumptions, governance approval, and assurance records before the sustainability statement is finalised.
The approval gate should confirm the material IRO list, the thresholds and methodology used, changes from the prior period, and the ESRS disclosure requirements covered by the sustainability statement. Approval should not be a broad sign-off on a slide deck; it should be tied to named records that can be updated, reviewed, and challenged.
After approval, map each material matter to the relevant ESRS topical disclosure requirements, ESRS 2 IRO-1, ESRS 2 SBM-3, ESRS 2 IRO-2, and any policies, actions, targets, or metrics required because the matter is material. If climate change is assessed as not material, ESRS requires a more detailed explanation than for other omitted topical standards.
Close the workflow by preserving the record of how the assessment was performed, not just the final matrix. EFRAG guidance notes that documentation can support governance of sustainability reporting and help assurance providers understand the materiality assessment process and results.
The audit trail should be versioned and reproducible. A reviewer should be able to see the source used, the evidence collected, the judgement applied, the stakeholder or value-chain limitation, the owner who approved the conclusion, and the disclosure consequence.
"Disclosure Requirements in ESRS covered"
"These documents are non-authoritative and support implementation."
"If the undertaking concludes that climate change is not material"
"General Requirements for Sustainability Assurance Engagements"