> For the complete documentation index, see [llms.txt](https://research.ambitiousimpact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://research.ambitiousimpact.com/other/our-prioritization-funnel.md).

# Our prioritization funnel

The “research round” process is the main way AIM Research sources and evaluates the non-profit intervention ideas we identify for the CEIP. 

This process can be understood as a funnel; it starts with hundreds of potential ideas and progressively narrows down to the most likely recommended ideas. 

The process can be separated into prioritization stages (stages 1 through 4) and evaluation stages (stages 5 and 6). The prioritization stage aims to narrow down the field pragmatically and roughly; the evaluation stage aims to gain clarity to equip decision-makers and implementers with the best possible information on how the ideas perform against the evaluative criteria.

{% stepper %}
{% step %}

### Process design, learning and brainstorming

Establish the scope, process, and longlist of ideas for the research round
{% endstep %}

{% step %}

### Quick prioritization

To narrow the long list of ideas to a shortlist by selecting the top-performing ideas.
{% endstep %}

{% step %}

### Shallow dive 

To look further into the short-listed ideas to narrow the field to the most promising ones.
{% endstep %}

{% step %}

### Medium dive (experts & uncertainties)

To resolve critical uncertainties and gain insight into the shortlisted ideas to identify the top ideas worth investigating in depth to conduct a rigorous assessment.
{% endstep %}
{% endstepper %}


---

# 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://research.ambitiousimpact.com/other/our-prioritization-funnel.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.