> 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/family-data-file-calworks-stage-3-child-care-program.md). # Family Data File - CalWORKs Stage 3 Child Care Program 18427 (a) For a family that transfers to a Stage 3 agency from a Stage 1, Stage 2, or another Stage 3 agency, the receiving contractor shall establish the family data file documentation based on the information provided by the transferring agency pursuant to section 18424. The family should not be required to produce new documentation until they are recertified for services pursuant to section 18425, unless they voluntarily request changes pursuant to section 18425.3. (b) For a family being recertified for services in Stage 3 pursuant to section 18425, the contractor shall establish and maintain a family data file in accordance with section 18081, as applicable. > NOTE: Authority cited: Sections 8261, 8261.5, 8263 and 8269, 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/family-data-file-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.