ESRS Gap Assessment: How to Compare Your Current Report with Revised Requirements

Technical status. The Commission adopted revised ESRS on 3 July 2026, but the amending delegated regulation remained not in force until publication in the Official Journal. A live assessment must therefore state whether it is testing current legally effective requirements, revised requirements for transition planning, or both. EFRAG’s 2023 implementation guidance can still inform process design where relevant, but EFRAG stated that no implementation guidance had yet been issued for revised 2026 ESRS.

Educational material. It does not replace the applicable delegated act, national law, legal advice, professional judgement or an assurance conclusion.

There are three legitimate objectives, and they produce different conclusions.

The baseline is the ESRS and national legal requirements effective for the reporting period. The assessment asks whether the current report and reporting system satisfy the applicable requirements.

The baseline is the revised 2026 ESRS as a planning target. The output is not a current-compliance conclusion. It identifies requirements that are removed, combined, changed, newly clarified or affected by transition provisions.

The baseline includes applicable reporting requirements plus expected evidence, controls, review trail and final-file governance. A disclosure may be substantively present but not assurance-ready because evidence is inaccessible or the calculation cannot be reproduced.

A project may run all three assessments, but they need separate status fields. The phrase “80% compliant with revised ESRS” is risky when the revised standards are not yet legally effective or the remaining 20% contains critical scope and materiality findings.

The assessment header should record:

legal reporting basis and jurisdiction;

reporting undertaking and period;

current effective ESRS source set;

amendments, corrigenda and national rules;

revised or draft source set used for planning;

effective-date assumptions;

applicable phase-ins and reliefs;

EFRAG implementation guidance edition;

assessor, reviewer and approval date; and

update triggers.

Use a source-status taxonomy such as:

This version layer prevents the assessment team from “correcting” a current report to a future draft while overlooking a current legal requirement.

A robust row contains more than an ESRS paragraph and a page number.

internal requirement ID;

ESRS standard, disclosure requirement and paragraph/datapoint reference;

requirement class: always required, subject to materiality, conditional or voluntary;

source edition and status;

related IRO and sustainability matter;

applicability and materiality conclusion;

boundary and period.

current report location;

current disclosure summary;

data/narrative owner;

methodology or estimate;

supporting evidence;

current control and reviewer;

known limitation.

gap type;

maturity score;

priority;

corrective action;

owner and due date;

dependency;

retest evidence;

review status and final sign-off.

The downloadable matrix accompanying this Knowledge Card package uses this structure and adds separate tabs for scope and version, double materiality, evidence and controls, digital readiness and publication gates.

Figure 1. Four-lens ESRS gap assessment: materiality, topic disclosures, controls and presentation. Original London Reporting Academy practitioner visual.

This lens asks whether the undertaking selected the right information before assessing how it is written.

Core tests

Is the reporting boundary complete for own operations and relevant value-chain relationships?

Are actual and potential impacts supported by operational, due-diligence and stakeholder evidence?

Are impact severity and likelihood assessed using controlled criteria?

Are sustainability-related financial risks and opportunities connected to finance evidence?

Are thresholds and qualitative overrides documented and approved?

Is the material-information filter applied at disclosure and datapoint level?

Are “not material”, “not applicable” and relief conclusions distinguishable?

Is every material IRO linked to report disclosures and management response?

Typical gaps

survey-only materiality;

no value-chain evidence;

one combined impact/financial score;

topics marked material because a standard exists;

no rationale for omitted datapoints;

stale IRO register not updated for acquisitions or incidents.

Evidence expected

IRO inventory, impact and financial tests, stakeholder evidence, threshold methodology, decision log, governance approval and IRO-to-disclosure map.

This lens tests whether the report provides the material information required by ESRS 2 and the relevant topical standards.

Core tests

basis of preparation, governance, strategy and IRO disclosures are specific and connected;

policies identify scope, owner and links to material matters;

actions have objectives, resources, coverage and progress;

targets have baselines, boundaries, methodologies, horizons and performance;

metrics use controlled definitions, units, periods and boundaries;

current and anticipated financial effects are connected to finance;

no-policy, no-action or no-target situations are disclosed accurately where relevant;

entity-specific disclosures fill material information gaps rather than add marketing narrative.

Typical gaps

generic policies;

activities presented as outcomes;

target ambition without measurable terms;

one metric boundary applied to all disclosures;

missing adverse performance and limitations;

disclosure copied from a framework with different materiality or definitions.

Evidence expected

Approved policies, action plans, budgets, target register, calculation files, methodology documents, finance bridge and narrative claim ledger.

This lens asks whether the disclosure can be reproduced, reviewed and assured.

Core tests

complete source population reconciled to master data;

controlled data dictionary and calculation methodology;

estimate assumptions, alternatives and uncertainty approved;

segregation between preparation and review;

version and change control;

evidence retention and access;

issue management, correction and independent retest;

management representations and final approval.

Typical gaps

spreadsheet owned by one person with no reviewer;

unsupported manual adjustments;

evidence stored in email or inaccessible systems;

