DataSolmu blog
Make ESG Reporting Handoffs Reviewable
Build a reporting operating model that makes ownership, evidence and decisions visible across functions.
ESG reporting rarely fails because one team did not care enough. It fails when work crosses teams without a clear handoff: a sustainability conclusion is not connected to finance, a data owner does not know what a reviewer needs, or a late change never reaches the people responsible for the public statement.
An effective operating model makes those connections visible. It does not require one universal organisation chart. It does require a shared way to assign ownership, bring decisions to the right forum and retain the evidence behind a reporting claim.
EFRAG's July 2024 review of selected early ESRS implementation practices describes several organisational patterns. It is a non-authoritative, time-bound state-of-play report, not a prescription for current reporting requirements. The practical lesson is still useful: reporting quality improves when functions can see and challenge the same work.
Start With A Clear Reporting Accountable
Choose an accountable reporting lead for the overall process. This may sit with Sustainability, Finance or a joint leadership arrangement. The important point is not the job title; it is that everyone can identify who resolves a scope question, approves a reporting timetable and escalates a blocked disclosure.
The accountable lead should not become the owner of every metric or judgement. Instead, connect each part of the reporting process to the people best placed to support it:
- Sustainability teams frame topics, policies, impacts and transition context.
- Finance teams connect reporting periods, entities, controls and links to financial information.
- Risk and business teams test whether risks, opportunities and operating facts are represented accurately.
- HR, Procurement, Operations and other specialists own the underlying facts in their areas.
- IT and data teams maintain dependable collection, access, change and validation processes.
This prevents the familiar last-minute pattern where one central team tries to reconstruct decisions that were made elsewhere.
Treat Handoffs As Reporting Controls
A handoff is a control point, not just a meeting. When a topic moves from assessment to data collection, or from draft to approval, record what changed, who is responsible next and what evidence must travel with it.
For example, a material workforce topic may move from a sustainability assessment to HR data collection, then to finance or control review before it reaches a disclosure draft. At each step, the team should be able to see the applicable entity and period, the evidence source, open assumptions, review status and decision owner.
That record creates a useful distinction between work that is complete, work that is waiting for evidence and work that needs a management decision. It also makes an exception visible before it turns into a vague caveat in public wording.
Give Cross-Functional Forums A Job To Do
Regular reporting forums are most valuable when they decide something specific. A useful agenda can include:
- changes to reporting scope, materiality or entity boundaries;
- data gaps, estimates and exceptions that need an owner or escalation;
- dependencies between sustainability, financial and operational information;
- readiness of evidence, review and approval for the next reporting milestone; and
- decisions that need executive or board-level attention.
Keep a concise decision log with the question, conclusion, owner, evidence reference and next review date. This reduces the risk that a workshop agreement is mistaken for a documented reporting judgement.
Design Data Work For Challenge, Not Collection Alone
Data collection systems should help a team answer more than "did we receive a number?" They should support questions such as whether the number covers the right population and period, which method was used, whether an exception applies and who checked the result.
Where existing financial-reporting controls can be extended, that may make evidence and review more consistent. Where different tools are necessary, the handoff needs to be explicit: define the data owner, the approved version, the validation rules and the route for changes. Technology can make the process repeatable, but it cannot decide materiality or resolve an unsupported claim.
Use A Readiness Check Before Public Wording
Before approving a sustainability statement, ask:
- Is there an accountable lead for the overall reporting decision?
- Does every material claim have a business owner, evidence source and reviewer?
- Have changes in data, scope or assumptions reached the teams responsible for related disclosures?
- Are exceptions, limitations and unresolved questions visible to the approver?
- Is the decision record clear enough for a later reviewer to follow?
Varmennappi can help teams connect evidence requests, owners, review comments and open gaps across the reporting workflow. It does not provide legal advice, auditor assurance, regulator acceptance or a guarantee of filing compliance. The reporting organisation remains responsible for its final judgements and professional review.
Practical Takeaway
Do not treat ESG reporting as a relay race between isolated functions. Make each handoff a visible, reviewable control: assign the next owner, carry the supporting evidence, record the decision and escalate what remains unresolved. That gives reporting teams a more dependable foundation for clear public disclosures.
Source
EFRAG: Implementation of ESRS — Initial Observed Practices from Selected Companies