> For the complete documentation index, see [llms.txt](https://t22.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t22.caqualityearlylearning.org/continuing-requirements/sign-in-and-sign-out.md).

# Sign In and Sign Out

101229.1

(a) In addition to the sign-in procedure requirement of Section 101226.1(b), the licensee shall develop, maintain and implement a written procedure to sign the child in/out of the child care center that shall, at a minimum, include the following: 

   (1) The person who signs the child in/out shall use his/her full legal signature and shall record the time of day. 

(b) The person who brings the child to, and removes the child from, the center shall sign the child in/out.

(c) A person who removes the child from the center during the day, and returns the child to the center the same day, shall sign the child in/out. 

(d) The sign-in and sign-out sheets with the signatures required by this section and by Section 101226.1 shall be kept for one month and shall be available at the center for review by the Department.

> NOTE: Authority cited: Section 1596.81, Health and Safety Code. Reference: Sections 1596.72, 1596.73, 1596.81 and 1597.05, Health and Safety 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://t22.caqualityearlylearning.org/continuing-requirements/sign-in-and-sign-out.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.