> 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/general-requirements/audit-requirements-for-subcontracts.md).

# Audit Requirements for Subcontracts

18032

(a) Subcontracts requiring Child Development Division approval shall be audited in accordance with California Department of Education (CDE) Audit Guidelines.&#x20;

(b) The cost of the audit shall be reimbursable and shall be borne by the contractor either directly or as an allowance in the subcontract.&#x20;

(c) The audit of the subcontract shall be submitted to the CDE as follows:&#x20;

&#x20;             (1) School districts, county offices of education and community colleges shall submit the audit of the subcontract by the fifteenth day of the fifth month following the fiscal year in which the subcontracted services were performed;&#x20;

&#x20;             (2) All other contractors shall submit the subcontract audit along with the contractor's audit as specified in section 18071 of this Division.

> NOTE: Authority cited: Section 8261, Education Code. Reference: Section 8448, 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/general-requirements/audit-requirements-for-subcontracts.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.
