> For the complete documentation index, see [llms.txt](https://guide.collaborativefunding.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.collaborativefunding.org/the-5-steps/step-3-generating-direction-with-high-quality-proposals/the-elements-of-a-good-proposal.md).

# The elements of a good proposal

Making a strong proposal needs to strike a good balance between being short and to the point, but include all key information and background for others to make an informed decision on it. You don’t want those reading it to feel overwhelmed, nor as if you were too lazy to give them a clear explanation of your pitch.

| Title           | catchy line to capture the essence of your proposal                                                                 |
| --------------- | ------------------------------------------------------------------------------------------------------------------- |
| Why             | What is this proposal? What problem do you aim to address?                                                          |
| Context         | Any relevant background to understand the context this is being proposed it. Why you are choosing to pitch this now |
| Detailed What   | All the relevant details about your proposal                                                                        |
| Further reading | Links to further material about your proposal that gives it more weight                                             |
| Who             | About the proposer: why are you well suited to do this work?                                                        |
| Budget          | <p>Total Budget requested and its breakdown into</p><ul><li>Deliverables and amounts</li><li>Milestones</li></ul>   |
| Timeline        | Deadlines for deliverables so you can be held accountable                                                           |


---

# 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://guide.collaborativefunding.org/the-5-steps/step-3-generating-direction-with-high-quality-proposals/the-elements-of-a-good-proposal.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.