> For the complete documentation index, see [llms.txt](https://title5.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://title5.caqualityearlylearning.org/resource-and-referral-program/written-referral-policies-resource-and-referral-program.md).

# Written Referral Policies - Resource and Referral Program

18244

(a) The contractor shall develop and implement written referral policies.&#x20;

(b) The written referral policies shall include the following information:&#x20;

&#x20;             (1) A statement that referral services are available to all persons requesting them regardless of income level or other eligibility requirements;&#x20;

&#x20;             (2) A statement that information received from the parent(s) is confidential; and&#x20;

&#x20;             3\) The conditions under which referrals to a provider may be discontinued.&#x20;

(c) The written referral policies shall be available to parents and providers upon request.

> NOTE: Authority cited: Section 8261, Education Code. Reference: Sections 8212 and 8214, Education Code.


---

# 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://title5.caqualityearlylearning.org/resource-and-referral-program/written-referral-policies-resource-and-referral-program.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.
