DataSolmu blog
Keep ESRS Datapoint Changes Under Control
A practical way to assess changed ESRS datapoints, keep materiality decisions visible, and protect reporting evidence.
ESRS reporting does not stand still once a disclosure inventory is built. A datapoint can be added, removed, renamed, reclassified, or clarified. If those changes are treated as a spreadsheet tidy-up, teams can lose the link between the reporting decision, the evidence behind it, and the public statement it affects.
A controlled change process keeps the reporting programme adaptable without turning it into an automatic checklist.
Treat Each Change As A Decision
When a disclosure requirement changes, create a short change record before editing the reporting inventory. Capture what changed, the reporting period affected, the reports or data flows that may be impacted, and the decision the team needs to make.
The useful question is not simply whether a line has appeared or disappeared. It is whether the change alters a material disclosure, a data request, a calculation, a policy statement, or a review step. That distinction helps teams focus effort where it protects the quality of the final sustainability statement.
Keep Materiality At The Centre
An updated datapoint list is a planning aid, not a substitute for judgement. A reporting team still needs to establish whether a matter is material, whether a condition applies, and whether the organisation has the policy, action, target, or evidence that a disclosure would describe.
Record that reasoning alongside the change. A concise decision note should show the materiality conclusion, the applicable entity and period, the people who reviewed it, and any open assumptions. This is especially valuable when a datapoint looks relevant at first glance but is not needed for the organisation's circumstances.
Assess Impact Across The Reporting Workflow
A small technical adjustment can affect several parts of the process. A change in data type may alter a calculation or validation check. A new conditional item may require a different evidence request. A revised reference may mean a reviewer needs to revisit the rationale behind an earlier decision.
For each change, assess the impact across four areas:
- reporting scope and materiality;
- data, calculations, and evidence;
- narrative, policies, targets, or actions;
- review, approval, and digital-reporting hand-offs.
This keeps the inventory connected to the work that makes a disclosure supportable. It also reduces the chance that a reporting team updates a label while leaving the underlying process unchanged.
Preserve The Evidence Trail
The change record should link to the evidence used to reach the decision, rather than copying it into a tracker. Note the responsible owner, the reviewer, the status of the impact assessment, and the date the decision was approved. Where a change affects a public claim, add a final confirmation that the evidence and wording still agree.
That trail makes later review faster. It lets the team answer practical questions such as what changed, why the response was appropriate, and whether related disclosures were checked together.
Make Change Visible Before Publication
Use a review gate before a changed item reaches a sustainability statement or other public channel. The gate should confirm that the scope decision is documented, the evidence is current, dependent calculations and narrative have been checked, and unresolved limitations are visible to the approver.
For a Varmennappi-style workflow, useful prompts include:
- Is the changed item connected to a documented materiality decision?
- Has an accountable owner confirmed the evidence and reporting impact?
- Do related data, narrative, and review records remain consistent?
- Are conditions, assumptions, and gaps visible before approval?
These prompts support preparation and traceability; they do not replace legal interpretation, professional judgement, or assurance work.
Practical Takeaway
Datapoint maintenance is reporting change management. Log the change, assess its materiality and workflow impact, keep the evidence connected to the decision, and approve the resulting public claim through a visible review gate. That gives teams a more reliable way to absorb technical adjustments while keeping disclosures explainable.
Source
EFRAG: Addendum to IG3 — Technical adjustments to the List of Datapoints