A carbon project can be financially structured around community land, employ people from surrounding villages, and still fail CCB's Community section — because the section isn't asking whether the project touches a community, it's asking whether the project leaves affected communities demonstrably better off than they would have been without it, and whether the project identified every group whose wellbeing it could plausibly affect, not just the ones who signed a benefit-sharing agreement.
The Without-Project Community Scenario
Like the Climate section, Community requires its own separately constructed baseline — in this case, a description of what community wellbeing, livelihoods and access to resources would look like without the project. This has to be built from actual engagement with affected stakeholders, not inferred from land-use maps or assumed from the project area's general socioeconomic profile. A project that skips direct stakeholder engagement at this stage is building its without-project scenario on guesswork, which undermines everything the Community section tries to measure against it.
Who Counts as "Affected"
| Group | Why they're in scope |
|---|---|
| Landholders inside the project boundary | Direct, obvious impact on land use and access |
| Communities with customary or informal land use nearby | Project activity can restrict access even without formal tenure |
| Groups historically marginalized in local land governance | Net positive impact has to be checked at this level, not only in aggregate |
| Communities affected by activity displaced outside the project boundary | Leakage of harm, not just leakage of emissions |
The scope question is where projects most often underestimate the Community section's reach. A project that benefits the formal landholders it negotiated with while restricting informal access for a nearby group with customary but unregistered use rights has not demonstrated net positive community impact — it has simply not yet surfaced the group whose wellbeing declined. CCB's Community section is explicitly built to require disaggregated assessment, not an aggregate net calculation that could mask a loss to one group behind a gain to another.
Net Positive, Not Just Consent
Free, Prior and Informed Consent (FPIC) is necessary but not sufficient under this section. A community can consent to a project and still experience a net negative impact if the consent process didn't surface the full range of effects, or if circumstances changed after consent was given. CCB's Community section requires ongoing monitoring of actual community impact against the without-project scenario, not a one-time consent event treated as proof the net-positive bar has been cleared for the life of the project.
Why This Section Catches Projects the Carbon Methodology Wouldn't
A carbon methodology's safeguards are typically framed around not causing harm that would undermine the carbon claim itself — land conflict that threatens project permanence, for instance. CCB's Community section is framed around genuine wellbeing improvement, independent of whether a given community impact would ever threaten the carbon accounting. A project can be carbon-sound and still fail this section if it cannot show the communities affected by it are better off, not merely unharmed in a way that would jeopardize credit issuance.
What a Project Team Should Prepare
The practical preparation is a disaggregated stakeholder map built before design decisions are finalized, not after — covering every group with a plausible claim to being affected, not only those with formal tenure — paired with an ongoing monitoring plan that can show, at each verification cycle, how community conditions for each group compare to the without-project scenario established at validation.
Move beyond estimates
Verifiers test sampling design, uncertainty and whether a number traces back to the field. TREEO dMRV captures that evidence in real time, in one auditable chain.



