> 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/awarded-teams/proposal-submission-1.md).

# Proposal submission

<figure><img src="/files/0k3HsKNZkq4rBdKGOSik" alt=""><figcaption></figcaption></figure>

Once you submit a proposal, it doesn’t move straight to funding. It goes through a multi-layered review process to make sure every project is treated fairly and evaluated based on its actual value.

Here’s the path a proposal follows before it can be awarded:

* Eligibility Review: A quick check to confirm your proposal meets the basic requirements for the round and fits within the updated pool structure.
* Community Peer Reviews: Community members read your proposal, rate it, and provide early feedback. This helps highlight strengths, blind spots, and any unclear parts.
* Community Expert Reviews: Reviewers with deeper technical or domain expertise examine the proposal more closely assessing feasibility, impact, and execution.
* Voting Phase: Proposals that pass the reviews move to voting, where the community decides which projects should receive funding.

\
**Note**: May be subject to change depending upon Round requirements.


---

# 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/awarded-teams/proposal-submission-1.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.