> 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/methodology-development/procedural/icr-methodology-approval-process-v3.1.md).

# ICR Methodology Approval Process v3.1

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FqdmpOQqSN6zhdsnNSs0h%2Fimage.png?alt=media&amp;token=6311959f-235f-49f3-967f-0b672d61007e" alt=""><figcaption></figcaption></figure>

#### *Summary*

ICR serves as a framework for climate projects of any size, promoting environmental integrity through accelerating credible action and ensuring credibility, consistency, and transparency in quantification, monitoring, reporting, validation, and verification.

| Version no.     | 3.1             |
| --------------- | --------------- |
| Date of Version | 9. October 2026 |

{% file src="/files/jIhwJTPPpIWHl2dTosFp" %}
The pdf version is the official version for the document
{% endfile %}

## Introduction

The ICR methodology approval process offers *project proponents,* methodology developers and other stakeholders a pathway for developing new *methodologies* and modules when no existing *methodology* or methodological component addresses their needs or can be applied to their climate solutions, or where revisions are needed. This ICR methodology approval process describes the framework, *criteria*, and process for development, assessment, approval, revision and review of methodologies, modules and tools under the ICR Program. *Methodologies* are subject to public stakeholder consultation, *validation* by an approved validation and verification body (VVB) in accordance with the ICR Validation and Verification Specifications, Completeness and Program Conformity Review by ICR, PAP recommendation where applicable, and final approval by the ICR Board. Modules and tools are subject to the applicable process determined under this document according to their nature, function and materiality. Once a *methodology* has been approved it may be applied as *criteria* for *validation* of *climate projects* applying the *methodology*.

## Scope

This document specifies processes and procedures for development, assessment, approval, revision, review, suspension and withdrawal of methodologies, modules and tools under the *ICR Program.* Requirements and procedures apply to modules and tools to the extent relevant to their nature, function and materiality.

## Normative References

* ICR Requirement Document
* ICR Additionality Specifications
* ICR Methodology Requirements
* ICR Validation and Verification Specifications
* ICR Definitions
* ISO 14064-2
* ISO 14064-3
* ISO 14065
* ISO 14066
* ISO 17029

## Definitions

For the purposes of this document, the terms and definitions given in the ICR Definitions apply.

## Methodology Approval Process

The process in this section sets out the approval framework for new methodologies and stand-alone modules and tools developed for application under the ICR Program. New methodologies follow the full approval process described in this section. For stand-alone modules and tools, ICR determines the applicable development, consultation, validation or technical assessment, review and approval steps based on their nature, function and materiality. A module developed as an integral part of a methodology may be developed, publicly consulted upon, validated, reviewed and approved as part of the methodology approval package.

Tools are developed under the control of ICR. Stakeholders may propose the development of a tool, and ICR may invite or accept collaboration from stakeholders or external experts in its development. Where a tool is developed in connection with a methodology, ICR determines whether the applicable consultation, assessment and approval steps are conducted together with the methodology or separately.

New *methodology* proposals and methodology revisions requiring the full approval process under Section 5 are approved through the process set out in this ICR Methodology Approval Process, consisting of a Concept Note, methodology development, public disclosure, public stakeholder consultation, methodology validation by an approved VVB, Completeness and Program Conformity Review by ICR, PAP recommendation where applicable, and final approval by the ICR Board.

Figure: Methodology approval process

During methodology development, the methodology developer may request an optional preliminary review by ICR in accordance with Section 4.2.1. The preliminary review is advisory and does not constitute methodology validation, approval of the methodology, approval of any project, confirmation of eligibility for issuance, or assessment of scientific integrity.

*Methodologies* include requirements applicable to a specific type of *climate project* that, when applied, support conformity with the requirements of *ISO 14064-2,* *ICR Requirements*, and other relevant normative requirements. They set out criteria and procedures for applicability, project boundary, baseline determination, additionality, quantification, monitoring and other applicable methodological requirements that ensure consistency in their application and result in *GHG emission mitigation outcomes*. If ICR or other *GHG programs* have not already approved a *methodology* applicable to the climate solution, a methodology developer may develop and propose a new *methodology* for approval by ICR.

The *methodology developer* shall follow the requirements in the ICR Methodology Requirements, use the latest version of the ICR Methodology Description template and strive to safeguard structural integrity, consistency, and readability. The *methodology* shall follow all instructions in the ICR Methodology Description template and justify all deviations.

The new methodology or stand-alone module proposal shall be submitted to ICR electronically via email to <submissions@carbonregistry.com>. The proposal's name shall be written in the subject line, accompanied by an explanation indicating the type of proposal submitted. All supporting documentation shall be delivered to ICR.

A stakeholder proposal for development of a tool may also be submitted to ICR. Acceptance of a proposal for consideration does not constitute a commitment by ICR to develop or approve the tool.

The costs of the approval process for methodologies and stand-alone modules consist of fees associated with applicable validation or technical assessment, charged by the *VVB* or other assessor, where applicable, and fees charged by ICR according to ICR’s fee schedule. The *methodology* or module *developer* bears all costs if no other arrangement has been agreed upon with ICR.

