> For the complete documentation index, see [llms.txt](https://documentation.carbonregistry.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.carbonregistry.com/documentation/icr-program/updates/october-2026-clarification.md).

# October 2026 - Clarification

Clarification on applicable ICR templates and Validation and Verification Specifications

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FEKNRH5GxTyR64Brt0l8H%2FApplication%20of%20templates.jpg?alt=media&amp;token=bcc84959-03d3-43d1-ba10-374603815935" alt=""><figcaption></figcaption></figure>

### Purpose and context <a href="#purpose-and-context" id="purpose-and-context"></a>

The ICR Program has issued different versions of its project documentation, monitoring, validation and verification templates. These templates have been developed to align with the corresponding versions of the ICR Requirement Document and the ICR Methodology Requirements.

This clarification identifies the applicable templates and supporting Program documents for each version of the ICR Requirement Document and ICR Methodology Requirements, and states how the ICR Validation and Verification Specifications and supporting documentation apply.

### Application <a href="#application" id="application"></a>

A project's documentation is governed by the version of the ICR Requirement Document it applies. For validation that version is fixed, the one against which the project was validated and registered. For monitoring and verification it may move. A project that has applied v6.0 or later takes up the current version from its next verification, so the applicable MR and VerR versions change as the project rolls forward. A project registered against a version earlier than v6.0 continues under its registered version unless it is required or elects to transition.

Accordingly:

1. **Validation documents.** The PDD and ValR shall use the versions identified for the ICR Requirement Document version against which the project was validated and registered. Where validation and verification are conducted jointly, the corresponding PDDMR and VVR shall be used. These versions do not change once validation is complete.
2. **Monitoring and verification documents.** The MR and VerR shall use the versions identified for the ICR Requirement Document version the project applies at that verification, which is not necessarily the version it was registered under. A project that has applied v6.0 or later takes up the current version from its next verification, and the next verification is the one set out in the MRV plan in the project's PDD. The applicable version is the one in force at that verification, irrespective of the version in force when the monitoring period began or when the monitoring report is submitted. Where a monitoring report is submitted without verification (Section 6.10 of the ICR Requirement Document), the MR version is the one identified for the ICR Requirement Document version in force when the monitoring report is submitted. A project registered against a version earlier than v6.0 continues under its registered version unless it is required or elects to transition. Applying a later version at verification does not of itself require re-validation.
3. **Applicable VVS.** The ICR Validation and Verification Specifications are not version-locked to the ICR Requirement Document. The current VVS applies to every validation and verification engagement conducted from its effective date, irrespective of the ICR Requirement Document or ICR Methodology Requirements version governing the project or methodology under assessment. The VVS governs how validation and verification are conducted; it does not alter the criteria the project or methodology must meet, which remain those of the applicable version identified in the matrix below.
4. **Consistency.** Templates from different Program generations shall not be combined unless expressly agreed by ICR. The latest published template is not automatically applicable where a project remains permitted to apply an earlier version of the ICR Requirement Document. This paragraph does not apply to the VVS, which applies as set out in paragraph 3.
5. **Transition.** Where a project is required or elects to transition to a later version of the ICR Requirement Document, subsequent documentation shall use the corresponding templates and supporting Program documents identified for that later version.
6. **Existing documentation.** Publication of a new template or VVS does not require previously completed and accepted documentation to be reformatted.
7. **Supporting Program documents.** The ICR Definitions, ICR Additionality Specifications and ICR Article 6.2 Procedures shall use the versions identified for the applicable ICR Requirement Document or ICR Methodology Requirements version.

**Why v6.0 is the boundary.** v6.0 restructured the requirements sufficiently that assessing a project registered under an earlier version against a later version would amount to a fresh validation rather than an update at verification. Those projects therefore continue under the version they are registered against, and may transition if they choose. The changes from v6.0 onwards have been incremental: applying a later version at verification does not of itself require re-validation, which is why projects on v6.0 or later move forward with each release.

### How to read the matrix <a href="#how-to-read-the-matrix" id="how-to-read-the-matrix"></a>

Read the matrix by the version a document is prepared under, not by the version the project was registered under. For validation documents those are the same. For monitoring and verification documents they diverge as soon as a project moves to a later version: a project's MR and VerR move down the rows over its lifetime while its PDD and ValR stay where they were unless the project is re-validated.

For example, a project validated and registered under v6.0 has a PDD 6.0 and a ValR 6.0, and those remain. Its monitoring and verification documents moved to 6.1 at the first verification after v6.1 took effect on 14 November 2025, and move to 6.2 at the first verification after v6.2 takes effect. A project reaching verification between those two dates uses MR 6.1 and VerR 6.1, not MR 6.0 and VerR 6.0. Where a monitoring period straddles an effective date, the verification is still conducted under the version in force at the verification, and the whole monitoring period is reported on that basis.

### Application matrix <a href="#application-matrix" id="application-matrix"></a>

| **ICR Program document**         | **Version** | **Effective date** | **PDD** | **MR**      | **PDDMR** | **ValR** | **VerR**    | **VVR** | **CN** | **MD** | **MValR** | **Definitions** | **AS** | **A6.2** |
| -------------------------------- | ----------- | ------------------ | ------- | ----------- | --------- | -------- | ----------- | ------- | ------ | ------ | --------- | --------------- | ------ | -------- |
| **ICR Requirement Document**     | 3.0         | 11 Aug 2021        | 2.0     | 2.0         | NA        | 2.0      | 2.0         | NA      | NA     | NA     | NA        | NA              | NA     | NA       |
|                                  | 4.0         | 14 Oct 2022        | 3.0     | 3.0         | 1.0       | 3.0      | 3.0         | 1.0     | NA     | NA     | NA        | 1.0             | NA     | NA       |
|                                  | 5.0         | 9 Oct 2023         | 4.0     | 4.0         | 1.0       | 4.0      | 4.0         | 1.0     | NA     | NA     | NA        | 2.0             | NA     | NA       |
|                                  | 6.0         | 15 Oct 2024        | 6.0     | 6.0/6.1/6.2 | 6.0       | 6.0      | 6.0/6.1/6.2 | 6.0     | NA     | NA     | NA        | 3.0/3.1†        | NA     | 1.0      |
|                                  | 6.1         | 14 Nov 2025        | 6.1     | 6.1/6.2     | 6.1       | 6.1      | 6.1/6.2     | 6.1     | NA     | NA     | NA        | 3.2             | 1.0    | 2.0      |
|                                  | 6.2         | 9 Oct 2026         | 6.2     | 6.2         | 6.2       | 6.2      | 6.2         | 6.2     | NA     | NA     | NA        | 3.3             | 1.0    | 2.0      |
| **ICR Methodology Requirements** | 1.0         | 19 Feb 2022        | NA      | NA          | NA        | NA       | NA          | NA      | 1.0    | 1.0    | 1.0       | NA              | NA     | NA       |
|                                  | 2.0         | 14 Oct 2022        | NA      | NA          | NA        | NA       | NA          | NA      | 1.0    | 2.0    | 2.0       | 1.0             | NA     | NA       |
|                                  | 3.0         | 15 Oct 2024        | NA      | NA          | NA        | NA       | NA          | NA      | 3.0    | 3.0    | 3.0       | 3.0/3.1†        | NA     | 1.0      |
|                                  | 3.1         | 14 Nov 2025        | NA      | NA          | NA        | NA       | NA          | NA      | 3.1    | 3.1    | 3.1       | 3.2             | 1.0    | 2.0      |
|                                  | 3.2         | 9 Oct 2026         | NA      | NA          | NA        | NA       | NA          | NA      | 3.2    | 3.2    | 3.2       | 3.3             | 1.0    | 2.0      |

“NA” (not applicable) means that the template or supporting Program document does not apply to that ICR Program document or version.

PDD: Project Design Description; MR: Monitoring Report; PDDMR: Project Design Description and Monitoring Report; ValR: Validation Report; VerR: Verification Report; VVR: Validation and Verification Report; CN: Concept Note; MD: Methodology Description; MValR: Methodology Validation Report; AS: ICR Additionality Specifications; A6.2: ICR Article 6.2 Procedures; VVS: ICR Validation and Verification Specifications; VVB: validation and verification body.

† ICR Definitions v3.1, issued on 1 November 2024, made minor clarifying changes between releases. Version 3.0 applies before that date and version 3.1 from it, for projects under ICR Requirement Document v6.0 and methodologies under ICR Methodology Requirements v3.0.

The ICR Validation and Verification Specifications are not shown in the matrix: the current VVS applies to every engagement from its effective date, as set out in paragraph 3.

### ESES Tool requirement <a href="#eses-tool-requirement" id="eses-tool-requirement"></a>

The ICR Tool for Environmental and Socio-economic Safeguards and Sustainable Development applies to all projects, irrespective of the ICR Requirement Document version identified in the matrix.

All project proponents shall complete and submit the ESES Tool. Projects already registered with ICR shall upload the completed tool to the registry, irrespective of whether the project intends to transition to a later Program version. This requirement was communicated in the [October 2024 Program update](https://documentation.carbonregistry.com/documentation/icr-program/updates/october-2024-program-update).

### Methodology development and validation <a href="#methodology-development-and-validation" id="methodology-development-and-validation"></a>

Each methodology is assessed under a version of the ICR Methodology Requirements. The MValR template and the supporting Program documents are the versions shown on that row of the matrix. Methodology development uses the latest published CN and MD templates, as required by the ICR Methodology Approval Process v3.1. The applicable VVS is determined under paragraph 3. As an exception, a methodology validation not completed by the effective date of VVS v3.0 uses the MValR v3.2 template, whatever version of the ICR Methodology Requirements the methodology is assessed under. A methodology validation completed before that date, with the validation opinion issued, may be submitted using the previous template under VVS v2.0.

### Status of this clarification <a href="#status-of-this-clarification" id="status-of-this-clarification"></a>

This clarification does not amend the effective dates, transition provisions or substantive requirements of any ICR Program document. Where applicability remains uncertain, the project proponent or VVB shall obtain confirmation from ICR before applying or submitting the relevant documentation.

***