> 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/milestone-reviewers-guides/key-dates.md).

# Key dates

This page contains key dates for Milestone Reviewers during the onboarding

**By December 19th 2024 EOD UTC** - Milestone Reviewers should create accounts in the Milestone Module

**20-31 December 2024 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 December 31st 2024 EOD UTC** - Milestone Reviewers should check if assigned projects are visible, and inform the Catalyst Team about being unable to review specific projects via ticket [here](https://catalystiog.zendesk.com/hc/en-us/requests/new). If the Catalyst Team is not informed by this date, then it would mean for Catalyst Team that each assigned project will be reviewed

**From December 20th 2024 to January 12th 2025 EOD UTC** - Milestone Reviewers should check email notifications daily to see if there are any milestones submissions/resubmissions to review

**By January 12th 2025  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/fund13-docs/project-onboarding/milestone-reviewers-guides/key-dates.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.