> 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.md). # Education CSF’s efforts to prevent child abuse include developing and disseminating child-safety education, ensuring resources reach those best positioned to protect children. CSF’s national strategy centers on strengthening the mandated reporter workforce, which represents over 28 million professionals responsible for identifying and reporting child abuse and neglect. View Strategy Deck *** ### **Theory of Change** **As a result of our strategy, we theorize that:** * The public will develop a stronger ability to recognize and report child abuse, leading to more informed, actionable reports. * Child protection will shift from being solely a professional duty to a shared community responsibility, fostering collective vigilance and intervention. * Unconscious bias and subjective assumptions in reporting will decrease, reducing unnecessary child welfare involvement when intervention is not warranted. * Child protection agencies will receive higher-quality reports, enabling more efficient resource allocation and ensuring timely responses to children at genuine risk. * A more informed public will help fill critical gaps caused by high turnover in child welfare, reducing the risk of children falling through the cracks. * Child protection efforts will strengthen sustainably without requiring constant agency expansion—training more individuals over time will create a resilient, community-driven safety net. * Systemic change will occur as child safety education becomes widely accessible, expanding the child protection network and strengthening efforts at every level. --- # 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.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.