For tools developed under the control of ICR, responsibility for development, assessment and other associated costs is determined by ICR and any applicable collaboration arrangement.

### Concept Note

Using the Concept Note template, the *methodology developer* shall prepare and submit a description of how the proposed climate solution and the *climate project* may mitigate climate change. Submission of a Concept Note is required before submission of a new methodology or stand-alone module under Section 4 and for a methodology or module revision where required under Section 5, unless otherwise agreed by ICR. For stand-alone modules, the Concept Note requirements apply to the extent relevant to the module’s nature and function.

A stakeholder may also submit a proposal for development of a tool using the applicable template provided by ICR. ICR determines whether to proceed with development of the proposed tool and the applicable development and assessment pathway.

The concept note shall include the following:

* a summary description of the *methodology* or module;
* reference to other similar *methodologies*, modules or tools, and distinction from other *methodologies* or methodological components;
* a summary of activities associated with the implementation;
* applicability conditions;
* assessment method of additionality, where applicable;
* quantification approach of *GHG emission mitigations*, where applicable;
* an initial identification of potential risks relating to leakage, non-permanence where applicable, double counting, uncertainty, and boundary definition, as applicable;
* a description of monitoring measures, where applicable;
* identification of any planned *projects* applying the *methodology* or module, where applicable;
* identification of the development team and their competence; and
* information on funding sources for developing the *methodology* or module and implementation of identified *projects,* where applicable.

The concept note shall be submitted to ICR electronically via email to <submissions@carbonregistry.com> with the name of the proposed methodology, module or tool in the subject line and an indication that it is a concept note or tool-development proposal, as applicable. The concept note will not be published publicly unless the *methodology* *developer* or proposer requests public disclosure.

ICR conducts a review of the Concept Note and assesses the following:

* whether existing approved, pending, or otherwise relevant methodologies or methodological components under the ICR Program or other GHG programs already cover, or could reasonably be revised to cover, the intended application described in the concept;
* whether the proposed methodology or module concept is described in sufficient detail to understand its intended project activities or functions, applicability conditions, baseline approach, additionality approach, quantification approach, monitoring approach, and expected GHG emission mitigation outcome, as applicable;
* whether the development team is appropriately competent or has identified appropriate expertise needed to complete development;
* whether sufficient capacity and funding are in place to ensure the approval process can be completed, where applicable.

The Concept Note review is a preliminary assessment and does not constitute approval of the methodology or module, approval of any project, confirmation of eligibility for issuance, or validation of conformity with ICR Requirements. For a proposed tool, acceptance of the proposal or a decision to proceed with development does not constitute approval of the tool.

ICR may request advisory input from an appropriately qualified external expert where specialist scientific, technical, sectoral, or methodological input is needed to support ICR’s consideration of the Concept Note or tool proposal. Such input is advisory and does not constitute methodology validation or assessment of scientific integrity under the ICR Validation and Verification Specifications.

ICR evaluates the concept note when enough information has been provided. When the evaluation has been completed, ICR will:

{% stepper %}
{% step %}

#### Confirm development may proceed

Confirm that the concept note meets the *criteria* and that development may proceed under the applicable pathway.
{% endstep %}

{% step %}

#### Request minor improvements

Request minor improvements to the concept note, where ICR specifies unmet *criteria*.
{% endstep %}

{% step %}

#### Request major improvements

Request major improvements to the concept note before it can be resubmitted.
{% endstep %}
{% endstepper %}

For methodology and stand-alone module Concept Notes, ICR will submit a review report to the methodology or module developer within 60 days.

### Methodology, Module and Tool Development

*Methodologies* provide a standardized framework for estimating, *monitoring* and *verifying* *GHG emission mitigations*, allowing for consistent and comparable results across different *GHG projects*. New *methodologies* are subject to public stakeholder consultation, validation by an approved VVB, Completeness and Program Conformity Review by ICR, PAP recommendation where applicable, and final approval by the ICR Board. Stand-alone modules and tools follow the applicable pathway determined by ICR in accordance with Section 4 and the ICR Methodology Requirements.

The *methodology developer* shall develop the methodology or module according to requirements described in the ICR Methodology Requirements, *ISO 14064-2* to the extent applicable, the principles of the ICR Program, and use the latest version of the applicable template provided by ICR.

A module developed as an integral component of a methodology may be developed and documented as part of that methodology. A stand-alone module shall clearly define its purpose, scope, applicability, relationship with applicable methodologies or other methodological components, and any relevant dependencies in accordance with the ICR Methodology Requirements and shall use the latest applicable template provided by ICR.

Tools are developed under the control of ICR. ICR may initiate development of a tool, proceed with a tool proposed by a stakeholder, and invite or accept collaboration from stakeholders, methodology developers, technical experts or other relevant parties. ICR retains responsibility for determining the scope of the tool, the applicable development and assessment pathway, and whether the tool is submitted for approval under the ICR Program.

