> 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/fund9-docs/the-statement-of-milestones-module-fund9-only/submitting-proof-of-achievement-poa/process-of-checking-poa.md).

# Process of checking PoA

1. FP submits PoA through the [Milestone Module](https://milestones.projectcatalyst.io/)
2. Catalyst Team Reviewer and Milestone Reviewers checks To do list/Updates section to see if there is PoA to review
3. Milestone Reviewers compare if the evidence of the milestone provided meets the following: expected outputs, acceptance criteria, or evidence of completion
   * If verified: PoA is approved by Milestone Reviewers
   * If not verified: PoA is not approved by Milestone Reviewers and feedback for FP is provided in the milestone module
4. Once Milestone Reviewers reviews PoA, Catalyst Team Reviewer makes second review
5. Catalyst Team Reviewer compares if evidence of the milestone provided meets the acceptance criteria approved in SoM
   * If verified: PoA is approved by the Catalyst Team Reviewer
   * If not verified: PoA is not approved by the Catalyst Team Reviewer, feedback for FP is provided and PoA resubmission requested
6. In case of divergent opinions between Milestone Reviewers and the Catalyst Team Reviewer, the Catalyst Team Reviewer gives a casting vote at this time


---

# 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/fund9-docs/the-statement-of-milestones-module-fund9-only/submitting-proof-of-achievement-poa/process-of-checking-poa.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.