VCS Standards for Carbon Credits - Verra Standards

» VCS Sectoral Scopes & Project Classification System Guidance

Purpose and structure of the guidance

This guidance introduces the VCS project classification system, described as a framework for classifying VCS-certified projects by:

• sectoral scopes

• project categories

• project activity types

It also includes:

• FAQs explaining how to determine classifications,

• equivalences between VCS sectoral scopes and other frameworks (CDM and PACM), and

• a full list mapping sectoral scopes to categories and activity types.

Why classification matters

The document explains that Verra uses the classification framework to determine which requirements apply to a project based on its characteristics. It also supports searching and filtering projects and VCUs in the registry by sectoral scope, project category, and project activity type.

Definitions and how to apply them (FAQ section)

• Sectoral scopes are used to group methodologies by industrial sector or GHG source; methodologies specify applicable sectoral scopes, and VVBs are approved to audit specific scopes based on competence.

• Project categories group activity types, sometimes linked to rules that apply only to certain categories; AFOLU projects may have specific category assignment rules referenced by the VCS Standard (v5.0 reference in the guidance).

• Project activity types are the most specific grouping for cross-comparison and for requirements that apply only to certain activity types.

How to determine classification:

• Determine sectoral scope from the applied methodology.

• Determine project category by intervention/technical sector and any methodology guidance.

• Determine project activity type by best-fitting grouping; multiple categories and activity types may apply if the project uses multiple methodologies or implements multiple activities.

Illustrative examples in the guidance

The guidance provides examples showing how a proponent would report classifications:

• An agroforestry project applying multiple methodologies, with sectoral scopes in forestry/land use and agriculture, multiple categories (ARR, ALM), and activity types (ARR for agroforestry, improved grazing).

• A biochar project with sectoral scopes in waste handling and engineered removals, categories (waste treatment, biomass-based removals), and activity types (organic waste management, biochar production/application).

Sectoral scope listing (classification table)

The guidance lists sectoral scopes and associated categories/activity types across areas such as:

• Energy supply, energy distribution, and energy demand

• Manufacturing industries, chemical industries, construction, transport

• Mining and mineral production, metal production

• Fugitive emissions (fuels, industrial gases/ODS), solvents

• Waste handling and disposal

• Forestry and other land use (ARR, IFM, REDD+, wetlands), agriculture, and other removal-related groupings

VCS Monitoring Report Template

Role of the monitoring report in the VCS cycle

The monitoring report is a core document used to present monitored results, data, calculations, and evidence in a structured way so that a VVB can verify emission reductions/removals and so issuance can be requested under the program procedures. This aligns with the procedural description that issuance requests include the monitoring report among the key submission documents.

Main required sections (template structure)

The template sets an expected structure including:

• Project identification and key details (project title, IDs, proponent, location)

• Monitoring period definition and alignment with crediting/vintage periods

• Description of implemented activities vs validated design

• Monitoring methodology application, data and parameters, and calculation approach

• Results tables for quantified reductions/removals (and where applicable, removals) and deductions (e.g., leakage)

• QA/QC and data management description

• Uncertainty treatment (where required), assumptions, and reconciliation notes

• Appendices and calculation sheets/spreadsheets references

Emissions/removals results presentation

The template requires reporting of:

• gross quantified outcomes,

• deductions (e.g., leakage where applicable),

• net outcomes used for crediting,

• and traceable documentation of parameter values and sources.

Evidence packaging and appendices

The monitoring report template anticipates that supporting files (calculation sheets, geolocation files where relevant, and other required documents) are packaged as appendices or referenced materials for verification and issuance review.

VCS Program Guide

Program role, scope, and governance positioning

The Program Guide explains that Verra manages the VCS Program as an independent nonprofit and maintains an impartial role (not a project developer and not a VVB), while overseeing project integrity, reviewing submissions, and overseeing VVBs. It also describes Verra’s ability to deny listing/registration or cancel VCUs where rules are not met or integrity is impacted, and to make reasons public on registry project pages.

VCU attributes (quality principles)

The Program Guide provides a table of VCU attributes that the program rules are designed to ensure. These include:

• Additional

• Durable (with safeguards for reversals, accounting/replacement where possible)

• Independently verified (by accredited VVB with appropriate expertise)

• Traceable and not double counted (secure, unique registry tracking; prevents double issued/claimed/used)

• Robustly quantified (in conformance with rules/methodologies)

• Participatory-based (stakeholder engagement, FPIC, grievance)

