> 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/fund11-docs/project-onboarding/f11-milestone-reviewers-guide/key-dates-during-the-onboarding-stage.md).
# Key dates during the onboarding stage
By February 16th - email to chosen Milestone Reviewers along with a link to reset password in the Milestone Module.
By February 17th EOD UTC - Milestone Reviewers should create accounts in the Milestone Module
19th - 20th February progressively - Catalyst Team will assign Milestone Reviewers to specific projects in the Milestone Module (allocation process depends on completion of onboarding form by Funded Projects)
By February 21st EOD UTC - Milestone Reviewers should check if assigned projects are visible, and inform the Catalyst Team about being unable to review specific projects via TG.
From February 19 to March 3 EOD UTC - Milestone Reviewers should check email notification on daily basis to see if there are any milestones submission/resubmission to review
By March 3 EOD UTC - All submitted/resubmitted milestones in SoM must be reviewed.
---
# 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/fund11-docs/project-onboarding/f11-milestone-reviewers-guide/key-dates-during-the-onboarding-stage.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.