> 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./model.md).

# Model

A Traumatic Exposure Notice (T.E.N.) is a minimal, time-sensitive communication from a first responder to a school that signals a child was present at or exposed to a traumatic event. The model builds from Handle With Care practices, which use brief notices to alert schools without sharing incident details. (1, 2)

The notice contains:

* The child’s name
* The child’s age and grade, where applicable
* The child’s school or childcare enrollment
* The date and time of the incident
* A signal phrase, such as “Handle With Care”

The notice does not contain:

* The nature of the incident
* The reason for law enforcement response
* Names of family members or others involved
* Clinical, investigative, or legal details

Why the Data Boundary Matters

The “no details” boundary serves three functions:

1. Privacy preservation. Limiting the notice to identifying information and a care signal helps keep sensitive family circumstances out of unnecessary records.
2. Trust preservation. Schools receive enough context to respond with care, but not enough to investigate or assign blame.
3. Operational clarity. Staff are not asked to interpret an incident. They are asked to adjust their response to the child.

Handle With Care materials indicate that notice processes are designed to support alignment with HIPAA and FERPA when content is limited to approved fields and routed through appropriate channels. T.E.N. preserves this same principle by treating data minimization as a core design requirement. (3, 4)

### How the Model Works

1. Exposure is identified

A first responder identifies that a child was present at or exposed to a traumatic incident. (1, 2)

2. Notice is generated

The officer, dispatcher, or authorized public safety contact generates a notice using only approved fields. (1, 2)

3. Notice is routed

The notice is sent to the designated school, district, or childcare contact before the next school day when possible. (1, 2)

4. School response begins

A designated school official receives the notice and shares it only with staff who need to know. Teachers, counselors, or support staff respond through trauma-informed care, observation, flexibility, and support. (1, 2, 5)

5. Additional support is activated if needed

If the child needs more support, the school may refer the child to a counselor, social worker, or other appropriate support pathway. Any clinical intervention remains governed by applicable school, family, and consent requirements.

What the Model Is Not

The T.E.N. model is a notification relay. It is not:

* A clinical tool
* A case management system
* A risk-scoring system
* A child welfare investigation
* A law enforcement reporting system
* An automated intervention model

T.E.N. does not diagnose children, prescribe interventions, or replace professional judgment. The notice creates awareness. The care response remains local, human-led, and based on the child’s needs.

Technology and the Model

Many Handle With Care implementations rely on manual transmission, while some jurisdictions use portals or digital systems. The technology used to transmit a notice may improve reliability, timing, routing, and accountability, but it should not change the core model.

Technology should preserve:

* Minimal notice content
* No incident details
* Role-based access
* Need-to-know sharing
* Human-led care response
* Local school judgment

The purpose of T.E.N. is not to make care automatic. The purpose is to make timely awareness more consistent so adults can respond with care when it matters.

***

### Sources

1. New Jersey Office of the Attorney General, “Attorney General Law Enforcement Directive No. 2020-9: Handle With Care.” <https://www.nj.gov/oag/dcj/agguide/directives/ag-Directive-2020-9\\_Handle-With-Care.pdf>
2. Handle With Care Oklahoma, “Template for HWC Notification Protocols.” <https://handlewithcareok.org/wp-content/uploads/2022/10/TEMPLATE-for-HWC-Notification-Protocols-updated-Jan-2022.docx>
3. U.S. Department of Education and U.S. Department of Health and Human Services, “Joint Guidance on the Application of FERPA and HIPAA to Student Health Records.” <https://studentprivacy.ed.gov/resources/joint-guidance-application-ferpa-and-hipaa-student-health-records>
4. Indiana Department of Health, “Handle With Care: Implementation and Technical Assistance.” <https://www.in.gov/health/safesleep/files/HWC-Implementation-and-TA.pdf>
5. SRI Education, “Evaluation of Handle With Care 2.0: Supporting Students Who Experience Trauma.” <https://www.sri.com/education-learning/student-behavior/evaluation-of-handle-with-care-2-0-supporting-students-who-experience-trauma/>


---

# 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./model.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.
