> 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/using-the-milestone-module/roles-and-responsibilities/funded-project-fp-using-the-milestone-module/actions-that-fp-can-carry-out-in-the-milestone-module/resubmit-milestones.md).

# Resubmit milestones

If there is a refusal, it will be displayed on the project dashboard, and the FP will receive a notification in the [Milestone module](https://milestones.projectcatalyst.io/) to-do list/updates area (please note that  FPs won’t receive this notification via email). 

In such a situation, FP may submit a new milestone to replace the previous one in such a situation by clicking the Resubmit Milestone button. Form to fulfill will appear with a button Clone latest submission, which can be used to prefill the form with previously submitted information. Once a milestone is resubmitted, it will be reviewed again. This feedback loop continues until all reviewers approve it. The Catalyst Team sign-off user locks the milestone for further submissions.

<figure><img src="https://lh4.googleusercontent.com/XwhyD0c3wGc5y7CCHdPxPO790iG3k4JvKoNimO3-q6iUcOd6DhwDiU36bJSaLiIXkn40HaLDSDhcS2JSOmrvXIlc93dA3Zd3rMZBah7NAXJly9ytPlLpUwNjs7ckBWWnAOMvwCMl2VEBg6Pae9hkdg" alt=""><figcaption></figcaption></figure>

FP can resubmit any milestone within SoM that is not yet closed. Once approved by the Catalyst Team sign-off user, the button to submit the milestone will disappear, and a green Approved by Catalyst Team sign-off user on button will become visible. All previous submissions and related reviews are visible on the project dashboard as an archived version.

<figure><img src="https://lh6.googleusercontent.com/gDQtXyXZj3F7_5qiB4bLToebUnbULjFI-Es73dzG3MljrCOwZHGJQyN9QZ6z0HhVuW7Z5bite6sFNjZircYCDPSQEAA0f4DUkCjWDSDJb14zXNZsE3jw5V7Kq8Zawjw3S9rSC_BqL-evUxKoJ1INlA" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://lh5.googleusercontent.com/g61BeJwZmA2pSVcuHwIt2GL3KybK3nU_7seOolfJR6YD0xMZ19c-hKatA6v7zZ-yIVkkOcQnZQsWFn3yNX1AGoyLerJbTVBX7R628opwqVK5D3apqhj5F-tplKwrVe224TnA9MVi_QCt645p-xKs4Q" alt=""><figcaption></figcaption></figure>

Once each milestone is approved by both the Milestone Reviewers and the Catalyst Team, the milestone in the SoM will be locked, and no further changes can be made unless a milestone [change request](https://docs.projectcatalyst.io/project-funding/funded-project-reporting-guideline/requesting-a-change-to-funded-project-in-f10) is submitted.&#x20;

See this section for more information about submitting [change requests](broken://pages/GcAPijhBeAYj3aqcUm31).[ ](https://docs.google.com/document/d/17TvVe5nnzvZgOHFR2GQjnhUWjUwBxIA9Iebld9u0RN0/edit?pli=1#heading=h.o44n0mgjeuut)


---

# 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/fund10-docs/project-onboarding/funded-proposers-fp/statement-of-milestones/how-to-use-the-milestone-module-in-f10/approval-of-the-proof-of-achievement/using-the-milestone-module/roles-and-responsibilities/funded-project-fp-using-the-milestone-module/actions-that-fp-can-carry-out-in-the-milestone-module/resubmit-milestones.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.