The methodology or module shall provide sufficient information and justification to enable assessment of conformity with the ICR Methodology Requirements including assessment of scientific integrity by the VVB during methodology validation where validation is required. For methodologies, this includes assessment of scientific integrity by the VVB during methodology validation. For stand-alone modules, scientific or technical assessment is conducted as applicable under the pathway determined by ICR.

During methodology development, the methodology developer shall prepare the PDD required under Section 7 of the ICR Methodology Requirements to demonstrate project-level application of the proposed methodology. The PDD may represent an actual or proposed project activity or a hypothetical demonstration project, as provided in the ICR Methodology Requirements.

For a stand-alone module, ICR determines whether demonstration of application through a PDD or other supporting documentation is required based on the module’s nature and function.

#### Preliminary Review

At the request of the methodology or module developer, ICR may conduct an optional preliminary review of a draft methodology or stand-alone module before formal submission for public disclosure, public stakeholder consultation, validation or other applicable assessment, and Completeness and Program Conformity Review.

The purpose of the preliminary review is to support efficient development by identifying structural, procedural, or program-level issues that may affect subsequent public consultation, validation, or other applicable assessment, or ICR review.

The preliminary review may consider structural consistency and completeness, alignment with the applicable ICR template, coverage of the ICR Requirement Document, ICR Methodology Requirements, ICR Additionality Specifications, and other applicable ICR program criteria, consistency with ICR Definitions and terminology, internal consistency between applicability conditions, boundary, baseline, additionality, quantification, leakage, non-permanence where applicable, uncertainty, and monitoring, as applicable to the methodological component, and readiness for public stakeholder consultation and independent validation or other applicable assessment.

The preliminary review does not constitute validation, approval of the methodology, module or tool, approval of any project, confirmation of eligibility for issuance, or assessment of scientific integrity under the ICR Validation and Verification Specifications. Scientific integrity is assessed by the VVB during methodology validation and, for stand-alone modules, through the applicable assessment pathway where relevant.

ICR may provide observations or recommendations to the methodology or module developer or parties collaborating in tool development, as applicable. Such observations are advisory and do not bind ICR, the VVB, the PAP, or the ICR Board in subsequent review, validation or assessment, recommendation, or approval decisions.

ICR may request advisory input from an appropriately qualified external expert where specialist scientific, technical, sectoral, or methodological input is needed to support the preliminary review. Such input is advisory and does not replace methodology validation by the VVB or any other assessment required under the applicable approval pathway. For methodologies and stand-alone modules, ICR provides written feedback to the methodology or module developer within 60 days, unless otherwise agreed with the developer.

### Public Disclosure

ICR creates a public webpage for the proposed *methodology* no later than when public consultation starts. Where public disclosure is required for a stand-alone module or tool under the applicable approval pathway, ICR similarly makes the relevant documentation publicly available.

The *methodology developer* shall provide ICR with the information required for public disclosure before the public stakeholder consultation starts. For methodologies, the *methodology developer* shall provide ICR with the following information using the applicable ICR template. For stand-alone modules and tools, the information shall be provided to the extent relevant to their nature and function using the applicable ICR template.

1. Summary description of the *methodology, module* or *tool*
2. *Project activities*, where applicable
3. Applicability conditions
4. Assessment of additionality (additionality level), where applicable
5. Quantification methods, where applicable
6. *Monitoring*, where applicable
7. *Sector* and *type*
8. Expected first *project* implementation and location, where known and applicable
9. Developer or contributor information, as applicable

Any request for non-disclosure of information or documentation shall be justified. Information necessary to determine applicability, baseline scenario, additionality, project boundary, quantification, leakage, uncertainty, monitoring, non-permanence where applicable, safeguards, or eligibility for issuance shall not be withheld from ICR or the VVB or other assessor, where applicable.

### Public Stakeholder Consultation

ICR publishes the proposed new methodology documentation on the ICR public consultation website for 30 days for consultation with *stakeholders* and the public. Where public stakeholder consultation is required for a stand-alone module or tool under the applicable approval pathway, ICR determines the consultation scope and period, taking into account its nature, function and materiality.

In collaboration with ICR, the *methodology developer* shall host an ICR webinar presenting the proposed new *methodology* to introduce it to *stakeholders*. ICR determines whether a webinar or other stakeholder-engagement activity is required for a stand-alone module or tool.

Any comments from *stakeholders* shall be submitted to <submissions@carbonregistry.com>, or through a webform on the public consultation page. Respondents shall provide their name, organization, country, and email address.

When the public consultation has concluded, ICR provides comments received to the *methodology or module developer* and the *VVB* or other assessor, as applicable. The *methodology or module developer* shall respond to all comments either by updating the *methodology* or module or demonstrating the insignificance or irrelevance of the comment. For tools, ICR coordinates the consideration and resolution of comments with relevant contributors or assessors, as applicable.

All comments, responses, and resulting changes to the methodology, module or tool shall be made available to the VVB or other assessor, where applicable, for consideration before the validation or assessment report is finalized. If comments are received too late for this purpose or after approval, they shall be considered as input to the review process, see Section 5.2.

After the formal public consultation period has concluded, ICR will allow *stakeholders* to continue to submit comments. Any comments received are shared with the *methodology* or *module developer* and the *VVB* or other relevant parties, as applicable.

