ESRS S3 Affected Communities: What the Standard Actually Requires and How to Build the File

When ESRS S3 applies and what it covers

ESRS S3 is materiality-gated. It applies when the double materiality assessment identifies material impacts, risks, or opportunities related to affected communities. If communities aren’t material, standard ESRS 1 paragraph 30 treatment applies and no S3 disclosure is required.

The standard defines “affected communities” broadly. These are communities that are or could be materially impacted by the company’s own operations, products, services, or business relationships across the value chain. The sub-topics include: communities’ economic, social, and cultural rights; communities’ civil and political rights; and rights of indigenous peoples. That last sub-topic carries a specific disclosure obligation. ESRS S3 paragraph 4(c) explicitly covers free, prior and informed consent (FPIC) and the right to self-determination.

The materiality trigger for S3 most often fires in extractives, construction, infrastructure, energy generation, large-scale agriculture, and waste management. But it also applies to companies whose operations create environmental externalities affecting nearby populations. A chemical plant whose air emissions affect air quality in a residential area has a potential S3 exposure, separate from the E2 pollution disclosure. E2 covers the emissions themselves. S3 covers the impact of those emissions on the community. The same physical event creates disclosures under two different standards.

Land use is another common trigger. A logistics company acquiring land for a new distribution centre in a peri-urban area may displace small businesses, increase traffic, and alter local water drainage patterns. None of these impacts involve the company’s own workforce (S1) or value chain workers (S2). They affect communities, and they belong in S3.

Companies with operations or supply chains connected to indigenous territories face the most demanding S3 requirements. FPIC isn’t just a policy commitment under this standard. If the company’s activities affect indigenous peoples, S3 requires disclosure of specific policy provisions for preventing and addressing those impacts, including whether the company has processes to obtain FPIC before proceeding with activities that affect indigenous lands or resources.

For European mid-market companies, indigenous peoples’ rights may seem remote. But supply chain connections bring it closer than expected. A company sourcing palm oil from Southeast Asia, timber from the Amazon basin, or cobalt from Central Africa has potential upstream exposure to indigenous land rights. The S3 materiality assessment must consider these connections even if the company has no direct relationship with the affected communities. If the supply chain link creates material impacts, the disclosure obligation applies.

How to run the S3 materiality assessment in practice

The S3 materiality assessment is where most teams get stuck. Unlike S1 (where the company controls the data) or S2 (where at least Tier 1 supplier relationships exist), S3 requires the company to assess impacts on communities it may never have interacted with.

The ESRS application requirements reference the LEAP approach (Locate, Evaluate, Assess, Prepare), the same four-phase process used for the environmental standards. Phase 1 asks the company to locate where in its operations and value chain community interfaces exist. This is a geographic mapping exercise: which sites are near residential areas, which supply chain nodes are in regions with documented community rights issues, which downstream activities affect local populations.

Phase 2 evaluates the nature of community impacts at each identified interface. Noise, dust, water quality changes, land use alterations, traffic increases, economic displacement, and loss of livelihood resources are all potential impact categories. Not all of them will be material for any given site.

Phase 3 assesses the resulting risks and opportunities. A company facing community opposition to a site expansion has a financial risk (permitting delays, litigation costs, reputational damage). A company that successfully engaged communities in its planning process may have reduced its operational risk.

For assurance, the test is whether the DMA covered affected communities with enough specificity to justify the conclusions reached. A DMA that states “no material community impacts” without describing which sites were assessed, what impact categories were considered, and what data sources were used is too generic to survive assurance testing. ESMA’s 2025 enforcement priorities emphasised exactly this point: materiality assessments must be entity-specific, not standardised templates.

The four disclosure requirements explained

The November 2025 Amended ESRS restructured S3 from five disclosure requirements to four, matching the simplified architecture applied across all social standards.

S3-1: Policies related to affected communities (paragraphs 10–11)

