> For the complete documentation index, see [llms.txt](https://df-manual.gitbook.io/df-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://df-manual.gitbook.io/df-book/review-circle/eligibility-proposals-review.md).

# Eligibility Proposals Review

The eligibility review process is a process that involves reviewers assessing project proposals using predefined criteria, based on objective rules and parameters.\
This review is done to give proposers the opportunity to correct any mistakes or omissions found by reviewers and have their work reassessed before a final decision on its eligibility.<br>

There are 2 teams of reviewers:&#x20;

* **Technical Team and**&#x20;
* **Non-technical team (Business team)**

The Technical team is assigned to proposals from the <mark style="background-color:orange;">Community Driven RFPs (Request for Proposals), New Projects, and RFP Design Pools.</mark>\
The Business team is assigned to proposals in the <mark style="background-color:orange;">Marketing and Ideation Pools</mark>.

There is also the <mark style="background-color:orange;">Miscellaneous Pool.</mark>&#x20;

Proposals in this pool can fall under Technical or Business.&#x20;

**PROCESS:**

1. The Review team is formed based on Pools and technical skill levels.
2. Coordinators are assigned to each team of reviewers to oversee and support them throughout the Deep Funding round, though they may interact and overlap sometimes.
3. The Coordinators will assign each proposal to a reviewer based on the number of submitted proposals in their designated pool. These assignments can be found [here.](https://docs.google.com/spreadsheets/d/1c-lqbAuZO6f5SRqY9MV2XZDSsYPXzioVsK7sSLvLHZA/edit?usp=sharing)
4. When assigned, the reviewer begins immediately to review the proposals for pool eligibility, milestone correctness and all other[ rules](https://deepfunding.ai/rules/) pertaining to the specific Deep Funding round and the pool entered. **What to look out for:**
   * [ ] <mark style="background-color:orange;">**A.  Pool Allocation Compliance**</mark> - Ensure that the submitted proposal is in the right pool. For instance, a proposal that aims to provide a service on the SingularityNET platform by integrating a custom knowledge graph builder with LLM capabilities cannot be in a Marketing pool but should rather be in the RFP pool.
   * [ ] <mark style="background-color:orange;">**B. Pool Conditions Compliance**</mark>- There are general rules that all pools have to comply with and also specific rules and conditions for each pool. The reviewer checks to see if the proposal has met these conditions.
   * [ ] <mark style="background-color:orange;">**C.  Milestones Compliance**</mark>- All proposals must have a breakdown of  milestones with deliverables and an attached budget to each milestone.
   * [ ] <mark style="background-color:orange;">**D. Deep Funding Resources Request Confirmation**</mark>- If the team requires SNET/DF personnel to engage in order for the project to deliver the milestones, they need to specify this in the proposal that the DF team has acknowledged and approved this. Else, it's not eligible.
   * [ ] <mark style="background-color:orange;">**E. Pool Ideation**</mark> - In this pool, proposers are required to be specific about any of the 4 topic developments in their proposal as stated in the rules. The topic developments are : Tangible deliverables such as a detailed project backlog, technical architecture, a clickable prototype, and preliminary market research. If the proposer doesn't go in any of these directions, it's a no-go for them.
5. The reviewers fill this [form ](https://docs.google.com/forms/d/e/1FAIpQLSccf9emLj0DnZUCPlxIZiryIZDM7PZpFZ8S0Ij-Gmjbs5ByRg/viewform?usp=sf_link)and input the information needed and submit to the coordinators, who then comment on the proposal alerting the proposal team of corrections to be made, if any.
6. Once the proposal teams have had opportunities to edit and realign their proposals based on reviewers feedback, the Coordinators will review each of the reviewer's determinations for accuracy and will refer the process to Deep Funding team for the next phase.
7. Prior to the blog post announcing the final results of  eligible proposals, the coordinators will communicate to teams regarding the status of their proposals.\
   This is to ensure transparency and clarity for all participants regarding the status of their submissions.
8. The coordinators update the eligibility status in WordPress. This informs the progress of the proposals to the community.&#x20;


---

# 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://df-manual.gitbook.io/df-book/review-circle/eligibility-proposals-review.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.
