> For the complete documentation index, see [llms.txt](https://handbook.regen.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.regen.network/regen-validation-and-verification/regen-registry-verification-and-validation-manual/validation-process.md). # 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.md) chapter. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://handbook.regen.network/regen-validation-and-verification/regen-registry-verification-and-validation-manual/validation-process.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.