In the previous article, When a Topic Is Material, Not Everything Is: Datapoint-Level Materiality Explained, we clarified how materiality operates at the datapoint level and why it’s not necessary to report everything. For many teams, that explanation can be helpful. But it also raises a new concern: If we report less, are we taking on more risk?
Across organizations, this question sits at the center of ESRS implementation. As flexibility becomes more visible, anxiety often increases assurance and enforcement. In practice, however, the relationship between flexibility and risk is often misunderstood.
The misconception: Flexibility equals exposure
Many practitioners still associate strong reporting with completeness. The instinct is understandable. Teams worry about omissions, anticipate auditor disagreement and assume that reporting more will reduce scrutiny.
Under the revised ESRS, this logic no longer holds.
Flexibility does not increase risk, if it’s applied well. What creates exposure is not proportionate reporting, but rather weak or unsupported judgment. Inconsistent narratives, unexplained omissions and conclusions that lack evidence are far more likely to attract scrutiny than well-reasoned selectivity.
What auditors actually focus on
In practice, assurance teams don’t look for perfection or exhaustive disclosure. They focus instead on whether decisions are understandable, consistent and supported.
Typically, this means checking that materiality decisions are clearly explained, applied consistently and aligned with the results of the double materiality assessment.
They also look for evidence that key judgments were grounded in structured analysis rather than informal assumptions.
The core question is rarely, “Why didn’t you report more?” Instead, it’s, “Can you explain how you reached this conclusion?”
What strong judgment looks like in practice
Strong judgment under ESRS is revealed by how decisions are explained and applied. Effective teams articulate clearly why a topic is material, how impacts, risks and opportunities were assessed and how those conclusions shape what is disclosed. Their reporting is internally consistent across narrative, metrics and governance sections. And it avoids contradictions between different parts of the report.
Weaker approaches are often exposed differently, relying heavily on templates, mechanically and replicating disclosures or default to over-reporting to avoid difficult decisions. In many cases, inconsistencies across sections signal a lack of structured reasoning rather than insufficient data.
The distinction is rarely technical. It is methodological.
The role of documentation without over-engineering
Documentation plays a central role in bridging professional judgment and assurance. Strong working papers explain how conclusions were reached, what evidence was considered and how decisions were applied consistently across the reporting process.
At the same time, over-engineering documentation does not reduce risk. Conversely, excessive complex files, duplicative records and unnecessary detail often create a burden without improving defensibility. What matters is clarity, structure and traceability.
Well-designed documentation supports judgment. It does not replace it.
What comes next
As teams grow more confident in applying professional judgment, a more operational question emerges: How should sustainability functions adapt their work?
In the next article, we will explore how workflows are evolving under the ESRS reset and what it means for sustainability teams in practice.
