# Regen Registry Handbook
A resource outlining the process of engaging with Regen Registry
### Regen Registry Overview
[Regen Registry](https://registry.regen.network) is an **ecological service registry** operating in the voluntary market that aims to support climate action by accelerating the adoption of nature-based solutions, which regenerate and restore natural ecosystems. Pulling on a combination of tools from Web3 and open source movements, Regen Registry aims to democratize and invigorate regenerative finance by empowering communities of Earth stewards, scientists, technologists, and climate entrepreneurs to govern the systems used to create new ecological assets.
Regen Registry is built on the understanding that ecological systems are inherently complex, and creating a one-size-fits-all solution does not address the financial constraints, access to scientific resources, and site specific limitations which prohibit the development of many ecological regeneration projects. By building the pathways for stakeholders to engage in the creation, development, and verification of ecological assets, we hope to maximize accessibility to payment for ecological services programs while ensuring regeneration projects best serve the needs of our communities and our planet and maintain high integrity.
### Regen Registry Handbook
The Regen Registry Handbook outlines the [structure of Regen Registry](/regen-registry-overview/structure), and details the frameworks stakeholders can use to create and issue ecological assets, known as [ecocredits](https://guides.regen.network/guides/regen-marketplace/ecocredits) on the Regen Registry, in an open marketplace. The handbook also outlines the general requirements for the quantification, monitoring, reporting, verification (MRV), project registration, administration and issuance of credits, and governance of the registry standards. More specific legal requirements are found in the Regen Registry Program Guide. Regen Registry credits are nature-based solutions, which provide ecosystem integrity, including GHG emission reductions and removals, biodiversity/habitat protection, improvement in water quality, etc.
# Structure
The Regen Registry can be divided into three main sections:
* The [Regen Registry Handbook](https://handbook.regen.network/) outlines the processes by which different stakeholders can engage in the **creation of new methodologies and programs** used to develop projects and issue credits using features provided by the Regen Marketplace App.
* The [Regen Ledger](https://docs.regen.network/) is the **underlying blockchain infrastructure** that stores all information related to claims made on ecological state to provide an open and audible trail for assets issued on our platform.
* The [Regen Marketplace App](https://app.regen.network/) is a **front-end application** which allows stakeholders to use Regen Ledger to register projects, buy and sell credits on an open marketplace, and engage in network governance.
# Scope
Regen Registry was developed to be a catalyst for ecosystem regeneration around the globe using blockchain, decentralized finance, and other Web 3.0 tools. To accomplish this, we are developing innovative ways to financially support people working to improve and maintain ecosystem health through the use of nature-based solutions (NbS). We follow a definition of NbS that is similar to the [International Union for Conservation of Nature (IUCN)](https://www.iucn.org) definition but we replace “sustainably” with “regeneratively” to define NbS as:
> “actions to protect, regeneratively manage and restore natural or modified ecosystems that address societal challenges effectively and adaptively, simultaneously providing human well-being and biodiversity benefits”.
This definition includes, but is not limited to, projects reducing negative direct impacts that humans have on ecosystem function, improving climate adaptation, and reducing global warming. Examples of projects that we support will be reflected in our growing list of methodologies.
{% hint style="info" %}
Regen Registry is focused exclusively on NbS. Other activities, for instance focused on sustainable energy or energy savings, transportation, industrial process, and construction, while undoubtedly important, are not the current focus of our program.
{% endhint %}
# Objectives
Regen Registry’s objectives are to:
* **Encourage nature-based solutions.** For example, solutions based on regenerative agriculture, conservation, and best management practices, as a strategy to mitigate (by removing/reducing GHG emissions) and/or adapt to climate change.
* Provide guidance for, and promote, **scientifically rigorous methodologies and credit classes** to foster the development of high quality ecological assets.
* **Create an open-source infrastructure** that allows cost-effective and rigorous MRV implementation, issues and tracks credits while avoiding double counting, and provides payments, billing, and marketing functionality.
* **Support best practices** in project-level GHG accounting and ecosystem services. Commercialize innovative types of credits bundled with valuable co-benefits and ecosystem services.
* Provide an environment to **develop new types of ecological assets** that will inform voluntary and regulated markets. Incorporate cutting-edge technologies, such as IoT sensors, satellite remote sensing, and digital signatures, in the use of project monitoring and verification.
* **Enhance public confidence** in market-based action for GHG removal and ecosystems’ regeneration.
# Definitions
This sections defines users that partner with Regen Registry and common terms used by Regen Registry
### **User Definitions**
**Aggregate Project -** A project in which multiple independently managed projects at different sites or locations within the same geographic region are registered together as a single project to strategically reduce the amount of data required for monitoring, reporting, and verification.
**Approved Methodology -** A methodology (or set of methodologies) that has been approved for use within Regen Registry, or more specifically, within a Regen Registry approved Credit Class.
**Baseline Scenario -** The hypothetical situation that represents the state or condition of an ecological system (like a habitat, species population, or ecosystem function) that would be expected in the absence of a proposed Project Activity. The Baseline scenario serves as a reference point against which outcomes resulting from the Project Activity can be measured to determine the net impact or benefit of those efforts. A baseline can be static, dynamic, project specific, or based on performance standard (or a combination of those).
**Buffer Pool -** A tool to mitigate credit class or project-specific risk factors associated with unintentional or intentional reversal events, or overestimation of credits issued. Buffer pools hold credits that cannot be sold to buyers, and reserve credits for potential cancellation from the Registry System to maintain accurate credit accounting.
**Buyer -** An individual or organization that is purchasing credits from the registry.
**Cancelation -** The permanent removal of an ecological credit from circulation in the Regen Registry System for purposes other than retirement. Reasons for cancellation could include reversals, non-compliance with Regen Registry or Credit Class standards, or migrating credits to a different registry system.
**Credit -** A digital asset, representing a quantifiable unit of measurement either tied to ecological or social benefit resulting from the implementation of a Project Activity, or tied to the successful implementation of a Project Activity rather than an explicitly measured benefit. Credits within the Registry System are tracked on Regen Ledger, and can exist in a Tradable, Retired, or Canceled state.
**Credit Class -** A standard or protocol which details the procedures for project registration and credit issuance for a specific set of Project Activities which provide ecological and social benefits. Such benefits could include GHG removal, emission reduction, environmental stewardship, and enhanced ecosystem function. Credit Classes define the structure, procedures, and prerequisites for registering projects and issuing credits. Typically, a Credit Class will establish one or more Approved Methodologies used to measure the impact of Project Activities. It also lays down the programmatic rules and stipulations for project registration and credit issuance, such as project eligibility criteria, Buffer Pool management and Verification requirements.. In certain instances, the process for measuring, reporting, and verifying ecological and social benefits might be directly integrated into a Credit class, rather than being outlined in a separate methodology.
Within the Regen Registry, each Credit Class operates as an independent standard or crediting program. This means that every Credit Class can possess its unique governance and issuance structure, buffer pool requirements, project registration prerequisites, and distinct group of project actors, all of which operate autonomously from other Regen Registry Credit Classes.
Credit Classes on Regen Registry also have a specific set of features provided by Regen Ledger (the Registry System used by Regen Registry). These include:
* A governance body known as the Credit Class Admin
* A set of on-chain anchored metadata defining the rules and regulations for this Credit Class, as well as a list of Approved Methodologies which may be used by projects registered in this Credit Class
* One or more on-chain Registry Agents who manage project registration and credit issuance
**Credit Class Admin -** An individual, organization, or group of individuals/organizations (private or public) that manages the rules and conditions necessary to issue credits under a Credit Class. The Credit Class Admin is responsible for maintaining the credit class protocol, list of approved methodologies, and subsequent documentation in accordance with the Regen Registry Program Guide. Additionally, the Credit Class Admin maintains the list of approved Registry Agents, maintains on-chain metadata for the Credit Class, and (if applicable) manages Buffer Pool Accounts for the Credit Class. To the extent that active management of the above allows, Credit Class Admins are responsible for ensuring integrity of all ecological claims accounted for in the Credit Class.
Credit Class Admins have sole control over the above on-chain components of a Credit Class, and can also transfer Credit Class Admin privileges to a new address at their own discretion. Credit Classes may be delisted from Regen Registry if a Credit Class Admin falls out of compliance with the Regen Registry Program Guide.
**Credit Designer -** An individual or organization that develops a new Credit Class or updates an existing one.
**Crediting Period -** The finite length of time for which a Project Plan is valid, and during which a project can generate credits.
**Credit Vintage -** The Credit Vintage refers to the year in which ecological credits were issued. Credit Vintages can generally refer to the year in which GHG emission reductions/removals or other ecological and social benefits occurred, however, the exact time frame might span multiple years for longer Reporting Periods.
**Issuance -** Issuance is the act of recording and assigning initial ownership of quantified ecological outcomes and carbon offsets in the form of a digital asset, known as credits, on the Regen Registry System, a public blockchain for recording all data, information, and transaction history related to carbon credits and other environmentally-related assets.
**Earth Steward -** The individual or organization that is implementing a Project Activity. This can be a farmer, rancher, conservationist, forester, fisherman, etc.
**Land Owner -** The individual or organization that holds title to the land where the project is occurring.
**Methodology -** A specific set of scientifically based criteria and procedures which outline the process for monitoring, reporting, verification of ecological and social benefits and practices for a defined Project Activity or set of Project Activities. This can include setting project boundaries, determining the Baseline Scenario, quantifying net GHG emission reductions or removals, measuring improvements in ecosystem function, and specifying monitoring procedures.
**Methodology Developer -** An individual or organization that develops a new Methodology or updates an existing one.
**Monitor -** An individual or organization that is contracted to measure the benefits / indicators defined in a given Credit Class based on the stipulations in the Approved Methodology.
**Monitoring -** The ongoing, systematic process of collecting and analyzing data to track the ecological and social benefits provided by a Project Activity, following the guidelines of an Approved Methodology.
**Permanence Reversal Buffer -** A dedicated Buffer Pool account that allocates a percentage of credits from each issuance in order to mitigate permanence related reversal risk, i.e. GHG removal reversal that has occurred over the permanence period of the project.
**Project Activity -** The specific land management practice or conservation activity employed by a project to support ecological or social benefits.
**Project Area -** The geographic area in which Project Activities are implemented.
**Project Boundary -** The geography within which the direct and indirect environmental, economic, and social impacts of the project are accounted for. This includes the Project Area as well as areas that may be indirectly affected, including potential offsite changes in GHG emissions or other ecological impacts attributable to the project’s implementation.
**Project Developer -** The individual or organization responsible for the detailed management of the project. The project developer, who can be the land steward or a third party, handles detailed planning, design, construction and implementation of the project.
**Project Page** - The dedicated web page for a given project on the registry. It provides an overview of the project, the activities taking place, timeline, images, maps, documentation, and more. All information on the Project age will be stored on Regen Ledger.
**Project Plan -** The document used to apply for Project Registration under a given Credit Class. The Project Plan describes the Project Activity or Activities, demonstrates project eligibility requirements, establishes project boundaries, specifies project stakeholders, justifies application of the Credit Class and Methodology, and more.
**Project Proponent -** The individual or organization that advocates for a project, identifies its requirements, and drives its initiation. The Project Proponent serves as the main point of contact with the Registry Agent throughout the course of the project and is responsible for initiating project registration, submission of all materials required by the Credit Class, Methodology, and Program Guide, and coordinating project actors. The Project Proponent must ensure correctness and compliance of all submitted documentation with the standards outlined in the Credit Class, Methodology, and Regen Registry Program Guide prior to to ensure credit quality. The Project Proponent receives the credits upon issuance and is responsible for coordinating sale and distribution between project actors.
**Project Start Date -** The date on which the project commences and begins generating and accounting for GHG emission reduction or removals or other ecological and social benefits. The Project Start Date may be before or after the project registration date as stipulated in the Credit Class. The Project Start Date marks the beginning of the Crediting Period.
**Project Termination** - The moment when a project that was registered on Regen Registry is canceled during its project term.
**Regen Registry -** A comprehensive program, platform, and process designed to establish community standards and legal frameworks for quantifying, monitoring, and trading ecological credits and managing other types of ecological claims. Regen Registry offers processes and tools for setting standards for Methodology and Credit Class development and approval, establishing and upholding frameworks for decision-making processes and appeals, and overseeing the use of the Regen Registry System by stakeholders using Credit Classes registered under the Regen Registry.
Central to its operation is the active engagement of the community. Designed with modularity in mind, the Regen Registry promotes shared decision-making among stakeholders. These stakeholders have the ability to propose and vote on pivotal decisions, form committees to supervise specific facets of the registry process, and collaboratively address disputes or challenges. As of Q3 2023, the stewardship of the Regen Registry is undertaken by RND PBC.
**Registry Agent -** The individual or organization appointed by the Credit Class Admin that operates the Registry System to register projects and/or issue credits under a given Credit Class. The Registry Agent is responsible for maintaining accurate accounting and ensuring compliance of registered projects, issued credits, and other ecosystem service claims as set forth in the Regen Registry Program Guide, Credit Class, Approved Methodology, and Project Plan. The Registry Agent is also responsible for ensuring updates made to the Registry Program, Credit Class, Approved Methodology and Project Plan are, if applicable, applied to existing projects in a way that is transparent and fair.
Selection of the Registry Agent is a crucial part of establishing checks-and-balances for credit issuance. As such, acceptance of Credit Classes to be registered under Regen Registry is contingent upon having a Registry Agent that has been approved or appointed by RND PBC as the stewards of Regen Registry.
**Registry System -** The technical infrastructure responsible for tracking information and claims related to ecological state. This system encompasses specific business logic, computer code, and programs that facilitate certain functions associated with the Regen Registry. While the Regen Registry sets the standards and frameworks, the Registry System provides the technical means to implement these functions. Built atop Regen Ledger, the Registry System's capabilities include, but are not limited to, registering projects, monitoring the issuance, ownership, transfer, and retirement (or cancellation) of ecological credits, anchoring and signing data, and transparently tracking decision-making practices.
Regen Ledger serves as the foundational blockchain layer upon which the Registry System operates to ensure transparency, security, and decentralization verification of all transactions and activities. The Regen Ledger is open-source and is publicly accessible.
**Reporting Period -** A period of time following the methodology guidelines in which Monitoring and Verification activities are completed.
**Retirement -** The permanent removal of an ecological credit from circulation in the Registry System after it has been claimed.
**Reversal -** A situation where project outcomes, such as carbon removals, improvements in biodiversity, or successful implementation of a practice are unexpectedly reversed. Reversal events can happen due to a variety of reasons, including natural disasters, changes in land use, poor project management, or failure to comply with project protocols.
**Site -** The location where a project implements the Project Activity or Activities. A project area does not need to be continuous and can have multiple sites.
**Validation -** The systematic, independent third-party assessment of a project prior to registration to determine whether a project conforms to the rules and requirements outlined in the Regen Registry Program Guide, Credit Class, and Approved Methodology, and evaluates the reasonableness of assumptions, limitations, and methods that support claims about the future outcome of Project Activities.
**Verification -** The systematic, independent, and documented assessment by a qualified and impartial third party of the Monitor’s assertions for a specific Reporting Period.
**Verifier -** An individual or organization that is contracted to execute the verification requirements stipulated in a given Credit Class.
### Methodology Definitions
**Co-Benefit** - The Intergovernmental Panel on Climate Change (IPCC) defines co-benefits of climate change mitigation as the positive benefits related to the reduction of greenhouse gasses. We define it more broadly as a benefit that is achieved along with the main indicator tracked and promoted in a given credit - which need not be a reduction of GHG. For example, a biodiversity credit might mainly promote the protection of a certain species and at the same time offer co-benefits, such as protection of water resources.
**Concept Note** - Means a submission of a methodology idea.
### Monitoring, Reporting, Verification Definitions
**Baseline Report** - The report that summarizes the Baseline Scenario.
**Monitoring Report** - The report that summaries the outcomes of the Monitoring Round.
**Monitoring Round** - A scheduled time following the methodology guidelines in which a monitor performs the measurement or estimation of an ecological indicator(s).
**Monitoring Service Provider**- An individual or organization that is contracted to measure the benefits/indicators in a given Credit Class based on the requirements of the approved methodology.
**Project Initial Monitoring Date** - The date when the baseline measurement was performed. Verification - A systematic, independent, and documented assessment by a qualified and impartial third party to the benefits assertions for a specific reporting period.
**Verifier Services Provider** - An individual or organization that is contracted to execute the verification requirements in a given Credit Class.
### Acronyms
* GHG - Greenhouse Gasses
* IPCC - Intergovernmental Panel on Climate Change (IPCC) is an intergovernmental body of the United Nations that is dedicated to providing the world with objective, scientific information relevant to understanding the scientific basis of the risk of human-induced climate change.
* AFOLU - Agriculture, Forestry and Other Land Use; a category of carbon credit projects that are related to agriculture, forestry, and other land uses (e.g. conservation).
* RND PBC - Regen Network Development, Public Benefit Corporation , the entity developing and operating the Regen Registry.
* SDG - the United Nations’ Sustainable Development Goals.
* GIS - Geographic information system is a conceptualized framework that provides the ability to capture and analyze [spatial](https://en.wikipedia.org/wiki/Spatial_analysis) and [geographic data](https://en.wikipedia.org/wiki/Geographic_data_and_information).
# Program Rules and Requirements
The Regen Registry Program Guide details the general requirements and specifications for the quantification, monitoring, reporting and verification (MRV), project registration, and issuance of credits on Regen Registry.
This document provides project stakeholders with programmatic structure from Regen Registry to develop projects, including credit classes and methodologies, the project registration process, project eligibility, and the issuance of tradable environmental assets to projects.
### [Regen Registry Program Guide v 2.0](https://regen-registry.gitbook.io/regen-registry-program-guide/)
* [Downloadable pdf Program Guide 1.1 ](https://registry-program-guide.regen.network/pdf/program-guide.pdf)Historical Document
# Template Library
A listing of resource templates for Regen Registry
#### Credit Class Template
* [Downloadable Credit Class Template](https://docs.google.com/document/d/11uUFU2CwjtXFMgBVkoQuxWc0UMfT-Pul56LHeSTMxaY/copy)
**Project Plan Template**
* [Downloadable Project Plan Template ](https://docs.google.com/document/d/1UNU0pcNoi44b7mHnLFTeYhVhpdhBDEOQCJfHXvmvMmI/copy)
**Monitoring Report Template**
* [Downloadable Monitoring Report Template](https://docs.google.com/document/d/1zZ1n7mOKKKno2_1Rj0RR9dPFizEG-F-HrI23Vwutq8E/copy)
**Credit Class Page Template**
* [Downloadable Credit Class Page Template](https://docs.google.com/document/d/1Q2ehJ8qaV1_e_FDXUwXfEPqF6YBtW4MKUTs7VJDvdc0/copy)
**Project Page Template**
* [Downloadable Project Page Template](https://docs.google.com/document/d/1AoD0JDDizdKObAmoTcH6g9MHmB96UN4jJGGpjIWhipE/copy)
# Registry Hylo Guide
Regen Registry Hylo is our dedicated gathering place for the Regen Registry community and the Regen Registry and Science teams.
The Regen Registry and Science teams seek to grow the community around the development of ecocredit standards, the Registry Guide, and the culture of Regen Registry as a community-driven regenerative registry. We use Hylo as the platform to encourage collaboration, support, and participation in this community. We invite all those with a desire to work with Regen Registry to join our community on Hylo.
This Guide illustrates how Regen Registry community members can engage with the Regen Registry and Science teams and with each other using the Regen Registry Hylo group. Find step by step instructions to orient you to the group, subgroups and Hylo’s functionality.
If you are interested in joining Hylo you can create an account [here](https://www.hylo.com/groups/regen-methodology-development) and introduce yourself.
{% tabs %}
{% tab title="Hylo Log In" %}
1. To start engaging on Hylo first create a Hylo account
2. This screen will prompt sign in and offer the user to login with google or manually enter an email
3. The user will be given the opportunity to tell us a bit about yourself, while this isn't required, it will make it easier to connect to others with similar goals
{% endtab %}
{% tab title="Joining Groups in Hylo" %}
1. In Hylo, a user can join groups and subgroups and they will be located in the group tab on the left of the screen. As more groups are joined, the stream, projects, and event pages will populate the content of the new groups
* These are all the groups that a user can join as a member of the Regen Registry group; however, some of them require admin approval
2. Simply, press the “Join” button to enter a new group
3. Access the groups joined by looking through the menu accessible from the top left corner
{% endtab %}
{% tab title="Posting " %}
1. One of the most important ways to engage with the community is through posting questions, events, and resources on Stream
2. Post by clicking the create button on the left side bar
3. Once in the post creation box, decide what kind of post it will be, the topics (hashtags), the title. You can cross post the same item in more than one group.
{% endtab %}
{% tab title="Events" %}
#### Events
1. The events feature is used to look for past and upcoming events, which can be accessed by toggling between the two
2. RSVP to events and invite other guests
3. Additionally, if a user has an event to share with the community, post it here by using the create button on the left side bar
####
{% endtab %}
{% tab title="Members" %}
1. The Member and Maps pages allow users to find new members in their bioregion or based on similar skills, interests or areas of work.
{% endtab %}
{% tab title="Resources & Projects " %}
#### Resources
1. All of the groups have group-specific resources available for viewing that can be found listed under the left sidebar below Map. For Regen Registry main page, we link out the Registry Homepage and the Registry Guide. Each group will have different resources.
#### Projects
1. Under Projects on the left sidebar, users can view under development methodologies being developed through Regen Registry
2. In each of the projects learn more about the scope, access links, and ask questions on the project thread
3. Projects from child groups will automatically populate in the main group. At this time, child groups projects tab will be empty as we configure relationships between child groups and the main Regen Registry group.
{% endtab %}
{% endtabs %}
# Protocol (Methodology) Development Overview
How to develop a protocol (also known as a methodology) with Regen Registry
The protocol details the credit type, credit unit, project activities, ecosystem type, monitoring, reporting and verification (MRV) process that is specific to a project.
As a methodology is being developed, the Regen Registry and Science Teams are available for limited internal feedback as part of teh Protocol Review process that as outlined below.
Please also join our [Hylo space](https://www.hylo.com/groups/regen-methodology-development) to engage in community support. See the [Methodology Development Support](/protocol-development/protocol-development-support) chapter for more details.
**Protocol Development Process:**
The development of a protocol includes:
* Research into existing approved methodologies in the [Regen Registry Methodology Library](https://handbook.regen.network/public-comment-upcoming-methods/) and those listed on other registries that may be similar, are tested and can be used as models for your methodology.
If using a methodology from an outside registry, it is the methodology developers responsibility to contact the author of the methodology to ask for permission to use that methodology. Cited resources and/or first hand interviews and accounts of regenerative work and observed successes from knowledgeable and experienced earth stewards in the projects specified ecosystem outline of researched monitoring approach including monitoring protocols and frequency description of verification process.
# Submitting a Methodology
### Where to Start
It might seem like an overwhelming process, but we’re here to help! Prior to developing a methodology, take a look to see if there is a similar methodology that is already approved on our program or other accepted programs either from our [Methodology Library](http://library.regen.network) or from various third party programs such as:
* Terrasos - [Biodiversity Credits](https://en.terrasos.co/_files/ugd/cfa1dc_5af4fd0405c04e4a85c59dc9a3e3293b.pdf)
* Verra: [VCS](https://verra.org/methodologies-main/), [CCB](https://verra.org/programs/ccbs/) & [Jurisdictional & Nested REDD+](https://verra.org/programs/jurisdictional-nested-redd-framework/) Programs
* UNFCCC - Afforestation and Reforestation for [small](https://cdm.unfccc.int/methodologies/SSCAR/approved) and [large](https://cdm.unfccc.int/methodologies/ARmethodologies/approved) scale projects
* [Gold Standard](https://globalgoals.goldstandard.org/documents/methodology/)
* [American Carbon Registry](https://acrcarbon.org/methodologies/approved-methodologies/)
* [Climate Action Reserve](https://www.climateactionreserve.org/how/protocols/)
* [Accounting for Nature](https://www.accountingfornature.org/method-catalogue)
* Greencollar [NaturePlus](https://greencollar.com.au/our-services/natureplus/) & [Grazing Land Management](https://greencollar.com.au/grazing-land-management-method-reef-credits/#)
If you plan to use a methodology from another existing registry program and would like to consider adding to this list, please contact us at .
{% hint style="info" %}
At this time, Regen Registry requires all parties to review and sign the [Regen Registry Terms of Service](https://docs.google.com/document/d/1WGvPI5NjsS4WhMCL3AyRa0oHP6j2R34YByNVRo8XDkA/edit#heading=h.ew69mclrluk) to legally engage with and fully understand definitions, contracts and processes of working with Regen Registry. If you plan on submitting a methodology to the Regen Registry program, please review our terms of service and our team will contact you upon submission. Please contact with any questions.
{% endhint %}
### Submitting a Fully Developed Methodology
To submit a methodology that has already gone through a peer review process, or exists on another registry, please submit through our [Methodology & Credit Class Intake Form](https://airtable.com/appzrw40tJdLBM2RS/shrLCL7ioWuGLSc7g). Your methodology will be reviewed by our Registry and Science Teams and we will get back to you with next steps.
### Submitting a New Methodology
#### Submit a Concept Note
A concept note is a short proposal of an idea for a project or methodology and/or credit class. If you are a researcher or project developer with an idea for a methodology and/or credit class, whether for monitoring a particular ecosystem change or an approach to address environmental and societal challenges, a concept note is a good starting point to get your thoughts on paper. Ideas can range from a fully developed concept note to a rough draft.
Use the [Concept Note Submission Form](https://airtable.com/shrunsKASd5BDfI0N) to submit a concept note. Upon submission, our team will review and respond within 3 weeks to approve or suggest edits required for approval.
#### Submit Your Methodology
Your methodology draft should outline standards and tools to monitor the ecological, environmental, and social indicators covered by your nature-based solution. Your approach can be region specific or cover a wide range of locations.
At this time, if you plan to register a new methodology with Regen Registry, we require that you go through internal review, expert peer review and a two-week public comment period to register a methodology with the Regen Registry. We also ask that you submit your credit class at the same time as your methodology. While the credit class and methodology are separate documents, Regen Registry requests that they be submitted together for internal and expert peer review process. The reasoning for this is that traditionally the contents of these documents have been combined into the methodology so the Regen Registry asks that they be submitted together due to the correlative nature of their content.
Note: We are working on options for a permissionless processes.
When you are ready to submit, use the [Methodology & Credit Class Intake Form](https://airtable.com/appzrw40tJdLBM2RS/shrLCL7ioWuGLSc7g) to submit a methodology draft for internal review.
For more information on methodology submission requirements and the continued development process please read the [Methodology Developments Overview](/protocol-development/protocol-methodology-development-overview) chapter.
# Protocol Development Support
Support during the stages of Methodology Development
Regen Registry supports protocol developers during the process of protocol development through internal support, facilitation of an Expert Review process and access to our broader community network.
Throughout the process of protocol development, [Regen Registry’s Hylo](https://www.hylo.com/groups/regen-methodology-development) and [Twitter](https://mobile.twitter.com/regennetworkdev) spaces will serve as community conversation spaces. These spaces allows for sharing updates on the latest news in all things Regen Registry: cutting edge protocols, carbon accounting, nature-based solutions, biodviersity credits, crypto and more. The RND community of scientists, Earth stewards, technologists and more engage in these spaces.
**Support:** Throughout the protocol development process, Regen Registry will provide email and call check-ins. These check-ins occur at the discretion of Regen Registry or as requested by the developer to address timeline, feedback and process questions. Regen Registry also works to connect protocol developers with targeted people and organizations in our network who can support the development of the protocol through active community networking and co-working spaces.
# Protocol Review Process
Internal Review, Expert Peer Review, & Public Comment
### Protocol Review Process
The protocol review process consists of four stages:
1. Initial Review of Concept Note/Draft and Acceptance into the Review Process
2. [Internal Review](#internal-review) (4 weeks)
3. [Expert Peer Review](#expert-peer-review) (approx. 3-6 months)
4. [Public Comment](#public-comment) (14 - 30 days)
Each stage is described below. The length of time to complete the expert peer review depends on availability and response time of expert peer reviewers as well as the amount of comments to address and number of review cycles needed for the methodology review lead to approve the methodology.
## Initial Review of Concept Note/Draft and Acceptance into the Review Process
In order to implement an effective and efficient review process we encourage protocl developers to submit high quality protocols for review. Regen Registry will do an initial review and assessment of the protocol to determine if it is ready to proceed with the review process of if it needs additional work before engaging in that process. The Regen Registry will provide suggestions for improvement at this stage if is determined that the protocol requires more work before proceeding to the nest stage of the Review Process.
## Internal Review
The intent of the internal review is to ensure that the protocol adheres to the requirements outlined in this Handbook and Guide and that the quality of the protocol framework is sufficient to warrant review by expert peers.
Regen Registry aims to complete the internal review in less than four weeks. If the protocol still requires updating, it will be returned to protocol developers with feedback on how to improve it. Otherwise, the methodology review lead will approve the methodology to proceed to the Expert Peer Review stage.
## Expert Peer Review
The Expert Peer Review will focus on ensuring that the proposed protocol is scientifically robust and likely to produce the expected outlined results. Regen Registry will hire a minimum of two peers from the expert community that have sufficient expertise to evaluate the proposed protocol. We may use the list of potential expert peer reviewers submitted with the protocol and will identify additional reviewers at the discretion of the protocol review lead. This selection process can take a few weeks to accomplish. More information about the process that reviewers will follow can be found in the [Expert Peer Reviewer Guidelines](#expert-peer-reviewer-guidelines) section below. When the protocol review lead is satisfied that the protocol is acceptable the protocol developer will be notified and the final [Public Comment](#public-comment) phase will begin.
#### **Anonymity**
We will be using a single-blind review process where the names of the protocol developers are known throughout the process but the expert peer reviewers remain anonymous until review have been completed. At that time the expert peer reviewers have the option of being listed as reviewers on the protocol listing.
#### **Review**
Once a reviewer accepts to review a protocol they will have four weeks to provide feedback. In some cases more time will be allotted to accommodate reviewer scheduling constraints.
Expert Peer Reviewers will fill in a Revision Report with suggested comments. This report if passed to the protocol developer by the protocol review lead.
#### **Revisions**
The protocol developer is required to address each comment and provided a tracked changes new version of the protocol along with responses to each comment in the Revision Report so that the expert peer reviewer may check that each of their comments were addressed in a complete manner. If necessary, the protocol review lead will request additional feedback to clarify expert peer reviewer feedback that is not clear or is contradictory.
Once the expert peer reviewer has completed the reponses check the protocol review lead will decide if the protocol needs to go out for a second (or more) round of expert peer review to resolve any comments. If it goes out for review again, an effort will be made to use the same reviewers (if they formerly accepted to review future versions) or new reviewers will need to be found. If new reviewers are used, they will be made aware this is a revised methodology and they will need to have access to the revisions and past comments.
### **Expert Peer Reviewer Guidelines**
The task of a reviewer is to provide critical feedback to the protocol developer to help them improve the protocol. The reviewer should consider themselves an ally of the protocol developers.
The protocol review lead will contact potential reviewers until a minimum of two people commit to review the methodology. When a potential expert peer reviewer is contacted they will be offered a stipend to complete a review at the discretion of the protocol review lead.
If a review cannot be submitted within the three week time period, the expert peer reviewer should contact the protocol review lead as early as possible to request an extension.
The review should provide feedback on the validity of the protocol. Specifically it should address the following:
* Is the protocol clearly written with adequate detail for implementation?
* Is the underlying foundation of the protocol clear?
* Is the protocol feasible?
* Will the proposed protocol achieve the defined results?
* Are the sampling and measurement protocols robust?
* Are there any alternative or additional steps that should be considered?
* Any additional questions noted by the protocol review lead
* Is governance and stakeholder engagement clearly outlined?
In addition to review comments, the expert peer reviewer should also indicate if they are willing to review a future version of the protocol and if they want to be named in the review.
## Public Comment
After a protocol has successfully completed the Expert Peer Review process it will advance to the final Public Comment stage. Comments about the protocol will be solicited from the general public for a period of 14 days. The public commenting period will be announced on [Regen Registry Hylo](https://www.hylo.com/groups/regen-methodology-development) and Regen Network Development (RND) typical social media platforms (ie [Twitter](https://twitter.com/regen_network?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) and [LinkedIn](https://www.linkedin.com/company/regen-network/)).
Protocols open to Public Comment are posted on the [Call for Public Comment](https://handbook.regen.network/methodology-library/~/changes/138/methodologies-and-credit-class-open-for-public-comment/call-for-public-comment) page. Comments can be made through the Public Comment link found on the posting page. People submitting comments directly will have the option to remain anonymous (the default option) or they can request to have their name attached to the comments.
Comments should be constructive and developed with the intent of improving the protocol and in the spirit of an ally with the protocol developer. The points noted in the [Expert Peer Reviewer Guidelines](#expert-peer-reviewer-guidelines) section can be used to guide the types of comments we are looking for.
After the 14 day Public Comment period, the protocol review lead will compile comments and synthesize them before sending them to the protocol developer. If there are major concerns that cannot be confidently resolved within Regen Registry, input from the expert community will be requested. Also, some clarification might be requested from the commenters when necessary by the protocol review lead.
The protocol developer will have six weeks to respond to the synthesized comments and return the revised protocol, along with responses to feedback, to the protocol review lead. The internal Regen Registry team will review the changes and decide if the protocol is sufficient to be accepted into the [Regen Registry Protocol Library](https://www.registry.regen.network/crediting-protocols), or if more work is required. If more work is required, the protocol review lead will request the protocol developer to make specific changes and resubmit to the internal team.
# Who are Expert Peer Reviewers
What we look for in Expert Peer Reviewers, the benefits of participation and how to participate
**Why An Expert Peer Review Is Important**
The peer review process provides valuable feedback for those developing methodologies. It is a method of review that is widely respected and understood and creates value for your project. Overall, the process works to advance the field of nature-based solutions (NBS) by helping to create standards that elevate the value of NbS’s.
**Why it is Important for Experts to Engage in Peer Reviews**
Reviewers benefit by exposure to novel applications in their fields of interest. Tenure committees look favorably on participation in peer review, and invitations to review underscore that the reviewer is a respected subject matter expert. Contacts made during the peer review process can lead to long-lasting collaboration.
Early career researchers (ECRs) could and should also become involved in methodology peer review. Becoming a reviewer early in your career helps you to better appreciate the feedback you receive as an author. A further benefit is it provides training in evaluating research critically. Are their methods suitable? Do their methods seem valid and appropriate for the intended goals? There is a clear reason for ECRs to become reviewers from a personal perspective, but the academic community benefits more widely. ECRs form a significant component of the academic community, and their involvement in peer review spreads out the workload, resulting in a more efficient process.
**How to Become a Regen Peer Reviewer**
Are you an expert in a nature-based solutions field, environmental economics, a specific ecological region or greenhouse gas accounting? Would you like to become involved in reviewing novel methodologies?
Peer reviewers should have significant expertise and experience with standardized approaches. Methodology developers, policy makers, market analysts and validation/verification bodies, among others, are invited to apply. Familiarity with VCS methodology development and assessment is useful but not essential.
Peer reviewers should expect to commit 4-8 hours to the task.
**Steps for Expert Peer Review (Regen Registry)**
* You will receive the methodology for review that you can add inline comments to
* You will receive a template for additional and general summary comments
* You will review and provide feedback and wait for a revision report and response from the methodology developer and review comments and revisions and send back as a pass or request additional updates
* A maximum a round of 3 reviews will be completed
* Payment - $300 stipend
* Goal will be to complete the process within 3 -4 weeks with variability expected depending on response times.
* Your name will appear on the project documentation as an Expert Peer Reviewer
Interested? Fill out our [Expert Peer Review](https://airtable.com/shrbKRhZUUQXhVI50) inquiry form!
# Approval of New Credit Protocols and Credit Types
This section describes how new credit protocols and credit types are formally approved into the Regen Registry once expert review and public comment have been completed.
### Overview
Regen Registry’s governance processes are designed to uphold the principles outlined at the beginning of this Handbook while ensuring decisions are transparent, participatory, and accountable. The goal is not only to confirm the technical rigor of new credit protocols and credit types, but also to align them with Regen’s broader mission of ecological regeneration and public benefit. To achieve this, protocols move through a sequence of expert and public review, community feedback, and on-chain decision-making. This structure ensures that diverse perspectives are heard, that approvals are guided by shared values, and that all outcomes are permanently and transparently recorded on chain.
### Approval of Credit Protocols
After the expert review and public comment period (described in previous chapters) the approval process proceeds:
* **Final Confirmation**: Once either (a) all comments are resolved, or (b) the Registry Agent has made a decision on outstanding issues, the protocol can proceed.
* **Notification**: The Registry team notifies the methodology developer of the approval decision.
* **On-Chain Record**: The Regen Registry team will create a proposal in the DAODAO Regen Registry and vote to approve the protocol. This ensures a transparent and permanent log of all approved protocols (beginning fall 2025).
### Approval of New Credit Types
If the credit protocol involves a new credit type, the new credit type must go through a governance process for acceptance.
* **Credit Protocols vs. Credit Types**: Most new methodologies are approved as credit protocols. However, if the proposal establishes an entirely new **credit type** (e.g biodiversity credits vs. carbon credits), it requires broader governance
* **Governance Pathway**:
1. **Forum Proposal**: The proposer must first introduce the credit type concept in the [Regen Forum.](https://forum.regen.network) This creates an open space for community members, stakeholders, and experts to review and provide feedback.
2. **Feedback Period**: A minimum **two-week period** is required for discussion, refinement, and feedback from the community before advancing to a formal vote. This ensures transparency and broad input.
3. **Governance Vote**: After the feedback window closes, the proposal can be submitted as a governance vote. Approval is determined by the Regen community of token holders, following the on-chain governance process.
* **Historical Log**: Approved credit types and the associated decision on acceptance are recorded on chain
**Note**: For step-by-step instructions on submitting governance proposals on chain, see the [Regen Network technical documentation on message-based governance proposals](https://docs.regen.network/tutorials/user/message-based-governance-proposals.html?utm_source=chatgpt.com#introduction).
# Key Protocol Components
**General requirements:**
* Project Eligibility: Ecosystem Service Classification, Ecosystem Type
* Project rules and regulations
* GHG Removal and Emission Reduction Requirements
* Verification requirements
* Purchasing, Retiring, Selling credits
* Buffer Pool
* GHG accounting related requirements including permanence, leakage and additionality
* Compliance requirements
* General Co-Benefits that could apply
* Crediting Unit
* Crediting Term
* Project emissions
**Measurement approach for developing monitoring reports:**
* Methodology overview
* Definitions
* Baseline scenario
* Monitoring and measurement approach
* Specific Co-benefits
* Reporting - methods and cadence
* Uncertainty
NOTE: There may be the option to work with a protocol developer to ammend a protocol - specifically the measurement approach - to be more propoerly tailored to a specific project and the stakeholders engaged in that project management and implementation.
# Credit Type
Each credit protocol is associated with a credit type that defines the primary unit of measurement used to quantify the ecological asset being traded (i.e. carbon, biodiversity, etc).
Carbon credits, for example, represent a metric ton of CO2e, which is a standard used to measure greenhouse gas emissions. This unit of measurement can be used across a variety of credit protocols. Reforestation projects, grazing practices, and blue carbon projects all focus on carbon sequestration and share the same credit type (carbon) despite corresponding to different credit protocols. Regen is exploring new credit types with various partners based on metrics of biodiversity, environmental stewardship, water, etc.
New credit types can be created via going through an on-chain governance proposal.
The list of allowed credit types is managed via on-chain governance. More information about governance can be found on [Regen Network Guides: Governance](https://guides.regen.network/guides/network-governance).
# Co-Benefits
A credit protocol may define a series of ecological and social co-benefits indicators to apply in conjunction with the approved protocols.
Co-benefits allow for a holistic assessment of the project beyond carbon sequestration based on credible and rigorous metrics.
The quantification process for each co-benefit shall be specified in the approved protocol(s).
# Writing a Credit Protocol - Guidelines
Project eligibility, rules and regulations, GHG removal and emission reduction requirements if applicable
{% tabs %}
{% tab title="Project Eligibility" %}
#### 1. Ecosystem Type / Ecosystem Service Classification
A credit class must define the ecosystem types, or other geographical boundaries such as proximity to a stream, elevation, or cultural or political boundaries where it can be applied. And if it can be applied to multiple classification types.
#### 2. Land Ownership Type
A credit class must stipulate the land ownership types that can be utilized, including private, public, and tribal as well as the documentation requirements or land ownership or approval by land owners or tenures.
#### 3. Conditions for Applicability
Conditions which make a piece of land eligible for enrollment in this program. Outline specifics requirements for how projects should prove applicable conditions and what needs to be reported during registration as part of the project plan. This could include geographic restrictions.
Outline the eligibility requirements for land which would be eligible for enrollment in this program. For instance projects which previously were wetlands or native forest which got removed recently should be excluded as it indicates that land stewards could have potentially removed native ecosystems to make money via the carbon market.
#### 4. Regulatory Compliance
Specify any checks projects must go through to ensure that their implementation and ability to make carbon claims adhere to any local laws, regulations, and other legally binding mandates directly related to project activites and participation in voluntary carbon markets.
You can either be specific with what these requirements are, or just state that the, “The Project Area has to adhere and provide attestation of compliance to the local laws,regulations, and other legally binding mandates directly related to project activities as presented in the approved and applied methodology.”
#### 5. Adoption Date
A credit class must stipulate the Adoption Date. A credit class must stipulate how many years an Adoption Date can be established prior to the Project Registration Date.
In order to claim an Adoption Date before the Project Registration Date, the Project Proponent must have maintained clear historical records to that effect, as specified in the Approved Methodology.
#### 6. Crediting Term
A credit class must define a crediting term - the number of years credits are eligible for issuance with the option to renew.
A credit class must define the frequency of credit issuance during the crediting term
A credit class must define the number of years in a renewal time period. There is no limit to the number of renewals on Regen Registry.
The project duration does not include the Permanence obligation of Regen Registry, which is additional.
{% endtab %}
{% tab title="Rules and Regulations" %}
**1.Approved Methodologies**
A credit class must list the approved methodologies that can be utilized with a given credit class. The credit class admin will update this list as new methodologies are added.
#### 2. Aggregate Projects
Aggregated projects (as opposed to a project aggregate) is when the Project Proponent registers a single project which would encompass many plots of land that collectively share data for MRV and split credit rewards.
When project aggregation is permissible, conditions under which aggregation is allowed would be defined here. Requirements for project aggregation can be broadly classified into two categories: eligibility requirements and monitoring requirements. Eligibility requirements refer to the conditions that must be met for multiple plots of land to enroll as an aggregated project. Monitoring requirements refer to the guidelines that aggregated projects must follow during reporting periods. Eligibility requirements should be stored in the credit class; monitoring requirements should be stored in the methodology.
The credit class should contain high-level summaries or programmatic requirements aggregate projects should follow whereas the methodology should specify implementation requirements (ie how to measure, aggregate data, and report).
#### 3. Carbon Sequestration and Net GHG reduction (if applicable)
A credit class must provide carbon removals which sequester carbon. To ensure a net positive effect, aside from CO2 removals from the atmosphere, other significant sources of GHG, such as Nitrous Oxide (N2O) and Methane (CH4), must be included.
The benefit that is monitored, quantified and used to infer the quantity of credits issued is Carbon Sequestration and Net GHG reduction. Regen Registry does not incorporate the other co-benefits monitored in this quantification.
The unit of measure used is tons of CO2e, i.e. each credit represents 1 ton of CO2e.
#### 4. Ecological and Social Co-Benefits
A credit class may define a series of ecological and social co-benefits indicators that can be applied in conjunction with the approved methodologies. For example, for a carbon sequestration methodology co-benefits might include increased biodiversity, improved health for local human communities, and improved soil health.
#### 5. Permanence and Buffer Pools
Buffer Certificates
Project Buffer - % allocation and type of buffer (see below)
Permanence Reversal Buffer
Permanence Period (time period)
Permanence Reversal Buffer - % allocation and type of buffer (see below)
***Structure Options:***
1. Credit Class Buffer - A single buffer pool for the credit class that all projects contribute to. As the project developer it allows for aggregating risk across projects as the structure is a larger pool to pull from if a single project experiences significant loss.
2. Project Specific Buffer - Each project would have its own buffer pool. This scenario places more risk on individual projects/the project developer if they experience loss because they might not have the credits to cover it and would have to resolve it as specified in our Regen Registry Program Guide. It does however address concerns individual projects might have on the idea of shared risk if they don’t want to cover other projects which might be deemed “more risky”.
\
\&#xNAN;*In the future the Regen Registry will set up a shared buffer pool that credit classes can opt into if they want to share risk with other crediting programs, but we will hold off on that until we have more credit classes and a better understanding of how we want to tackle the idea of fungibility.*
**6. Verification**
In this section you should specify exactly what the requirements verifiers must follow to audit a monitoring report.
1. Define if ISO certification is required
2. What type of audit the verifier should conduct (desk audit, field audit, or combination) and a list of specific things they should be checking for
A credit class must define requirements, if any, for 3rd party, independent verification of outcomes.
A credit class may define adaptations for specific locales in the Supplement section.
{% endtab %}
{% tab title="GHG Removal and Emission Reduction Requirements" %}
#### 1. Additionality
The Approved Methodology specifies how the baseline and the additional carbon emissions reduction and/or removal is calculated.
Carbon sequestered is carbon removed from the atmosphere and quantified through the approved methodology, not only reduced future emissions.
#### 2. Leakage
Carbon sequestration to land reservoirs can be associated with reductions in GHG emissions both within and outside of project boundaries. A credit class must define the relevant carbon pools for approved project activities.
Project Proponents that expect leakage above de minimis shall account for that in the Project Plan.
**The Regen Registry Program Guide outlines the rules and requirements for:**
* Credit Class & Methodology Approval
* Project Registration
* When credits can be issued (i.e. when all conditions in credit class are met)
* Credit issuance, distribution, and reconciliation in the case of reversals
* Buffer pool and permanence pool management
* Project termination & credit reconciliation
* Documentation hierarchy: Program Guide -> Credit Class -> Methodology
{% endtab %}
{% endtabs %}
# Credit Class Template
The credit class template may be used to help with credit class writing - this is a guide to be followed or adapted as needed.
[Downloadable Credit Class Template](https://docs.google.com/document/d/11uUFU2CwjtXFMgBVkoQuxWc0UMfT-Pul56LHeSTMxaY/copy)
Preview of Credit Class Template
{% embed url="" %}
# Project Development Overview
Project Development is the process of registering and implementing a project on Regen Registry
Projects are developed by methodology developers, project developers or Earth stewards using methodologies and credit classes from the following:
* [Regen Registry Library](https://library.regen.network)
* Methodologies with approval to use from [another registry](/protocol-development/submitting-a-methodology)
* [Your own methodology](/protocol-development/protocol-methodology-development-overview) and [credit class ](/credit-type/key-protocol-components)
During the project term, changes in ecological state are monitored to track how successfully the methodology was implemented and calculate the number of credits eligible to be sold in the market.
## Project Development Process
* [Project Registration](/project-development/project-registration)
* [Project plan submission](/project-development/project-registration/project-plan-template) and review
* Project validation
* [Monitoring report](/project-development/monitoring-overview/monitoring-report-and-template)
* [Project Marketing](/project-development/project-marketing)
* [Project page](/project-development/project-marketing/create-a-project-page)
* [Credit Issuance ](/credit-issuance/credit-issuance)
* Project lifecycle
Once the data is verified credits can be created to list in on [Regen Ledger](https://docs.regen.network/) and sold through the [Regen Marketplace](https://app.regen.network/)
Regen Registry provides support to project developers and Earth stewards throughout the project development process with the following: templates, documentation reviews and open source science tools.
# Project Registration
### Registration Process Overview
This chapter outlines the process for project proponents to register a project with the Regen Registry. The examples of phases outlined below are designed for GHG emission reduction and/or removal projects but can be adjusted for other types of ecological outcomes.
The role of Regen Registry is to review the project registration documents submitted for completeness and compatibility with the credit class and approved methodology. Additional information may be requested as needed.
Project Registration begins with Project Application that includes the following steps:
{% tabs %}
{% tab title="Project Plan Submission" %}
Each project proponent registering a project must submit a project plan with key information for the credit class and approved methodology. Regen Registry offers a template of a generic [project plan ](https://drive.google.com/file/d/19pYU0N69IDpeav6Hk747l1w0-a5-i53o/view?usp=share_link)to adapt for each credit class. Please download the editable [project plan template](https://docs.google.com/document/d/1p_HN4Q5vUjp3hni04lLFGYuAUPoB60a9Tc-I6PObZOo/copy) and submit it using the [Project Registration Submission](https://airtable.com/shrYitbUuFQcD8jcT) form. Project proponents may use other templates if the final document demonstrates sufficient information to register a project.
As applicable, monitoring reports should be submitted with the project plan. See Regen Registry [Monitoring Report Template](/project-development/monitoring-overview/monitoring-report-and-template).
Project proponents may request to designate portions of the project plan or project documentation as personal/commercially sensitive information. This information must be available for review by Regen Registry and, if applicable, the approved verifier (with non-disclosure agreements, as necessary), but will not be posted publicly as part of the project documentation on the project page unless specifically allowed. Examples of sensitive information include:
* Entity name and contact information
* Land tenure category (public, private, communal)
* Land ownership type (owner, tenant, trust)
* Established project boundaries
Regen Registry encourages that all or the majority of the information is shared publicly to the extent that is possible for the sake of transparency.
{% endtab %}
{% tab title="Project Validation" %}
Once the project plan has been submitted, the project will move into project validation to ensure projects:
* Pass project eligibility checks specified in the approved credit class and methodology
* Successfully generate GHG emission removal and/or reductions expected using the models and methods outlined in the project plan including:
* Internal Validation
* Third Party Validation
#### Internal Validation
Projects will be reviewed by the Regen Registry using the following criteria:
* Adherence to protocols in approved methodology
* Adherence to requirements in credit class, with particular reference to:
* Project ownership is stipulated in project description for the project proponent to be able to carry out project activities
* Project ownership validity that provides reasonable assessment of ownership claim by the project proponent to ensure the project proponent can legally carry out project activities. This includes a review of jurisdictional and regulatory conflicts.
* If a GHG Emission reduction and/or removal project as specified by methodology and credit class:
* Regen Registry can recommend further assessment of projected GHG emissions reduction and/or removal estimates based on models, methodology equations and project-specific contexts
The Regen Registry team may require additional information or further clarification. If so, the project developer must make the changes and resubmit the documents within 10 days of receiving requests for additional material.
#### Third Party Validation
In addition to internal validation, project proponents may need third-party verification as required by the credit class. Third-party verifications, often by a validation/verification body (VVB), provide extra assurance that a project follows the rules and requirements in the credit class and [Regen Registry Guide: Program Rules and Regulations](/regen-registry-overview/program-rules-and-requirements). Fees and agreements for third party verification are decided by the project proponent and the third party.
{% endtab %}
{% tab title="Project Approval" %}
Projects which have passed the project validation phase are eligible to be registered with the Regen Registry. If a project proponent decides to register a project, they must sign necessary contracts.
Once these activities have been completed, the project will be instantiated on the [Regen Ledger](https://docs.regen.network/) and a corresponding project page will be created on the [Regen Marketplace](https://app.regen.network/).
{% endtab %}
{% endtabs %}
\
# Project Plan Template
Each project proponent registering a project must submit a project plan with information required by the credit class and methodology. Regen Registry offers a generic project plan template below.
Submit the project plan using the [Project Registration Submission](https://airtable.com/shrYitbUuFQcD8jcT) form. Project proponents may use other templates if the final document demonstrates the required information to register a project.
[Downloadable Project Plan template ](https://docs.google.com/document/d/1UNU0pcNoi44b7mHnLFTeYhVhpdhBDEOQCJfHXvmvMmI/copy)
[Preview of Project Plan Template](https://drive.google.com/file/d/19pYU0N69IDpeav6Hk747l1w0-a5-i53o/view)
{% embed url="" %}
# Project Plan Example
This is an example of a completed Project Plan
{% embed url="" %}
# Monitoring & Verification
Regen Registry requires monitoring to be conducted by a project developer or an independent monitor chosen by the project proponent and recognized by Regen Registry. The monitor shall follow the requirements in the approved methodology to collect data and report on the benefits and indicators outlined in the methodology. Monitoring results will be used to determine the crediting amount using calculations defined in the methodology.
Each methodology will explicitly specify methods that need to be implemented by a monitor, as well as monitoring event timing, event frequency, and reporting requirements. For most methodologies, the collection of baseline data at the start of a project will be a requirement, so it is important that independent monitors are identified early in the project formation process. At the discretion and expense of Regen Registry, an independent auditor will occasionally verify monitoring reports to ensure appropriate monitoring methods and reporting are being followed.
# Monitoring Report & Template
Project monitoring reports shall be completed for each monitoring period. The monitor will submit the report to Regen Registry including any corrections/revisions identified by the verifier (if applicable). The monitoring report should describe the current status of project operation, and include the data monitored, the monitoring plan, the calculated emission reductions and ecological indicators for the reporting period stated in the credit class and following the guidelines in the approved methodology. See Regen Registry's template to use as needed:
[Downloadable Monitoring Report Template](https://docs.google.com/document/d/1zZ1n7mOKKKno2_1Rj0RR9dPFizEG-F-HrI23Vwutq8E/copy)
Preview of Monitoring Report Template:
{% embed url="" %}
# Verification
Coming Soon!
# Project Marketing
Regen Registry offers support for co-marketing and sales initiatives related to developed credits. To effectively carry out these activities, it is required for project developers to create a credit class page and project page. The credit class page provides an overview and key features of the credit class and a summary of the primary impacts and co-benefits. The project page encompasses various project elements, including the project name, short and long-form project descriptions, developer information, and media resources such as photos, videos, and logos. Regen Registry offers a [Credit Class Page template](/project-development/project-marketing/create-a-credit-protocol-page) and a [Project Page template](/project-development/project-marketing/create-a-project-page) to document this information.
Our team utilizes this information to generate marketing assets, such as a dedicated credit class and project webpages on [Regen Marketplace](https://app.regen.network). We also encourage the further development of collaborative co-marketing campaigns to support credit sales, depending on availability.
Below is an example of a Credit Class page on [Regen Marketplace](https://app.regen.network), also linked [here](https://app.regen.network/credit-classes/C04).
Below is an example of a Project page on [Regen Marketplace](https://app.regen.network), also linked [here](https://app.regen.network/project/C02-005). 
# Create a Credit Protocol Page
Each project developer/proponent will create a Credit Protocol page with key information about the Credit Protocol including outlining benefits, images, and media.
The Credit Protocol will then be listed on our Credit Protocol page with all the information that has been entered through the [Credit Protocol Intake Form.](https://airtable.com/appzrw40tJdLBM2RS/shr9e0V5295KBe8XP)
This information from this form with appear on the [Regen Registry Credit Protocol](https://www.registry.regen.network/crediting-protocols) page as well as on our Marketplace such as in [this example](https://app.regen.network/credit-classes/KSH01).
# Create a Project Page
Each project proponent registering a project must create their Project Page which will populate on our Marketplace will allow your audience to understand the details of your project.
We encourage project developers and proponents to start their Project Page that will appear on our [Marketplace](https://app.regen.network/projects/1) as soon as possible. Consider adding [Data Streams](https://guides.regen.network/guides/regen-app-project-developers-and-land-stewards/using-regen-data-stream) as it is a great way to build awarness and appreciation for your project and give potential buyers a way to track your progress - even well before listing credits.
Visit our [Creating a Project Page](https://guides.regen.network/guides/regen-app-project-developers-and-land-stewards/creating-projects) guide to get started.
# Credit Issuance
More coming soon
### **Project Lifecycle**
**Project Credits**
The project proponent stipulates the ownership of credits issued to the project. Regen Registry supports fractional ownership of the credits allocated to a project in a given issuance event, therefore credits can be split between Earth stewards, land owners, project developers, and buyers. The crediting term officially begins on the project registration date, the date when the project has been approved by Regen Registry. If an adoption date (date when new practices were implemented) precedes the project registration date, the crediting term will commence at the project initial monitoring date (or baseline) as defined by the approved credit class.
1. **Retiring Credits:** Traditionally in carbon markets, credit retirement involves allowances from regulated emission trading schemes as a method for offsetting carbon emissions. Regen Registry is not a regulated emission trading scheme because Regen provides buyers with a way to voluntarily offset their carbon footprint. Credits can only be retired once. Once a credit has been retired, it cannot be transferred or sold anymore. Regen Registry provides the ability for buyers to trade their credits, i.e. sell them to other buyers on a secondary market. In the future, a secondary marketplace functionality will be added. Credit buyers will have access to the project proponent’s information, the project location, monitoring reports, and other pertinent data which is made publicly available on Regen Registry. Buyers must indicate the owner of the beneficial interest in the GHG mitigation claim for each credit they retire.
2. **Tradability:** Credit buyers will have the option to sell their credits so long as they have not yet been retired. Credits are treated as commodities, not as securities. Regen Registry is committed to comply with all relevant regulatory frameworks, both in the US and internationally. In the future, additional functionality to support secondary market trading will be added. Aggregate project proponents may be able to create efficiencies around reporting and verification by strategically combining a group of project areas participating in an
3. **Aggregate Projects:** Project areas should be grouped so their defining characteristics are as homogeneous as possible. Verifiers may select randomly which project areas will receive on-site visits, or apply a risk analysis to identify project areas with the strongest influence over an aggregate project’s outcomes. Verifiers can use their own discretion to determine the data sampling approach, yet all sites require at least a desk-based review. Sites must have similar soil types and be located within the same pre-defined geographic region, following the ecosystem types as outlined in the taxonomy document. At the end of the crediting term, the project proponent will engage in a final project verification. The report will be made public on Regen Registry. The project proponent has the choice to renew the project (renewal duration stipulated in credit class).
4. **Project Renewal:** Submitting an updated project plan in compliance with up-to-date credit class and approved methodology. The final project monitoring and verification round of carbon stock and/or other ecological indicator estimates will be automatically used as the renewal up-to-date baseline. Project proponents may renew a project multiple times. Regen Registry does not limit the number of periods of renewal that are allowed for a given project.
5. **Project Compliance:** Project compliance stipulations are outlined in the approved credit class. The following cases apply to any relevant credit class in Regen Registry:
* Project proponents that choose to put their land under permanence convenance are required to inform prospective buyers of any permanence obligations associated with the land when selling their property.
* Previous rejection by other registry
* Regen Registry may consider a project rejected by other registries, due to procedural or eligibility requirements, if the project complies with the credit class and approved methodology. The project proponent for such a project shall include a statement in the project plan that lists all other programs to which the project proponent has applied for registration and was rejected, the reason(s) for the rejection, and pertinent documentation.
* A project may be placed on hold under the following circumstances:
* Project proponent fails to comply with the reporting requirements stated in credit class and the approved methodology.
* A verification report is submitted with a rejection rating.
* In the case of a GHG removal credit, an intentional reversal of carbon stock is identified.
* Other violations of requirements outlined in approved methodology and credit class
* Projects that are non-compliant include the following cases:
* Regen Registry may consider a project rejected by other registries, due to procedural or eligibility requirements, if the project complies with the credit class and approved methodology. The project proponent for such a project shall include a statement in the project plan that lists all other programs to which the project proponent has applied for registration and was rejected, the reason(s) for the rejection, and pertinent documentation.
* These cases will be seen as a breach of contract, subject to dispute resolution as stipulated in the legal contracts. If the dispute is not resolved, the project will be canceled from the Regen Registry and all issued credits remaining in the project proponent’s account along with the project credits allocated to buffer pool and permanence reversal buffer (if applicable) will be canceled.
* Non-compliant projects will be delisted from Regen Registry and, depending on the case, at RND discretion, the project proponent might be restricted from listing any future projects on Regen Registry.
# Regen Registry Verification and Validation Manual
July, 2025
Regen Registry provides the option for organization looking for third party verification to work with a team of experts appointed by Regen Registry staff to conduct verification and validation of their project as required for credit issuance.
Disclaimer
This document has been prepared for informational and procedural purposes only. Its contents are not intended to constitute legal advice. Regen Network Development, PBC (RND) maintains the right to amend or depart from any procedure or practice referred to in this guideline as deemed necessary.
# Introduction
The Regen Registry Validation & Verification process was developed to address the need for a more cost effective solution to third party validation and verification required by most protocols. This step while necessary for the integrity of the project, often proves to be expensive and thereby dilutes the funds that can be redistributed back to the projects and local stakeholders involved in the the projects.
Regen Registry is passionate about working to return as much of the financial benefits from a project back to the project and the local community to continue to promote the regenerative work and emergent benefits.
# Overview
For each validation and verification Regen Registry assembles an Validation & Verification Committee (VVC) of 3-4 members not associated with the project and that includes a local person that can do on the ground confirmation of adherence to the project plan, verification of monitoring procedures, and validation that local stakeholders were aware of and agreed to the project processes and procedures and have been informed of any financial benefits that the project may render and were informed on fund dispersement procedures.
The VVC will work with the project proponents to answer a set of questions that will be used to validate and verify the project plan and data collected through the monitoring report. The VVC checks for adherence to the procedures outline in the protocol, the project plan, and required elements as outlined in the [Regen Registry Program Guide](https://regen-registry.gitbook.io/regen-registry-program-guide/).
All requests for clarification from the EC to the project proponents must be documented as detailed as described in VVC[ Requests for Additional Information](/regen-validation-and-verification/regen-registry-verification-and-validation-manual/vvc-request-for-additional-information) chapter.
# Submitting Documents for Review
Required documents for Validation and Verification must be submitted via the [Project Information Submission Form](/regen-validation-and-verification). This includes the Project Plan or Project Design document and Monitoring Report. All submitted documents will be recorded on Regen Ledger to transparently show the Validation & Verification process.
Regen Registry will as needed provide NDA's for parties to sign as well as label and classify documents as "Confidential", "Internal Use Only" to indicate level of sensitivity. These documents should be watermarked as such by those submitting the documents.
Regen Registry may offer services for encypted documentation as needed for data privacy and security.
Contracts between the VVC, Regen Registry and Project Proponent members should establish a clear time frame for retaining sensitive data and outline protocols for securely disposing of information when no longer needed. A well-defined data retention policy ensures that sensitive information is retained only for necessary periods and is then securely destroyed.
Regen Registry will regularly review and update document management policies to adapt to new technologies or legal changes is imperative. Keeping policies current ensures that sensitive information is consistently protected and managed in line with the latest standards and requirements.
# Requirement & Compensation for VVC Members
**Requirements**:
To be added to our list of potential VVC Member's the following requirements must be met:
Evidence of expertise in biodiversity, biology, ecology, marine science, social impact, community governance that includes a PhD or master's degree and or at least 10 years proven experience in the field that inculdes published articles or documented participation in evaluation and or reporting experience.
Local Experts must show proven active participation in and knowledge of specific activities and ecosystems addresses in the protocol as well as community governance and/or local community nature-based issues such as ecology, biodiversity, water quality/usage, etc. Local expert must be committed to executing field visits and interviews with local stakeholders as needed. Local experts are not required to have advanced degrees.
Additional Requirements:
1. Verifiers for all Credit Classes must satisfy these minimum requirements:
* Have sufficient proof of identity.
* Be in a position of fiduciary duty.
2. Verifiers must sign a statement confirming their lack of conflict of interest with the Project Proponent. The Registry Agent and the Project Proponent must be satisfied that any potential for conflict of interest can be mitigated.
3. To limit the potential for conflict of interest, Verifiers will not conduct a verification for any project in which:
1. Any member of the verification team has a financial interest in the project or the Project Proponent.
2. The Verifier has played a role in developing this project specifically - this excludes tangential relationships such as tools or knowledge basis that are informing the project.
4. The verifier will disclose all relationships, such as familial or fiduciary, within the past three years between the Verifier on the one hand, and the project and Project Proponent on the other.
**Compensation/Payment:**
Project Proponent is responsible for engaging and paying for verifications.
# Initiation of Validation & Verfication
Step 1: Project Proponent must fill in the [Application for Validation & Verification](https://airtable.com/appzrw40tJdLBM2RS/pagn1mmN0sgdHaXUq/form) to be added to the list of projects working to engage with Regen Registry Verification & Validation.
Step 2: Regen Registry will review the application and request any additional details or information as needed. Once approved, Project Proponent will submit a list of suggested reviewers and Regen Registry will compile a list of approved VVC members developed fromt that suggested list. Reviewers must have no connection to or vested interest in the project or Regen Registry. The final list is then shared with the project proponent for the project proponent to select the committee members and directly contract with each expert . This process is designed to parallel how a project proponent would select a third party verifier. Each VVC member selected will be required to sign a "Conflict of Interest" form to record their status in relationship to the project. The contract will include a "not to exceed" statement and fee outlined as defined by the Project Proponent.
Step 3: Regen Registry will assign a specific consultant to guide the process for the project proponent and VVC members. Likewise the VVC panel will select a team lead to be the primary committee member to lead communications between the project proponent, team members and the appointed Regen Registry consultant.
Step 4: The VVC will meet with the Regen Registry consultant and coordinate on meeting cadence and type to be adhered to during the Verification & Validation process. The team lead will provide agendas for following meetings to be ditributed to VVC members as well as the selected Regen Registry consultant if they are to attend the meeting. The Project Proponent, Regen consultant and the VVC will work to develop a timeline for the Validation & Verficaition process once all members of the process have been contracted.
# Validation Process
Step 1: Project Validation Review: Evaluation of the Project Plan or Project Design Document for alignment with both the Regen Registry Program and the protocol that the project was run under. VVC members will be required to complete the Project Validation Review that examines project benefits, governance, additionality, safeguards, land tenureship, monitoring and measuring procedures, financial distribution and mechanisms of distribution, compliance with laws and regulations, and other key elements. The VVC will also complete due diligence on baseline selected and metrics used as well as a review of possible risks inherent to the project and how the project developers addressed those risks. The local VVC member will conduct a thorough analysis and if need complete additional interviews with local stakeholders and community members to ensure there was compliance with and full knowledge of the projects activities and financial resources and distribution processes. The VVC team members will then collectively asses any additional information regarding local community stakeholders and members that is revealed through this additional research.
Step 2: Project Validation Report Submission: The VVC team lead will submit the completed Validation Report to the Regen Registry consultant for review. The Regen Registry consultant will conduct a thorough review of the answers provided and submit comments or questions in the document that need clarification.
Step 3: Project Validation Report Approval: The VVC team will work to address each comment until marked as resolved by the Regen Registry consultant. Once all comments have been resolved each VVC member and Regen Registry consultant will be required to sign a the document stating completion and approval.
Step 4: Begin Verification Report Submission: The verification report focuses on verify data submitted via the Monitoring Report and any additional documents submitted via the Data Post, Google Drive or any other agreed upon file sharing platform.
All requests for clarification from the VVC to the project proponents must be documented as detailed as described in [VVC Requests for Additional Information](/regen-validation-and-verification/regen-registry-verification-and-validation-manual/vvc-request-for-additional-information) chapter.
# 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](/regen-validation-and-verification/regen-registry-verification-and-validation-manual/vvc-request-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.
\
# Governance
As the governing body, the VVC ensures that projects adhere to Regen Registry Program and the applied protocol/methodology. Through careful evaluation and adherence to the guidelines set forth in the Validation & Verification Manual, the VVC upholds transparency, fairness, and maintains the highest standards in certifying credits to support environmental regeneration.
VVC members must adhere to the requirements for timely response and communication as outlined in the contract they sign with the Project Proponent. The assigned consultant will be responsbile for reporting any failure to do so that may result in termination of contract. In this case, the VVC will need to pause progress until a new committee member is contracted.
# VVC Request for Additional Information
If the VVC determines that additional information is need beyond what has been submitted in the project plan, monitoring report, and any submitted supplemental information that request must be done via email or via a shared document that will then be saved and added to the documents associated with the credit approval and linked to the Regen Ledger.
Required documents for Validation and Verification must be submitted via the [Project Information Submission Form](/regen-validation-and-verification).
Regen Registry will as needed provide NDA's for parties to sign as well as label and classify documents as "Confidential", "Internal Use Only" to indicate level of sensitivity. These documents should be watermarked as such by those submitting the documents.
# Conflict Resolution & Appeals
\
Given the critical role of the VVC is overseeing the the integrity of projects onboarded to Regen Registry, it is paramount to establish effective procedures for managing appeals and complaints. The VVC's handling of grievances, both internally and from external stakeholders, plays a key role in upholding fairness, accountability, and transparency within the certification process.
To bolster the VVC's appeals and complaints management processes, the following enhancements should be considered:
Rules of Procedure of the Experts Committee: \
• Transparent communication channels: maintain transparent communication channels led by identified VVC lead and Regen consultant to facilitate the submission of appeals and complaints by internal and external stakeholders. Clearly communicate the processes for lodging grievances and establish channels for stakeholders to provide feedback throughout the resolution process.
\
• Objective evaluation mechanisms: establish impartial review mechanisms within the VVC to conduct fair and unbiased assessments of appeals and complaints. Designate a dedicated team or committee responsible for objectively evaluating grievances and reaching informed decisions based on evidence.
• Timely resolution framework: implement frameworks for the timely resolution of appeals and complaints within stipulated timelines. Adhering to predefined timelines for addressing grievances demonstrates the VVC's commitment to swift and effective resolution, thereby enhancing stakeholder trust and satisfaction.
• Comprehensive documentation practices: ensure thorough documentation of all\
appeals and complaints received, actions taken, and outcomes achieved. Maintaining detailed records allows for accountability, trend analysis, and continuous improvement in the VVC's grievance resolution processes.
• Continuous assessment and improvement: regularly evaluate and enhance the appeals and complaints management procedures based on feedback received and lessons learned from past cases. By embracing a culture of continuous improvement, the VVC can refine its processes to better address grievances and enhance stake-\
holder engagement.
• Stakeholder engagement framework: foster stakeholder engagement throughout the appeals and complaints resolution process to solicit feedback, provide updates, and promote collaboration in addressing grievances. Involving stakeholders in the resolution process enhances transparency, accountability, and trust within the Regen Registry framework.
# V\&V Iterative Design Process
To continued to evolve the VVC Validation & Verification process the Regen Registry will work to debrief with all committee members, project poponents and interested stakeholders after each Validation and Verification process. This will be in the form of a request for written feedback or a 30 minute call. This feedback, as well as updates as needed given technological advances, will work to evolve the VVC process to provide the most efficient, cost effective, transparent, and trusted validation and verification of credits and ultimately ensure high quality regenerative ecological work is being carried out in alignment with all stakeholders best interests.
# Call for Public Comment
The [Regen Registry Public Comment Process](https://library.regen.network/v/regen-registry-program-guide/methodology-development/methodology-review-process#public-comment)[ ](https://registry.regen.network/v/regen-registry-handbook/methodology-development/methodology-review-process)allows community members to participate directly in the development of methodologies, credit classes, and registry program materials. Regen Registry invites comments from the public about whether the below methodologies and credit classes meet the requirements and integrity of our registry. Comments solicited from the public should be constructive and developed with the intent of improving the processes and tools used to develop projects.
### How to Comment
The Public Comment period for each methodology and credit class is 15-days. During this period community members can comment directly on the methodology using the template provided below. Reviews should provide feedback on the validity of the methodology. Specifically it should address the following:
* Is the methodology clearly written with adequate detail for implementation?
* Is the underlying foundation of the methodology clear?
* Is implementation of the methodology feasible?
* Will the proposed methods achieve the results defined in the methodology?
* Are the sampling and measurement protocols robust?
* Are there any alternative or additional steps that should be considered?
During the Public Comment process, we encourage public discourse around the methodology . Those interested in participating in an active and real time responsive discussion can visit the Hylo Public Comment thread that is linked in each specific Public Comment announcement.
### How to Submit Comments
To submit your comments, submit the [Public Comment Submission Form](https://airtable.com/shrHn8lLVSSftTQP6). People submitting comments directly will have the option to remain anonymous (the default option) or they can request to have their name attached to the comments. We ask for contact information in case there is a need for clarification of your comment.
### How Comments are Incorporated
At the conclusion of the public comment period, comments are compiled into a report and sent to the Methodology Developer, who then has 30 days to respond to comments in writing and incorporate relevant feedback to a revised version, which is then posted on the methodology page. If there are major concerns that cannot be confidently resolved within Regen Registry, input from the expert community will be requested. Also, some clarification might be requested from the commenters when necessary.
{% content-ref url="/pages/tVJT08jpN2HRNwPgJNic" %}
[Protocols Open for Public Comment](/public-comment-upcoming-methods/methodologies-and-protocols-open-for-public-comment/call-for-public-comment/protocols-open-for-public-comment)
{% endcontent-ref %}
# Protocols Open for Public Comment
List of protocols/standards/methodologies open for Public Comment on Regen Registry
## **Currently Open for Public Comment:**
#### **None currently open**