Registry Agent Review
## Project Registration
| Project Name | |
| :---: | :---- |
| **Project ID** | C06-\_\_\_ |
| **Crediting period** | |
| **Date of Submission** | |
| **Credit Protocol** | GHG Benefits in Managed Crop and Grassland Systems **Methodology**: Soil Organic Carbon Estimation in Regenerative Cropping and Managed Grassland Ecosystems. v 1.2.2 |
| **Regen Registry Program Guide Version** | 1.1 |
| **Project Proponent** | |
| **Registry Agents** | |
| **Documents Submitted:** | |
1. #
2. # **Registry Agent Review Overview**
### **Registry Agent Role in Project Registration**
The Registry Agent serves as the primary evaluator for new projects seeking to register under the Regen Registry Program. During project registration review, the Registry Agent conducts a comprehensive assessment of the Project Plan document and supporting documentation to verify compliance with Program Guide and Credit Protocol requirements. The Registry Agent must ensure that all foundational elements are properly documented and all requirements have been met before a project can be registered on Regen Ledger.
### **Registry Agent Review Checklist**
The Registry Agent Review Checklist provides a systematic framework for evaluating project compliance with the Regen Registry Program Guide and associated Credit Protocol. The checklist is organized by key requirements, with each requirement referencing specific Program Guide or Credit Protocol sections, defining required evidence, providing space to document submitted evidence, and including approval status and Registry Agent comments. Each requirement is assessed individually with decisions based on concrete evidence. This structured approach ensures thorough review of documentation while maintaining consistency across different projects and reviewers.
### **Approval Categories**
Approval determinations are made based on concrete evidence submitted by Project Proponents. For each requirement, the Registry Agent must verify that submitted evidence adequately demonstrates compliance. When evidence is insufficient or missing, the Registry Agent documents specific deficiencies and required actions for the Project Proponent.
Approval Categories indicate whether a submission meets Program requirements.
* Approved: The submitted evidence fully satisfies the requirements
* Not Approved: The evidence is either insufficient or missing, requiring additional documentation or clarification (note: projects may request requirements deviations is unable to provide sufficient evidence)
Approval means that the Registry Agent found that the project fully met the requirements for project registration with the submission of the Project Plans and supplementary documentation.
3. # **Review Outcome**
| Review Outcome Review Status \[ \] Approved \[ \] Not Approved Outcome Summary Required Actions: |
| :---- |
4. #
5. # **3 Registry Agent Review Checklist**
| Project Registration | | | | | |
| ----- | :---- | :---- | ----- | ----- | ----- |
| **Category** | **Requirement** | **Accepted Evidence** | **Submitted Material** | **Approved** | **Comments** |
| **General** | Projects shall apply the latest version of the applicable credit class and methodology **Source:** Program Guide, Section 8.1.3 | Project plan, methodology and credit class version are up to date. | **Primary Documentation: Supplementary Evidence**: | | |
| **Land Tenure** | Provide evidence of legal land tenure and control over the project area for the crediting period. In the case of leased land this must include landowner approval. **Source:** Program Guide, Section 8.2; Credit Class, Section 3.4, 3.5 | Deeds, lease agreements, land use agreements, or legal attestations confirming long-term control and ownership. | **Primary Documentation: Supplementary Evidence**: | | |
| **Project Area** ** ** | Demonstrate the property was not converted from natural ecosystems in the ten years before the project start date. **Source:** Program Guide, Section 8.3.1, Methodology, Section 2.1 | Timestamped image from sentinel color composite, NDVI, Google earth historical data, legal proof or attestation of land use history or similarly rigorous proof | **Primary Documentation: Supplementary Evidence**: | | |
| | Clearly define geographic boundaries of the project area with clear demarcation of areas eligible or ineligible for credit estimation. **Source:** Program Guide, Section 8.3.2. | GIS shapefiles and maps, with delineations of eligible and ineligible land. | **Primary Documentation: Supplementary Evidence**: | | |
| **Project Boundary** | Describe the project boundary, including relevant GHG sinks, sources, reservoirs, and other relevant ecological indicators. (if applicable) **Source:** Program Guide 8.4.1. | Project Plan section describing relevant GHG sinks, sources, reservoirs, and relevant indicators. | **Primary Documentation: Supplementary Evidence**: | | |
| **Project Ownership** | The project proponent must stipulate the ownership of credits and how they are distributed among stakeholders. **Source**: Program Guide, Section 8.5.1 | Document of credit ownership structure requirement in Project Plan or reference contracts | **Primary Documentation: Supplementary Evidence**: | | |
| **Project Start Date** | Project must stipulate the Project Start Date and justify how it meets the eligibility requirements **Source:** Program Guide, Section 8.6 | Explicit mention of the name, start date, and duration of the project in Project Plan. | **Primary Documentation: Supplementary Evidence**: | | |
| **Ecosystem Type** | **Classification**: Identify and classify the ecosystem being restored or managed, with details on vegetation types, soil characteristics, and climate zone. **Source**: Credit Class, Section 3 | Ecological assessment reports detailing ecosystem classification, including types of vegetation, soil, and climate characteristics. | **Primary Documentation: Supplementary Evidence**: | | |
| | **Conditions of applicability:** Project area ecosystem type may not change within 5 years prior to project start state. **Source**: Credit Class, Section 3.2 | Provide proof of land use for a 5-year period preceding project registration in the Project Plan and evidenced by farm-management records. | **Primary Documentation: Supplementary Evidence**: | | |
| **Crediting Period** | Define the crediting period and ensure compliance with credit class rules, which allows for a 10 year crediting period with option to renew **Source**: Program Guide, Section 8.7.2; Credit Class*,* Section 3.7 | Statement of crediting period length | **Primary Documentation: Supplementary Evidence**: | | |
| **GHG Accounting** | **Additionality**: prove that additionality test has been undertaken using one of the listed tests **Source**: Credit Class, Section 5.1 | Proof of additionality, either project or performance based | **Primary Documentation: Supplementary Evidence**: | | |
| | **Leakage**: Demonstrate that leakage is \>10% reduction in baseline yield **Source**: Credit Class, Section 5.2 | Included in annual report of crop yields | | | |
| | **Permanence Period:** the project shall have a 10-year permanence period **Source**: Credit Class, Section 5.3 | Explicit permanence period duration in the Project Plan | **Primary Documentation: Supplementary Evidence**: | | |
| **Regulatory Compliance** | Provide attestation of regulatory compliance demonstrating the project is materially compliant to all laws, regulations, and other legally binding mandates directly related to project activities. **Source**: Program Guide, Section 8.8 | Documentation of all relevant laws, regulations, or other legally binding mandates directly related to Project Activities and indications of where Project Activities violate compliance. | **Primary Documentation: Supplementary Evidence**: | | |
| **Registration on Other Registries** | Project Proponents must disclose if they have applied, been listed, registered, or issued credits under another registry, or if they have known plans to apply in the future. **Source:** Program Guide Sections 8.9.1., 8.9.2. | Official documentation from other registries detailing the project status, issued credits, or correspondence regarding approvals or rejections. | **Primary Documentation: Supplementary Evidence**: | | |
| **Project Plan Deviations** | Project Plan deviations must provide evidence that the proposed deviation meets the conservativeness standards of the Credit Protocol. **Source**: Program Guide, Section 8.12.2. | Statement in the Project Plan of proposed deviation | **Primary Documentation: Supplementary Evidence**: | | |
| **Monitoring Plan** | Provide a detailed plan for ongoing monitoring, including indicators, methods, and responsibilities. **Source:** Methodology, Section 5.1 | Monitoring schedules, soil sampling protocols, remote sensing details, and monitoring responsibility assignments. | **Primary Documentation: Supplementary Evidence**: | | |
| **Risk Management** | Provide buffer pool contributions of each issuance of 20% **Source:** Credit Class*,* Section 5.4 | Buffer pool allocation. For final permanence period monitoring, a buffer pool report is required. | **Primary Documentation: Supplementary Evidence**: | | |
| **Safeguards** | **Environmental, socio-economic safeguards**: Project Proponents must identify and address any negative environmental and socio-economic impacts of Project Activities and engage with local stakeholders to mitigate them. **Source:** Program Guide, Section 8.11.1. | Description of safeguard activities in Project Plan, impact reports, mitigation strategies and agreements. | **Primary Documentation: Supplementary Evidence**: | | |
| | **No Net Harm**: detail any potential negative socio-economic and environmental impacts of the project and the steps taken to mitigate them. **Source:** Program Guide, Section 8.11.1 | Documentation of conflict resolution, mitigation plans, grievance redresses | **Primary Documentation: Supplementary Evidence**: | | |
| | **Local Stakeholder Consultation:** Project Proponent must indicate how local stakeholders were identified and consulted prior to project implementation. **Source:** Program Guide, Section 8.11.2 | Descriptions in Project Plan, consultation documentation | **Primary Documentation: Supplementary Evidence**: | | |
| | **Environmental Impact:** Project Proponent must indicate if environmental impact assessments were undertaken and describe the process and findings. **Source:** Program Guide*,* Section 8.11.3 | Environmental impact reports and statements | **Primary Documentation: Supplementary Evidence**: | | |
| | **Public comment:** Specify if community public consultation was undertaken during the project implementation and how comments were addressed. **Source:** Program Guide*,* Section 8.11.4 | Statements and documentation from public consultation process | **Primary Documentation: Supplementary Evidence**: | | |
