The first criterion of the Climate, Community & Biodiversity (CCB) Standards version 3.1, G1, is where a project defines itself. Many later criteria point back to it: the map, the list of communities, the causal model, the dates. A mistake here spreads everywhere. The most common confusion is between the project area and the project zone.
Two boundaries, two purposes
G1 asks the proponent to define both boundaries and to map them. The standard's definitions are:
| Term | What the standard says |
|---|---|
| Project area | The land area in which project activities aim to generate net climate benefits |
| Project zone | The area encompassing the project area in which project activities that directly affect land and associated resources are implemented. It includes activities such as alternative livelihoods and community development |
The key difference is purpose. The project area is where the climate benefit is aimed. The project zone is the wider area where the project works on land and resources, including livelihood and development activities that sit outside the carbon footprint. The zone contains the area.
For grouped projects the zone also includes all potential future project areas.
Why the difference matters
Later criteria use the zone, not the area. For example, the community and biodiversity without-project scenarios and the net positive impact tests describe conditions in the project zone. Biodiversity impacts outside the zone are handled separately in an offsite criterion. If the zone is drawn too narrowly, communities that depend on the land can fall outside the baseline study. If it is drawn too broadly, the project takes on assessment work it cannot support.
The map the standard asks for
G1 asks for a map that identifies:
- the location of communities, - the boundaries of the project area or areas, - the boundary of the project zone, - any high conservation value areas identified in the community and biodiversity criteria, - additional areas predicted to be impacted by project activities, identified in the offsite climate, community and biodiversity criteria.
A footnote sets the precision rule. Location information must allow the boundaries of the project area to be identified unambiguously and with a reasonable level of certainty, through digital data such as GPS coordinates, KML files or shape files.
Defining stakeholders
G1 also sets the vocabulary used throughout the standard. The footnotes define:
- Communities: all groups of people, including Indigenous Peoples, mobile peoples and other local communities, who derive income, livelihood, cultural values or other well-being contributions from the project area at the start of the project or under the with-project scenario. - Community groups: sub-groups whose members derive similar benefits and whose values differ from other groups, such as Indigenous Peoples, women, youth or other social, cultural and economic groups. - Other stakeholders: all groups other than communities that can affect or be affected by project activities and may live inside or outside the zone.
The standard allows some judgement. Where many small communities share similar social organisation, political structure and livelihoods, they may be listed as one community. It also permits considering the significance of user populations and level of use, so distant or intermittent users with very limited dependence on the site need not be treated as communities.
The proponent must explain the identification and analysis process, and a footnote says the analysis should include an assessment of rights, interests and relevance for each group.
Dates and periods
G1 asks for the project start date and lifetime, the GHG accounting period, and the biodiversity and community benefits assessment period if relevant. Differences between them must be explained and justified. The definitions are:
- Start date: the start of implementation of activities that will lead to emission reductions or removals. - Project lifetime: the period over which activities are implemented. It starts on the date activities aiming to generate climate, community or biodiversity impacts begin. - GHG accounting period: the period over which changes in emissions reductions or removals are monitored for use as offsets.
A project also supplies an implementation schedule with key dates and milestones.
Causal relationships
G1 asks for a brief description of each project activity and its expected outputs, outcomes and impacts, showing the causal relationships that explain how the activities will achieve the predicted benefits. A footnote says these should be built on a theory of change analysis and on the same analysis of drivers and actors of land use change used for the without-project scenarios. Appropriate imprecision is permitted.
Risk and long-term viability
Finally, G1 asks the proponent to identify likely natural and human-induced risks to the benefits during the lifetime and to outline mitigation measures. Risks listed in a footnote include risks over the shorter and longer term, continued community willingness to participate and the ability to adapt to climate change and variability. The proponent also describes measures to maintain benefits beyond the project lifetime.
A checklist
This is our reading, not standard text:
- One map with every layer listed above, plus a data file in a standard format. - A short table of communities and community groups with the reason each was included or merged. - A timeline showing start date, lifetime, accounting period and milestones. - A one-page causal diagram that later sections can refer back to.
Takeaway
Draw the zone around where the project touches land and people, draw the area around where carbon benefit is aimed, and keep both consistent across every later section.
Turn climate goals into a verified portfolio
TREEO connects the full carbon cycle — eligibility, simulation, real-time monitoring and registry-ready reporting — combining expert consulting with dMRV technology so the evidence exists before anyone asks for it.



