A waterfall in two streams drops down a rock face in the centre, with a smaller cascade at lower left, framed by dense green foliage and blue sky.
← Back to blog

How to Read the CCB Standards: Validation, Verification and Version History

Sustainability•10 November 2026•TREEO Indonesia•4 min read

The Climate, Community & Biodiversity (CCB) Standards version 3.1 are long, and many readers dip in at one criterion. A few paragraphs in the introduction explain how the whole document is meant to be read, and the closing sections explain where it came from. This article collects both.

Two audit stages

The introduction says use of the CCB Program requires independent validation and verification bodies to determine conformance with the CCB rules at two stages.

- Validation is the systematic, independent and documented process of evaluating the design of a land management project against the criteria of the standards. - Verification is the systematic, independent and documented process of evaluating a project's delivery of net climate, community and biodiversity benefits. It is done in line with the project's validated design and monitoring plan and the criteria of the standards.

The standard adds a timing rule: verification must be performed at least every five years.

What verification unlocks

Successful verification allows a permanent marker, the CCB label, to be added to a greenhouse gas credit listed on a registry. The label indicates that the verified reductions or removals represented by the credit came from a project that satisfies and is verified to the CCB rules. Further detail on adding the label sits in the CCB Program Rules, a separate document.

The documents audited

The standard defines the two documents at the centre of the audit:

- The project description describes the project design and how it meets each requirement. It uses the CCB project description template or the combined CCB and carbon standard template. - The monitoring report describes how the project has been implemented in line with its validated design and records the data needed to assess net positive benefits for a given period. It uses the matching monitoring report template.

Criteria and indicators

Each criterion in the standard has a concept statement and a set of indicators. A footnote explains that criteria are conditions that must be met, and indicators are the quantitative or qualitative parameters that let a reviewer judge whether a criterion is met. The audit bodies use the indicators to decide.

Reading the verbs

The "Using this Document" section is a short guide to the language, and it helps explain why the same criterion can feel different at the two stages.

Word or styleMeaning
"Shall"A requirement that must be followed for conformance
"Can be used"Applies to manuals, methods and tools that are recommended as guidance. The proponent may choose others
"Describe the measures needed", "explain or specify the criteria and process", "project design"Wording that generally applies to validation
"Describe the measures taken", "have been included", "demonstrate that conditions have been met", "implementation"Wording that generally applies to verification
Italic textRequirements that are more relevant for verification and that should be addressed in the monitoring report

The standard also notes that some activities must already be in place at validation, for example parts of stakeholder engagement. In those cases the verification-style wording, such as "describe how" or "demonstrate", may apply at validation too.

What is published

The introduction lists what appears on the registry database: project descriptions and other documents submitted for audit, those approved by the audit process, any public comments received, the name of the audit body, the audit report and statement, whether the project met the requirements for Approved or Gold Level (stating which Gold Level criteria were achieved), the audit date, and any validations or certifications against other relevant standards.

The consequence for a team is simple: write every submitted document knowing that it will be public.

Who governs the standards

Section 6 explains that the standards were developed by an alliance of conservation and development organisations. Management of the program passed to the carbon standard owner in November 2014. A steering committee that includes representatives of the alliance members supports the owner in governance, strategic direction and ongoing development.

Version history

The standard gives a short history, summarised here.

VersionDateNotes
First edition, v1.012 May 2005Released after a two-year development process with input from community and environmental groups, companies, academics and project developers; tested on projects in Asia, Africa, Europe and the Americas and peer reviewed by three research centres
Second edition, v2.02 December 2008Revised to respond to the evolving context for land-based carbon, with two public comment periods of 60 and 30 days; program rules added in June 2010
Third edition, v3.012 December 2013Revision aimed to incorporate user feedback and to make it easier for smallholder and community-led projects to reach carbon finance; two 60-day public comment periods in 2013
Third edition, v3.121 June 2017Main aim to align terminology and formatting with the carbon standard program; a 60-day public comment period in 2016

The v3.1 changes listed in the appendix include numbered sections, moving governance and acknowledgements to the end, removing the glossary because definitions moved to a separate program definitions document, and several term changes. Examples are approved auditor becoming validation or verification body, right of use becoming project ownership, and project implementation report becoming monitoring report. The definition of start date was updated and the start of the project lifetime clarified.

Which version applies

The older editions are still relevant only to projects already validated to them, per the standard's own scope. For new work, v3.1 is the edition in this slice.

Takeaway

Read each criterion twice, once as a design question and once as a delivery question. Keep documents public-ready, and plan verification at least every five years.

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.

Related Articles

CCB Validation, Verification and Version History | TREEO Indonesia