### Validation

The proposed new *methodology* is subject to independent *validation* by an *approved* *VVB*. The *methodology* *developer* shall contract a *VVB* to conduct the *validation* of the *methodology*. The *VVB* shall meet the requirements set out in the ICR Validation and Verification Specifications.

A module developed as an integral component of a methodology may be assessed within the methodology validation engagement. For stand-alone modules or tools, ICR determines whether independent validation or another technical assessment is required based on their nature, function and materiality. Where validation is required, it shall be conducted in accordance with the ICR Validation and Verification Specifications.

Where ICR requires a technical assessment other than validation, the assessment shall be independent of development of the methodological component. ICR specifies the assessment scope, applicable criteria, competence requirements and required assessment record.

The *VVB* shall produce a methodology validation report for the methodology and shall conduct the validation in accordance with *ISO 14064-3, the ICR Methodology Requirements,* and the ICR Validation and Verification Specifications. The VVB shall meet the applicable accreditation and competence requirements specified in the ICR Validation and Verification Specifications.

Methodology validation shall include assessment by the VVB of whether the methodology conforms to applicable methodology validation criteria, including scientific integrity, evidence basis, applicability conditions, baseline determination, additionality, quantification, leakage, uncertainty, monitoring, non-permanence where applicable, and suitability for project-level application.

The VVB shall consider public stakeholder consultation comments, the methodology developer’s responses, and any resulting revisions to the methodology before issuing the final methodology validation report.

Where an actual or proposed project is used to demonstrate application of the methodology, the project PDD may be validated in conjunction with the methodology in accordance with the ICR Validation and Verification Specifications. A demonstration PDD prepared solely to demonstrate project-level application is assessed as supporting documentation for methodology validation and does not constitute validation of a project.

The methodology validation report shall be separate from any validation report for a project applying the proposed methodology. The methodology validation report shall be submitted to ICR with the final methodology approval package.

For methodology revisions, in accordance with Section 5, the *VVB* shall determine in accordance with the ICR Validation and Verification Specifications whether the *methodology* shall undergo complete *validation* or validation limited to the revised elements and affected sections. The *VVB* shall consider the *validation* *report* for the underlying *methodology* when determining the scope of *validation*.

### Completeness and Program Conformity Review

When the *methodology* or module *developer* has submitted the final proposal to ICR along with the methodology validation report or other required assessment record, public consultation comments and responses, and all other relevant documentation, i.e., *PDD*, project validation report where applicable, reference documentation, modules, *tools*, etc., ICR conducts a Completeness and Program Conformity Review.

For tools, once the applicable development, consultation and any required independent validation or technical assessment have been completed, ICR assembles the approval record for final consideration under Sections 4.7 and 4.8.

The Completeness and Program Conformity Review assesses whether the approval package is complete, whether the methodological component documentation is internally consistent and clearly structured, whether public consultation comments have been addressed where consultation was required, whether the applicable validation or technical assessment has been completed in accordance with applicable ICR Requirements, and whether the approval record is sufficient for PAP recommendation where applicable and ICR Board decision-making.

The Completeness and Program Conformity Review does not replace or duplicate independent validation or other required technical assessment and does not constitute an independent reassessment of scientific integrity. For methodologies, scientific integrity is assessed by the VVB during methodology validation.

If ICR identifies issues or missing documentation in the submitted approval package, ICR communicates findings to the *methodology or module developer* and the *VVB* or other assessor, as applicable.

ICR may request advisory input from an appropriately qualified external expert where specialist scientific, technical, sectoral, or methodological input is needed to support ICR’s review, PAP consideration, or ICR Board decision-making. Such input is advisory and does not replace any required validation or technical assessment, or the ICR Board’s approval decision.

ICR provides the *methodology* or *module developer* with a review report within 60 days after final documentation has been submitted for final Completeness and Program Conformity Review. The *methodology* or *module developer* and/or *VVB* or other assessor, as applicable, shall provide clarifications or submit further documentation to address the findings within 30 days of receiving the review report. If the *methodology or module developer* or *VVB* or other assessor, as applicable, does not respond to ICR’s request for clarification and/or corrections within 90 days, ICR considers the approval request withdrawn. These timelines do not apply to tools developed under the control of ICR.

If the Completeness and Program Conformity Review reveals that the *methodology*, module or tool does not meet applicable *ICR Requirements*, ICR may decline to proceed to PAP recommendation or ICR Board consideration, as applicable, or request further clarification, correction, validation or technical assessment before the approval process continues.

### PAP Recommendation

Following completion of the applicable Completeness and Program Conformity Review, ICR may submit the methodological component approval record to the Program Advisory Panel for review and recommendation before ICR Board consideration. For tools, this follows completion of the applicable development, consultation and any required independent validation or technical assessment under Sections 4.5 and 4.6.

The PAP recommendation shall support ICR Board decision-making by considering whether the applicable approval steps have been completed and whether the approval record is complete and suitable for Board consideration.

