ESRS S3 affected communities

The reporting question is not simply how much the undertaking spent on community projects.

The ESRS overview places S3 within the standards architecture.

A statement about community benefit needs a defined claim and source basis rather than a generic goodwill narrative.

Do not reuse original-standard content or phase-in summaries without checking the revised provisions Original ESRS S3 ESRS 1 paragraphs 125–127.

The CSRD thresholds guide addresses the separate reporting population under the directive Directive 2026/470.

In the fictional Quayside Storage case, a changed access arrangement affects people using a local route.

The example is invented and does not determine a legal right, actual impact or company-specific materiality conclusion.

Its reporting problem is whether a broad community-supported statement reflects the evidence available.

Quayside’s reviewer retains the meeting record and the unresolved concern rather than selecting the more favourable source.

No real community, consultation result or project approval is implied.

The materiality template keeps those decisions separate.

IG1 is non-authoritative guidance for the 2023 standards rather than a source of revised paragraph numbering IG1 disclaimer EFRAG guidance status.

A participation count is not a substitute for understanding the substance of the issue.

Quayside’s fictional file keeps an unresolved issue visible even where most recorded comments were favourable.

The stakeholder-engagement guide develops the evidence method without prescribing one universal survey.

A funded project and a resolved adverse effect are different statements.

The response record should preserve which concern it addresses and what remains to be assessed.

Positive impacts are assessed separately rather than netted against negative impacts ESRS 1 paragraph 44.

Quayside’s fictional statement can describe the completed action while retaining the unresolved effect.

The reporting principles guide develops balanced and verifiable explanation.

The ESRS S2 guide develops the separate worker record.

A shared location or business relationship should not make different affected groups invisible.

The evidence map should show which source supports which answer.

The draft list is supporting human navigation rather than every fact every undertaking reports Draft list release.

The ESRS datapoints guide develops the distinction.

The draft XBRL taxonomy provides technical representation and does not make tagging mandatory at this stage EFRAG taxonomy release.

A valid digital field cannot establish the meaning of a community-support claim.

Ask a demonstrator to show how differing perspectives survive an export and later review.

Quayside’s fictional export should reveal whether the broad community-support wording rests on a narrow group, and whether the changed access concern received a distinct review.

Ask CSRD consultants and reporting software suppliers to demonstrate those distinctions.

The standards homepage provides the wider comparison before community information is reused for another reporting purpose.

Quayside’s fictional review preserves both the positive action and the unresolved access concern.

The example is an editorial starting point rather than a finding about a real project, legal obligation or reporting conclusion.