> For the complete documentation index, see [llms.txt](https://globalimpact.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://globalimpact.gitbook.io/untitled/partners-contexts-trials/the-life-you-can-save-tlycs.md).

# The Life You Can Save (TLYCS)

Leads: Bilal Siddiqi, Neela Saldhana; Other partner contact: Jon Behar (Giving Games)

We have completed various trials in conjunction with [The Life You Can Save](https://www.thelifeyoucansave.org/), the most recent being the[Advisor signup (Portland)](/untitled/partners-contexts-trials/the-life-you-can-save-tlycs/advisor-signup-portland.md) city-level YouTube test. There are a number of additional proposed trials and tests, however, at the moment these considerations are limited to the private Gitbook.

\
Note that in the past TLYCS has worked with the Graduate Policy Workshop School of Public and International Affairs at Princeton University, who produced the ['Behavioral Insights to End Global Poverty'](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mf8cHxdwePMZXRTKnEE%2Fuploads%2Fgit-blob-f50d8b78d3244b5dc6ad32998a469ea2dc5ec4cd%2FBehavioral_insights_to_end_global_poverty_12-15.pdf?alt=media) report embedded below.

<details>

<summary>Quick takeaways from the "Princeton" report</summary>

(From 'summary'... the report authors' takes are given *except where italicized*)

* 5 key principles: choice architecture, social norms, empathy, overhead cost aversion, and anchoring

**Factual:**

* TLYCS demographics are predictable (White, Male, tech...)
* Donations cluster at the end of the tax year

**Pages and promotion**

* Social media channel is promising
* The "Best charities" page underperforms: there is a high bounce rate
  * *DR: Maybe because Givewell etc do better at this?*
* "Visual presentation of charities does have an effect
  * *DR: Not clear how this is causally identified*
* Ran "social media tests' they claim are underpowered.
  * *DR:* but these could be analyzed with Bayesian methods for actionable insights
* They suggest simplified presentation/navigation, and a 'decision tree quiz' to reduce cognitive load

</details>

>

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mf8cHxdwePMZXRTKnEE%2Fuploads%2Fgit-blob-f50d8b78d3244b5dc6ad32998a469ea2dc5ec4cd%2FBehavioral_insights_to_end_global_poverty_12-15.pdf?alt=media>" %}

\\

\\


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://globalimpact.gitbook.io/untitled/partners-contexts-trials/the-life-you-can-save-tlycs.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 `build a script that syncs our docs to a CMS` 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.
