> 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/what-is-proof-of-achievement-poa.md).
# What is Proof of Achievement (PoA)?
Under F10, Projects are required to deliver against their planned milestones throughout the lifespan of their project as outlined in the Statement of Milestones. When individual milestones are met, funded projects must submit Proof of Achievement (PoA). Proof of Achievement differs from the monthly progress reports that projects must submit during the project lifecycle. Proof of Achievement is essentially documentation that has to be submitted by the Projects showing that the acceptance criteria for a milestone as set out in the Statement of Milestones have been fulfilled and the milestone has been completed.
Funding is contingent on the Proof of Achievement being submitted and accepted as set out in this guide.
---
# 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/what-is-proof-of-achievement-poa.md?ask=&goal=
```
`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.