• Safeguarded from unmitigated harm (human rights, Indigenous rights, equity; mitigation of negative impacts)

• Aligned with sustainable development goals

• Aligned with net zero transition (avoiding lock-in of incompatible technologies/activities)

These align with the program’s public description of VCU quality assurance principles and the role of validation/verification and Verra review in confirming these characteristics.

Project lifecycle and submission flow (overview)

The guide describes a typical lifecycle:

• validation and verification by a VVB (sometimes combined),

• submission of documents through the registry,

• Verra completeness review and possible accuracy review,

• publication of documents on the public registry and issuance of VCUs into the proponent’s account when conformance is determined.

Verra Registry functions

The Program Guide describes the registry as:

• the public interface to project/program/VCU information,

• the generator of VCU serial numbers ensuring uniqueness,

• a transparency platform for documentation, issuance records, retirement records, and buffer accounts,

• and the operational system for holding, transferring, and retiring VCUs, including custodial records of legal ownership.

This aligns with the public “Program Details” description of projects/programs and issuance of VCUs through a rigorous process.

VVB eligibility and accreditation framing

The Program Guide includes eligibility framing for VVBs, including accreditation and approval expectations (e.g., recognition under ISO-based accreditation structures and listing as active/approved).

(For your website, this is best presented as “independent third-party validation/verification under recognized accreditation,” without over-claiming beyond what is stated.)

Liability / erroneous issuance and review rights

The guide describes that registered projects and issued VCUs are subject to review. It also describes a framework where project proponents may be responsible for compensating for excess issuance under certain conditions (fraud, negligence, misrepresentation, mistake), with a statute of limitations approach.

» VCS Standard

The official VCS “Program Details” page lists VCS Standard v4.7 as active (with later version 5.0 issued) and describes the Standard as setting out specific requirements for developing projects and for validation, monitoring, and verification of GHG reductions/removals.

Your uploaded v4.7 document is the detailed rulebook for:

• project eligibility and design requirements,

• additionality and baseline requirements,

• quantification, monitoring, and verification requirements,

• and other cross-cutting safeguards and program integrity expectations.

Typical structure and “what it governs”

Within v4.7, the Standard organizes rules around:

• how a project is defined and bounded,

• how methodologies must be applied,

• how baseline and project scenarios are constructed,

• how reductions/removals are quantified (including leakage/uncertainty where relevant),

• how monitoring evidence must be collected and reported,

• and how validation/verification supports issuance readiness.

Additionality and baseline logic (program principle)

The program-wide statement is that VCUs represent reductions/removals beyond business-as-usual and driven by carbon-market incentive.

The Standard operationalizes this concept through eligibility, methodology application, and validation/verification requirements.

Durability, reversal risk, and accounting for reversals

The VCU attribute definition in the Program Guide specifies that where reversal risk exists, safeguards must minimize risk, reversals must be accounted and reported, and—where possible—replaced, over the longer of project longevity and crediting period.

The Standard and procedural documents connect this to program structures for eligible project types (see pooled buffer accounts in the Program Guide and Registration/Issuance Process).

Traceability and no double counting (registry-anchored integrity)

The program’s stated approach is that VCUs are transparently recorded and tracked to ensure uniqueness and to prevent double issuance, double claiming, and double use.

The registry role in generating serial numbers and tracking retirement supports this.

Stakeholder engagement and safeguards

The Program Guide explicitly includes participatory-based requirements (active engagement, FPIC, grievance mechanisms) and safeguard expectations (mitigate negative impacts, uphold rights, equity).

The Standard is the place where these requirements are specified in operational terms for project documentation and audits.

» Registration and Issuance Process

Purpose and positioning relative to the VCS Standard

This document defines the procedures for pipeline listing, registration, and issuance, and clarifies it is intended for market participants and process use—while the VCS Standard defines the underlying project development rules.

Contents and main process stages

The contents show major sections covering:

• Opening a registry account

• Pipeline listing process

• Project registration process (steps 1–7)

• AFOLU and GCS pooled buffer accounts

• Quality control of registered projects

• Further information (communications agreement, proponent change, comments outside public comment periods, exemptions)

• Document history

Registry account opening and system entry

The registry is positioned as the operational platform where account holders interact to list/register projects and issue/hold/transfer/retire units, and as the public repository of project/VCU documentation.

Issuance request documentation package

The issuance procedure describes that issuance submissions can include:

• monitoring report,

• verification report,

• verification representation,

• issuance representation,

• calculation sheets,

• geolocation file,

• and other required documents—followed by automated checks and serial number generation.

