Verification Process

This section provides a general overview of the requirements for ex post verification of credits by the Regen Registry VVC that aligns with the Regen Registry policy for an independent third-party verifier. As defined in this section, verification will be conducted by the VVC team chosen by the Project Proponent as per the requirements stipulated in the applied protocol.

Regen Registry seeks a balance between adequate assurances, the overhead, and costs associated with verification. Therefore, each protocol can stipulate the requirements that are best suited to the ecosystem, best management practice and/or locale(s) to which it pertains.

Evidence Gathering

Verifiers shall take necessary and appropriate steps to assure the project inputs are authentic, using a random sampling approach whenever appropriate. If additional reports or evidence is required for the VVC to feel confident in approving data and/or monitoring report statements, all requests for clarification from the VVC to the project proponents must be documented as detailed as described in VVC Requests for Additional Information chapter.

Verifiers are required to provide assurance as to the reasonableness, accuracy and validity of the data the Project Proponent has provided to the Registry Agent and the Monitor. The VVC should check that there is alignment to:

1. Any specific guidance on the scope of evidence gathering necessary to provide reasonable assurance with respect to the data the Project Proponent provides the Monitor.

2. The verification requirements specified in the protocol should include but is not limited to the following categories:

   1. Project Plan - the verifier shall verify the information provided in the Project Plan.

   2. Project Ownership and/or Rights

      1. Verifier shall verify that the Project Proponent has legal rights/permits required to operate on the land or marine space defined in the project boundaries. If the Project Proponent is an organization, the verifier shall also verify the documents provided to the Registry Agent have been signed by the organization’s representatives without a reasonable doubt.

      2. The verifier shall choose the appropriate level of Land Owner rights verification from the list below, where the default shall be the least strictest approach. Documentation verification levels, from strictest to least:

         1. Evidence of land title or deed of ownership - official documentation of Federal / State government.

         2. Rate payments, such as utility services provided by local jurisdictions to the property and Project Proponent.

         3. Copies of email exchanges, letters, agreements or similar documentation (or their extracts).

      3. In the case the land is leased, the verifier shall also verify the lease agreement between Project Proponent (or the entity/individual represented) and Land Owner.

      4. If the Project Proponent is representing the Land Owner, the verifier shall verify the Deed of Representation between the Project Proponent and the Land Owner.

   3. Data inputs provided by Project Proponent to the Monitor - as stipulated by the Approved Methodology.

   4. The Monitor followed the procedures stipulated in the Approved Methodology.

   5. Compliance with protocol requirements such as:

      1. Project eligibility - see section above for full details. Including, but not limited to:

         1. Ownership/Permitting type - matches the type mentioned in Project Plan

         2. Project Activity falls within the defined accepted list of activities

         3. Project Area matches land tenure descriptions

         4. Adoption Date falls after the earliest accepted date and evidence is provided to attest to that

      2. No double issuance - see Avoiding Double Counting section

      3. Compliance with existing laws and regulations

   6. Leakage - verifying estimated leakage by Project Proponent is a reasonable estimate (for example, uses regional default emission factors or is in line with similar projects).

Verification Report

The collective VVC shall generate a report summarizing their findings per the requirements stipulated in the protocol, including a verification rating using the following or similar language:

Acceptance - if all the corresponding requirements in the Evidence Gathering section (10.4) have been satisfactorily met.

Acceptance with Contingencies

• If there were any deviations from the protocol

• If data provided by the Project Proponent (e.g. in the Project Plan) which is inconsequential to GHG or biodiversity metric estimation, could not be satisfactorily verified.

Rejection

• If project ownership could not be satisfactorily verified.

• If the Monitor did not follow key Methodology guidelines (excluding minor deviations).

• If data provided by the Project Proponent for the estimation of the key metric is suspected to be fraudulent.

• Lack of compliance with Project Eligibility, Double Counting requirements, or existing laws/regulations.

Verification Acceptance

1. The Regen consultant will review each the VVC verification report and proceed based on its rating as specified below.

2. The Regen consultant will post all verification reports publicly.

3. The Regen Agent will do a final check on the reports once they have been approved and submitted by the Regen consultant.

Acceptance

1. Regen Registry will issue credits (if applicable) to the Project Proponents per the monitoring outcome and Program Guide/Protocol stipulations.

Acceptance with Contingencies

1. The Project Proponent shall make the necessary corrections and clarifications per the contingencies identified in the report. If needed, the Verifier will resubmit their report after reviewing the information provided by the Project Proponent.

2. Registry Agent will issue credits (if applicable) following the Acceptance procedure above.

3. If the resubmitted verification report still retains the Acceptance with Contingencies, Registry Agent will highlight this in the corresponding MRV section.

Rejection

1. The project is put on hold until the issues identified are addressed (see Project on Hold section).

2. The carbon stock level will revert to the last level that was recorded and verified with the verification report with Acceptance or Acceptance with Contingencies rating. If the project has already been issued credits, then the Buffer Pool will be used to reconcile any gaps (see Buffer Pool section).

Verification Schedule

1. Verification is required prior to issuance. Any issuance of GHG removal or other forms of ecological credits which require verification based on the requirements stipulated in the credit class shall require a verification report prior to issuance.

2. Project Proponents shall follow the verification schedule required by the Credit Class. The Verification shall be completed within three months of the monitoring round.

Unscheduled Verification

1. The following circumstances will warrant a potential additional verification:

   1. A previous verification report with a Rejection or Acceptance with Contingencies ranking.

   2. Compliance verifications - when the Registry Agent has reasonable grounds to suspect the Project Proponent has contravened, is contravening, or is proposing to contravene with the rules and regulations.

Verification Oversight

1. The Registry Agent reserves the right to conduct oversight activities of verification performance participating verifiers. Oversight activities are conducted to ensure an adequate level of quality control and are intended to supplement accreditation body oversight and audit processes.