> For the complete documentation index, see [llms.txt](https://docs.rainbowstandard.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rainbowstandard.io/~/changes/113/rainbow-standard-documents/validation-and-verification-bodies-vvbs.md). # Requirements for Validation and Verification Bodies (VVBs) ## Purpose of this document The aim of this document is to present guidelines for Validation and Verification Bodies (VVBs) for conducting comprehensive evaluations of greenhouse gas emission avoidance and/or removals of Project Developers under the Rainbow Standard. This document delineates the requirements and procedures necessary for ensuring compliance with the [Rainbow Standard Rules](/~/changes/113/rainbow-standard-documents/rainbow-standard-rules.md) and [Rainbow Procedures Manual](/~/changes/113/rainbow-standard-documents/procedures-manual.md). It pertains to the following types of audits: * Validation Audits * Verification Audits ## Introduction This guidance is part of the larger framework of the Rainbow Standard system, which encompasses the Rainbow Standard Rules and the methodologies. Moreover, it complements the Rainbow Procedures Manual that delineates project registration and supervision This document offers targeted guidance for auditors performing validation and verification audits within the specialized scope of Project Developers. The guidelines detailed in this document become binding upon its formal release. Post this date, any VVB that meets the requirements can contribute to the validation and verification of Rainbow Standard Projects. Existing VVBs must reapply and provide the necessary documentation outlined in this text before continuing validation or verification tasks. For VVBs who have an existing formalized agreement with Project Developers before the activation date of this guidance, a grace period of twelve months is given to apply again and comply with the new requirements. Henceforth, Project Developers can only collaborate with VVBs officially recognized by Rainbow, based on the requirements and processes defined herein. Projects already registered that haven't transitioned to the Rainbow Standard Rules might be subjected to different review templates than those mentioned here.\\ ## VVB acknowledgement I hereby acknowledge that I have read and understand the above requirements. \\ Company name:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ \\ Name:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ \\ Signature: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ Date:\_\_\_\_\_\_\_\_\_\_\_\_\_ \\ --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.rainbowstandard.io/~/changes/113/rainbow-standard-documents/validation-and-verification-bodies-vvbs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.