DataSolmu blog
Show What Mitigation Changes in an Impact Assessment
Use timing and evidence to distinguish an environmental impact, an effective response and a future intention.
An environmental incident and the response to it are different facts. A containment measure may limit the harm, later restoration may address damage, and a planned improvement may reduce future exposure. Combining them into a single statement that an impact is "managed" can hide the reasoning behind a materiality decision.
EFRAG's May 2024 materiality assessment guidance distinguishes actual environmental impacts from potential ones and considers the timing of mitigation and remediation. For actual impacts, it recognises the effect of mitigation that worked before or during an event, while separating subsequent remediation and future actions from that assessment. It also cautions against dismissing a potential impact by assuming an unavailable future treatment will solve it.
This article explains that non-authoritative guidance for the 2023 ESRS. It does not determine the rules applicable to a later reporting period. The examples and evidence workflow are DataSolmu recommendations for reviewing environmental impact judgements.
Build The Timeline Before Assessing The Claim
Consider a fictional site where a storage failure releases contaminated water. An automatic isolation valve limits the release. The team later removes affected soil and proposes a replacement storage system.
The reporting file should distinguish the observed event, the valve's actual performance, the later repair work and the proposed system. A timestamped operational record may support the claim that the valve closed. It does not, by itself, establish the amount of contamination prevented or the condition of the surrounding environment.
Our recommendation is to connect each assertion to evidence suited to that assertion: monitoring results for observed conditions, operating records for the response, and appropriate specialist review for conclusions about environmental consequences. Keep uncertainty explicit where measurements or investigations are incomplete.
Explain The Effect Of The Response
Ask what the action changed, when that change occurred and how the team knows. The answer should distinguish an installed measure from a tested one, and a successful intervention from a planned improvement.
A budget approval demonstrates a decision to invest. A work order demonstrates that work was requested. Neither should silently become evidence that a future system already prevents harm. If the assessment depends on an assumption about performance, identify the assumption and who will verify it.
For an impact that began in an earlier period, check the remaining environmental consequences. Closing an incident ticket is an administrative event; the environmental evidence needs its own review. The guidance recognises that effects can remain material across reporting periods.
Keep Potential Impacts Visible
A proposed operational change needs a separate account of what could happen. Record the activity, the environmental pathway, the available safeguards and the uncertainties that remain. Avoid describing an anticipated technology or an untested design as if its effectiveness were already demonstrated.
Where colleagues disagree, preserve the competing assumptions and identify the evidence needed to resolve them. The assessment owner can then review the conclusion when testing, operating conditions or relevant information changes. This is more useful than repeatedly copying a reassuring sentence into the reporting file.
Connect The Assessment To A Reviewable Decision
DataSolmu recommends keeping the impact description, response timeline, supporting evidence and reviewer judgement connected. A reader of the internal record should be able to distinguish what happened from what management intends to do next.
That is a useful role for a Varmennappi workflow: make missing evidence and changed assumptions visible before a public statement is approved. The reporting organisation and its professional advisers remain responsible for the assessment; this environmental example should not be treated as a universal method for social impacts or financial risks.
Varmennappi supports reporting-data management, evidence traceability, validation workflows, and XBRL-related output review. It does not provide legal advice, auditor assurance, regulator acceptance, or a guarantee of CSRD, ESRS, VSME, ESEF, or XBRL filing compliance. Customers remain responsible for final reporting judgments, source-data quality, filing decisions, and professional review.
Source
EFRAG IG 1: Materiality Assessment Implementation Guidance — May 2024