The company discloses its policies for managing material impacts on affected communities, per ESRS 2 GDR-P. The disclosure must specify whether policies cover all affected communities or specific ones. Paragraph 11 requires disclosure of any particular policy provisions for preventing and addressing impacts on indigenous peoples. The company must also describe its human rights policy commitments relevant to affected communities, including processes to monitor compliance with the UN Guiding Principles on Business and Human Rights, the ILO Declaration on Fundamental Principles and Rights at Work, or the OECD Guidelines for Multinational Enterprises.

For assurance, the test is whether the policy exists, is documented, and matches the disclosure. A company that claims to respect FPIC but has no documented procedure for conducting FPIC assessments before new projects has an internal consistency issue. The assurance provider should expect to see the policy document, its approval date, its scope, and evidence that it has been applied (or that no situations requiring its application arose during the period).

S3-2: Engagement with affected communities (paragraphs 12–15)

The company describes how it engages with affected communities or their legitimate representatives. The disclosure should cover who engages (which function or role has operational responsibility), how engagement is conducted (meetings, consultations, participation in planning processes), and how community perspectives inform the company’s decisions.

The amended draft also requires disclosure of whether grievance channels exist for communities to raise concerns. As with S2, the UN Guiding Principles Principle 31 effectiveness criteria are the benchmark. Third-party mechanisms (government complaint channels, NGO-operated mechanisms, industry collaborative mechanisms) can count if they are accessible to the affected communities.

Paragraph 19 introduces the mandatory human rights incident datapoint (carried over from the S2 structure). The company must disclose whether human rights incidents connected with affected communities have been reported during the period and, if applicable, provide details. This is a new mandatory datapoint in the November 2025 draft.

S3-3: Actions and resources related to affected communities (paragraphs 16–18)

Key actions taken or planned to prevent, mitigate, and remediate material negative impacts on affected communities, per ESRS 2 GDR-A. The disclosure must include the company’s approach when tensions arise between community protection and other business pressures (paragraph 17 gives the example of practices around planning and land acquisition).

The company must also describe how it tracks and assesses effectiveness of its actions. AR 33 (from the 2023 version, referenced in the amended text) permits the company to disclose lessons learned from previous periods. If no effectiveness tracking exists, that’s a legitimate disclosure, not a compliance failure, but the absence must be stated.

S3-4: Targets related to affected communities (paragraph 20)

Targets per ESRS 2 GDR-T. As with the other social standards, targets can be qualitative or quantitative. “Maintain good community relations” is not a target. “Complete environmental impact consultations with all communities within 5km of new facility sites before construction begins” is. If no targets have been set, the company must disclose this fact and explain why.

The S2/S3 boundary and cross-standard interactions

ESRS S3 interacts with multiple other standards, and the boundary questions matter for assurance.

S2 versus S3: workers versus communities. The line is the relationship to the company’s operations. S2 covers people who work in the value chain (supplier employees, outsourced workers). S3 covers people who live near operations, are affected by environmental externalities, or whose land or resources are impacted by the company’s activities. The distinction is about the nature of the relationship, not the severity of the impact. A mine has S2 obligations toward the contractor workforce at the site and S3 obligations toward the village downstream whose water supply is affected by runoff. Same site, same operation, different stakeholder groups, different standards.

S3 versus E2 (Pollution). E2 covers the pollutant emissions themselves (quantities of NOx, particulate matter, water contaminants). S3 covers the impact of those emissions on communities (respiratory health effects, loss of agricultural productivity, displacement from contaminated land). If a client’s air emissions are material under E2, the assurance team should ask whether those same emissions create material community impacts under S3. The two assessments are separate, but the data often comes from the same source.

S3 versus E4 (Biodiversity). Pollution that degrades biodiversity in an area used by communities (fishing grounds, forests used for livelihoods) creates potential disclosures under both E4 and S3. Again, the environmental standard covers the ecological impact. S3 covers the human impact.

For assurance file organisation, the working paper should cross-reference the relevant environmental disclosure where S3 impacts are caused by environmental externalities. An S3 community health impact caused by E2-reportable emissions should trace back to the same source data.

What the November 2025 amendments changed

The Amended ESRS submitted by EFRAG in November 2025 made four changes to S3 that affect how practitioners build the file.