The PAP shall not conduct methodology validation, verification, academic peer review, or an independent reassessment of scientific integrity. For methodologies, scientific integrity and conformity with validation criteria are assessed by the VVB during methodology validation. For stand-alone modules and tools, the applicable technical or scientific assessment is performed through the independent assessment pathway determined under Section 4.

The PAP may recommend that the approval record is suitable for Board consideration, suitable subject to specified clarifications or conditions, deferred pending resolution of specified issues, or not suitable for Board consideration. The PAP’s role is advisory. Final approval authority remains with the ICR Board.

Where PAP recommendation is requested, the PAP should provide its recommendation within 30 days of receiving a complete approval record, unless otherwise agreed by ICR.

### ICR Board Approval

ICR prepares the relevant documentation relating to the proposed methodology, stand-alone module or tool for submission to the ICR Board, following completion of the applicable review steps under Section 4.6, taking into account the comments received from public *stakeholder* consultation where applicable, the applicable validation or technical assessment record, and any PAP recommendation, using the applicable ICR approval form.

The ICR Board considers the approval proposal, applicable validation or technical assessment record, public consultation record where applicable, the Completeness and Program Conformity Review or other applicable review record, and any PAP recommendation. The ICR Board makes every effort to conclude its consideration and finalize the decision as soon as practically possible, but no later than 30 days after submission for final approval.

At the next scheduled ICR Board meeting, the approval is placed on the agenda. The ICR Board takes due account of the approval record and may decide either to:

{% stepper %}
{% step %}

#### Approve

Approve the proposed methodology, module, tool or revision.
{% endstep %}

{% step %}

#### Approve subject to conditions

Approve the proposed methodology, module, tool or revision subject to specified clarifications or conditions.
{% endstep %}

{% step %}

#### Defer the decision

Defer the decision pending resolution of specified issues.
{% endstep %}

{% step %}

#### Reject

Reject the proposed methodology, module, tool or revision.
{% endstep %}
{% endstepper %}

The ICR Board does not re-perform independent validation or technical assessment, the Completeness and Program Conformity Review or other applicable review, or the PAP recommendation. The ICR Board determines whether the approval record provides a sufficient and credible basis to approve the methodological component for use under the ICR Program.

If the ICR Board identifies issues in the proposed *methodology*, module or tool that may be addressed with clarifications or modifications, ICR communicates the issues to the *methodology* or module *developer* and the *VVB* or other assessor, as applicable.

The *methodology* or module *developer* and/or *VVB* or other assessor, as applicable, shall provide clarifications or submit further documentation to address issues raised within 30 days of receiving such request. The proposal submission shall be considered withdrawn if the *methodology or module* *developer* or *VVB* or other responsible assessor does not respond to issues raised within 90 days. These response deadlines do not apply to tools developed under the control of ICR.

If the ICR Board approves the proposed *methodology*, module or tool or revision, the approved methodological component is published on the ICR website within seven days of the approval using the applicable ICR format, and the relevant list of approved methodologies, modules or tools is updated accordingly.

## Methodology, Module and Tool Revisions and Review

### Revisions

Methodology revisions shall be prepared using the applicable ICR template. Module revisions shall use the latest applicable template provided by ICR. Methodology and module revisions may represent limited modification, including clarification or correction, or more extensive modifications.

ICR classifies proposed methodology and module changes based on their materiality. The classification considers whether the proposed change affects applicability conditions, baseline determination, additionality, quantification, monitoring, leakage, non-permanence, safeguards, uncertainty, data requirements, validation conclusions, or any other provision material to environmental integrity or conformity with ICR Requirements.

The *methodology or module developer* may consult with ICR to determine whether a methodology or module revision represents a limited or extensive modification. If the revision is extensive, the revision process shall follow the applicable steps in Section 4 above.

For limited modifications, the *methodology* or module may be updated by ICR in coordination with the *methodology or module developer* and the *VVB* that completed the latest *validation* or other assessor, as applicable. ICR may issue a new version.

VVB input or validation shall be required where the proposed revision may affect validation conclusions, conformity with ISO 14064-2 or the ICR Methodology Requirements, applicability conditions, monitoring requirements, or quantification procedures. For stand-alone modules subject to another form of technical assessment, ICR determines whether reassessment is required based on the nature and materiality of the change.

Tools may be revised by ICR. Stakeholders or other contributors may identify the need for a revision and may collaborate with ICR in its development. ICR determines the applicable consultation, independent validation or technical assessment, review and approval requirements based on the nature and materiality of the revision.

ICR may request advisory input from an appropriately qualified external expert where the proposed revision raises specialist scientific, technical, sectoral, or methodological issues. Such input does not replace VVB validation or other required independent technical assessment where such assessment is required.

Where revisions have been made to existing *methodologies*, modules or tools and approved by the ICR Board, the revisions are published on the ICR website and may be applied in accordance with their applicable scope and effective date.

A reference to the underlying *methodology* being revised shall be included where an ICR revision is based on a methodology originating from another GHG program. The revision shall be applied to the current version of the *methodology* at the time the revision is developed. The revision shall use the latest applicable ICR template, and the rationale for the revision shall be clearly stated both in summary and in modified sections. Sections not modified shall refer to the underlying *methodology*.

