> 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/prohibition-against-presigned-checks-child-development-division-prior-written-approval.md).

# Prohibition Against Presigned Checks, Child Development Division Prior Written Approval

Except for external payroll services, private contractors:&#x20;

(a) Shall not use any presigned, preauthorized, or pre-stamped checks, without the prior written approval of the Child Development Division; and&#x20;

(b) Shall require two (2) authorized signatures on all checks unless:&#x20;

&#x20;             (1) the contractor has a policy approved by its governing board requiring dual signatures only on checks above a specified dollar amount; and&#x20;

&#x20;             (2) the annual audit verifies that appropriate internal controls are maintained.

> NOTE: Authority cited: Section 8261, Education Code. Reference: Section 8261, 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://title5.caqualityearlylearning.org/general-requirements/prohibition-against-presigned-checks-child-development-division-prior-written-approval.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
