Community-Level Monitoring: The Missing Piece in Supply Chain Due Diligence

Ask most companies about their supply chain and you will get a confident answer about Tier 1. The factory that assembles the product, the mill that processes the timber. That is the layer where questionnaires get answered and audits get scheduled. It is also, very often, where visibility stops.

Step back one or two links, toward the actual source of the commodity, and the picture changes. Who harvested the rubber on that plantation? Which vessel caught the fish? How many smallholder farms supplied the cocoa, and under what conditions? For most companies, nobody really knows. And the commodity source is where the most severe environmental and human rights risks live.

That mismatch is not a small gap. Under the EU Corporate Sustainability Due Diligence Directive (CSDDD), it is a compliance problem, because the directive does not stop at Tier 1. It requires companies to look at the full value chain, all the way to the source. This post is about why the commodity source stays invisible, and what closing that gap takes.

Where Supply Chain Visibility Ends

Most supply chain technology is built for the links a company directly controls. Enterprise resource planning systems track orders from Tier 1 suppliers. Audit schedules are built around their production calendars. The tools, the budgets, and the headcount all point at the first link, because that is the link with contracts and invoices.

The links beyond Tier 1 look different. A typical consumer goods company may buy from a few hundred Tier 1 suppliers, but the commodity flows behind those suppliers pass through thousands of farms, plantations, vessels, and mines. Each one is small, dispersed, and usually not under contract with the buyer. There is no invoice to trace and no facility to inspect.

The risks that regulators, investors, and customers actually care about are concentrated at exactly the point where the map goes blank. Deforestation happens on the farm, not in the processing plant. Labor exploitation happens on the vessel, not on the factory floor. Forced labor, child labor, land grabbing, illegal clearing, unsafe working conditions: the severe impacts sit at the commodity source, in the least visible part of the chain.

Why the Commodity Source Is a Blind Spot

It is tempting to assume the commodity source is simply a smaller version of Tier 1: harder to reach, but observable with the same tools. In practice, the standard tools break down there for three reasons.

1. Suppliers do not report upstream conditions

Your Tier 1 supplier can report on its own factory, its own payroll, its own compliance program. It cannot report on the fishing vessel that caught the fish it bought, or the smallholder cooperative two links further back. Suppliers have no window into their own upstream, and little incentive to dig for bad news. Asking them to certify the whole chain is asking them to vouch for conditions they have never seen.

Most due diligence today runs on self-reported questionnaires. The supplier fills it in, the company files it, and a risk assessment is generated from declarations rather than observations. A questionnaire is only as good as the person filling it in. At the commodity source, neither is reliable. The people filling in the form usually do not know what happens upstream of them.

2. Audits cannot reach the source

Audits work well for a single facility you can walk through in a day. They work far less well for ten thousand smallholder farms spread across a province, or a fleet of vessels at sea for months. Even a diligent audit is a snapshot: one site, one day, one set of documents. By the time the report is written, the snapshot is stale.

This is not a criticism of auditors; it is a scale problem. The commodity source is dispersed by nature. Smallholder agriculture, artisanal mining, and capture fisheries are made up of countless small operations that no audit program could physically reach on a meaningful cycle. Auditors can sample, but a sample of a thousand sites tells you almost nothing about the other nine thousand. The places where risk is highest are the places audits visit least.

3. Satellite data alone cannot see labor

Satellites have transformed our ability to watch the land. Deforestation, encroachment into protected areas, the expansion of plantations: all visible from orbit, and increasingly monitored continuously. But from orbit you cannot see wages, working hours, debt bondage, coercion, child labor, or safety conditions on the ground. The human dimension of supply chain risk is invisible to every sensor in the sky.

Satellite monitoring is an essential tool, and this post will come back to it, because verification matters. But on its own it covers the environmental half of the picture and misses the human half. A due diligence system built on imagery alone can tell you that a forest disappeared. It cannot tell you who cleared it, or who worked the land under what conditions.

