> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/previous-funds/fund13-docs/project-onboarding/funded-proposers-guides/formal-due-diligence-process.md). # Formal Due Diligence Process All proposals are classified either as business or individual grants. For each grant there must be a declared official party that will hold responsibility for the execution of it. All Grantees must complete due diligence verification which includes submitting complete and accurate information for know your customer (KYC), know your business (KYB), anti-money laundering (AML) and similar screenings conducted. Instructions will be provided to Grantees via email once they complete their submission of onboarding forms to complete the due diligence process. * For each grant there must be a declared official Grantee that holds responsibility for the execution of it * Grantees are classified as: * Individuals * Incorporated organization * Unincorporated organizations * Access to the verification portal * After correctly and duly completing the onboarding form, you will receive a link via no reply email from the Catalyst team within 1-2 hours. If any issues occur, please raise a ticket [here](https://catalystiog.zendesk.com/hc/en-us/requests/new). * For returning Grantees * If you are a returning Grantee from Fund12 (or a verified community member in Fund13 for individuals only) and your details have not changed, your existing verification will carry over to Fund13. It is crucial to use the same email address as your reference from the previous KYC/KYB process you’ve passed; otherwise, you will need to repeat all verification steps or risk delaying onboarding. --- # 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://docs.projectcatalyst.io/previous-funds/fund13-docs/project-onboarding/funded-proposers-guides/formal-due-diligence-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.