Verra has delayed the effective date of version 5 of its Verified Carbon Standard (VCS) Program by six months, moving the deadline from January 1, 2027 to July 1, 2027, according to Carbon Pulse. The extension responds directly to project developers, validation/verification bodies (VVBs) and market participants who warned that the original date would collide with a backlog of audits started under the previous program version. For developers and buyers, the decision pushes back the point at which the world’s most widely used voluntary crediting program fully switches rulebooks, and it sets a hard line for every project request filed after that date.

What Verra Changed

The core change is a single date shift. Verra is changing the effective date of VCS Version 5 from January 1, 2027 to July 1, 2027, Verra announced on 27 October 2026, describing the move as delivering on a clear request from project developers, VVBs and market participants.

The reason is operational congestion. A large number of projects are seeking to complete audits and submit project review requests that were initiated under VCS Version 4, and the volume of projects trying to meet the original deadline placed significant pressure on VVB capacity, according to Verra. Verification capacity, not methodology readiness, is what broke the original schedule.

Why the Backlog Forced the Delay

Transitioning to a new program version requires significant effort from project proponents and VVBs, and Verra judged that the transition should not disrupt ongoing audits and project review processes, according to its announcement. Forcing mid-audit conversions would have meant projects updating their designs and rewriting documentation onto new templates halfway through an active verification cycle.

The extension is designed to remove that friction. It will enable project proponents to prepare accurate, high-quality documentation for ongoing audits and reduce unnecessary costs and administrative burdens, Verra states. Projects that complete their ongoing audits under Version 4 can then dedicate full attention to updating to Version 5 at a later point.

The Hard Rules After July 1, 2027

The new date comes with no further flexibility. Verra expects all stakeholders to reach full conformance with VCS Version 5 and to use Version 5 templates for all project requests submitted after July 1, 2027, and it will not provide additional implementation exemptions beyond those already set out in the effective dates document, according to Verra.

Registration requests submitted on or after July 1, 2027 must use VCS v5.0 templates regardless of the template version used for the initial audit or public comment period, with no exceptions to this effective date, according to the VCS Version 5 resources page. For developers, the message is that the delay is a one-off rescheduling, not an open-ended transition window.

Two Template Tracks and the CCBS Alignment

The template system introduces a split that developers must track carefully. Verra has released combined templates for projects using both the VCS and the Climate, Community & Biodiversity Standards (CCBS) Programs, aligned with Version 5 reporting requirements on project design, safeguards and stakeholder engagement, according to Verra. From July 1, 2027, all VCS Program-related project review requests, including combined VCS and CCBS submissions, must use the applicable Version 5 template.

Each combined template exists in two versions. Projects with a start date before July 1, 2027 use the v5.0A templates, while projects starting on or after that date use v5.0B, according to Verra. Earlier projects may adopt v5.0B voluntarily, but all such projects must transition to v5.0B at their next crediting period renewal or upon their next baseline reassessment request submitted after January 1, 2030.

Digital Templates Stay on the Original Clock

One element of the timeline did not move. Digital versions of the VCS Version 5 templates remain on track to be available on January 1, 2027, allowing projects using digitalized methodologies to submit documentation digitally via the Verra Project Hub, according to Verra. That gives early adopters a six-month window in which digital tooling exists before its use becomes effectively mandatory for new requests.

Implications for Developers and Buyers

For developers, the extension converts a compressed compliance sprint into a sequenced transition. Projects already in audit under Version 4 can finish on the old rules without a costly mid-stream conversion, but the July 1, 2027 cut-off and the January 1, 2030 outer bound for v5.0B adoption now define the planning horizon. VVB capacity remains the bottleneck variable: the backlog that caused this delay does not disappear, it is deferred.

For buyers, the delay means Version 4 and Version 5 documentation will coexist in the pipeline longer than expected. Vintage and template version will become a due diligence data point for credits registered around the transition, and the split between v5.0A and v5.0B projects adds a second layer to that screen.

What to Watch

  • Release of digital VCS Version 5 templates on January 1, 2027 and their uptake via the Verra Project Hub.
  • Whether VVB capacity clears the Version 4 audit backlog before July 1, 2027.
  • The share of early-start projects opting into v5.0B templates before they are required.
  • Any congestion effects around the July 1, 2027 deadline, when all requests must switch to Version 5 templates.
  • Baseline reassessment submissions after January 1, 2030, the final trigger for full v5.0B transition.