From Forest to Credit: The 14 Steps of Carbon Certification

Creating a verified carbon credit is not a simple process. From initial project screening to the moment a credit is retired and its impact claimed, a carbon project passes through multiple stages involving project developers, communities, registries, verification bodies, and buyers. Understanding this lifecycle is essential for anyone entering carbon markets — whether as a developer, investor, or buyer. This guide walks through the complete 14-step process that takes a nature-based project from concept to certified, tradeable carbon credits with community revenue distribution.

Step 0 — Project Screening and Due Diligence

Before any resources are committed, a project undergoes preliminary screening. This includes land verification (does the developer have legitimate tenure or usage rights?), conflict checks (are there overlapping claims or disputes?), reputational risk assessment, and eligibility evaluation against target methodologies. Projects that fail screening are stopped here — saving months of wasted effort.

Step 1 — Project Onboarding

Projects that pass screening enter structured onboarding. Information is collected across six blocks: project identity, technical inputs (species, area, baseline data), safeguards and FPIC documentation, financial structure, land tenure documentation, and crediting period definition. This structured approach ensures that all data required for later stages is captured upfront, reducing delays during PDD preparation and registry submission.

Step 2 — Feasibility GO/NO-GO

A comprehensive feasibility assessment evaluates the project across nine dimensions: methodology eligibility, baseline credibility, additionality, GHG quantification potential, remote sensing data availability, financial viability, FPIC readiness, risk factors, and expert review. The output is a GO, Conditional GO, or NO-GO recommendation. This prevents projects from entering the expensive certification pipeline without confidence in their viability.

Step 3 — Pre-PDD Draft (AI-Assisted)

With a GO decision, a Project Design Document is drafted. Modern platforms use AI to generate methodology-specific PDD sections — pulling from project data, satellite imagery, and methodology requirements. The PDD is generated in the format required by the target standard: Verra VCS PD Template, Gold Standard PDD Template, or Article 6.4 PDD Template. Data gaps and methodology flags are identified for expert resolution.

Step 4 — Registry Submission

The project is submitted to the relevant registry: Verra Project Hub, Gold Standard Impact Registry, or the UNFCCC Article 6 database. The registry reviews the submission and assigns a Project ID. Status is tracked through the platform. For Article 6 projects, the host country DNA must issue a Letter of Authorization before or during this stage.

Step 5 — PDD Final

The PDD is finalized with the Project ID injected, stakeholder feedback integrated, and a formal approval gate applied. A critical compliance requirement: the project manager cannot self-approve their own PDD. This requires sign-off from an independent party — typically a platform administrator or VVB lead. This separation of duties is mandated by Verra and is a fundamental integrity safeguard.

Step 6 — MRV (Monitoring, Reporting, Verification)

Once the project is registered, monitoring begins. Three modes cover different project types: continuous monitoring for forests (satellite imagery plus ranger field patrols), campaign-based monitoring for soil carbon (periodic field sampling and lab analysis), and production monitoring for biochar (manufacturing logs and stability testing). All field evidence is hashed and secured with tamper-proof digital records for immutability.

Step 7 — Monitoring Report Preparation

MRV data is aggregated into a formal monitoring report — a distinct document from the PDD. This report compiles satellite analysis, field measurements, community action documentation, and calculated emission reductions for the monitoring period. The monitoring report is what the VVB will audit.

Step 8 — VVB Validation and Verification

An independent Validation and Verification Body (VVB) audits both the PDD and the monitoring report. The VVB may issue Corrective Action Requests (CARs) or Clarification Requests (CLs) that the project developer must resolve with documented evidence. Verra now permits combined validation and verification in a single audit cycle, reducing costs and timelines. Gold Standard maintains separate processes.

Step 9 — Credit Issuance

Once the VVB signs off, the registry issues carbon credits with unique serial numbers. Buffer pool deductions are applied: Verra uses the Non-Permanence Risk Tool (VT0099) with deductions ranging from 10-60% depending on project risk factors. Article 6.4 applies Share of Proceeds (5% Adaptation Fund + 2% administrative) before any credits reach the project developer.

Step 10 — Digital Registry Integration (Conditional)

Verified credits may be enhanced with additional digital traceability for improved transparency. This step is conditional: Verra requires written authorization before any additional digital integration, and Article 6 ITMOs have specific registry restrictions. The digital traceability layer adds transparency but must respect registry rules.

Step 11 — Trading and Marketplace

Credits are sold through platform marketplaces or off-platform channels. Pricing is differentiated by standard (Verra vs Gold Standard vs Article 6), project type (REDD+ vs ARR), vintage, co-benefits documentation, and external quality ratings. Transaction commissions are captured by the platform.

Step 12 — Retirement and Cancellation

When a buyer uses a credit to offset emissions, the credit is permanently cancelled on the registry (retirement). For Article 6 credits, corresponding adjustments must be applied at retirement. This tracking ensures no credit can be used twice.

Step 13 — Revenue Split and Community Payments

Revenue from credit sales is distributed automatically: developer share, community share (minimum 20%), and platform fee. For Article 6.4 projects, the SOP is deducted first. Automated rules calculate splits and emit payment instructions. Third-party payment providers (Orange Money, MTN, PIX) execute real-world payments to community members. Digital proof of payment is generated for DFI and investor reporting.

The Renewal Loop

At crediting period expiry, the process loops back to Step 1 for renewal: updated PDD, new monitoring period, new VVB validation. Carbon projects are long-term commitments — crediting periods typically span 10-30 years with periodic renewal and re-verification.

Why Understanding the Full Lifecycle Matters

Each of these 14 steps involves specific actors, data requirements, compliance gates, and potential failure points. Projects that lack visibility into the full lifecycle face delays, cost overruns, and compliance risks. The platforms that manage all 14 steps end-to-end — with integrated compliance enforcement, AI-assisted documentation, and transparent community impact tracking — are the ones that will scale carbon markets to meet the compliance demand now emerging from CORSIA, CBAM, and Article 6.