Restructuring from five to four disclosure requirements. The 2023 version separated engagement (S3-2), grievance and remediation (S3-3), actions (S3-4), and targets (S3-5). The November 2025 draft merges engagement and grievance into S3-2, renumbers actions as S3-3, and renumbers targets as S3-4. Substance is preserved. The structure is simpler.

Stronger anchoring in human rights frameworks. The amended text references the UN Guiding Principles, the ILO Declaration, and the OECD Guidelines more explicitly. For companies already operating under the CSDDD, this alignment reduces duplication between sustainability reporting and due diligence obligations.

A new mandatory datapoint on substantiated human rights incidents was introduced at paragraph 19. The company must disclose whether incidents connected with affected communities were reported and substantiated during the period. This aligns with SFDR principal adverse impact indicator #14 in Table III of Annex I of Commission Delegated Regulation (EU) 2022/1288.

Transitional relief was extended. Wave 1 companies may omit all S3 disclosure requirements for financial year 2026 under the amended ESRS 1 transitional provisions. Wave 2 companies (delayed to FY 2028) have an even longer preparation window. But the double materiality assessment must still cover affected communities during the transitional period. If communities are material, high-level narrative disclosures are expected even where the detailed S3 requirements are phased in.

Worked example: documenting S3 for a Belgian aggregates company

Pieters Grind & Beton NV, a Limburg-based aggregates and ready-mixed concrete company with €38M revenue and 120 employees. Operates two gravel extraction sites (one active, one in permitting phase) and four concrete batching plants. The active extraction site is 800 metres from the village of Maasmechelen-Eisden (population approximately 4,200).

Step 1. Confirm S3 materiality at sub-topic level

The DMA identifies communities’ economic, social and cultural rights as material for the Maasmechelen-Eisden extraction site. Specific impacts: noise from blasting and heavy vehicle movements (12–15 loaded trucks per hour during operating days), dust emissions affecting four residential streets, and groundwater level changes detected in monitoring wells 300 metres from the site boundary. Indigenous peoples’ rights are assessed as not material (no indigenous communities in the operating area). Civil and political rights are assessed as not material.

The four concrete batching plants are located in industrial zones with no residential neighbours within 500 metres. S3 is not material for these sites.

Step 2. Disclose policies (S3-1)

Pieters has a Community Relations Policy (approved by the board in March 2024) that commits the company to consulting with affected communities before changes to blasting schedules, operating hours, or site expansion. The policy does not reference the UN Guiding Principles or the OECD Guidelines. It does reference the Flemish environmental permit conditions (VLAREM) and the EIA consultation requirements under Flemish law.

Step 3. Describe engagement and grievance channels (S3-2)

Pieters holds an annual community meeting in Maasmechelen-Eisden (most recent: October 2025, 47 attendees). The site manager is the designated contact point for community complaints. During the reporting period, 23 noise complaints and 8 dust complaints were received and logged in the site’s environmental management system. All complaints were responded to within 10 working days. No formal grievance mechanism meeting the UNGP Principle 31 criteria exists. The complaint log is an operational tool, not a rights-based mechanism.

No substantiated human rights incidents connected with affected communities were reported during the period (paragraph 19 datapoint).

Step 4. Disclose actions (S3-3)

Two actions documented. First, Pieters installed a 4-metre acoustic barrier along the eastern site boundary in Q1 2025 (€180K capex) to reduce noise exposure for the four most affected residential streets. Post-installation monitoring shows a 6 dB(A) reduction at the nearest receptor point. Second, Pieters implemented a water spray dust suppression system on the main haul road (€45K capex) in Q3 2025. Dust monitoring at the site boundary showed a 40% reduction in PM10 concentrations during operating hours.

The working paper records the capex amounts, the monitoring evidence, and the measured outcomes. No effectiveness tracking for the community meeting exists (attendance is recorded but no survey or feedback mechanism measures whether community concerns are being addressed).

Step 5. Disclose targets (S3-4)

One target set: reduce average noise level at the nearest residential receptor to below 55 dB(A) LAeq during operating hours by December 2027 (current measured level: 58 dB(A) post-barrier installation; pre-barrier level was 64 dB(A)). This target is linked to the acoustic barrier action in S3-3 and to the Flemish VLAREM noise limit for residential areas.

