> 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/funded-project-reporting-guideline/catalyst-team-monthly-reports-approval-process.md).

# Catalyst Team Monthly Reports approval process

Catalyst receives submitted reports on the basis of [monthly report (MR) form](https://bit.ly/CatalystMonthlyReport). 

1. Reviewers check if:
   * The MR is submitted within the deadline. 
   * The current MR is a duplicate of previously submitted MR. Each report should reflect new information and evidence of progress since the last reporting period
   * Evidence is different for each project submitted by the same funded-proposer. See [what is good evidence](broken://pages/WpXNujSconpNE01GfvfN) /[ what is not good evidence](broken://pages/Ku2MdiMGJhmH9OQ81sEV) for ideas. 
   * Evidence is relevant to the approved proposal’s description of deliverables, plan, and timeline
   * All evidence files and links are able to be opened
   * There is a clear description of what was provided as evidence in the MR.
2. If there are discrepancies with the above (b-f), project MR is not approved and the funded-proposer will be notified via Catalyst no-reply email and asked to resubmit the report, or will be asked via email to  send a change request(CR) linked form.
   * Funded Proposer (FP) can re-submit the report before or on the 20th of each month to be re-reviewed for approval and next funding disbursement
3. In case the MR misses the approval deadline, Catalyst informs FP via mail, whose MR was not approved, that funds will not be released this month and offers a path for resolution to get back on track.

<br>


---

# 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/funded-project-reporting-guideline/catalyst-team-monthly-reports-approval-process.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.