> 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/accounting-and-reporting-requirements/enrollment-and-attendance-accounting.md).

# Enrollment and Attendance Accounting

18065

(a) Contractors operating centers and/or family child care homes shall use daily sign-in/sign-out sheets as a primary source document for audit and reimbursement purposes. 

(b) One of the following persons shall enter the time of arrival and departure on a sign-in/sign-out sheet and, except as specified in Subsection (c) below, shall sign the sheet using their full signature: 

              (1) The parent or other adult authorized by the parent to drop off/pick up a child; or 

              (2) The staff person designated by the contractor as the person responsible for entering the times of arrival and departure if the child is not dropped off/picked up by a parent or other adult authorized by the parent. 

(c) First and last initials of the contractor's authorized representative along with a notation of the time are required to document when a school-age child departs for and returns from school during the day. 

(d) Contractors operating an Alternative Payment program may use an alternative to daily sign-in/sign-out sheets as documentation of attendance for reimbursement purposes with the prior written approval of the Child Development Division.

> NOTE: Authority cited: Sections 8261 and 8269, Education Code. Reference: Sections 8261 and 8269, 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/accounting-and-reporting-requirements/enrollment-and-attendance-accounting.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.