VCS Project Registration Process Step by Step

Updated 2026-11-02 · 4 min read · By the akar.earth specialist team

VCS project registration step by step: pipeline listing, public comment, validation, Verra review and first issuance, plus the Indonesian approvals to plan for.

To register a project under Verra’s VCS Program, the proponent lists it on the Verra Registry, completes a public comment period, has an approved validation and verification body (VVB) validate the project description, and then requests registration, which Verra reviews before approving. Credits come later, after a separate verification of actual results.

The sequence is the same for every VCS project, but AFOLU projects in Indonesia face extra layers: land rights, community consent and national carbon rules. This page walks through each step.

Before you start

• Pick the methodology. For example VM0047 for ARR or VM0048 for REDD+. Check the version and any grace periods.
• Check the VCS Standard version. Verra issued VCS Standard v5.0 and Methodology Requirements v5.0 on 16 December 2025. v4.7 of the Standard remains active until 1 July 2027. Confirm which applies to your project.
• Check the fee schedule. Verra’s Program Fee Schedule v1.2 was issued 15 September 2026. Fees apply at several stages.
• Confirm the start date rules. VCS links the project start date to validation deadlines. Check the current requirements.

Registration step by step

1. Open a registry account. The proponent opens an account on the Verra Registry and completes know-your-customer checks.
2. Draft the project description. Verra calls it the project description; other programmes call it a project design document. It covers eligibility, baseline, additionality, quantification, monitoring, safeguards and stakeholder engagement. Read project design documents.
3. List the project in the pipeline. Submit the draft project description so the project appears on the registry as under development or under validation.
4. Public comment. The project description is posted for public comment. Respond to every comment received.
5. Contract a VVB. Choose an approved VVB with the right sectoral scope. See validation and verification bodies.
6. Validation. The VVB reviews documents, visits the site, raises findings and checks responses. Findings are usually corrective action requests and clarification requests.
7. Validation report. The VVB issues a validation report and statement once findings are closed.
8. Request registration. Submit the final project description, validation report and other required documents, such as the non-permanence risk report for AFOLU.
9. Verra review. Verra checks completeness and may review accuracy, raising its own questions.
10. Registration. The project is listed as registered.

Issuance needs a later step: monitoring, a monitoring report, verification by a VVB and a request for issuance. Validation and first verification can sometimes run together.

Indonesia-specific steps

Running in parallel with Verra:

• Land and carbon rights. Show who holds rights to the land and to carbon. Read carbon ownership in Indonesia.
• Forestry carbon rules. Permenhut 6/2026 sets procedures for forestry carbon trading, and names social forestry groups, customary forests and communities as legitimate participants.
• National registry. Exchange-traded units must be recorded in SRUK, which replaces SRN-PPI. POJK 10/2026 applies from 6 July 2026 to exchange trading.
• Authorisation and corresponding adjustments. Needed if credits will be used toward another country’s target or certain compliance uses. Read authorisation letters.
• Free, prior and informed consent. Community consent processes must be documented before validation.

Common delays

• Incomplete land tenure evidence.
• Methodology version changes during drafting.
• Long gaps between VVB findings and responses.
• Missing stakeholder consultation records.
• Uncertainty over national approvals.

Documents to have ready

Before requesting registration, assemble:

• the final project description on the current template;
• spatial files for the project boundary and strata;
• the validation report and statement;
• the non-permanence risk report for AFOLU projects;
• evidence of land rights and carbon rights;
• consultation and consent records;
• the carbon calculation files used for estimates;
• any deviation documentation.

Missing items are the most common reason for slow Verra review. Name files consistently and cross-reference them in the project description, so that Verra and the VVB find each piece of evidence quickly. Keep a register of every comment received during public comment and how it was answered.

Who does what

The project proponent owns the project and its registry account. A technical consultant often drafts the project description and models. The VVB is independent and cannot design the project it audits. Verra reviews and registers. In Indonesia, government bodies handle national approvals and SRUK records. Clear roles, written into contracts, prevent gaps and conflicts of interest.

Typical timeline

Expect at least a year from first draft to registration for a well-prepared AFOLU project. Complex REDD+ or grouped projects often take longer. Read the carbon project lifecycle for the full arc from idea to issuance.

Our PDD development service prepares project descriptions and evidence packs. See the standards hub for related rules.