no change log for factors or boundaries;

findings closed by the preparer;

narrative claims not included in controls.

Evidence expected

Data dictionary, evidence register, calculation workpapers, review sign-offs, estimate register, access logs, issue tracker and retest record.

This lens tests the statement the reader will actually receive.

Core tests

required location and architecture of the sustainability statement;

understandable separation of basis, governance, strategy, IROs and topics;

precise and permitted incorporation by reference;

functioning cross-references and links;

consistency of numbers across tables, narrative, financial statements and EU Taxonomy disclosures;

clear boundaries, periods, methods and limitations;

version, approval and final-file control;

publication, accessibility, language and digital status.

Typical gaps

a matrix page reference points to a generic paragraph;

external policy link changes after approval;

financial effects are disconnected from the accounts;

board-approved numbers change during design;

the published PDF differs from the assured file.

Evidence expected

Final page map, cross-reference test, reconciliation log, board/audit-committee approval, checksum, publication evidence and archived final file.

A five-level score supports prioritisation without pretending that all requirements have equal weight.

The score should not replace a finding. A maturity 3 row can still contain a critical unresolved error. Record gap type and priority separately.

Useful gap types include:

missing disclosure - required material information is absent;

incomplete disclosure - some information exists but a necessary element is missing;

materiality gap - inclusion or omission decision is unsupported;

boundary gap - entity, value-chain, site or population scope is incomplete;

method gap - definition, calculation or estimate is not controlled;

evidence gap - the disclosure cannot be substantiated;

control gap - preparation, review, change or retention controls are weak;

presentation gap - location, cross-reference, balance or understandability is poor;

version gap - requirement or report source is outdated or mixed;

governance gap - responsibility or approval is missing.

Classification improves the remediation plan. “Add disclosure” is the wrong action when the root cause is a missing population reconciliation or an unapproved materiality judgement.

A practical priority score considers five factors.

Can the gap affect the reporting claim, legal scope, a material omission, a key metric or the assurance opinion?

Does the gap concern a significant impact, principal risk, major opportunity, key target or decision-useful financial effect?

Does the issue block many disclosures? A weak value-chain boundary or data dictionary may affect dozens of rows.

Does correction require new systems, supplier data, scenario analysis, board approval or assurance work?

Can the issue be corrected through drafting, or does it require redesign of the process and evidence chain?

Use an override: scope, version, materiality, core boundary, key estimates and final-file integrity should normally be high priority even if the immediate drafting effort is small.

Figure 2. Maturity and remediation priority are separate judgements. Original London Reporting Academy practitioner visual.

Each action should state:

the root cause;

the exact requirement and affected disclosures;

required output and evidence;

accountable owner;

dependencies and decision makers;

due date;

reviewer and retest method;

publication consequence if unresolved.

Compare weak and stronger actions:

Context. A listed industrial group published its first ESRS statement using the 2023 source set. It wants to understand readiness for revised ESRS without making an early-compliance claim.

Approach. The team creates two source columns: “current FY20X5 requirement” and “revised ESRS transition target”. Removed or simplified datapoints are not deleted from the evidence system immediately; they are marked for rationalisation after the effective source set is confirmed.

Findings. The report contains strong climate metrics, but the gap assessment identifies four higher-priority issues: the value-chain boundary is not connected to the DMA, financial effects use different time horizons from finance, three policy disclosures lack scope, and incorporation by reference points to mutable web pages.

Scoring. Climate metrics receive maturity 3 because the calculations operated but factor-change review is incomplete. The value-chain boundary receives maturity 1 and critical priority because it affects E2, E4, S2 and S4. The cross-reference issue receives maturity 2 and high priority because it can be corrected quickly but affects publication integrity.

Result. Management receives a remediation roadmap rather than a single readiness percentage. The transition column remains labelled “planning against revised ESRS adopted 3 July 2026 - not current legal compliance conclusion”.

Myth: “A high ESRS gap-assessment score means the report is ready for publication.”

Reality: A percentage can hide critical findings. Publication readiness depends on whether scope, version, materiality, key disclosures, evidence, controls, assurance findings and final-file approvals are closed. A 95% matrix with an unresolved reporting-boundary error can be less ready than an 80% matrix with transparent, controlled remediation.

Primary connections

Revised ESRS 1 - requirement architecture, double materiality, material information, reporting boundary, estimates, presentation and transition.

Revised ESRS 2 - BP, GOV, SBM, IRO and general disclosure requirements.

Topical ESRS - matter-specific policies, actions, targets, metrics and financial effects.

EFRAG IG 1, IG 2 and IG 3 - non-authoritative process and datapoint support for the 2023 ESRS.

ESMA enforcement reporting - materiality, statement structure, incorporation and connected information observations.

Next practical materials

ESRS Compliance Checklist and Free Disclosure Matrix: downloadable workbook in this package.

Common ESRS Reporting Mistakes: 25 Problems That Undermine Compliance and Assurance.

ESRS Limited Assurance Readiness: Evidence, Controls and Common Findings.