Put the three reasons together and the pattern is clear. The commodity source is the blind spot in the middle of due diligence, and no amount of process at Tier 1 will change that.

The Community Is the Sensor

The fact that changes the equation: the people at the commodity source can see everything. The workers on the vessel know what is caught, how long the shifts run, and whether anyone is being held against their will. The smallholder farmer knows whether the forest behind the plot is being cleared. The plantation worker knows what is in the spray tank. Indigenous communities know the state of the land and water they have watched for generations.

These are the frontline communities: fishers, smallholder farmers, plantation and mine workers, indigenous groups. They live where the commodities are produced, which means they are the first to see the impacts due diligence is supposed to catch. A wage that goes unpaid, a river that changes color: none of it happens in secret from the people on the ground.

And yet, in most supply chain programs, they are the last to be asked. Their knowledge has been treated as anecdote rather than data. The most valuable observation network in the entire value chain is already in place and already watching. It is just not connected to anything.

Ground truth lives with the people on the ground. A worker who reports low pay, a farmer who reports a new clearing, a fisher who reports a vessel that never returns to port: no questionnaire, audit, or satellite can replace these observations. Community knowledge is not a nice-to-have supplement to the monitoring stack. It is the only source that covers the human and environmental reality of the commodity source at all.

How Community Monitoring Works

Putting that idea to work means building a reporting channel that fits the reality of the people using it. Community monitoring, as Earth PBC practices it, is designed around that reality. The mechanics matter.

Reporting from an ordinary smartphone

Field reporters use simple apps on smartphones they already have. The interface is built around a few taps rather than forms: select what you saw, describe it briefly, send it. No training manuals, no dedicated hardware. The barrier to participation is deliberately low, because the whole model depends on people actually using it.

GPS-tagged and time-stamped

Every report carries its location and timestamp automatically. A report about a clearing, a discharge, or a labor practice is anchored to a precise point on the map. It lets the data be analyzed spatially, so patterns across a region become visible, and it turns a personal account into a piece of evidence with coordinates.

Multilingual by default

Reporting happens in the language the reporter actually speaks. The platform handles reporting in many languages and translates the analysis for the companies reading it. A fisher in one country and a farmer in another can both report in their own words, and the buyer sees one coherent picture.

Offline capability

Connectivity is not a given at the commodity source. Vessels spend weeks beyond coverage, and remote valleys may have no signal at all. Reports composed offline are stored on the device and uploaded automatically when a connection returns. The reporting channel works where the operations happen, not just where the wifi is.

Behind the interface, AI-assisted analysis does the heavy lifting: clustering similar reports, translating between languages, flagging patterns that a human reviewer would otherwise miss, and routing urgent signals for attention. The point of the technology is not to replace judgment. It is to make sure a credible report from a remote site is not lost in the noise, and a pattern across a hundred reports is not missed.

Safety is built into the design. Reporters should never be put at risk by the act of reporting, so channels respect anonymity where it is needed, and the data is handled carefully throughout. A monitoring system that endangers its reporters is not a monitoring system.

Independent Verification

A report is a claim until it is verified. Any monitoring system that relies on a single source, including its own community reports, will eventually be challenged on that point. The answer is to combine independent sources, so each can check the other.

Earth PBC pairs community reporting with satellite imagery from Planet Labs. The Planet constellation passes over every point on Earth more than 200 times daily, covering more than 3 million square kilometers of imagery per day. That is not a once-a-year snapshot. It is a continuous watch on the land, and it operates independently of anything any human reports.

The two sources cross-reference cleanly. When a community report describes deforestation at a GPS point, the satellite record of that exact patch of land can confirm whether tree cover was removed, when, and how fast. When a report describes a fire, imagery can corroborate the scale. When imagery shows a new clearing with no community report, it becomes a question for the people nearby. Each source keeps the other honest.

Community ground truth combined with satellite verification reaches around 90 percent verification accuracy, because the two sources fail in different ways. A satellite cannot be bribed, and a community member can see what a satellite cannot. Together they produce something neither could produce alone: a record that holds up under scrutiny.

