> 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/readme.md). # Ambitious Impact Research Open-access research, recommendations and methodological guidance from the Ambitious Impact Research Team {% columns %} {% column width="58.333333333333336%" %} Welcome to the **AIM Research Team's site**. We identify impactful, tractable, neglected and relevant non-profit interventions to alleviate problems faced by human and non-human animals, and recommend them to the [Charity Entrepreneurship Incubation Program (CEIP)](https://www.ambitiousimpact.com/), where prospective founders pick them up and deploy them. We use this site to open-source our recommendations, our methodological guidance and our training materials. Our team spends 5000+ hours each year identifying and evaluating potential charity opportunities. Ideas come from experts, existing research and our own investigation before being funnelled through increasingly rigorous rounds of inquiry. The ideas that survive scrutiny become open-access research and implementation reports, giving founders the evidence they need to build effective charities. {% endcolumn %} {% column width="41.666666666666664%" %}
{% endcolumn %} {% endcolumns %} ## Current recommendations
Cover image

Simulation-based training for emergency obstetric and newborn care

cover-bemonc.pnghttps://ambitious-impact.gitbook.io/ambitious-impact-docs/bemonc/

Using Mass Communication to Improve Learning Outcomes

cover-mass-communication.jpghttps://ambitious-impact.gitbook.io/ambitious-impact-docs/using-mass-communication-to-improve-learning-outcomes/

Treating depression with guided digital self-help programs

cover-depression.jpghttps://ambitious-impact.gitbook.io/ambitious-impact-docs/treating-depression-with-guided-digital-self-help-programs/
## How we choose what to recommend

Idea selection

To be recommended for incubation through the CEIP, an idea must be:

  • Subjected to rigorous research, in most cases by the AIM Research Team itself using the processes described on this site.
  • Viewed to clear a high bar across our evaluative criteria. Some ideas do notably better on some criteria than others and are recommended based on the cost/benefit judgement of the decision-making team.
https://ambitious-impact.gitbook.io/ambitious-impact-docs/ambitious-impact-eval/

Where do ideas come from?

We are pragmatic and opportunistic about the source of ideas and evaluate all of them against the same criteria. An idea can currently become recommended:

  1. Through our research rounds.
  2. Through CEIP applications by individuals with their own ideas.
  3. Through recommendations from experts and other organizations, which go through a process similar to our research rounds.
https://ambitious-impact.gitbook.io/ambitious-impact-docs/other/
## All ideas we've looked at in depth {% embed url="" %} *This site is maintained by the* [*Ambitious Impact Research Team*](https://www.ambitiousimpact.com/team)*.* *We'd like to thank contributors and past team members who have shaped our research approach and contributed to the materials presented here, including Aidan Alexander, Sam Hilton, Karolina Sarek, Joey Savoie, James Che, Leonie Falk, Akhil Bansal, and Erik Hausen.* --- # 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/readme.md?ask=&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.