First ESRS Reporting Cycle: A 15-Month Project Plan for Companies and Groups

A mature annual reporting process can run on an established calendar, known definitions and recurring controls. A first ESRS cycle cannot. The organisation is simultaneously interpreting scope, creating governance, assessing materiality, defining metrics, building evidence, redesigning group instructions, preparing narrative and quantitative information, and learning what the assurance provider will need. Treating that work as a three-month drafting project creates predictable failure: late scope changes, unstable calculations, unapproved estimates, inconsistent subsidiary data and a board asked to approve conclusions it has not previously seen.

The 15-month model below is an LRA implementation plan, not a timetable prescribed by ESRS. It assumes that the company begins before the reporting year-end and can overlap workstreams. A complex group, weak data environment, acquisition programme or late legal-scope decision may need more time. A smaller and well-controlled entity may compress the plan, but it should not remove the critical decision and evidence gates.

Figure 4. Illustrative 15-month first-cycle programme and critical-path gates.

Some tasks can be delayed without stopping publication; others cannot. The critical path is the sequence of decisions whose delay pushes the final release date or forces uncontrolled shortcuts.

R = Responsible; A = Accountable; C = Consulted; I = Informed. The allocation must be adapted to the undertaking’s governance and national law. Preparation and independent challenge should remain separated even where individuals hold several roles.

Issue one controlled group reporting manual with definitions, boundaries, units, evidence expectations, cut-off and escalation rules.

Classify reporting units by material activity and data risk rather than giving every subsidiary an identical workload.

Require local management sign-off and central review, with targeted deep dives for high-risk topics, estimates or unusual movements.

Reconcile legal-entity population, acquisitions and disposals with the financial consolidation process.

Prevent local changes to formulas or classifications without central method approval.

Provide a translation and terminology protocol where submissions or evidence are multilingual.

Maintain a group exception log and quantify the effect of unresolved gaps on the sustainability statement.

Months 1-4. The group confirms scope and version, maps the business model and relationships, and performs a top-down DMA with focused assessment for high-risk water, workforce and supply-chain issues. The board committee approves the methodology and material conclusions.

Months 4-9. The disclosure matrix identifies required and entity-specific information. The group reuses the controlled GHG process, but creates new definitions and evidence rules for non-employee workers, supplier incidents and water-stress sites. A dry run in month 8 finds that three entities use different worker classifications and two sites cannot reproduce recycled-water data.

Months 9-13. The group fixes classifications, introduces a proxy with transparent limitation for one water population, performs a pre-assurance evidence review and drafts the statement. Finance reconciles capital-allocation and anticipated-financial-effect language with budgets and impairment papers.

Months 13-15. Period-end controls are completed, open issues are escalated, the assurance provider performs agreed procedures, management signs representations and the board approves the statement. The archive records final figures, source extracts, method versions, review evidence and publication files.

Starting the DMA before legal scope, group boundary and business-model evidence are sufficiently clear.

Collecting every datapoint before material IROs and disclosure objectives are mapped.

Allowing the project plan to show tasks but not controlled outputs, approvers or evidence gates.

Leaving finance, legal, IT, internal control or subsidiaries outside the design phase.

Designing methods during final collection and changing them after local submissions arrive.

Using the assurance provider as the process owner or expecting assurance to repair management evidence.

Scheduling the board only for final approval, with no earlier methodology or materiality challenge.

Publishing the report while the website, policies, targets, investor deck or financial statements use inconsistent claims.

Legal scope, reporting boundary, applicable ESRS edition and national requirements are documented.

Programme governance, RACI, budget, board calendar and escalation are approved.

DMA, disclosure matrix, data dictionary and evidence register have named owners and deadlines.

Metric methods and group instructions are approved before main collection.

Dry runs test source access, calculations, estimates, review evidence and consolidation.

Finance, legal, control and assurance milestones are integrated into the plan.

Material limitations and open issues have decision dates and governance owners.

The final publication, digital output, assurance report and archive are controlled as one release package.

1. Which unresolved decision would move the publication date if it slipped by four weeks?

2. Are metric methods approved before subsidiaries and data owners begin the main collection?

3. Does each programme milestone produce evidence and an approval, or only a meeting and a status update?

Source check completed on 2 August 2026. This article is an educational publication draft. It does not provide legal, assurance or organisation-specific advice. Confirm the applicable ESRS edition, the final Official Journal text, national implementation and the undertaking’s facts before public use.

Changes to national CSRD scope, filing, digital-tagging or assurance deadlines.

Publication and effective date of revised ESRS or further transition reliefs.

New assurance standards, CEAOB guidance or national assurance pronouncements.

Material changes to the group, acquisitions, disposals, reporting period or ERP/data environment.

Label all resourcing figures and timing assumptions as LRA planning estimates, not ESRS requirements.

Adapt the timeline to statutory filing dates, board calendars and assurance availability.

Do not postpone materiality, methodology or boundary decisions until final drafting.

Separate management responsibility from assurance-provider procedures and advice.