If a new version of the underlying *methodology* is issued under the relevant *GHG program*, ICR reviews whether the change affects the continued integrity, applicability or conformity of the ICR revision with ICR Requirements. Where a material effect is identified, ICR may suspend the ICR revision until it has been updated and re-approved or otherwise determined to remain suitable for use.

### Review

ICR reviews approved *methodologies*, modules and tools to ensure that they remain active, suitable for use under the ICR Program, and reflect best practices, best available scientific and technical knowledge, scientific integrity, where applicable, and relevant technical advancements. A review may be initiated at any time where information indicates that a methodological component may no longer conform to applicable ICR Requirements or remain suitable for use under the ICR Program.

A review may be initiated due to the following:

* New or amended ICR Requirements that may affect the continued conformity of the methodological component.
* Concerns that *methodologies, modules* or *tools* do not reflect best practices or relevant scientific or technical knowledge, or are materially inconsistent with *ICR Requirements*.
* Concerns relating to scientific integrity, validation or assessment conclusions, environmental integrity, program integrity, or continued suitability for use under the ICR Program.
* Material scientific, technical, regulatory or methodological developments that may affect the basis or application of the methodological component.
* Relevant stakeholder comments, project experience, VVB findings or other information indicating a potential material issue.

ICR conducts or coordinates the review, as applicable. The depth of review is proportionate to the materiality of the concern. Input from the methodology or module developer, the VVB that validated the methodology or other independent assessor, stakeholders, and appropriately qualified external experts may be obtained as required for the review.

Where the review concerns validation or technical assessment conclusions, scientific integrity, conformity with ISO 14064-2, the ICR Methodology Requirements, or the ICR Validation and Verification Specifications, ICR may request input from the VVB that validated the methodology or another VVB approved by ICR for the relevant scope or another appropriately qualified independent assessor, as applicable. Where the review concerns a stand-alone module or tool that was subject to another form of technical assessment, ICR may request input from the independent assessor or another appropriately qualified independent assessor.

For tools, where the review concerns the scientific or technical basis, conformity or environmental integrity of the tool, the substantive review is conducted independently from development of the matter under review, either by personnel not directly involved in its development or through an independent external review or assessment arrangement.

Where the review raises material environmental integrity, program integrity, governance, or policy-level concerns, ICR may request PAP review and recommendation before ICR Board decision-making.

* If the review determines that the *methodology, module* or *tool* requires limited modifications, ICR coordinates the applicable revision in accordance with Section 5.1, involving the methodology or module developer, VVB or other assessor, as applicable.
* If the review determines that the *methodology, module* or *tool* requires major revision, ICR may temporarily suspend the methodological component where continued use could affect conformity with ICR Requirements, environmental integrity or program integrity. Reinstatement requires completion of the applicable revision and approval pathway under Sections 4 and 5.1. If the identified issues are not addressed, ICR may withdraw the methodological component in accordance with Section 5.4.
* If the review determines that the *methodology, module* or *tool,* continues to meet applicable *ICR Requirements* and remains suitable for use under the ICR Program, no further action is required.

### Periodic Review of Approved Methodologies, Modules and Tools

ICR conducts periodic reviews of *methodologies* developed under the *ICR Program,* including relevant modules and tools, and underlying *methodologies* or methodological components originating from other GHG programs where these are relied upon under the *ICR Program* to ensure that methodologies, modules, and tools remain aligned with best practices and best available scientific and technical knowledge. This process supports ensuring that *methodologies*, modules and tools are consistent with the development of the *ICR Program*, remain suitable for use, and establish robust *criteria* and procedures to meet the *ICR Requirements*.

Following a review, ICR may revise the *methodology, module* or *tool* or issue guidance and clarification documents. Additionally, ICR may suspend previously approved *methodologies, modules or tools,* or withdraw them from the *ICR Program* where identified issues materially affect their continued conformity with ICR Requirements or suitability for use. Where a review identifies a material concern requiring further assessment, ICR may conduct a review in accordance with Section 5.2.

Relevant *stakeholders* are kept informed as appropriate throughout the review process. The review procedure is outlined in Sections 5.3.1 to 5.3.3. These procedures apply to all *methodologies*, modules and tools to the extent applicable to their nature and function.

#### Review

ICR initiates a periodic review of each *methodology*, module, and tool within five years of its approval, last update or review.

ICR reviews the status of *methodologies* or methodological components originating from other *GHG programs* and relied upon under the ICR Program periodically, and at least every two years, to identify changes that may affect their continued application under the ICR Program.

Reviews may be initiated at any time if the *methodology* or *module developer, VVB, project proponent,* *stakeholder*, or ICR identifies an issue, such as:

{% stepper %}
{% step %}

#### Significant inconsistency with ICR Requirements

Significant inconsistency with *ICR Requirements* (e.g., significant differences in the quantification of *GHG emission mitigations* by *projects* applying the *methodology* or methodological component).
{% endstep %}

{% step %}

#### Material scientific or technical advancements

