# ICR Process Requirements v5.0

**Summary**

_ICR serves as a platform for climate projects of any sizes where environmental integrity is promoted with credibility, consistency and transparency of quantification, monitoring, reporting, validation, and verification._

| Version no.     | 5.0              |
| --------------- | ---------------- |
| Date of Version | 6. February 2024 |

{% file src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FQ7fQZLC1P5YiTRDeZEkq%2FICR%20Process%20Requirements%20v5.0.pdf?alt=media&token=05feab7d-006e-44d0-827d-5ebac3db8677" %}
PDF version
{% endfile %}

## 1. General <a href="#toc158103529" id="toc158103529"></a>

The International Carbon Registry (ICR) is a GHG program and a comprehensive platform that adheres to the principles of the Paris Agreement and ISO 14064 series of standards, providing a robust framework for managing and validating climate projects globally. ICR offers a user-friendly registry system for project proponents to manage the entire lifecycle of climate projects, including tracking carbon credit inventories, facilitating market reach, and managing carbon credit portfolios by organizations.

### 1.1 ICR program <a href="#toc158103530" id="toc158103530"></a>

This document summarizes the ICR processes, i.e., for pre-registration of projects, registering projects, issuing ICR carbon credits (ICCs), activating ICCs, and retiring/cancelling ICCs or other environmental instruments according to the ICR requirement document or other scheme requirements. This document intends to serve project proponents, project developers, general organizations, market participants, validation and verification bodies (VVBs), and other entities participating in the carbon market. Still, the focus is on project proponents registering their climate projects, issuing carbon credits, and interacting with ICR and VVBs. Note that the ICR requirement document and related documents provide rules and requirements for climate projects to be eligible for registration. This document, ICR process requirements, complements the ICR requirement document. Further, the ICR registry user guide assists project proponents in familiarizing themselves with the ICR registry platform.

Projects may have one or more project proponents and may be supported by project developers. For readability, this document uses project proponent in the singular tense, and project developer and proponents are not distinct.

The project proponent interacts with ICR when they have project concepts, pre-register projects in development, when undergoing validation, finalizing registering projects post validation, during issuance of ICCs, and activation of ICCs post verification of GHG emission mitigation outcomes. All supporting documentation shall be uploaded to the ICR registry by the project proponent, its authorized representative, and VVBs for any documentation relating to validation and verification. Validation and verification bodies (VVBs) are responsible for validating climate projects and verifying their GHG emission mitigation outcomes. ICR is responsible for undertaking document review, administering registration, issuance, activation of ICCs, and other aspects of administering the ICR program and registry further outlined in the ICR terms and conditions, ICR terms and conditions for projects, and the ICR registry user guide.

The ICR registry platform provides a central source for all information and documentation relating to projects under the ICR program. The ICR registry platform also provides assurance of the uniqueness of projects and their GHG emission mitigations, and issues serialized ICCs, and tracks transfers, retirements, and cancellations. ICR makes information and documentation of projects publicly available, but some information may not be publicly disclosed when information is subject to confidentiality and/or intellectual property rights. All documentation is, however, available for VVBs. ICR is responsible for reviewing project documentation and overseeing VVBs accreditation to ensure the integrity of projects and ICCs within the registry platform.

This ICR process requirements is updated periodically, and project proponents or other users shall ensure that they are using the most current version of this document or other documentation issued by the ICR.

### 1.2 Blockchain <a href="#ref158066240" id="ref158066240"></a>

The ICR registry platform leverages blockchain technology to issue carbon credits and transactions with carbon credits. The blockchain-backed nature of the ICR registry platform permits live inventory management and dissemination to marketplaces and end users of tools, enhancing transparency and favoring all parties involved. With blockchain technology, numerous difficulties confronted by VCMs are tackled right from the beginning as it provide for the traceability of credits in a manner that is auditable by the public.

Thus, the blockchain functions as a public record, maintaining a permanent and unalterable log where sellers, buyers, and other stakeholders can inspect and authenticate, thereby eliminating the possibility of duplication and fraudulent activities.

Tokenization is the process of converting rights to an asset into a digital token on a blockchain.

**Tokenization with Blockchain:**

**Security and Trust:** The blockchain ensures the tokens are secure and the ownership records are tamper-proof.\
**Decentralization:** The information is not stored in a centralized server, making it resistant to hacking or manipulation.\
**Liquidity:** Tokenization on blockchain allows fractional ownership, improving the liquidity of assets.\
**Transparency:** Every transaction is recorded on the public ledger, ensuring transparency.\
**Interoperability:** Tokens can be easily exchanged and used across different applications and platforms.\
**Smart Contracts:** Automate processes like dividend payments or voting rights.

**Tokenization without Blockchain:**

**Centralized Control:** Without blockchain, tokenization would need a centralized authority or database to keep track of ownership and transactions.\
**Limited Trust and Security:** The central system could be susceptible to manipulation, errors, or hacking.\
**Lower Liquidity:** Traditional systems may not support fractional ownership to the same extent as blockchain, making some assets less liquid.\
**Opacity:** Transactions may not be as transparent or easily verifiable by all parties involved.\
**Limited Interoperability:** Tokens might be confined to specific platforms or systems and may not be easily transferable.

Tokenization with blockchain provides more security, transparency, and liquidity compared to traditional tokenization/crediting methods.

All credits/tokens issued are generated on [Polygon](https://polygon.technology/), found at [https://polygon.technology/](https://polygon.technology/). Polygon is constructed on the [Ethereum](https://ethereum.org/en/) blockchain.

Further documentation on blockchain applications can be reviewed in ICR documentation using the following link. [https://documentation.carbonregistry.com/documentation/on-chain/how-it-works](https://documentation.carbonregistry.com/documentation/on-chain/how-it-works).

### 1.3 Transparency <a href="#toc158103532" id="toc158103532"></a>

Increasing transparency in voluntary carbon markets is pivotal for fostering trust and ensuring the effectiveness of climate projects and trust from their supporters. To achieve this, it's essential to implement standardized reporting, third-party validation and verification, public disclosure, clear framework, price transparency, oversight, and global alignment of transparency standards.

**Clear reporting**: Clear and standardized reporting requirements for climate projects.

**Third-party validation/verification**: Third-party verification of project claims, ensuring impartial assessment by a competent and accredited validation and verification body.

**Public disclosure**: Public access to relevant project information, including project documentation, monitoring data, and validation/verification results.

**Standardization**: Adherence to standardized rules and requirements governing climate projects, ensuring consistency and integrity.

**Additionality transparency**: Make details on the significance of support projects needs to scale, facilitating fair market pricing and accuracy in reflecting climate impact.

**Oversight**: Oversight to ensure compliance with relevant laws and regulations.

**Global alignment**: Harmonize transparency standards, i.e., CDM, at a global level, aligning with the Paris Agreement and frameworks under article 6.4 and ISO standards.

In addition, the presentation of information in an understandable format.

### 1.4 Traceability <a href="#toc158103533" id="toc158103533"></a>

Enhancing traceability in VCMs by replacing outdated technology with modern solutions, particularly by leveraging blockchain as a native database and tokenizing carbon credits, is pivotal in scaling climate action. The phased transition to new technology ensures that carbon credits and climate projects are accurately tracked, preventing double counting and fostering trust and transparency.

Blockchain's role as a native database is crucial because it provides immutable and transparent ledgers, making data tamper-proof and accessible to all stakeholders. This enhanced traceability, facilitated by blockchain and tokenization, builds confidence, attracts more participants, increases investments, and accelerates climate action. It ensures that the market operates efficiently and with integrity, ultimately driving the transition to a more sustainable, low-carbon future.

ICR relies on native issuance of carbon credits (tokens) on the Polygon blockchain, which is a public blockchain.

![Figure 1: Comparison of current credit issuance and tokenization utilizing public blockchain.](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FVqy93GHgLQGmcHB3FtTe%2F1.png?alt=media)

## 2. Registry <a href="#toc158103534" id="toc158103534"></a>

ICR's registry platform is electronic and can be accessed through all internet-connected computers, tablets, or phones at [www.app.carbonregistry.com](http://www.app.carbonregistry.com/). ICR's registry platform is developed by Mojoflower ehf. (Mojoflower) [www.mojoflower.io](http://www.mojoflower.io/). Further information about the [ICR registry user guide](https://documentation.carbonregistry.com/documentation/icr-program/registry-user-guide) may be found on the ICR documentation site.

![Figure 2: Create an account](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F7FptmCM1ztCRrjRpnjrZ%2F2.png?alt=media)

The registry has user accounts and organizational accounts. Projects and credits belong to organizational accounts. Users make all actions and transactions on behalf of organizations.

![Figure 3: Accounts relationship.](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FWX9xTlPQlv3UGwhjV8FI%2F3.png?alt=media)

### 2.1 Account opening <a href="#toc158103535" id="toc158103535"></a>

To benefit from using the ICR program, an ICR registry account needs to be opened to pre-register, register, issue, trade, or retire ICCs. The ICR registry is administered and maintained by ICR.

### 2.2 Users <a href="#toc158103536" id="toc158103536"></a>

Everyone can join the ICR registry. Individuals can establish an account from the ICR registry platform by providing the necessary information.

![Figure 4: Create a user account](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FDxL0SlhNTKqDBNc0YCF6%2F4.png?alt=media)

For users to be able to perform specific actions, they need to be verified, i.e., complete the Know your Customer (KYC) checks (**"verified users"**). The KYC check can be completed from the registry platform.

![Figure 5: KYC](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FnTMAZo3LKc8b30QmV4ul%2F5.png?alt=media)

### 2.3 Organizations <a href="#toc158103537" id="toc158103537"></a>

For organizations to participate in the ICR ecosystem as a project proponent, project developer, market participant, or general organization for issuing, transferring, trading, or retiring ICCs, they need to establish a registry account with ICR. Users can create a registry account for an organization, i.e., project proponent, developer, market participant, or general organization, from their user account\[1].

![Figure 6: Create organizational account](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FDsv1XuwVLPiezbdH5zUG%2F6.png?alt=media)

The account opening is completed via the ICRs platform by a user who has the authority to represent the organization (Authorized representative). Organizations that want to have a public profile or intend to participate as a project proponent, project developer, VVBs, or market participant need to complete a Know Your Business (KYB), and the user creating the organizational account shall be a verified user. _Note: Different fees are applicable for organizations based on the type of organizations and their verification._

Organizational types are:

* Project proponent
* Project developer
* Validation and verification body (VVB) (see section 8)
* Market participant
* General organization

![Figure 7: KYB](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FFdHHgzFbbTnjCrShv0vK%2F7.png?alt=media)

Organizations (project proponents or project developers) who want to register climate projects and issue ICR carbon credits (ICCs) shall have a verified account with ICR before any documentation review can proceed. For further information on the climate project requirements of ICR, refer to the ICR requirement document, ISO 14064-2, and other applicable documentation.

Any organization intending to submit a project to ICR needs to open an account by a user with the authority to represent the proponent through the ICR registry platform and register as a project proponent or a project developer.

Other organizations open registry accounts as applicable for their usage\[2]. User permissions are limited to the purpose of use, and some are subject to special agreements with ICR, e.g., market participants and VVBs.

Market participants who want to act as custodians of carbon credits for users or trade or retire carbon credits on behalf of organizations shall establish a market participant account with ICR and sign a market participant agreement with ICR.

Validation and verification bodies need to establish an account with ICR. When an agreement has been signed with ICR, the VVB is explicitly identified in the registry. Only VVBs with an agreement with ICR are identified as VVB.

Organizations holding ICCs shall open a general organizational account with ICR if they intend to retire or hold carbon credits for use later and publicly disclose their aggregated holdings of ICCs and retirements.

All applicants for organizational account opening must sign terms and conditions for organizations and are subject to Know Your Business (KYB) check with ICR for them to be verified (**"verified organization"**). Only verified organizations may have a public organizational profile.

ICR will inform the organization of the review of the KYB and accompanying documentation. If further documentation is needed, ICR will inform the organization.

When all applicable fees have been paid, the account is verified, and the verified organization may perform its actions with the ICR registry platform.

Authorized representatives of organizations can invite current users in the ICR registry platform to join the organizational account and become members of their account by adding them to the organization. The invitation is delivered by email\[3]. The users may be subject to KYC upon request. Users identified as members in organizational accounts have different roles, either administrative rights (admin) or content editing rights (editors). All user invitations to the organization's account and their roles are the organization's and authorized representatives' responsibility. At all times, at least one member needs to be an admin.

Detailed information on the ICR registry software, including step-by-step instructions for creating accounts, entering information, issuing, transferring, and retiring instruments, can be found in the ICR user guide.

Note that some organizations may publicly or privately disclose ICC inventory ownership. Only general organizational accounts allow for private accounts and private inventory.

## 3. ICR project cycle <a href="#toc158103538" id="toc158103538"></a>

Project registration involves the formal process of submitting a climate project design to ICR and to an approved validation and verification body for assessment, providing detailed information about the project's objectives, procedures, and expected GHG emissions mitigations. The registration ensures transparency, accountability, and credibility in projects, allowing them to issue ICCs that may be traded and used to compensate for GHG emissions or contribute towards reducing or removing atmospheric GHG emissions by organizations or others. The timing of project registration may be independent of its start date. In other words, projects may be submitted after they begin operation (subject to eligibility) or before they begin operation. However, the steps outlined in this section shall be followed.

The lifecycle of a project may generally be described according to the following diagram.

![Figure 8: Project cycle](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FyqH7WbQUFknL4NUvnTeo%2F8.png?alt=media)

Projects have different status based on their project cycle. The status of a project may be:

1. Concept
2. Under development
3. Under validation
4. Validated
5. Closed
6. Delisted

The status represents the stage in the project cycle it is in.

### 3.1 Methodological criteria and procedures <a href="#toc158103539" id="toc158103539"></a>

A methodology refers to a systematic approach or set of procedures used to quantify and measure GHG emissions mitigations. These methodologies provide a standardized framework for estimating, monitoring, and verifying emission mitigations, allowing for consistent and comparable results across different projects applying the methodology. These methodologies typically establish criteria and prescribe procedures for projects to follow for data collection, quantification, monitoring, and reporting GHG emissions mitigations for projects ex-ante and ex-post and serve as good practice guidance.

Project proponents developing a climate project should review approved methodologies under ICR for their applicability and follow them where possible.

![Figure 9: Methodologies](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F35V0PWFgjrfVgBX71aJ7%2F9.png?alt=media)

The ICR has pre-approved methodologies listed in ICR approved methodologies and available on the ICR documentation page.

When approved methodologies do not cover the project activities, the project proponent may develop a project by establishing methodological criteria and procedures according to the requirements of ISO 14064-2 and the ICR requirement document, e.g.:

* Boundary
* Baseline
* Additionality
* Quantification
* Monitoring

When establishing methodological criteria and procedures, ISO 14064-2 states in section 6.1 that project proponents shall identify, consider, and use all relevant criteria and procedures for every stage of the GHG project cycle where these are available. Here, consideration of section 0.3 in ISO 14064-2 is relevant.

If criteria and procedures are not available, the project proponent shall use relevant current good practice guidance. The project proponent shall select and apply established criteria and procedures from a recognized origin if available. Often, methodologies developed under GHG programs are considered a recognized origin.

Please refer to the ICR methodology approval process if the project proponent intends to develop a new methodology.

All documentation, irrespective of the origin of methodology, criteria, and procedures, shall use available templates on the ICR website and follow any instructions outlined. Note, however, section 6.

Copyright of methodologies developed by entities other than ICR following the ICR methodology approval process are theirs, not ICR's. Methodologies developed by ICR are the copyright of ICR.

Methodologies not developed by ICR may be subject to copyright. Methodologies, however, contain standardized processes for, e.g., measuring and verifying GHG emissions reductions or removals associated with a project or activity. They establish criteria and procedures, e.g., for establishing baseline, boundary, monitoring, and quantifying the amount of carbon dioxide or other GHGs that are reduced, avoided, or removed from the atmosphere due to the project implementation.

Copyright law protects original works of authorship fixed in a tangible medium of expression, like an issued methodology. However, it does not protect ideas, procedures, methods, or systems, even if they are included in methodologies. Therefore, using or referencing processes, methods, and procedures in a methodology typically does not violate its copyright (if it exists).

Processes, methods, or procedures may be eligible for protection under different forms of intellectual property, including patents. Nevertheless, the ICR does not have any records of GHG programs or methodologies developed under those programs being protected under patent law. Should a methodology's processes be patented, the methodology documentation should explicitly mention this information.

ICR, however, respects the associated cost of developing methodologies. Where a methodology has been developed partially or entirely by third parties approved and published by other GHG programs and is applied in all significant aspects, as a good practice guidance, to demonstrate conformity to ISO 14064-2 and ICR requirements methodology developer(s) may be eligible to receive royalties from project proponents applying the methodology.

Where ICR deems a methodology has been applied, developers are offered royalties according to the ICR fee schedule as compensation for their contribution. ICR determines eligibility on a case-by-case basis. Methodology fees are collectible for 12 months from transfers of ICCs applying the respective methodology. If not collected, ICR will deposit the methodology fee to a methodology development fund.

ICR acknowledges and makes explicit the copyrights of approved methodologies (or other methodologies). ICR respects and preserves the existing trademarks and logos in the published materials (methodologies from other GHG programs).

### 3.2 Project concept <a href="#toc158103540" id="toc158103540"></a>

A project concept refers to the basic outline and description of an initiative to mitigate GHG emissions or sequester carbon dioxide from the atmosphere. Project proponents may submit a project concept in the ICR registry where they have not completed the project documentation according to the ICR requirement document and procedures.

For the public viewing project concepts, they should be aware that there's no certainty that the project will be implemented or issue ICCs in the future. Projects listed as a "Project concept" are not considered pre-registered or registered.

Information needed to be eligible for listing a project concept is submitting a project concept description. If the project proponent intends to develop a methodology, he may submit a methodology concept note.

**Information to complete in the registry platform:**

1. Descriptive project name
2. Short descriptive summary of project activities
3. Website
4. Estimated start date
5. Sector
6. Estimation of additionality levels
7. Other SDGs
8. Project type
9. Location of the project

**Documentation:**

1. Project concept note
2. Methodology concept note (optional)

Projects may be listed as a project concept for up to 6 months. If the concept status has not been updated to "under development" and has been pre-registered after six months, the concept listing will be withdrawn from the public registry.

After the project proponent has submitted the project concept for review, ICR shall respond within one week of submission of the project concept.

When ICR has no further observations of the information provided or the documentation, ICR approves the project concept 1 week after the proponent has attended to the findings raised by ICR.

If ICR suspects that the information and documentation submitted are false or misleading, ICR reserves all rights to decline a request to list the project concept and disclose the occasion.

Where a project requesting a listing of a project concept has not followed the instructions and ICR believes it is spam, ICR reserves the right to reject the listing request without providing any findings to the proponent.

![Figure 10: Project concept listing](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2Fb0KWg1cFHdDwhDFg1eYN%2F10.png?alt=media)

### 3.3 Pre-registration <a href="#toc158103541" id="toc158103541"></a>

The ICR registry features a project pipeline that showcases projects before their official registration. Projects can be pre-registered during initial development stages, marked as "under development," or categorized as "under validation" when prepared to initiate the validation process.

Project proponents applying for pre-registration of a climate project in the ICR registry can do so at any time before or during the implementation of the actual project and its operations. Pre-registration may be to showcase projects in implementation for potential off-takers or investors or to increase awareness of prominent climate actions being developed. Pre-registration of a project does not constitute a validation by the ICR of the project or its eligibility for final registration. Pre-registration is a preliminary review of project information provided to the ICR. It is not a final determination of the project's eligibility or validation, nor does it guarantee the issuance of instruments.

When validating or verifying the project activities, the VVB shall check the project's status in the ICR registry. If the project has not been pre-registered with the ICR, the VVB shall advise the proponent to do so. When the VVB has been contracted for validation/verification, they have access to the project in the registry, and the audit team will have access to all documentation submitted to the ICR.

![Figure 11: Pre-registration process](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FLnzuiDAQT3UFijA4g0Rz%2F11.png?alt=media)

#### 3.3.1 Process <a href="#toc158103542" id="toc158103542"></a>

When the project proponent has completed a draft PDD, an admin initiates registration of a new project from the ICR registry platform's organizational account, and the editor may modify information. See the ICR user guide for details of pre-registration items.

The project proponent appoints an individual(s) or an entity responsible for communication with ICR throughout the crediting period of the project activities depicted in the project design description as an "Authorized representative." The appointment is done in a representation dee&#x64;**\[4]**.

If the individual is not already holding a user ID, the organization provides the individual authorization to be associated with the project with a user ID with admin rights for the project during the completion of the registration form. See details in the ICR user guide.

The admin can invite other users to edit and modify information about the project. They are added as editors to the project.

_Note: editors may edit information about the project, upload documentation, and share insights, but admins are also permitted to submit projects for review by the ICR and request issuances._

When the registration form has been completed, an admin submits the project for pre-registration in the ICR registry platform as either "under development" or "under validation." The difference represents the status of implementation and the contractual relationship with a VVB. Those under validation are projects that have completed the project design description and contracted a VVB for validation (and verification), while projects "under development" have not.

Documentation needed for pre-registration for "under development":

1. Projects eligible for pre-registration shall submit the following documentation and approve terms and conditions applicable for projects in the registry platform ("project agreement" ):
   1. Proof of ownership (private document)
   2. A draft project design description (or project design description and monitoring report) with the following sections completed\[5] (public document):
      1. 1.1 - 1.16
      2. 2.1 – 2.4
      3. 4.1 – 4.4 (if applicable)
   3. Representation deed (private document)

Documentation needed for registration for "under validation."

1. To register the project as "Under validation," the following documentation shall be submitted:
2. Proof of ownership (private document)
3. Completed project design description with all sections completed (public document)
4. Proof of contracting a VVB, proof of contracting can be in the form of a legal agreement, letter of intent/memorandum of understanding (private document)
5. Representation deed (if applicable) (private document)

For projects initially pre-registered as under development, the status shall be updated to "under validation" before the validation starts, providing all necessary documentation listed for projects "under validation" and selecting the VVB contracted to conduct the validation from the registry platform.

All documents regarding the project shall be submitted in electronic format.

The project proponent uploads all relevant documents to the ICR registry. The project proponent shall use information from the project documents to complete the registration form in the ICR registry. All documents uploaded should be posted publicly, except for commercially sensitive information and proof of contracting.

The project proponent pays all relevant outstanding fees according to applicable Terms and conditions and the fee schedule.

When fees have been received, ICR reviews submitted documents and information provided in the registry platform for completion and consistency.

If the submitted documentation is insufficient, the proponent is informed of corrections/improvements needed.

The project status is confirmed by ICR as "under development" or "under validation," subject to review of the documentation and confirmation by ICR.

If more than one proponent or developer represents a project, all organizations are subject to the terms of the project agreement and shall submit an agreement where one focal for the project is appointed, see section 10.1. Other proponents shall be added as partners to the project in the registry platform.

Relevant documentation shall be uploaded to the ICR platform for pre-registration of the project and public disclosure. The project is registered as appropriate as "under development" or "under validation."

1. All submitted documents and records are kept for at least seven years after the last retirement of the instrument issued and activated resulting from the project activities. If the project that has been pre-registered fails to complete registration and no ICCs are issued, documents and records are kept for at least seven years.
2. All information about a project that is registered on-chain can't be removed\[6].
3. If a project has been pre-registered and does not complete validation within 12 months. from initial pre-registration, the project status is updated to "Inactive." Subject to objective evidence of ongoing implementation, the status is updated or reverted. Pre-registered projects shall complete validation and registration within 24 months from initial pre-registration. If projects do not complete validation and registration within 24 months, they're delisted from the ICR registry.
4. If ICR suspects that the information and documentation submitted are false or misleading, ICR reserves all rights to delist the project and disclose the occasion.

When the project has been pre-registered on the ICR registry and relevant documentation made available on the ICR registry platform, stakeholders may comment on the project and its public documentation. Comments on the project activities shall be submitted to [admin@carbonregistry.com](mailto:admin@carbonregistry.com) with information, e.g., name, organization, address, and email address of the disclosing party. Comments received are shared with the project proponent and the VVB.

Where the project requesting pre-registration has not followed the instructions and ICR believes it is spam, ICR reserves the right to reject the pre-registration request without providing any findings to the proponent.

When ICR determines that the project does not conform to the ICR program, ICR will reject the pre-registration request.

After the proponent has requested a review by the ICR for pre-registration and all fees paid, the ICR shall respond with findings within two weeks. When the proponent has resolved all outstanding issues raised by ICR, ICR shall complete the pre-registration within one week.

![Figure 12: Pre-registration](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FkjlPISY4egxoecU5sZku%2F12.png?alt=media)

### 3.4 Validation <a href="#ref158066910" id="ref158066910"></a>

Before a project may be registered, it needs to be validated by an approved VVB. A list of approved VVBs may be found on ICR's website and the registry platform.

![Figure 13: Validation process](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FP18EwaEmdBE41VD8j7mY%2F13.png?alt=media)

#### 3.4.1 Project design description for validation <a href="#toc158103544" id="toc158103544"></a>

When projects have been pre-registered, and the project design description has been completed, projects can undergo validation\[7].

1. Before initiating the validation, the project design description needs to be completed and submitted to ICR as it is submitted to the VVB for assessment.
2. The project proponent shall use all applicable templates from ICR for the documentation and follow all outlined instructions.
3. If the project includes other environmental or social benefits subject to validation, the proponent shall inform the VVB and add it as criteria for validation, and necessary documentation shall be made available for the VVB for validation. ICR allows for additional labeling of other certifications or other benefits, such as the UN Global Goals. The proponent shall disclose during registration and to the VVB if he intends to have the benefits verified.
4. Other benefits shall be described in the project design description and on the project registration page.
5. For validation to be completed, the project design description shall meet the validation criteria, i.e., conform to all requirements of ISO 14064-2, the ICR requirement document, and, where relevant, the applied methodology. Note that the minimum criteria for validation are the ICR requirement document and ISO 14064-2. The project proponent may decide to have an approved methodology as an added criterion for validation.
6. The project proponent shall adhere to and demonstrate conformity to all applicable requirements.
7. All documents regarding the project shall be submitted to the VVB in electronic format or a format requested by the VVB.

The proponent shall not request to change the registration status to "Validated" until it has completed validation, received the validation report, and the VVB has submitted the report to ICR.

#### 3.4.2 Validation of projects <a href="#toc158103545" id="toc158103545"></a>

The validation process shall be completed for projects to be eligible for registration and issuance of ICCs. With limitations, projects are eligible to issue ICCs post validation (prior to monitoring and verification). See section 3.4 in the ICR requirement document. If project proponents issue ex-ante ICCs after validation of projects, they are inactive and, as such, can't be retired by organizations holding them. Ex-ante ICCs can, however, be transferred. Issuance of ex-post ICCs is subject to verification of GHG emission mitigation outcomes by the VVB. Note that issuance of ICCs ex-ante does not guarantee them becoming ex-post ICCs, as discussed under section 4.2.&#x31;**.**

Criteria for validation, including requirements for VVB, are set out in the ICR requirement document. Further guidance and specifications on validation and verification may be found in ICR validation and verification specifications. Projects must complete validation before requesting registration and issuance of ICCs. The process for requesting issuance of ICCs is discussed under section 0.

The proponent shall identify the relevant criteria for validation and verification in the registry platform. See the ICR user guide.

When the proponent has contracted a VVB for validation, the VVB is selected in the registry platform that will conduct the validation/verification of the project. When the VVB has been selected, he will have access to all information relevant to the project on the registry platform. See further in the ICR user guide.

The VVB shall review if the information in the project registration aligns with the documentation. Further, any images or posts the project proponent shares relate to the project activities.

Project proponents shall submit documentation to the VVB according to requests by the VVB.

The VVB assesses the documentation and accompanying evidence of conformity to ISO 14064-2 requirements, the ICR requirement document, and, where applicable, the applied methodology or other criteria.

The VVB submits findings to the project proponent with findings and requests for corrective actions as applicable.

If applicable, the project proponent responds to the requests for corrective actions, and the VVB assesses the measures taken.

The VVB submits the final validation report with findings to the project proponent and uploads it to the registry platform.

The project proponent shall review that all relevant and necessary documentation has been uploaded to the registry and that relevant documents are available for public access.

1. Project design description,
2. Validation report,
3. Methodology specific documentation,
4. Documentation relating to other criteria,
5. Representation deed.
6. Validation plan,
7. Validation agreement,
8. Ownership proof.

When the proponent has confirmed that all documentation necessary for the registration has been uploaded, the project status may be changed to "Validated." A project proponent admin shall request a review of the project for registration from the registry platform.

ICR reviews the documentation and validation report for completeness, findings, and opinion.

If the validation report or supporting and required documents are insufficient or need clarification, ICR advises the VVB and/or the project proponent, respectively.

### 3.5 Registration <a href="#toc158103546" id="toc158103546"></a>

The project proponent initiates the registration process from the ICR platform. The project review process is initiated when relevant documentation for registration or renewal of the crediting period is submitted to ICR via the registry platform. The process initiates no sooner than when all necessary documentation has been submitted to ICR and a request has been submitted by an authorized representative (admin) from the ICR registry platform. The project review process consists of a documentation review.

![Figure 14: Registration process](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FHyA5MfWmH5KEZfmXrhvY%2F14.png?alt=media)

Registration is possible when the project has been validated, the proponent has resolved all non-conformities, and the VVB has submitted the validation report.

The project review fee shall be paid before ICR completes the project review and the project is registered in the registry.

When a project is registered, relevant documents shall be made available in the registry platform as follows and are disclosed publicly:

1. Project design description,
2. Validation report,
3. Methodology specific documentation,
4. Documentation relating to conformity to other criteria,

The following documents shall be provided to the ICR and are not disclosed publicly:

1. Representation deed.
2. Validation plan,
3. Validation agreement,
4. Ownership proof.

Project proponents shall advise ICR before disclosure if any documentation is subject to non-disclosure or confidentiality.

The purpose of documentation review is to ensure that all applicable documents are complete and signed where necessary. When an eligible VVB has completed the validation and/or verification, GHG emission mitigation outcomes have not been issued as instruments under another GHG program (or been cancelled as appropriate), appropriate information has been used to complete all project documents, the VVB holds required accreditation, and the competence of the audit team is appropriate. Further, check if the newest versions of methodologies or tools have been applied and if all information provided in the registry platform is consistent with the project documentation.

If information is missing or incorrect, ICR will request that project documentation be updated, or information be added to the registry platform. Any findings from the documentation review shall be addressed before the registration or issuance request for instruments can be completed.

The registry stores all project documents in its record-keeping system for at least seven years from the retirement date of the last ICC to which the project documents relate.\[8]

If the project proponent or VVB fails to address findings from the ICR, the ICR informs the VVB and/or the project proponent that the project has failed to demonstrate conformity to the ICR program requirements and is ineligible for registration or issuance.

Note that documentation review is also applicable for all issuances of ICCs ex-post. See section 0.

When the project has completed both validation and verification, the sections below are also applicable, but monitoring reporting shall be included in the ICR project design description and monitoring report.

![Figure 15: Review process](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FuLWOhLRnzkBCfpqHhdSo%2F15.png?alt=media)

After the proponent has requested a review by the ICR for registration, the ICR shall respond with findings within four weeks after all fees have been paid. When the proponent (or VVB) has responded to findings raised or resolved all outstanding issues raised by ICR, ICR shall complete a review of responses and/or the registration within two weeks.

After validation and final step in the registration process of a climate project, ICR publishes publicly the validated estimation of GHG emission mitigations (ICCs) for the crediting period. This involves no-issuance event but merely a transparent public disclosure of validated projected GHG emission mitigations, which may be compared later to actual GHG emission mitigations of the project.

![Figure 16: Project review timelines](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F75PLUgfE91WQ5dTCCf3K%2F16.png?alt=media)

### 3.6 Monitoring <a href="#toc158103547" id="toc158103547"></a>

During the project's operation, the GHG emission mitigations shall be monitored according to the monitoring plan and reported in a monitoring report. Any deviations from the monitoring plan shall be addressed and justified in the monitoring report.

If a deviation has been made to the project design description, a revised project design description shall be issued and uploaded to the registry as a public document, along with an updated validation report.

When a VVB has been contracted, the project proponent shall submit a verification agreement and verification plan to the registry. Further, the proponent shall select the contracted VVB from the registry platform.

Proponents shall select the monitoring period and monitored GHG emission mitigations when they submit monitoring reports. An admin shall submit the monitoring report and request review. See the ICR user guide.

### 3.7 Verification <a href="#ref158068307" id="ref158068307"></a>

After monitoring, the GHG emission mitigation shall be verified by an approved VVB to be eligible for issuance of ex-post ICCs. If ICCs have been issued ex-ante, verification is mandatory to activate ex-ante credits.

![Figure 17: Submitting monitoring and verification reports](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FNNhC5paVWT0uRO4341fE%2F17.png?alt=media)

When GHG emission mitigation outcomes have been monitored according to the monitoring plan and verified by the VVB, ex-post ICCs may be issued, and ICCs may be activated; see section 4.3.

Criteria for verification, including requirements for VVB, are set out in the ICR requirement document. Further guidance and specifications on validation and verification may be found in ICR validation and verification specifications. Projects must complete verification before requesting issuance of ex-post ICCs. The process for requesting issuance of ICCs post-monitoring is discussed under section 4.3. The proponent shall identify the relevant criteria for verification in the registry platform. See the ICR user guide.

When the proponent has contracted a VVB for verification, the VVB is selected in the registry platform that will conduct the verification of the GHG emission mitigations. When the VVB has been selected, he will have access to all information relevant to the project on the registry platform. See further in the ICR user guide.

The VVB shall review if the information in the project registration aligns with the documentation. Further, assess any images or insights the project proponent publicly shares that relate to the project activities.

Project proponents shall submit documentation to the VVB according to VVB's request.

The VVB assesses the monitoring and accompanying evidence of conformity to the verification criteria.

The VVB submits findings to the project proponent with findings and requests for corrective actions as applicable.

If applicable, the project proponent responds to the requests for corrective actions, and the VVB assesses any measures taken.

The VVB submits the final verification report with findings to the project proponent and uploads it to the registry platform.

The project proponent shall indicate the monitoring period in the registry and review that all relevant and necessary documentation has been uploaded to the registry and that relevant documents are available for public access.

1. Updated project design description (if applicable),
2. New validation report (if applicable),
3. Monitoring report,
4. Verification report,

and the following documents are private

1. Validation plan (if applicable)
2. Verification plan
3. Verification agreement.

ICR reviews the request to ensure all documents are complete and signed where necessary. An eligible VVB has conducted the verification, instruments have not been issued under another GHG program (or been cancelled as appropriate) for the same GHG emission mitigation, and appropriate information is included in all documentation. The VVB holds the necessary accreditation, and the competence of the audit team is appropriate. Further, to check if the newest versions of methodologies or tools have been applied and all information provided in the registry platform is consistent with the project documentation.

When the verification has been confirmed, ICCs are minted and delivered to the ICR holding account. The supply of verified ex-post ICCs for the monitoring period is provided on-chain\[9]. Ex-ante ICCs issued are activated corresponding to ex-ante ICCs that have been transferred to other accounts within the ICR registry and ICCs sitting on adjustment accounts.

The project proponent may issue ICCs according to monitoring findings as stated in the monitoring report and verified according to the verification report, see section 4.3.

![Figure 18: Verification review](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2Fq0LmasXSx7PBsdJwfXZX%2F18.png?alt=media)

### 3.8 Crediting period renewal <a href="#toc158103549" id="toc158103549"></a>

If the crediting period has been renewed, a revised project design description and new validation report and validation agreement shall be provided to ICR.

If the crediting period has been renewed, the following documents shall be uploaded to the registry as public documents.

1. Revised project design description
2. Methodology specific documentation
3. New validation report

and the following documents are private

1. Validation agreement
2. Validation plan
3. Ownership proof.
4. Representation deed.

For renewal, the proponent shall follow section 3.4.

## 4. Issuance <a href="#toc158103550" id="toc158103550"></a>

ICR issuing carbon credits on a blockchain offers several advantages in terms of transparency and security compared to traditional databases. Blockchain operates on a decentralized network of computers, which means that the data is not stored in a single location; see section 1.2 further. This enhances transparency, as every transaction on the blockchain is recorded on a public ledger accessible to anyone. This means that all ICC transactions, e.g., issuances, transfers, and retirements, are publicly visible, making it easier to track their origin and ensure they are not double-counted. Once a transaction is recorded on a blockchain, it cannot be altered or deleted. This immutability provides a high level of security against tampering and fraud. This ensures that the records are accurate and remain unaltered, thereby maintaining the integrity of the credits.

Ex-ante and ex-post ICCs differ primarily in terms of the timing of the realization of the GHG emission mitigations activities they represent:

* **Ex-ante ICCs** are issued based on projected or expected GHG emission mitigations that will occur in the future. They are issued before the actual impacts, based on predictive calculations or models of the project's expected impact. Ex-ante ICCs become ex-post ICCs subject to successful verification of impacts.
* **Ex-post ICCs** are issued after the GHG emission mitigations have occurred and been verified. These credits represent real, measurable GHG emission mitigations that have been achieved and verified, confirming the project's actual impact.

![Figure 19: Ex-post vs. ex-ante.](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F8cupNLtjoyYUKYXGOHqv%2F19.png?alt=media)

Issuance of ICCs, either ex-ante or ex-post may generally be described according to the following diagram.

![Figure 20: Ex-ante ICC issuance.](https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2Fu1t9QL1b1E6N6ja3kbox%2F20.png?alt=media)



<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F5hSr8FfqQ9LmewOLaekF%2Fimage.png?alt=media&#x26;token=e61fd215-a8e9-49e1-8acc-3ebeec313ddf" alt=""><figcaption><p><em>Figure 21: Ex-post ICC issuance.</em></p></figcaption></figure>

Ex-ante issuance refers to the issuance of ICCs before impacts, and ex-post issuance refers to issuance after verification of real impacts. Ex-ante ICCs have vintages in the future, but ex-post vintages in the past.

Issuances are either pre-monitoring (ex-ante) or post-verification (ex-post). The ICR registry displays the status of every ICC that has been issued. ICR allows projects that have been validated to issue ex-ante ICCs. ICCs may have a different status that represents the attribute of the credit. ICCs may be inactive (ex-ante), active (ex-post), retired, or cancelled. Please refer to ICR definitions for detailed definitions on different statuses. The project proponent may request partial or complete issuance of ICCs in the registry, subject to limitations. See section 3.4 in the ICR requirement document.

When a proponent requests partial issuance, it shall be no less than 10.000 t CO2-e for each issuance unless validated or verified GHG emissions mitigations are less than 10.000 t CO2-e. When registration and issuance coincide, the documentation review is completed in parallel.

### 4.1 Serialization <a href="#toc158103551" id="toc158103551"></a>

Serial numbers play an important role in ensuring the integrity and traceability of carbon credits. Even though the tokenization of credits on chain ensures the uniqueness of a project and a credit, a credit serial number further serves as a consistent unique identifier assigned to each vintage of each project, representing a reduction, avoidance, or removal of CO2-e. The serial number ensures that each credit is distinct and traceable. Relying on serial numbers helps prevent double counting and fraud. It ensures that a specific carbon credit can be tracked throughout its lifecycle, from issuance to retirement, which is essential for maintaining credibility.

The serialization of ICCs helps to see the credits' attributes and compare projects easily. The serialization structure is provided below.

<table data-header-hidden data-full-width="true"><thead><tr><th></th><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Component</strong></td><td><strong>Order</strong></td><td><strong>Type</strong></td><td><strong>Length</strong></td><td><strong>Range</strong></td><td><strong>Comment</strong></td></tr><tr><td>Credit identifier</td><td>1</td><td>Letter</td><td>3</td><td>Text</td><td>Fixed value. Unique registry identifier. (ICC, FCC)</td></tr><tr><td>Project Country</td><td>2</td><td>Letter</td><td>3</td><td>ISO 3166-1</td><td>Three-letter country code for the project (e.g., Iceland is ISL).</td></tr><tr><td>Project country dialing code</td><td>3</td><td>Numeric</td><td>3</td><td>1-999</td><td>Three-digit country code for the project (e.g., Iceland is 354).</td></tr><tr><td>Project ID</td><td>4</td><td>Numeric</td><td>4</td><td>1-9999</td><td>Registry assigned identifier for the project, unique in the registry.</td></tr><tr><td>Sector</td><td>5</td><td>Numeric</td><td>2</td><td>1-16</td><td>Sectors from CDM</td></tr><tr><td>Type</td><td>6</td><td>Letter</td><td>1</td><td>A, R, H</td><td>Avoidance, Removal, Hybrid</td></tr><tr><td>Host country attestation</td><td>7</td><td>Numeric</td><td>1</td><td>1;0</td><td>1 = Yes, 0 = No attestation</td></tr><tr><td>Vintage (Year)</td><td>8</td><td>Numeric</td><td>4</td><td>0-9999</td><td>The vintage year of the credits.</td></tr><tr><td>Multiple project activities</td><td>9</td><td>Numeric</td><td>3</td><td>0-999</td><td>ID of a sub-project. If not multiple project activities, this identifier is not used.</td></tr></tbody></table>

_Example: ICC-ISL-354-33-13-A-0-2022_

_**GHG program:** International Carbon Registry_

_**Project Country**: Iceland_

_**Dialling code:** 354_

_**Project ID:** 33_

_**Sector:** Waste handling and disposal_

_**Type:** Avoidance_

_**Host country attestation:** No approval for ITMO transfer._

_**Vintage**: 2022_

_**Multiple project activities:** Not a Multiple project activity._

### 4.2 Ex-ante <a href="#ref157455456" id="ref157455456"></a>

ICR acknowledges the importance of early funding projects to minimize associated costs, access to funding, and the possibility of quickly scaling climate methodologies/projects. Therefore, project proponents can issue ICCs after projects have been validated and before GHG emission mitigation outcomes have been verified, subject to limitations as further discussed in the ICR requirement document. This may ease funding, facilitate climate actions, scale climate actions, and provide market visibility and credibility to climate projects. Note that ICCs are issued based on validated estimation of GHG emissions mitigation outcomes. Ex-ante ICCs cannot be retired until verified and exchanged for ex-post ICCs.

Issuance is allowed for projects where mitigations have not been verified, i.e., pre-monitoring and verification if they meet additionality level 4b or have insurance cover or warranty to compensate for any non-performance of the projects. Meeting level 4b allows issuing up to 50% of validated GHG emission mitigation for each vintage for the crediting period, notwithstanding ICCs demarcated for adjustment account(s). Projects with insurance cover or warranty may issue ex-ante ICCs up to 100% of the validated GHG emission mitigations.

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FZmUZF6mrfF0KlTTamN31%2Fimage.png?alt=media&#x26;token=85e07419-e77a-41e4-ae4b-d29599d10db8" alt=""><figcaption><p>Figure 22: Ex-ante issuance.</p></figcaption></figure>

When ICCs are issued ex-ante, the proponent shall either:

1. Meet additionality level 4b, or
2. Have insurance cover or warranty for non-performance.

Project meeting additionality level 4b and issue ex-ante ICCs shall deposit 2% to an adjustment account. The adjustment account is to rectify issued ICCs that fail to result in real mitigations or reversal events.\[10]

Ex-ante allows issuing up to 50% of validated GHG emission mitigation of each vintage for the crediting period, notwithstanding ICCs demarcated for adjustment account.

Projects with insurance covered or warranty by a licensed insurance company for non-performance may issue up to 100% of validated GHG emission mitigation of each vintage for the crediting period. The insurance cover shall be publicly available.

All ex-ante ICCs have not been verified for real GHG emission mitigation outcomes and are inactive. As such, they can't be retired and used to offset emissions. When an approved VVB has verified GHG emission mitigation outcomes, ICCs are replaced with ex-post ICCs and may be retired (see section 4.2.1**Error! Reference source not found.**).

Vintages are displayed for ICCs based on validated estimates in the project design description and validation report for ex-ante issuance of ICCs.\[11]

Requests for issuance of ex-ante ICCs are made from the registration platform. See the ICR user guide for further information.

#### 4.2.1 Ex-ante post verification <a href="#ref151644164" id="ref151644164"></a>

This process relates to verification submission when projects have issued ex-ante ICCs.

For each verified monitoring period, the project proponent shall submit a monitoring report and a verification report and request the conversion of ex-ante ICCs to ex-post ICCs.

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F10O1W2UF6bhfLaZo31cS%2Fimage.png?alt=media&#x26;token=fa7965ba-9f1b-4716-85c1-e5489a50324e" alt=""><figcaption><p>Figure 23: Ex-ante post verification</p></figcaption></figure>

When monitoring and verification have been completed, the proponent shall submit the monitoring and verification reports from the registry and request review. When the review has been completed, ICR converts the corresponding number of ex-ante credits to ex-post credits.

1. If verified GHG emission mitigations are greater than issued ex-ante ICCs, ex-post credits are delivered directly to current holders of ex-ante ICCs, and ex-ante ICCs are replaced with ex-post ICCs, subject to confirmation by ICR admin.
2. If verified GHG emission mitigations are less than issued ex-ante ICCs and the monitoring period for the respective vintage has not been closed, ex-post ICCs (according to the verified GHG emission mitigations) are delivered to an escrow account. ICCs remain on the escrow account until the monitoring for the respective vintage has been completed and verified. The project proponent shall complete verification of the respective vintage within 12 months.
3. If, after the completion of the verification of the monitoring period, verified GHG emission mitigations are greater than issued ex-ante ICCs, ex-post ICCs are delivered from the escrow account, and remaining ex-post credits to the current holders of ex-ante ICCs and any excess ex-post ICCs may be issued according to the verification report.
4. If, after verifying the monitoring period, verified GHG emission mitigations are still less than issued ex-ante ICCs, 3. applies.
5.  If monitoring for a monitoring period, where a vintage has been completed, and verification confirms fewer GHG emission mitigations than the number of issued ex-ante ICCs for the respective monitoring period (vintage), the project proponent is responsible for compensating for excess ex-ante issuance unless insurance or warranty covers non-performance of the project.



The following applies for compensation by the proponent:

1. The project proponent shall deposit ex-post ICCs of earlier vintage to an escrow account within the ICR registry. ICCs shall be owned by the project proponent. Excess ICCs shall be deposited from the project proponent's registry account and shall not have been retired or cancelled. Such ICCs deposited to an escrow account shall be delivered to the current holders of ex-ante with ex-post ICCs issued for the respective vintage subject to non-performance, proportionally.
2. Deposit of issued ex-post ICCs from subsequent vintages of ICCs to the project following the same requirements as in i. If the project proponent has insufficient holdings on the account, deductions shall be made after subsequent monitoring and verification, subject to approval by current affected holders of ex-ante ICCs.
3. Purchase by the project proponent of an equivalent number of replacement ICCs or equivalent carbon credits issued by an approved GHG program for the same project type, sector, and vintage, determined by the ICR. Such ICCs shall be deposited to an escrow account within the ICR registry. Other carbon credits shall be cancelled for the same amount. The deposit or cancellation shall be completed within 60 business days of receiving formal notification of such required action from ICR. ICCs deposited or remaining on an escrow account shall be delivered to the current holders of ex-ante with ex-post ICCs issued for the respective vintage subject to non-performance proportionally. When carbon credits have been cancelled, confirmation from the ICR of such cancellation shall be delivered to the current ex-ante holders.
4. Where the project proponent fails to compensate for excess issuance and non-performance, ICR may act against the project proponent, including applying sanctions with respect to its registry account activities until the excess issuance has been compensated.
5. In cases where the project proponents fail to compensate for over-issuance and non-performance, ICR will deliver ex-post ICCs from the ICR adjustment account to the escrow account. Such ICCs deposited to an escrow account shall be delivered to the current holders of ex-ante, proportionally with ex-post ICCs issued for the respective vintage subject to non-performance.
6. If insurance or warranty covers part or total non-performance, the insurance or warranty terms shall compensate for the non-performance of the ex-ante issuances.

If the VVB has verified that GHG emission mitigation is more than issued ex-ante ICCs, the project proponent may issue the remaining ICCs not eligible for ex-ante issuance at registration, see section 4.2. Further, if monitoring confirms fewer/more mitigations than estimated in the project design description and verified by VVB, additional issuance shall be made accordingly for the monitoring period.

### 4.3 Ex-post <a href="#toc158103554" id="toc158103554"></a>

For each monitoring period that has been verified, the ex-post ICCs may be issued.

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F1yF6mH2EQrPbuJFUmWSm%2Fimage.png?alt=media&#x26;token=181bde0c-e906-496c-ba73-451f077fd0ee" alt=""><figcaption><p>Figure 24: Ex-post issuance.</p></figcaption></figure>

When ICCs are issued for a monitoring period, relevant documents shall be provided to ICR that are disclosed publicly:

1. Monitoring report,
2. Verification report\[12],
3. Methodology specific documentation,
4. Documentation relating to conformity to other criteria,
5. Documentation regarding cancellation of GHG credits under another GHG program (if applicable) or statement of no double issuance.

Further, the following documents shall be provided to the ICR and are not disclosed publicly:

1. Verification plan,
2. Verification agreement.

If material deviation to the project design description has been applied during implementation and a revised project design description has been issued, the new version of the project design description shall be provided to the VVB for validation and to ICR, accompanied by a new validation report. The new version of the validation report and the previous version are available publicly.

Project proponents shall advise ICR before disclosure if any documentation is subject to non-disclosure or confidentiality.

During issuance, the proponent shall select which documents are private or public.

ICR reviews the monitoring and verification reports for completeness, findings, and opinion.

If the verification report or supporting and required documents are insufficient, ICR advises the VVB and/or the project proponent, respectively.

All documentation shall be submitted to ICR via electronic means.

Issuance of ICCs is subject to a successful documentation review.

After issuance of ICCs, they are first deposited to the ICR holding account, as discussed in section 3.7, until the proponent requests to have them delivered to his account. ICR only invoices issuance of ICCs delivered to the proponent's account\[13]. ICR can only transfer ICCs issued by the proponent to the ICR holding account to his registry account. Whenever the proponent intends to have ICCs delivered from the ICR holding account, he requests delivery from the registry platform. See the ICR registry user guide.

### 4.4 Buffer and adjustment <a href="#toc158103555" id="toc158103555"></a>

ICR addresses the risk associated with project activities' non-permanence and non-performance of estimated GHG emission mitigation outcomes by requiring the project proponent to set aside non-tradable adjustment ICC credits. This is completed to cover unforeseen losses in carbon stocks and unforeseen obstacles in the operations of projects. The adjustment credits from all CDR projects are held in ICR's single pooled buffer adjustment account. Buffer adjustment ICCs can be drawn upon in the event of a reversal in carbon stocks, or if projects fail to produce real GHG emission mitigation outcomes in any individual project where ICCs have been retired or from the ICR adjustment account, then ICCs have been transferred ex-ante in an inactive state and fail to deliver validated GHG emission mitigations.

Deposits to adjustment accounts are completed during the issuance of ICCs.

When credits are issued ex-ante with permanence risk, the buffer adjustment is applicable for the ex-ante issuance of ICCs.

#### 4.4.1 Buffer <a href="#ref157459131" id="ref157459131"></a>

The number of ICCs to be deposited in the pooled buffer account is determined by non-permanence risk following the requirements in the ICR requirement document. The non-permanence risk rating and this percentage are applied to the project's carbon stocks verified to determine the number of ICCs to be deposited in the ICR pooled buffer account.

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FQ69Re7bC40FdzNxbfVvI%2Fimage.png?alt=media&#x26;token=f9f45ace-7d3f-43af-a955-fa42531c4af5" alt=""><figcaption><p>Figure 25: Buffer allocation.</p></figcaption></figure>

At the submission of the verification report and minting of ICCs to the ICR holding account, ICR allocates the buffer credits to the ICR buffer adjustment account. Buffer ICCs are not subject to issuance fees.

ICCs within the pooled buffer adjustment account from different projects are functionally distinct, although administered in one pooled account in the ICR registry. Therefore, ICCs from the same project types will compensate for reversal events for the same project type. ICR will retire ICCs from the buffer adjustment account to compensate for reversals on a first-in, first-out rule after identifying which ICCs meet the criteria above for reversal compensation.

**Cancellation of buffer ICCs**

Buffer credits are cancelled from the ICR buffer account when a reversal event or other events result in the loss of carbon stocks issued as ex-post ICCs. When buffer ICCs are cancelled, the reversal event resulting in the cancellation is disclosed as the reason.

**Reversal events**

In the event of a potential reversal event, the project proponent shall notify ICR within 30 days of discovering the potential reversal event. If there have been previous issuances of ICCs, the report must be prepared and submitted to the ICR Registry, following these guidelines:

1. The reversal event report shall use the ICR reversal event report template. Based on monitoring the entire affected area, it shall contain a conservative estimation of the reversal of previously verified GHG emission mitigations due to decreases in carbon stocks from the project.
2. The reversal event report shall be submitted to the ICR registry within two years from the discovery date of the reversal event. Failure to submit the reversal event report within this timeframe will render the project ineligible to issue ICCs.
3. The ICR registry will temporarily hold buffer credits from the ICR buffer adjustment account, equivalent to the estimated reversal stated in the reversal event report.
4. The project proponent shall account for the reversal at the following verification after the reversal event.
   1. If the verified net GHG emission mitigations are negative, the withheld buffer credits shall be cancelled, and any remaining buffer credits released.
   2. If the reversal is greater than stated in the reversal event report, an equivalent number of buffer credits are cancelled.
   3. The withheld buffer credits are released if the GHG emission mitigations are positive.
5. ICR reversal event report shall be publicly available.

#### 4.4.2 Adjustment <a href="#toc158103557" id="toc158103557"></a>

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2Frop9MLkpgv0qpuwetfsv%2Fimage.png?alt=media&#x26;token=98190e57-ec07-4e63-96ce-8345525bd497" alt=""><figcaption><p>Figure 26: Adjustment account allocation.</p></figcaption></figure>

Project proponents shall deposit adjustment credits into the adjustment account following this process.

1. The number of credits to be deposited in the adjustment account is 2% of each issuance of ICCs, irrespective of the timing of issuance prior to verification.
2. Adjustment credits are essentially considered ICCs but are only eligible for compensation for non-performance events. Adjustment credits are not subject to any issuance fees.
3. At verification events, they are converted to ex-post ICCs and can be used to compensate for non-performance.
4. At the end of each project crediting period, the project proponent can apply for reimbursement of deposits of adjustment credits. They are reimbursed by ICR's sole discretion and with respect to the status of the adjustment account and cancellations made by the ICR due to non-permanence and/or non-performance.

**Non-performance**

In the event of a non-performance of the project, the project proponent shall notify ICR within 30 days of discovering non-performance. If there have been previous issuances of ex-ante ICCs, the report must be prepared and submitted to the ICR registry following these guidelines:

1. The non-performance report shall use the ICR non-performance report template. It shall contain a conservative estimation of the impacts of previously validated GHG emission mitigations due to the non-performance of the project based on monitoring.
2. The non-performance report shall be submitted to the ICR registry within six months from the non-performance discovery date. Failure to submit the non-performance report within this timeframe will render the project ineligible to issue further ICCs.
3. The ICR registry will temporarily hold adjustment credits from the ICR adjustment account, equivalent to the estimated difference stated in the non-performance report.
4. The proponent shall account for the non-performance at the following verification after the project.
   1. If the net GHG emission mitigations verified are greater than issued ex-ante ICCs
      1. the project proponent shall compensate for the difference by replacing ICCs from the same project.
      2. Notify the insurer of non-performance and exercise the insurance or warranty.
   2. If the proponent can't compensate, adjustment credits are cancelled, and any remaining adjustment credits are released.
5. ICR non-performance report shall be publicly available.

If the GHG emission mitigations are less than issued ex-ante credits, the proponent shall use any ex-post credits to replace ex-ante credits, and the withheld adjustment credits will be released.

## 5. Transfer, Retirements, and cancellations <a href="#toc158103558" id="toc158103558"></a>

Transfers, retirements, and cancellations have specific meanings. A transfer means transferring an instrument from one account to another and representing a transfer of beneficial ownership of GHG emission mitigation entitlements. Retirement means permanently removing an ICC from circulation in the registry system, representing a compensation of one metric tonne of CO2 equivalent (CO2-e). Cancellation means permanently removing an ICC from circulation in the registry system for purposes other than retirement (e.g., converting ICCs into another form of GHG credit, compensating for excess ICC issuance, expiry, etc.). See further in ICR definitions. The ICR user guide provides details about transfers, retirements, cancellations, and other credit actions.

### 5.1 Transfers <a href="#toc158103559" id="toc158103559"></a>

Transfers involve transferring a set number of ICCs from one registry account to another. This process includes changing the rights to beneficial ownership of GHG emissions mitigations they represent as defined in ICR definitions. ICR registry functionality always guarantees instrument delivery, and buyers can always expect to have ICCs delivered.

Each transfer and related information, including the address of each credit, is traceable in the platform or through the blockchain ledger. Historical transfer can be accessed on the platform and public blockchain ledger.

From a registry account, an admin initiates a transfer from the registry. There are two instances of transfers.

1. Transfer to organizations that have accounts with ICR
2. Transfer to organizations that don't have an account with ICR

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FqtV91uTLaZJcnVFzewyd%2Fimage.png?alt=media&#x26;token=34e9bdcc-0fcd-4128-8996-761dacec85e7" alt=""><figcaption><p>Figure 27: Transfers</p></figcaption></figure>

#### 5.1.1 Transfer to existing accounts. <a href="#toc158103560" id="toc158103560"></a>

From the registry account, the organization admin either searches for the name of the organization receiving the ICCs or provides an account number of the organization registry account. The project, vintage, and number of ICCs to be transferred are provided, and then the transfer is completed and confirmed. Both entities receive a notification and confirmation of the transfer with an email and within the registry platform to admins. The organization can transfer credits in both active and retired states.

#### 5.1.2 Transfers to new organizations <a href="#ref158055853" id="ref158055853"></a>

If the receiving organization has not established an account with ICR, the transferring organization needs to collect information about it to deliver the ICCs. Information required is.

1. Name of organization
2. Country of registration
3. Name of contact
4. Email of contact

By providing this information, the transferring organization can complete the transfer.

When completing the transfer, the transferring organization may choose to provide a comment to the receiving organization and, if the credits will be transferred in a retired state (only applicable for ex-post ICCs), a retirement reason. When transferring in a retired state, the receiving organization is the beneficiary of the retirement, and the transferring organization shall provide a reason for retirement.

After the transferring organization has confirmed the transfer, the contact person receives an email invitation to claim their user account and is provided with login details to access the ICCs in the ICR registry, where he can complete registration of the organization and view the inventory of ICCs and downloads certificates of retirement.

By default, the account created is private, with no public disclosure of inventory of ICCs or details of the organization. See further ICR registry user guide.

### 5.2 Retirement <a href="#toc158103562" id="toc158103562"></a>

The process of retiring ICCs in the registry is set out below.

1. An organization account admin needs to initiate a retirement from his respective user account.
2. Details of all retirements are stored on-chain on a public ledger, also presented in the ICR registry platform.
3. The admin selects the respective ICR ICC credits, vintage, and the number of ICCs for retirement.
4. The admin provides information about the reason for retirement.
5. ICCs are retired from the registry account holder's ICC holdings (i.e. when the holder requests ICC retirement of a part of its holdings).
6. A retirement certificate can be downloaded from the platform when the retirement has been completed.

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2FhZ4IkCzxfUZq2o3ZugXf%2Fimage.png?alt=media&#x26;token=81cddfb3-907e-49e0-879e-0a133f8688a7" alt=""><figcaption><p>Figure 28: Retirement process</p></figcaption></figure>

### 5.3 Cancellation <a href="#toc158103563" id="toc158103563"></a>

A cancellation of ICCs is initiated by the registry account holder, the other GHG program in which the registry account holder may participate, or ICR. Note that the initiator and recipient of an ICC cancellation request depend on the circumstances of cancellations (e.g., whether ICCs are being converted into another form of GHG credit). The cancellation request may be submitted to ICR by the other GHG program in which the registry account holder participates or collaborates.

An admin for a registry account initiates a cancelation from his user account.

The account holder may execute a cancellation through its ICR registry account. Details of all cancellations are recorded on the blockchain and mirrored in the registry platform.

The registry account holder may be asked to confirm the details of the request for ICC cancellation.

ICCs with a vintage T – 10 years, issued T – 3 years, and still active are cancelled by the ICR registry admin and are ineligible for retirement.

## 6. Transition from other GHG programs <a href="#ref157424868" id="ref157424868"></a>

Projects registered under an approved GHG program with a start date after 1. January 2020 may transfer their registration or also register their projects with the ICR. In such cases, the documentation required for the project registration process is the same as required for projects registering under the ICR requirements only, but noting the following:

* Reference to the project in the approved GHG program registry and for dual listing approval from the approved GHG program registry for dual registration.
* The latest version of the project design description from the approved GHG program and the latest version of the validation report from the VVB shall be uploaded to the ICR registry.
* Submission of the reason for transition or dual registration with ICR.
* The proponent shall further complete the ICR project design description by providing information in the following sections in addition to the cover page.
  * 1.1 - 1.16
  * 2.1 – 2.4
  * 4.1 – 4.4
* During the next verification event, the VVB shall complete validation on conformity to the ICR program criteria, i.e., ICR requirement document and ISO 14064-2.
* If a project remains registered with another GHG program that has completed monitoring and verification and the proponent intends to split up GHG emission mitigations between the ICR program and the approved GHG program. The proponent shall provide evidence that any GHG emission mitigation outcomes presented for ICCs issuance have not been and will not be issued as an environmental instrument under another GHG program or if such carbon credits have been issued under the GHG program that they have been cancelled. In the latter of these cases, the project proponent shall also sign and submit to ICR a formal letter of conversion to ICCs and provide evidence of cancellation.
* AFOLU and CDR projects are subject to the rules and requirements for non-permanence risk analysis and buffer withholding in section 4.4.1 and the ICR requirement document. A risk assessment determines the buffer withholding percentage and shall be applied to the ICCs to be issued under the ICR program and deposited to the buffer adjustment account.
* When a project, previously registered with another GHG program, seeks a renewal of the crediting period with the ICR, the project design description shall be updated using the ICR project design description template with relevant sections complete, as set out in the ICR requirement document and following instructions in the ICR templates. The criteria for validation shall be according to the ICR program. For the renewed crediting period, the ICR crediting period applies, and the project shall conform to ICR program criteria. Further, the project shall follow section 3 of the project cycle.
* If projects have created another form of GHG-related environmental instruments, such as renewable energy certificates, evidence shall be provided to ICR demonstrating that the GHG emission mitigation outcomes presented for ICCs issuance have not also been recognized as another GHG-related environmental instrument or that any such instrument has not been used and have been cancelled under the relevant program.

### 7. Withdrawal <a href="#toc158103565" id="toc158103565"></a>

If a project proponent wishes to withdraw a project from ICR (e.g., to transfer the project to another GHG program), the following applies:

1. The project proponent shall request formally that the project requests to be withdrawn from ICR. The letter shall, for a minimum, include the following:
   1. Project name
   2. Project ID
   3. Reason for withdrawal
   4. Signature of the authorized representative of the project.
2. ICR reviews the request and may request further information, e.g., outstanding fees payable or outstanding ICCs have been transferred and not been activated.
3. If ex-ante ICCs have been transferred and have not been activated, ICR may reject the request or require the project proponent to compensate for ICCs that have not been activated.
4. Upon approval of the request, the project's status is updated to "Closed" in the ICR registry, and details of the withdrawn project remain publicly available.
5. Any ICCs deposited to adjustment accounts cannot be reimbursed for the withdrawn project.
6. The process shall, from the time of submission of withdrawal, not exceed four weeks, subject to responses from the proponents to ICR clarification requests.

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F2WMLrUiR3NIBmslQfZtM%2Fimage.png?alt=media&#x26;token=326c0d7c-6a7e-45b9-9cfb-90dbfd9ad241" alt=""><figcaption><p>Figure 29: Project withdrawal.</p></figcaption></figure>

1. Withdrawn projects may rejoin the ICR conditional to a formal letter requesting participation and updated documentation.
   1. Project description document
   2. New validation report
   3. Verification report
   4. any methodology-specific documentation or other applicable documentation.
2. ICR reviews the documentation according to section 3.5 and determines if the project is eligible for participation again.

If the project is accepted, its status is updated accordingly.

### 8. Validation and verification bodies <a href="#ref157462282" id="ref157462282"></a>

All projects are subject to validation of projects and mitigations are subject to verification. Validation/verification bodies (VVBs) assess projects for conformity to ICRs requirements, ISO 14064-2. VVBs are qualified, independent third parties that ICR approves for validation and verification based on their accreditation. Validation and verification bodies are eligible to provide validation and verification services under the ICR if they have signed an agreement with ICR and are accredited under an ICR approved GHG program and/or accredited under ISO 14065 by an accreditation body that is a member of the International Accreditation Forum (IAF).

VVBs who are in the process of achieving accreditation or expanding their sectoral scope of accreditation may conduct a validation or verification as a part of their witness audit during their accreditation process with a member of the IAF.

### 8.1 Approval process <a href="#toc158103567" id="toc158103567"></a>

#### 8.1.1 Application <a href="#toc158103568" id="toc158103568"></a>

An authorized representative of the VVB completes an application form available on ICR's documentation page and submits it to ICR along with supporting evidence of accreditation.

#### 8.1.2 Application review <a href="#toc158103569" id="toc158103569"></a>

ICR confirms receipt of the application within 24 hours, reviews the application for completeness, and further requests to complete KYC and KYB. If improvements are needed, the applicant is informed. The process continues when requested improvements are complete, and KYC and KYB have been completed.

#### 8.1.3 Approval meeting <a href="#toc158103570" id="toc158103570"></a>

ICR suggests an introductory meeting for ICR to introduce the ICR program, the program documentation, and the role of VVBs and respond to questions from the VVB. After the meeting ICR shares a standard VVB agreement.

#### 8.1.4 VVB agreement signing <a href="#toc158103571" id="toc158103571"></a>

If both parties agree upon the terms of the VVB agreement, it is electronically signed by both parties, formalizing the contractual relationship between the parties and disclosing the terms and conditions of the relationship.

#### 8.1.5 Registry account <a href="#toc158103572" id="toc158103572"></a>

If the VVB has not already created a registry account, ICR will provide the details of the VVB, sectoral scope of accreditation, and other relevant information. The authorized representative will be assigned an admin role for the account.

Further, the VVB is added to the project registration form as an option for VVB.

#### 8.1.6 Status of approval <a href="#toc158103573" id="toc158103573"></a>

If the VVB does not comply with the terms and conditions of the VVB agreement, ICR may suspend or terminate the agreement. In such cases, ICR will change the status of approval.

<figure><img src="https://2441265052-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfIdoGcZZdvap67xjb5h1%2Fuploads%2F4oxFnoV8UG8Y3CuQMkSd%2Fimage.png?alt=media&#x26;token=2ceb0627-7464-4a3a-9f8b-8713494432fd" alt=""><figcaption><p>Figure 30: VVB approval</p></figcaption></figure>

### 8.2 Validation <a href="#toc158103574" id="toc158103574"></a>

VVBs validating projects and ex-ante estimation of GHG emission mitigations and requesting registration with the ICR shall follow ICR validation and verification specifications in addition to ISO 14064-3 when validating projects intending to register with the ICR.

In addition to the specifications, the VVB shall confirm that the project has been pre-registered with the ICR before signing a validation agreement with the project proponent.

During the validation assessment, the validation team shall be added as project members in the registry platform.

The validation team shall consider all information provided in the registry, the documentation provided by the project proponent, consistency with documentation provided to the VVB by the project proponent, and information in the registry platform.

The validation team shall consider all media provided by the proponent to the registry platform. All insights provided for the validation team shall assess if they relate to the project activities and represent the documentation fairly.

### 8.3 Verification <a href="#toc158103575" id="toc158103575"></a>

VVBs verifying monitoring reports and ex-post GHG emission mitigation shall follow ICR validation and verification specifications in addition to ISO 14064-3 when verifying projects' GHG emission mitigations and intending to issue ICCs with the ICR.

In addition to the specifications, the VVB shall confirm that the project has been validated and registered with the ICR before signing a verification agreement with the proponent\[14].

During the verification assessment, the verification team shall be added as project members in the registry platform.

The verification team shall consider all information provided in the registry, the documentation provided by the project proponent, consistency with documentation provided to the VVB by the project proponent, and information in the registry platform.

The verification team shall consider all media provided by the proponent to the registry platform. For all insights provided, the verification team shall assess if they relate to the project activities and represent the documentation fairly.

## 9. Assessment of conformity <a href="#ref157461216" id="ref157461216"></a>

The project registration, issuance, activation, or project crediting period renewal request process may be subject to an assessment of conformity by ICR. An assessment may be initiated at ICR's sole discretion.

ICR may, at its discretion, undertake an assessment of the registration, issuance, activation, or project crediting period renewal request to safeguard conformity to the principles and requirements of ICR.

If ICR undertakes such an assessment, ICR informs the project proponent and the VVB before any inspection is conducted. Any issues raised because of the assessment shall be addressed before further actions are completed in relation to the assessment of the project.

If no issues are raised during the assessment, ICR informs the project proponent and the VVB thereof, and the initiating process of the assessment can proceed.

If non-conformities are identified during the assessment, the project proponent and/or the VVB shall respond to the non-conformities by ICR. All communications shall be in writing by electronic means.

Where significant non-conformities are identified during the assessment, ICR informs the project proponent and/or the VVB and requests corrective action and/or clarification.

1. The project proponent and/or the VVB shall provide a written response to each non-conformity, undertake, or ensure that the project proponent undertakes, as appropriate, improvements to the documentation or other measures if necessary and submit all revised documents to ICR.
2. If findings are significant and not corrected to the satisfaction of ICR, ICR may conclude that the project has failed to demonstrate conformity to the principles, requirements, and/or applied methodology, and further registration, issuances, or activations are postponed until further notice or entirely withdrawn. ICR notifies the project proponent and the VVB. ICR will inform the relevant accreditation body of its findings.
3. If the project proponent and/or the VVB fails to address findings within 60 business days, ICR reserves the right to assume that the proponent does not intend to pursue further actions. If ICR has determined this to be the case, requests are not accepted, and ICR notifies the project proponent and the VVB.

At its discretion, ICR may review registered projects, issued ICCs, and activated ICCs if ICR has concerns about project conformity to the principles, requirements, and/or the applied methodology. Any of the following may initiate a review:

1. VVB identifies an error or quality issue in a previous validation or verification.
2. A project proponent identifies an error or quality issue after registration, issuance, or activation.
3. Interested party has concerns about a registered project.
4. ICR identifies error(s) or quality issues as part of routine operations or internal auditing.

If a conformity assessment is initiated, ICR informs the project proponent and the VVB of the review, which may postpone further issuance/activation while the assessment is performed.

If the findings identified during the review are significant, the VVB shall provide a written response to the findings. If not already suspended, ICR suspends further issuance/activation.

Follow-up actions of the VVB and/or project proponent shall include:

1. VVB shall conduct a root cause analysis.
2. If significant performance issues are found, and as appropriate, disciplinary action may be taken against the VVB, and its accreditation body will be informed.
3. VVB or project proponent, as appropriate, shall revise project documents.
4. The project proponent may need to compensate for excess issuance.
5. ICR cancels suspension on ICCs issuance and/or activations upon acceptance of project document revisions.
6. ICR and or the project proponent upload revised project documents to the registry.

When severe issues are ongoing and non-conformity to the principles, requirements, and/or, where relevant, applied methodology, ICR may cancel permission for future issuances of ICCs and/or registration of projects.

If ICR determines that ICCs have been issued in excess of the actual GHG emission mitigations, the following applies:

1. The project proponent shall deposit ICCs on ICR's adjustment account.
   1. Where excess ICCs remain in the project proponent's registry account, and it can be demonstrated that they have not been used for compensation purposes, immediate cancellation of the ICCs.
   2. Replacement of ICCs through immediate cancelation from subsequent issuances of ICCs from the project. If the project proponent has no holding on its registry account, deductions shall transfer to the subsequent activation of ICCs.
   3. Purchase by the project proponent of an equivalent number of replacement ICCs and cancellation of the same within 60 business days of receiving formal ICR notification of such required action.
2. Where the project proponent fails to compensate for excess Issuance, ICR may act against it, including applying sanctions with respect to its registry account activities until such time as the excess issuance has been compensated.

The project proponent pays all costs associated with the assessment of conformity when it relates to the project documentation.

If the assessment of conformity relates to validation and/or verification, the project proponent shall not bear the cost of any additional assessment.

Where the assessment of conformity is initiated due to routine operation or internal audit, ICR bears the cost of the assessment.

ICR may, at its sole discretion, decide to outsource the assessment.

## 10. Miscellaneous <a href="#toc158103577" id="toc158103577"></a>

### 10.1 Representation <a href="#ref151761248" id="ref151761248"></a>

The purpose of a representation deed is to establish an authorized representation for a project by appointing a focal. This representative is selected by the project proponent(s) to serve as their focal in matters concerning a project and/or the organizational account(s). Templates for representation deeds are available on the ICR documentation page.

Where multiple project proponents are involved, they all need to sign the representation deed, which is then submitted to the ICR and the registry platform. The focal can either be a third party or selected from among the project proponents themselves.

A communications agreement can also be used to appoint representation authority for projects with a single proponent.

To revoke the authority of representation, the sole project proponent (in single proponent projects) or all the proponents (in multi-proponent projects) shall provide a signed written notice of this termination to ICR. Following this, the project proponent(s) need to adhere to the stipulations above to create a new representation deed, as applicable. The new representation deed overrides any previous (terminated) representation of the project.

At any given time, a project may only have one designated focal, as determined through the representation deed.

The focal shall appoint individuals from the registry platform who are allowed to act as authorized representatives for the project.

The authorized representatives are identified as "admin" in the registry platform of each project.

### 10.2 Monitoring and reporting <a href="#toc158103579" id="toc158103579"></a>

Project details may be updated regularly by the project proponent, and, as necessary, further information on causes may be provided.

Any changes to the validated project design description shall be documented as soon as they occur. An updated project design description shall be uploaded to the registry, along with an updated validation report as applicable.

Project proponents shall respectfully submit monitoring and verification reports per the monitoring and verification plans. If the project proponent fails to submit a monitoring and/or verification report to the registry within six months of the monitoring plan and verification plan, the following applies:

1. ICR requests evidence from the project proponent showing that the project is still active.
2. The project proponent shall submit objective evidence within 60 days of receiving the request.

If the project proponent fails to confirm continuing implementation/operation, ICR may act against the proponent, including applying sanctions regarding its registry account activities until continuing implementation/operation has been confirmed.

When a project has not submitted a monitoring and verification report for 12 months based on stipulations in the monitoring and verification plan, the project is identified as inactive.

### 10.3 Insights <a href="#toc158103580" id="toc158103580"></a>

Project proponents may use the insights feature in the registry platform to share information about project activities. Note that insights shall be used conservatively, and when sharing insights about a project, they shall relate to that particular project. Images and videos shared shall directly relate to the project and include geo-location in the image or video file.

Project proponents, developers, VVBs, or other organizations may use the insights feature to share insights about their organization unrelated to specific projects. When doing so, they shall choose that the insight is posted on behalf of the organization, not a project.

### 10.4 Public comments <a href="#toc158103581" id="toc158103581"></a>

Stakeholders may submit comments about any project activities. Such comments shall be submitted to [admin@carbonregistry.com](mailto:admin@carbonregistry.com).

Comments received are shared with the project proponent, and the VVB performing the following validation/verification. Where the VVB has not been contracted, ICR shares comments received with the project proponent, and he shall provide the comments and any actions taken or comments responses to the validation/verification body.

Any comments received shall be addressed at the current or subsequent validation or verification unless ICR determines that an assessment of conformity is required, as described in section 9 above.

***

### Appendix – Document History <a href="#toc158103582" id="toc158103582"></a>

| Version | Date       | Comment                                                                                                                                                                                                          |
| ------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 2.0     | 11.8.2021  | Initial version under version 2.0.                                                                                                                                                                               |
| 3.0     | 6.1.2022   | <p>Main changes:</p><ul><li>Transition requirements from other GHG programs amended</li><li>Definitions amended, consistency referring to defined terms</li><li>Flowcharts improved for clarity</li></ul>        |
| 4.0     | 14.10.2022 | Alignment with revision of ICR requirements document and ICR methodology requirements in October 2022.                                                                                                           |
| 4.1     | 28.2.2023  | Update due to new platform                                                                                                                                                                                       |
| 5.0     | 6.2.2023   | Alignment with of ICR requirement document v.5.0 and ICR validation and verification specifications v1.0. Better alignment with ICR registry platform, processes to address reversal events and non-performance. |

1. VVBs are also identified specifically but identification is administered by the ICR. ↑
2. Temporary Organizational account may be created during retirements or transfers of ICCs, see section 5.1.2. ↑
3. Users may also be invited to join projects, see further in section 3 and in the ICR user guide. ↑
4. NOTE: Authorized representatives may be others than defined as stakeholders to the organization ↑
5. Note that the draft rationale does not have to include evidence of conformity at this stage and does not need to be publicly available. ↑
6. Private documentation and confidential information are never published on-chain. ↑
7. Projects may complete validation and verification jointly if they have been implemented completed monitoring for a monitoring period and completed a project design description and monitoring report. ↑
8. Information stored on-chain can‘t be removed. No private data or confidential information are disclosed on-chain. ↑
9. Minted ICCs are only eligible for delivery to the project proponent’s account. ↑
10. Deposits to adjustment accounts are always from the issuance of ICCs, e.g. if a project proponent issues 50% of estimated mitigation outcomes, he must deposit 2% of the issuance, i.e. 2%\*50%=0,1% of the total validated GHG emission mitigation. ↑
11. Additional credits can be added to each vintage based on findings in monitoring reports and verification by VVB. ↑
12. Validation and verification can be reported in a validation and verification report. ↑
13. For example: Verification report confirms 100.000 t CO2-e of GHG emission mitigations. 100.000 ICCs are issued and delivered to ICR holding account but the proponent only requests 10.000 ICCs delivered to its account. The proponent is invoiced for issuance 10.000 \* Ex-post issuance fee at issuance event. ↑
14. When performing joint validation and verification, the project needs to be pre-registered. ↑
