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

# Experience

Our strategy is grounded in multi-year, firsthand experience within the child welfare system. This fieldwork, conducted while embedded within the Oklahoma Department of Human Services (OKDHS), served as the Child Safety Fund’s formative activity prior to its formal registration. During this period, we processed 1,703 child abuse reports, screening out 947 and assigning 756 for investigation.

Working as an abuse and neglect intake specialist revealed a consistent gap between what the public believes constitutes abuse or neglect and how states legally define it. Over time, it became clear that limited state resources had resulted in minimal training for mandated reporters on how to accurately identify and report concerns. This gap was reinforced by frequent requests from mandated reporters seeking additional guidance and training.

The following real-world examples illustrate the challenges we observed and became pivotal in shaping the rationale for establishing the Child Safety Fund.

***

### **Reporting Too Late**

A report was made alleging that a parent physically harmed their child, resulting in bruising, with video evidence provided. However, because the incident occurred a year earlier and there was no new information suggesting ongoing harm, the report was screened out due to lack of recent evidence.

***

### **Biased Reporting**

In another case, a mandated reporter *believed* a parent had injured their child despite medical evidence proving otherwise. Both law enforcement and medical professionals determined the parent had acted appropriately after the child’s injury. Nevertheless, due to the reporter’s personal bias, a second report was filed, escalating the concern and triggering an unnecessary priority response. A child abuse specialist later ruled out abuse or neglect, but the family still endured an unwarranted investigation.

***

### **Incomplete Reporting**

States accept reports through various methods. In Oklahoma, one option is voicemail. In one instance, a mandated reporter left a voicemail alleging a child was being beaten and confined to a corner but failed to include their contact information or any identifying details about the family. As a result, the report was screened out because investigators were unable to locate or identify the child.

***

These examples underscore the urgent need for standardized, evidence-informed training to ensure all reports are accurate, unbiased, and actionable, protecting children while preventing unnecessary investigations.

*<mark style="color:blue;">Collectively, this frontline experience represents CSF’s first operational phase—immersive field research that identified systemic barriers and informed the design of our national education strategy.</mark>*


---

# 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/education/experience.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.
