> 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/verification-of-excused-absence-policies.md).

# Verification of Excused Absence Policies

18066

(a) If the absence is claimed by the contractor as an excused absence as defined within the definition of “Attendance” in Education Code section 8208, the attendance accounting records shall contain verification that includes: 

              (1) The name of the child; 

              (2) The date(s) of absence; 

              (3) the specific reason for the absence; and 

              (4) The signature of the parent or the contractor's authorized representative if verification is made by telephone. 

(b) If an excused absence is based on the time spent with a parent or other relative as required by a court of law, the basic data file shall contain a copy of the Court Order. 

(c) Contractors shall adopt reasonable policies delineating circumstances that would constitute an excused absence for “family emergency” and “in the best interest of the child.” 

(d) Contractors shall not disenroll any family due to excessive absences, except in circumstances described in section 18066.5. 

(e) Contractors shall inform parent of these policies. 

(f) Except for children who are recipients of protective services or at risk of abuse or neglect, excused absences “in the best interest of the child” shall be limited to 10 days during the contract period.

> NOTE: Authority cited: Sections 8261 and 8263, Education Code. Reference: Sections 8208, 8261 and 8263, 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/verification-of-excused-absence-policies.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.