> For the complete documentation index, see [llms.txt](https://charity.childsafetyfund.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://charity.childsafetyfund.org/strategy/technology/t.e.n..md).

# T.E.N.

Traumatic Exposure Notice

T.E.N. is a child safety technology strategy focused on Traumatic Exposure Notices.

The strategy begins with a simple problem: children may experience traumatic events outside of school, but the adults who see them the next day may have no context for what happened. Without timely awareness, schools and child-serving organizations may miss the opportunity to respond with care, flexibility, and support.

T.E.N. builds from the existing Handle With Care model ([1](https://handlewithcareok.org/)), which shows that first responders can send a minimal notice to schools without sharing incident details. The strategy does not replace Handle With Care. It studies, clarifies, and extends the model by defining how traumatic exposure notices can become more consistent, timely, privacy-preserving, and easier to operationalize across jurisdictions.

CSF’s role is to define the strategy, evidence base, model, and guardrails. The strategy may later inform technology development by aligned implementation partners, but this section focuses on the public-interest strategy itself.

The following sections explain why T.E.N. exists, what evidence supports it, how the model works, where current systems break down, and what objectives guide future development.

***

### Theory of Change

Insert

***

### Sources

1. <https://handlewithcareok.org/>


---

# 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://charity.childsafetyfund.org/strategy/technology/t.e.n..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.