Retirement and cancellation mechanics

The process states:

• the registry displays the status of every VCU,

• retirements are initiated by the registry account holder and recorded by the registry,

• retirement fees apply,

• incremental retirements can be done by designating specific VCUs, subject to any thresholds/timeframes Verra may specify.

It also distinguishes cancellation pathways and potential initiators (account holder, other program, or Verra) depending on context.

Labels (certification and market labels)

The issuance process describes that VCUs may be labeled either:

• to designate conformance with another certification standard (certification label), or

• to indicate eligibility for a national/sectoral/investor-specific market (market label).

Label requests require documentation demonstrating conformance for the period covered; some labels may be applied retroactively depending on type; and fees may apply before labeling.

This aligns with the public program page explanation of labels as certification or market labels.

Pooled buffer accounts and quality control

The contents include pooled buffer account procedures for AFOLU and GCS (assignment, release, cancellation/holding) and a quality control review mechanism for potential non-conformance.

» CCB Standards

Purpose and role

The CCB Standards are presented as a framework to foster projects that deliver credible and significant climate, community and biodiversity benefits in an integrated manner, with best practices for net positive outcomes.

The introduction cites climate/ecosystem risk framing referenced from assessment work by IPCC.

Structure of the standard (sections and criteria)

The Table of Contents shows:

• Introduction (justification, role, safeguards alignment, validation/verification)

• General (G1–G5): project goals and viability; without-project land use/additionality; stakeholder engagement; management capacity; legal status/property rights

• Climate (CL1–CL4 + GL1): without-project climate scenario; net positive climate impacts; leakage; climate monitoring; gold-level adaptation benefits

• Community (CM1–CM4 + GL2): without-project community scenario; net positive community impacts; other stakeholder impacts; community monitoring; gold-level exceptional community benefits

• Biodiversity (B1–B4 + GL3): without-project biodiversity scenario; net positive biodiversity impacts; offsite biodiversity impacts; monitoring; gold-level exceptional biodiversity benefits

• Governance/development, acknowledgements, document history

Conformance language and audit framing

The CCB Standards specify how to interpret requirement language:

• “shall” indicates mandatory requirements,

• some content is guidance (“can be used”),

• validation focuses on design and planned measures,

• verification focuses on implemented measures and demonstrated outcomes,

• and monitoring-report-relevant requirements are indicated (including italics usage described).

Validation and verification cadence; label concept

CCB use requires independent VVB validation and verification. Verification must be performed at least every five years. Successful verification enables adding a permanent CCB label marker to a GHG credit on a registry, indicating the credit came from a project verified to CCB rules.

Publication and transparency

The standard describes publication of key documents and audit information (project docs, public comments, VVB name, audit reports/statements, gold level criteria achieved, dates, and other standards achieved) on the VCS project database/registry context.

What the core criteria require (high-level)

• G1: clear objectives for climate/community/biodiversity, risk identification and management, and project overview details.

• G2: a without-project land use scenario and additionality reasoning to establish that benefits are incremental.

• G3: stakeholder engagement requirements and processes.

• G4: management capacity and best practices.

• G5: legal status and property rights.

Climate, community, and biodiversity sections then require scenario setting, net positive impacts accounting, leakage/offsite impacts assessment, and monitoring frameworks.

» Sustainable Development Verified Impact Standard

Purpose (as positioned in the program ecosystem)

SD VISta is framed as a standard for certifying sustainable development impacts, separate from (but potentially complementary to) carbon crediting. The public Verra program page positions it as a “premier standard for certifying sustainable development impacts.”

Document’s function: turning sustainable development outcomes into verified claims/assets

Your uploaded standard defines requirements to:

• identify and define sustainable development outcomes and indicators,

• monitor and measure outcomes,

• verify results through third-party assessment,

• and use the results to support defined claim/asset constructs (as described within the standard’s definitions and program logic).

Core requirement areas (high-level)

The standard’s requirement design typically covers:

• defining the intervention and its theory of change/results chain,

• choosing indicators and methods,

• defining monitoring periods and evidence,

• applying safeguards and stakeholder engagement expectations (aligned with program approaches),

• verification/assurance steps and reporting.

Adaptation Notice under the VCS Standards

This text has been adapted in accordance with the guidelines set forth by the VCS Standards. In our efforts to ensure transparency, accountability, and alignment, we have carefully reviewed and incorporated VCS Standards into the content. This adaptation process reflects our commitment to high-quality, accurate, ensuring that the information presented adheres to internationally recognized standards.