Material scientific or technical advancements in a specific industry/*sector*.
{% endstep %}

{% step %}

#### Other material concerns

Any other concerns raised about an approved *methodology, module* or *tool* that are considered *material*.
{% endstep %}
{% endstepper %}

ICR public consultation sites allow for ongoing public stakeholder comments. ICR shares all relevant input received from ongoing public *stakeholder* consultations with the *methodology* or *module developer,* the *VVB* or other assessor, and the *PAP* where appropriate to the nature and materiality of the issue.

Where input received through ongoing consultation raises issues relating to scientific integrity, validation or technical assessment conclusions, or conformity with ISO 14064-2, the ICR Methodology Requirements, or the ICR Validation and Verification Specifications, ICR may request input from the VVB that validated the methodology or another VVB approved by ICR for the relevant scope, or another appropriately qualified independent assessor, as applicable. ICR may also request advisory input from an appropriately qualified external expert where specialist scientific, technical, sectoral, or methodological expertise is needed. Where the input raises material environmental integrity, program integrity, governance, or policy-level concerns, ICR may request PAP review and recommendation.

For tools, where a periodic review concerns the scientific or technical basis, conformity or environmental integrity of the tool, the substantive review is conducted independently from the development of the matter under review in accordance with Section 5.2.

ICR may review the continued need for a methodology, module or tool where it has not been applied within five years of its approval, last update or review. Following the review, ICR may retain, suspend or withdraw the methodological component in accordance with Section 5.4, taking into account its continued relevance, expected future use and any applicable integrity or program considerations.

#### Review Procedure

The review of the *methodology, module* or *tool* and any relevant issues is conducted or coordinated by ICR. ICR may request input from the *methodology* or *module developer,* *stakeholders*, *VVBs*, other independent assessors, and where appropriate, appropriately qualified external experts.

For tools, where the review concerns the scientific or technical basis, conformity or environmental integrity of the tool, the substantive review is conducted independently from development of the matter under review in accordance with Section 5.2.

ICR may initiate a public *stakeholder* consultation, where broader *stakeholder* input is appropriate to assess continued conformity with ICR Requirements, alignment with relevant best practices, best available scientific and technical knowledge, or relevant technical or methodological advancements.

During the review, the *methodology*, module or tool may be temporarily suspended in accordance with Section 5.4 where material concerns indicate that continued use could affect environmental integrity, program integrity or conformity with ICR Requirements.

ICR documents the basis for the review, material inputs considered, findings and outcome.

#### Outcome

If the review determines that the *methodology, module* or *tool* is in alignment with the *ICR Program,* meets applicable ICR Requirements, remains suitable for use, reflects relevant best practices and best available scientific and technical knowledge, and relevant technical advancements, no further action is taken.

If corrections or clarifications are needed, ICR may issue corrections and clarification documents and issue a new version referring to the corrections/clarifications.

If minor revisions are needed, ICR follows the procedure set out in Section 5.1.

If major revisions are needed, ICR may suspend the methodology, module or tool in accordance with Section 5.4 where continued use could affect conformity with ICR Requirements, environmental integrity or program integrity. The methodological component may be reinstated following completion of the applicable revision and approval pathway under Sections 4 and 5.1.

A suspended or withdrawn methodology or module may be revised by ICR or a third-party in accordance with the applicable requirements and submitted for reinstatement or reintroduction under the *ICR Program*. Where a major revision is required, the applicable Concept Note and approval requirements under Sections 4 and 5.1 apply.

A suspended or withdrawn tool may be revised by ICR, including in collaboration with relevant stakeholders or external experts, and is subject to the applicable independent assessment, review and approval requirements determined under Sections 4 and 5.1.

ICR may permanently withdraw a *methodology*, module or tool if ICR determines that a revision is unlikely to resolve the identified issue sufficiently to restore conformity or suitability for use. A methodological component permanently withdrawn on this basis may only be reintroduced where ICR determines that the underlying issue has been materially resolved and the component completes a new approval process.

### Suspension and Withdrawal of Methodologies, Modules and Tools

Suspension means that the methodology, module, or tool remains listed under the ICR Program but is temporarily unavailable for new project submissions, except as expressly permitted by ICR. Withdrawal means that the methodology, module, or tool is no longer eligible for new project submissions under the ICR Program. ICR publishes the applicable status and effective date of suspension or withdrawal.

Grace periods may apply to suspended or withdrawn *methodologies, modules* or *tools*.

A grace period is only applicable to projects that requested *pre-registration* when the *methodology*, module or tool version becoming suspended or withdrawn was active or that had already been *validated* using that version.

Withdrawn *methodologies, modules* or *tools* are not eligible for application to new *project* *activities* for *registration* under the ICR Program.

In the case of revision of a *methodology, module or tool*, the revision documentation will explicitly specify how the revision applies to *registered* *projects* before the renewal of the *crediting period,* where applicable.

Where a methodology, module or tool is withdrawn due to material environmental integrity, scientific integrity, or conformity concerns, ICR may require affected registered projects to undergo additional review, apply a revised or replacement methodology or methodological component, revise the project design description, undergo re-validation, or satisfy other conditions before further issuance. ICR determines the applicable treatment of registered projects based on the nature and materiality of the concern that led to suspension or withdrawal.

{% stepper %}
{% step %}

#### Revised component

Where a *methodology, module* or *tool* is revised, *project proponents* may apply the previous version for up to six months from the approval of the new version, unless otherwise specified by the ICR.
{% endstep %}

{% step %}

#### Underlying component withdrawn, excluded or replaced

Where an ICR-approved revision relies on a methodology or methodological component originating from another GHG program and the underlying component is withdrawn, excluded or replaced, *project proponents* may use the previously accepted version for up to six months from the applicable date determined by ICR, unless otherwise specified by ICR.
{% endstep %}

{% step %}

#### Suspended or withdrawn component

Where a previously approved *methodology, module* or *tool* is suspended or withdrawn, *project proponents* may continue to apply the affected version for up to six months from the date it was suspended or withdrawn, subject to any conditions specified by ICR, unless otherwise specified on the ICR website.
{% endstep %}

{% step %}

#### Registered projects

*Registered* *projects* applying a *methodology, module or tool* that has been suspended or withdrawn may not continue to apply the affected methodological component after the applicable grace period unless ICR expressly permits continued use or approves an applicable transition, revised version or replacement methodological component.
{% endstep %}
{% endstepper %}

ICR reserves the right to specify different grace periods.

ICR may shorten, extend, waive, or condition any grace period where necessary to safeguard environmental integrity, avoid over-crediting, maintain conformity with ICR Requirements, or address project-specific circumstances.

## Appendix I – Document History

| Version | Date       | Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| ------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1.0     | 19.2.2022  | First version.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| 2.0     | 14.10.2022 | Second version.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| 3.0     | 15.10.2024 | Reference to ICR validation and verification specifications. Review process defined in more detail. Suspension and withdrawal of methodologies clarified. Timelines added. After public consultation some language has been made clearer.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| 3.1     | 9.10.2026  | Updated the methodology approval process to align with the ICR Methodology Requirements, ICR Validation and Verification Specifications, and ICR Program Advisory Panel procedures. Clarified the development, assessment, approval, revision, review, suspension and withdrawal pathways for methodologies, modules and tools. Added provisions for stand-alone modules and ICR-controlled tool development, including stakeholder proposals and collaboration, proportionate assessment pathways, and safeguards for independent technical assessment. Added an optional preliminary review by ICR during methodology development. Clarified that scientific integrity is assessed by the VVB during methodology validation and removed the need for a separate scientific integrity evaluation step. Clarified treatment of demonstration PDDs, public consultation comments, Completeness and Program Conformity Review by ICR, PAP recommendation, and ICR Board approval. Clarified revision classification, periodic review, and transition arrangements for suspended or withdrawn methodologies, modules and tools. General terminology, capitalization, and readability improvements throughout the document. |

## Appendix II – Timelines

Table: Timelines for the applicable approval and review process divided by subject and section

| Subject                                                                                                                                                              |   Days | Months | Years |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -----: | -----: | ----: |
| 4.1 Concept Note - ICR review report                                                                                                                                 |     60 |        |       |
| 4.2.1 Preliminary Review optional                                                                                                                                    |     60 |        |       |
| 4.4 Public Stakeholder Consultation                                                                                                                                  |     30 |        |       |
| 4.6 Completeness and Program Conformity Review – review report                                                                                                       |     60 |        |       |
| 4.6 Completeness and Program Conformity Review – Response to findings raised.                                                                                        |     30 |        |       |
| 4.6 Completeness and Program Conformity Review – Approval request considered withdrawn when no response received.                                                    |     90 |        |       |
| 4.7 PAP recommendation:                                                                                                                                              | 30[^1] |        |       |
| 4.8 ICR Board Approval                                                                                                                                               |     30 |        |       |
| 4.8 ICR Board Approval - Response to findings raised.                                                                                                                |     30 |        |       |
| 4.8 ICR Board Approval – Approval request considered withdrawn when no response received.                                                                            |     90 |        |       |
| 4.8 ICR Board Approval - Publication of approved methodologies, modules and tools on the ICR website                                                                 |      7 |        |       |
| 5.3.1 Review - Periodic review of ICR methodologies, modules and tools                                                                                               |        |        |     5 |
| 5.3.1 Review - Review of methodologies or methodological components originating from other GHG programs and relied upon under the ICR Program                        |        |        |     2 |
| 5.3.1 Review - Review of continued need where a methodology, module or tool has not been applied: 5 years                                                            |        |        |     5 |
| 5.4 Suspension and Withdrawal of Methodologies - Application of previous methodology version, module or tool version following approval of a revised version         |        |      6 |       |
| 5.4 Suspension and Withdrawal of Methodologies - Transition where an underlying methodological component from another GHG program is withdrawn, excluded or replaced |        |      6 |       |
| 5.4 Suspension and Withdrawal of Methodologies - Continued application following suspension or withdrawal                                                            |        |      6 |       |

[^1]: Where applicable
