When a Topic is Material, Not Everything is: Datapoint-Level Materiality Explained

In the previous article, Double Materiality After November 2025: Less Scoring, More Judgment, we clarified that double materiality under the revised ESRS does not require exhaustive identification and scoring of every impact, risk and opportunity. For many teams, that approach was reassuring. But it quickly led to a new question: Once a topic is material, what exactly needs to be reported? In practice, this is where confusion now concentrates.

The Misunderstanding: “Material Topic Means Report Everything”

Many teams respond to topic of materiality by defaulting to full disclosure across all related ESRS requirements. While this instinct is understandable, it is often driven by audit anxiety, internal pressure to avoid omissions and a belief that completeness signals robustness.

In reality, this approach frequently leads to over-reporting. Disclosures become longer, less focused and more difficult to interpret. More importantly, it can dilute the information that actually matters. ESRS does not require this level of complexity.

What ESRS Actually Requires

Materiality continues to operate beyond the topic level. Even when a topic is identified as material, not every disclosure and datapoint under that topic is automatically material.

The core principle that remains is decision-usefulness. Information should be reported if it can reasonably influence user decisions. That logic applies equally at the topic, disclosure and datapoint level.

Partial reporting within material topics is entirely consistent with the ESRS framework. The objective is not completeness for its own sake, but coherence between materiality drivers and what is ultimately disclosed.

A Practical Way to Think About Datapoint Materiality

In practice, experienced teams approach datapoint selection by returning to the original materiality rationale, following these steps.

Step 1: Anchor Datapoints to Materiality Drivers

Start by asking why a topic is material? What impacts, risks or opportunities led to that conclusion? Datapoint selection should follow directly from those drivers. Reporting data that is disconnected from the underlying rationale rarely improves decision-usefulness.

Step 2: Apply Three Practical Lenses

For each datapoint under consideration, teams typically ask:

• Is this datapoint clearly relevant to the materiality driver?
• Does it add incremental decision-useful insight beyond what is already disclosed?
• Could omitting it reasonably mislead users?

These questions function more as a structured qualitative filter than a scoring exercise.

What This Means in Practice

Strong reporting teams tend to prioritize clarity over volume. They group disclosures logically, focus on datapoints that illuminate the core issue and document the rationale for omissions where appropriate. Most importantly, they ensure alignment across the narrative, metrics and governance sections of the report.

Less effective approaches often replicate full ESRS disclosure lists within material topics. They can include datapoints that are only tangentially relevant to the underlying issue or produce disclosures that feel internally inconsistent. These outcomes are usually driven by caution rather than regulatory expectations.

The ESRS framework does not reward volume. It rewards clarity, coherence and defensible judgment.

What Comes Next

Once datapoints are selected, another challenge emerges: how should teams confidently apply professional judgment and defend their decisions under scrutiny?

In the next article, we will examine the evolving role of judgment under ESRS and what reviewers and auditors are looking for in practice.