> 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/statement-of-milestones/how-to-use-the-milestone-module-in-f10/approval-of-the-proof-of-achievement.md).

# Approval of the Proof of Achievement

Once the project submits a PoA, should check To-do/Updates section in the Milestone module on daily basis

* Milestone Reviewers reviews of PoA evidence will be visible on the dashboard in the Milestone module, and each FP will receive a notification in the To-do/Updates section
* In case PoA clarifications are required a follow-up submission may be requested&#x20;
* Please follow up swiftly to address any issues to alleviate any potential delays
* Incomplete/inadequate submissions risk delay in verifying evidence and following payment distribution

### Expectations

* Monthly disbursements to reach the next milestone will resume once project has demonstrated achievement of milestone completion and the reviewers have documented the verifications
* PoA submission is for every individual milestone needs to be documented for public accountability:&#x20;
  * Evidence of Outputs and acceptance criteria as per the verified milestone must be addressed
  * More relevant and explicit documented evidence, the higher the likelihood of smooth approval
  * It is recommended to include video walkthrough demonstrations for best chance of approval and contextual understanding as this provides narrative and dynamic visual evidence
  * Project evidence should be considerate of the general public’s level of comprehension

### Key factors

The amount and timing of funding project receives is primarily based on:&#x20;

* The amount project was approved during vote stage
* The amount per milestone as agreed in the SoM
* The proposed end date for each milestone as agreed via SoM documentation during onboarding
* The quality and timeliness of reporting requirements over the lifecycle of a project


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.projectcatalyst.io/previous-funds/fund10-docs/project-onboarding/funded-proposers-fp/statement-of-milestones/how-to-use-the-milestone-module-in-f10/approval-of-the-proof-of-achievement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
