The disclosure standard that governs how mining companies report on communities has a problem its drafters understood well. You cannot report your way to a good relationship. You can, however, report your way to a worse one. The EU Corporate Sustainability Reporting Directive, through its standard on affected communities, now asks companies to describe three things. How they engage the people their operations touch. What harms those operations cause. And what they do about them. For any extractive project, that standard, ESRS S3, is not optional to consider. It is almost always material.
Here is the trap. A company under reporting pressure will be tempted to produce disclosure the way it produces any other deliverable, by assembling what looks defensible and publishing it. The communities named in that report can read it. So can the auditors, the buyers, and the investors who have learned to tell a real engagement record from a polished one. This piece looks at what ESRS S3 actually asks companies to disclose about communities. It covers how to gather that information credibly, and why honest reporting strengthens the working relationship instead of straining it. The reporting protects the investment only when it also respects the people.
What ESRS S3 actually asks you to disclose
ESRS S3 is the topical standard on affected communities inside the CSRD. It covers the impacts a company has on communities through its own operations and through its upstream and downstream value chain. The scope reaches economic, social, and cultural rights, civil and political rights, and the specific rights of Indigenous Peoples. For a mine, that is the whole terrain of community relations, translated into disclosure obligations.
The standard is organized into five disclosure requirements, and knowing them shapes what you need to be able to show. S3-1 asks for your policies on affected communities. S3-2 asks how you engage those communities about impacts, including whether the engagement happens with the affected people or their credible representatives, and at what stage. S3-3 asks about your processes to remediate harm and the channels communities use to raise concerns. S3-4 asks what action you take on material impacts and how you judge whether it works. S3-5 asks about your targets, and how you set them.
Read those five together and a pattern emerges. Four of the five are about a relationship, not a metric. S3-2 and S3-3 explicitly point companies to the UN Guiding Principles on Business and Human Rights for engagement and grievance handling. You cannot answer them honestly from a spreadsheet. You answer them from a live practice of engaging communities, hearing their concerns, and acting on them. The disclosure is downstream of the work. If the work is not happening, the disclosure has nothing true to describe, and increasingly, someone will notice.
Report versus do, and why the two are joined
The CSRD and the CSDDD are often discussed as if they were rival burdens. They are two halves of one machine. The CSRD addresses what a company must report. The Corporate Sustainability Due Diligence Directive addresses what a company must do. In practice, the due diligence a company runs generates the substantive information that feeds its CSRD disclosures. The two reinforce each other.
That connection matters for anyone tempted to treat S3 as a writing exercise. Consider what the standard wants: who you engaged, what you heard, what harm you found, how you responded. That is exactly the information a genuine due diligence process produces as a byproduct. A company doing the underlying work has a report almost written for it. A company that skipped the work faces a choice between admitting the gap and manufacturing content to fill it. The first is uncomfortable. The second is a liability, because the CSRD sustainability statement is subject to independent assurance, and because the communities described in it are witnesses who were there.
This is where the reporting duty quietly becomes a governance tool rather than a paperwork tax. When the board knows that next year’s S3 disclosure has to describe real engagement, the incentive to fund that engagement changes. The reporting deadline pulls the underlying practice forward. Used well, ESRS S3 stops being the thing you dread each spring and becomes the annual forcing function that keeps community work from being cut in the budget round. Reporting rules and the field relationship stop being separate concerns. That is the same logic behind how ESG requirements reshape community engagement.
Double materiality means mining almost always reports
Some companies hoped the Omnibus rollback would let them off. It raised the CSRD threshold to more than 1,000 employees and 450 million euros in turnover, cutting the reporting population by around 80 percent. It made many S3 data points conditional and phased in some value-chain reporting. It did not remove double materiality. That principle was expressly retained. Only the mechanics were simplified.
Double materiality is the test that decides whether you must report on a topic at all. It has two lenses. Impact materiality asks how your operations affect people and the environment. Financial materiality asks how sustainability matters affect your business. A topic that is material through either lens must be disclosed. For a mining operation, affected communities clear that bar almost automatically. Large-scale land use, operations near Indigenous territories or in conflict-affected regions, and any history of community grievances are precisely the indicators that make S3 material.
So the question for most miners is not whether they will report on communities. It is whether their report will describe a relationship they can defend. A company that has run real engagement can disclose material impacts, explain its responses, and show its targets with a straight face. A company that treated community relations as a line item will find the materiality assessment forcing it to disclose a topic it has no good story for. The rules now make the absence of engagement visible in a way an annual report used to hide. That is a reason to build the engagement, not to game the assessment.
Gathering the information the way that also builds trust
The credible way to gather S3 information and the effective way to run community relations are the same activity. This is the part most compliance teams miss when they hire a consultant to draft the disclosure at year end.
Consider a scenario drawn from patterns across copper and lithium projects in the Andes. A company needs to report under S3-2 on how it engages the community and under S3-3 on its grievance channel. The desk approach commissions a survey, tallies meetings held, counts grievances logged, and writes it up. The numbers look fine. They also mean nothing, because a meeting attended is not a concern heard, and a grievance logged is not a harm remedied. Worse, the community reads a report describing engagement it did not experience, and the small trust that existed erodes.
The alternative gathers the same information as a natural output of real practice. Engagement that is two-way and iterative, run early enough to shape decisions, produces a genuine record of what communities raised and how the company responded. A grievance channel that people actually trust generates data that is a live signal, not a tally. Feeding what you hear back to the community, and showing what changed because of it, is not a courtesy. It is the mechanism that keeps engagement from becoming an extractive exercise where the company takes information and gives nothing back. The difference between a channel that surfaces problems early and one that logs them for a report is the subject of designing grievance mechanisms that actually resolve conflict. Do the engagement properly and the disclosure writes itself from a true record. Skip it and the disclosure is fiction with a deadline.
Honest disclosure is a trust instrument, not a confession
Companies fear that reporting problems invites attack. The opposite is closer to the truth. Stakeholders are increasingly able to distinguish genuine progress from performative disclosure. A report that describes only successes reads as public relations and is discounted accordingly. A report that names the challenges alongside the achievements reads as credible, and credibility is the scarce resource in community relations.
Good S3 disclosure covers what risks you identified and how you prioritized them, what measures you took, what outcomes you achieved, and what challenges remain. That last category is the one companies want to cut and the one that earns trust. A community that sees its own unresolved concerns acknowledged in a public report knows the company is not pretending. An investor who reads a balanced account trusts the numbers more, not less. Reporting relationship quality honestly, including where it is strained, is how relationship-quality reporting becomes an asset. The habit of tracking that quality rather than only outputs is what turns disclosure into management information, a theme developed in measuring the quality of the company-community relationship.
Honest disclosure also changes the internal conversation. When a company commits to reporting its community challenges, it has a reason to resolve them before the next cycle. The report stops being a retrospective gloss and becomes a live account of a relationship the company is actively managing. That is the difference between disclosure as a chore and disclosure as a discipline.
Turn your S3 obligations into a disclosure you can defend
Before your next reporting cycle, run your community disclosure through the ESRS S3 Social Disclosure Readiness Checklist. It is a downloadable 16-point instrument organized into five sections that track the standard itself. The sections cover policies and material impacts, engagement processes, the grievance and remediation channel, actions and targets, and disclosure credibility. Each checkpoint tests whether you have real practice behind the words you plan to publish, and you score it In place, Partial, or Absent. The Absent items are the sentences in your draft report that a community, an auditor, or an investor could challenge, because there is no field reality underneath them. Use it to find the gaps between your narrative and your practice while a cycle remains to close them. That beats defending a claim you cannot support after publication. Download the ESRS S3 Social Disclosure Readiness Checklist
The mediated path to a report worth reading
The companies that will disclose credibly on communities are the ones with something real to disclose. That comes from engagement that resolves disagreement rather than merely records it, which is a mediation discipline. Independent, structured facilitation produces the genuine record S3 wants, because it forces the concerns into the open, tests them against the facts, and reaches responses both sides accept. A grievance handled through facilitated dialogue leaves a trail of a problem actually resolved, which is exactly the content a defensible disclosure needs.
This is the work behind the Social Accord Architecture, the field-tested methodology I use to build the underlying relationship that reporting then describes. The SAA (Social Accord Architecture) runs on dual accountability. A process is credible only when it answers to both the community whose livelihoods are affected and the company whose investment is exposed. The moment it appears to favor one side, it loses the trust of the other. That balance is also what makes its record trustworthy to a third party. Corporate social responsibility narratives communities dispute, and campaign claims companies deny, both fail as disclosure. An independent, structured process produces a version of events both sides recognize, which is the only version worth reporting.
Legislation can compel disclosure. It cannot compel the honesty that makes disclosure worth anything. Build the engagement that gives you a true story to tell, and the reporting stops being a risk and becomes evidence of a relationship that works. To pressure-test your S3 readiness, or to set up a structured dialogue that produces a record you can stand behind, reach me at thomas@thomasgaultier.com.