This is what separates evidence-grade data from self-reported questionnaires. Each record is location-stamped, time-stamped, and independently corroborated. When a regulator, auditor, or customer asks how you know, the answer is a documented trail rather than a declaration. That distinction is the entire ballgame under the new due diligence rules.

What This Means for CSDDD Compliance

The CSDDD is built around a straightforward expectation: companies must identify their adverse impacts, prevent the ones that have not happened yet, and remediate the ones that have. Delivering it requires a monitoring system that can actually do all three, and that is where most compliance plans quietly stall, because their systems only ever see Tier 1.

Identify: Article 8

Article 8 requires companies to identify and assess actual and potential adverse impacts across their value chains. Community monitoring turns this from a periodic exercise into a live one. Reports surface impacts as they happen: a wage dispute, a clearing, a safety failure. You do not discover the problem eighteen months later in an audit report. You learn about it while it is still current, which is the only time identification is worth much.

Prevent: Article 10

Article 10 requires preventing and mitigating potential adverse impacts. Early warning is the core of prevention. A pattern of reports from one region, one vessel, or one operation lets a company intervene before a violation escalates into a crisis. Prevention is not a policy document. It is the ability to act while there is still time.

Bring to an End and Remediate: Articles 11 and 12

Article 11 requires bringing actual adverse impacts to an end, and Article 12 requires remediation where the company caused or contributed to the harm. Evidence-grade data makes remediation possible in a way that vague allegations never could. You can confirm what happened, where, and to whom, then respond proportionately. Direct payments to affected communities are a concrete form of remediation that demonstrates action rather than asserting it. Earth PBC supports direct stablecoin payments to communities in more than 100 countries, cutting out intermediaries and delays.

Engage: Article 13

Article 13 requires meaningful engagement with stakeholders, and the directive is explicit that this includes workers and communities. Community monitoring is stakeholder engagement built into the operating model rather than bolted on as a consultation exercise. When the people at the source have a working channel to the buyer, engagement is continuous, documented, and verifiable.

Following the EU's 2025-2026 Omnibus simplification process, the CSDDD now applies to a single group, EU companies with 5,000 or more employees and more than €1.5 billion in turnover (and non-EU companies with more than €1.5 billion in EU turnover), from 26 July 2029. Compliance is not a one-time filing. It is a standing capability that generates evidence continuously. Companies that build that capability now will enter the compliance period with data already flowing. Companies that wait will face the same requirement with nothing behind it but paperwork.

Beyond Compliance

It would be a mistake to treat community monitoring as a checkbox for the directive. The same system that produces compliance evidence also changes the quality of the supply chain itself, for reasons that have nothing to do with regulation.

Trust is the first benefit. When communities are treated as partners with a voice, rather than as risks to be managed, relationships change. Reporters who see their reports lead to action keep reporting. Communities that are heard and paid fairly become more stable suppliers, and stable suppliers mean reliable supply. A buyer who can see the source of its commodity, and respond when something is wrong, is a buyer people want to work with.

There is also a fairness argument worth making out loud. The people who produce the world's commodities are usually the last to benefit from them. A system that pays communities directly for verified monitoring work, and routes remediation payments straight to the affected people, puts money where the work happens. That is not charity. It is a supply chain that rewards the people it depends on, which is the only kind that lasts.

None of this is abstract. The technology exists today, it works on ordinary phones, and it operates in more than 100 countries. The question is not whether community-level monitoring is possible. It is whether your due diligence system is going to keep looking at the supply chain from Tier 1, or finally see all the way to the source.

If you are mapping your CSDDD obligations and finding that the commodity source is a blank space on the map, that is the gap Earth PBC was built to close. We combine community reporting, satellite verification, and direct payments into one system, so identify, prevent, and remediate are things you can actually do. Get in touch and we can walk through what that would look like for your supply chain.