This file gives a reviewer a complete S3 trail for a company with one material community impact site. Working papers connect each disclosure to named source documents (EIA, noise monitoring reports, complaint log, community meeting attendance records, capex invoices). The disclosure is honest about what’s in place (complaint log, annual meeting, acoustic barrier) and what isn’t (no UNGP-compliant grievance mechanism, no community feedback survey). An assurance provider performing limited assurance would find a traceable evidence chain and no inconsistencies between disclosed policies and described actions.

Assurance considerations for S3

Two observations on the assurance approach for S3 are worth highlighting. First, community impact data is often qualitative rather than quantitative. Unlike E1 (where emissions can be measured in tonnes) or S1 (where headcount and turnover are numerical), S3 disclosures may consist of descriptions of engagement processes, lists of complaints received, and narrative accounts of actions taken. The assurance provider’s testing shifts from recalculation and reconciliation to consistency checking. Does the disclosed engagement match the available evidence? Does the disclosed policy match the documented procedure? Does the claimed action match the capex records?

Second, S3 is the standard most likely to generate reputational risk if the disclosure is inaccurate or incomplete. Communities talk to media. A sustainability statement that claims successful community engagement while a local newspaper carries reports of unresolved complaints creates a credibility gap that goes beyond assurance findings. The assurance provider should consider publicly available information (local media, planning authority records, NGO reports) as part of the evidence gathering for S3 disclosures.

Practical checklist for your current engagement

1. Run the DMA for affected communities at sub-topic level (economic/social/cultural rights, civil/political rights, indigenous peoples’ rights) and document which sub-topics are material for each operating site. Sites in industrial zones with no residential neighbours may legitimately exclude S3.
2. If the client has operations or supply chain connections to indigenous territories, confirm whether FPIC provisions exist in policy and whether FPIC assessments have been conducted. The absence of FPIC provisions when indigenous peoples are affected is a specific S3 disclosure gap that assurance providers will flag.
3. Verify whether a grievance mechanism accessible to affected communities exists and assess it against UNGP Principle 31 effectiveness criteria. A complaints log is not the same as a grievance mechanism. Document the distinction.
4. Record the paragraph 19 human rights incident datapoint as a binary disclosure for each material community group. If incidents occurred, document their nature, severity, and the company’s response.
5. Cross-reference S3 community impacts with E2 pollution disclosures and E4 biodiversity disclosures where environmental externalities are the cause of the community impact. The source data (emission measurements, ecological surveys) should be consistent across standards.
6. If the client’s operations involve land acquisition, displacement, or changes to local environmental conditions, check whether the S3-3 disclosure describes the company’s approach to tensions between community protection and business pressures (paragraph 17). This is an explicit disclosure requirement, not optional context.

Common mistakes to avoid

• Treating S3 as applicable only to extractive industries: ESMA’s 2025 enforcement review found that several companies with material environmental externalities (noise, dust, traffic, water quality) did not assess whether those externalities created community impacts under S3. The standard applies whenever communities are materially affected, regardless of the industry. A food processing plant with odour complaints from 200 households has a potential S3 exposure even if it has never displaced anyone.
• Describing one-way communication as engagement: companies that disclosed community engagement often described one-way communication (newsletters, website updates, public meetings) without explaining how community perspectives actually informed decisions. ESRS S3-2 asks specifically how the views of affected communities are taken into account in the company’s decision-making. Disclosure that describes information provision without describing two-way engagement falls short of the requirement.

Related Ciferi content

Related guides:

Put audit concepts into practice with these free tools:

Frequently asked questions

Further reading and source references

• ESRS S3, Affected Communities: the source standard governing disclosure requirements for community impacts, risks, and opportunities.
• ESRS 1, General Requirements: covers the double materiality assessment framework and transitional provisions.
• UN Guiding Principles on Business and Human Rights: the international framework referenced by ESRS S3 for policy alignment and grievance mechanism effectiveness (Principle 31).
• OECD Guidelines for Multinational Enterprises: the due diligence framework referenced by the amended ESRS S3 for community engagement and impact management.