Before you lock your FY2026 ESRS scope, wait for EFRAG’s new datapoint list

You have probably already told your board the good news: the revised ESRS cut mandatory datapoints by more than 60 percent. It landed well. Fewer disclosures, lower cost, less strain on a team that spent last year drowning in the first cycle. So now you want to lock your FY2026 scope and move on.

Here is the catch. “Sixty percent fewer datapoints” is a headline, not an instruction. It does not tell you which datapoints you now report, which of last year’s you can drop, or which survived under a new number. Until you can answer that at the line-item level, your FY2026 scope is a guess dressed up as a decision.

The document that turns the headline into an instruction is being published this month. It is genuinely useful — and using it the wrong way is one of the easier ways to create a pile of re-work in October. Let’s walk through what it is, why it is a trap if you treat it as final, and how to use it now without getting burned.

What EFRAG has just put in front of you

Two things happened in the space of a week, and together they change what you can actually do before year-end.

The Knowledge Hub is live

EFRAG has published an interactive version of the 2026 Revised ESRS and the new Voluntary Standard. It is not just the text. It carries a glossary, links from each revised requirement back to the corresponding 2023 ESRS paragraph, an evolution view against the November 2025 simplified draft, and a per-standard log of what changed. For the first time you can trace a single requirement from where it started to where it landed, without a manual diff.

One caveat worth noting up front: the Implementation Guidance for the revised standards is not there yet. The interactive text helps you read the standard. It does not yet tell you how to apply the harder judgements.

The datapoint list is days away

At its 29 July meeting, EFRAG’s Sustainability Reporting Board cleared two drafts for release: a draft List of Datapoints effective from 2026 — roughly 300 datapoints, a slightly deeper cut than the 61 percent reduction signalled last December — and a draft XBRL taxonomy. The list is expected on the Knowledge Hub in the first half of August.

The operational key sits alongside it: a mapping workbook that connects each old datapoint from the 2023 IG3 list to its new equivalent, or marks it as removed. That is the piece that matters most to you, and it is the piece most people will misuse.

Why you cannot just adopt the list and stop

This is the part to slow down on, because it is where the re-work comes from.

The list is being issued as EFRAG Secretariat supporting material, not as authoritative Implementation Guidance. It is explicitly a draft. It goes through an eight-week fatal-flaw review over August and September, and it is not final until October or November — around the same time the revised standards themselves are expected to clear European Parliament and Council scrutiny and enter the Official Journal.

So the list is usable, but it is a moving target. Anything you build directly on the draft numbering — a locked tagging map, a frozen data-collection template, a signed-off scope memo — carries the risk that a datapoint moves, splits or disappears before the final version lands. Treat the draft as a planning instrument, not as a system of record, and you get most of the value with none of the exposure.

The trap underneath the headline

There is a second, quieter risk in the 60 percent figure, and it is the one that actually determines your scope.

A shorter datapoint list does not shrink your double-materiality assessment. Which topics are material — and therefore which disclosure requirements apply to you at all — is still decided by your materiality analysis, not by the length of the datapoint catalogue. Fewer datapoints per topic does not mean fewer material topics. If you let “60 percent fewer datapoints” quietly become “60 percent less to assess,” you will under-scope the assessment that everything else hangs off. The datapoint cut is a reporting simplification. It is not a materiality simplification.

The FY2026 decision you actually have to make

Before the mapping is useful, you need to know which regime you are mapping to. For a FY2026 statement you have three routes, and the revised standards do not apply automatically until they are in force.

• 2023 ESRS plus the Quick Fix: Report under the standards already in force, using the transitional relief already available.
  
  • Best fit if you want certainty now and cannot wait for the revised text to enter the Official Journal
• Revised ESRS in full (early application): Apply the 2026 revised standards early, once in force, to capture the full datapoint reduction.
  • Best fit if you are prepared to move as soon as the Official Journal publication lands, expected in Q4 2026.‍
• Hybrid: Combine transitional reliefs with elements of the revised approach where permitted‍
  
  • Best fit if you want to lighten the load without betting the whole cycle on the revised text’s timing.

The revised standards are expected to apply for FY2027, with early FY2026 application allowed once they enter into force — which commentators currently place in November. The draft datapoint list is what lets you cost each of these routes properly instead of choosing on instinct.

A re-map and decide sprint you can run this month

Here is how to turn the draft into a decision without creating throwaway work.

1. Pull your FY2024 or FY2025 datapoint inventory — the list you actually reported against last cycle.
2. Run it through the old-to-new mapping workbook the moment it publishes. Tag each line as carried over, renumbered, merged or removed.
3. Isolate the removals. These are your candidate savings — but confirm none of them were carrying a disclosure your materiality assessment still requires.
4. Re-confirm your material topics independently of the datapoint count, so scope is driven by materiality, not by list length.
5. Cost the three FY2026 routes against the mapped inventory, and take a provisional recommendation to your steering group — provisional, because the list is not final until Q4.
6. Keep everything version-tagged to the draft. When the final list drops in October or November, you re-run the mapping, not the whole analysis.

The dates to hold in view

• First half of August 2026: Draft List of Datapoints and old-to-new mapping workbook published on the Knowledge Hub
• Late August to early September 2026: Draft revised ESRS XBRL taxonomy opens for public consultation, running about 90 days
• October to November 2026: Fatal-flaw review closes; datapoint list finalised; revised ESRS expected to clear scrutiny and enter the Official Journal
• FY2027: Revised ESRS apply; earliest point mandatory digital tagging is expected to bite

What to do before the final list lands

You do not have to wait for October to make progress, and you should not lock anything before it. The move this month is to map, not to freeze. Use the draft list to see exactly which of last year’s datapoints survived, re-anchor your scope to your materiality assessment rather than to the datapoint count, and cost your FY2026 route while the decision is still cheap to change. When the final list arrives, a company that mapped early re-runs a workbook. A company that guessed re-does a cycle.