> 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/records/records-on-file-concerning-service-providers.md).

# Records on File Concerning Service Providers

18231

The contractor shall maintain in its files the following records concerning each service provider: 

              (a) A statement of the service provider's current fees with information regarding the provider's usual and customary services provided for those fees; 

              (b) A statement signed by the provider that the child care and development services being provided do not include religious instruction or worship; 

              (c) A document that contains the rate and schedule of payment for approved services that is signed by both the service provider and the contractor; 

              (d) A copy of the facility license that shows the authorized capacity of the facility; 

              (e) The name, address and telephone number of the service provider; and 

              (f) The age group(s) served by the provider.

> NOTE: Authority cited: Section 8261, Education Code. Reference: Sections 8261 and 8266.5, 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/records/records-on-file-concerning-service-providers.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.