> 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/fund10-docs/project-onboarding/funded-proposers-fp/what-do-you-need-to-do-next.md).

# What do you need to do next?

1. You will need to complete the onboarding form by noon UTC on 25 September 2023.&#x20;
2. On September 26th, you will receive an email with a link to reset your password and create a new one in the Milestone Module
3. By 27th of September at 23:59 UTC you should inform the Catalyst Team via email if you would like to have additional milestones in the Milestone Module
4. You should submit your Statement of Milestones between 26 September 2023 and 02 October 2023
   * Each funded project must submit a Statement of Milestones before the project goes live and before first payment is received.&#x20;
   * Your Statement of Milestones will need to be submitted for review by no later than 02 October 2023.
5. Attend one of the Catalyst Celebration Onboarding Meetings on 26 September 2023 (not mandatory, but recommended). You will get the opportunity to ask questions and clarify any outstanding doubts.&#x20;

   * [F10 Onboarding Session A](https://us06web.zoom.us/meeting/register/tZwvdOyhrTkrGtIBcVDQQI83i_gJ0d-fUihp) - 8AM UTC
   * [F10 Onboarding Session B](https://us06web.zoom.us/meeting/register/tZApdeGorT8vG9VR7JQTcvneqz_HGgQkA8Pv) - 5PM UTC<br>
6. To assist you as a Funded Project, a Challenge Team (CT) is assigned to you:&#x20;
   * CT is made up of community members taking up the role of stewarding challenges, they are ambassadors for Catalyst and will be engaged to learn about your progress over the course of the project.
   * Each challenge has its own specific CT and the Catalyst team will introduce you to your Challenge Teams and send them your project's contact information via email by the end of the day on 26 September 2023.
   * CTs are helping to onboard you and you will need to confirm your Proof of Life (PoL) in order for Catalyst to release your initial batch of funding.&#x20;
     1. Gentle reminder; PoL is mandatory in order to set your project to LIVE
     2. Schedule a short meeting. CTs will be engaged over the course of your project, they’re an important part of the process.&#x20;
   * Note: If you have already completed a PoL you do not need to complete it again (you are automatically confirmed)
   * Your Challenge Team will contact you with a schedule of available meeting slots for your PoL meeting, which will take place between 26 September to 2nd October 2023. There are multiple opportunities to meet with CT to confirm PoL.&#x20;


---

# 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/fund10-docs/project-onboarding/funded-proposers-fp/what-do-you-need-to-do-next.md?ask=<question>&goal=<user_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.
