> 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/enrollment-into-calworks-stage-3/contractor-responsibilities-calworks-stage-3-child-care-program.md). # Contractor Responsibilities - CalWORKs Stage 3 Child Care Program 18430 (a) The contractor shall comply with chapter 19, subchapter 10, article 2 (commencing with section 18221, except for section 18224(a)(2)). (b) The contractor shall assist parents in choosing a child care provider by providing parents with a referral to the local resource and referral agency. The contractor shall inform parents of policies developed pursuant to section 18428(d). (c) The contractor shall not require the family or the provider to furnish any need and eligibility documentation previously provided to a county welfare department or an alternative payment program. (d) The contractor shall permit the review of the family data file by the child's parent(s) upon request and at reasonable times and places. The family data file may be reviewed by a representative of the parent if the parent provides written authorization for the review. The use or disclosure of all information pertaining to the child and that child's family shall be restricted to purposes directly connected with the administration of the program. > NOTE: Authority cited: Section 8261, Education Code. Reference: Sections 8354 and 8358.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/enrollment-into-calworks-stage-3/contractor-responsibilities-calworks-stage-3-child-care-program.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.