> 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/appeal-and-dispute-resolution-procedures/conditional-status-addendum.md).

# Conditional Status Addendum

18305

A conditional status contract shall contain a bill of particulars specified in Education Code section 8406.6 called a Conditional Status Addendum explain-ing the contract conditions. The Addendum shall include the following: 

              (a) The specific item(s) of noncompliance which the contractor must correct; 

              (b) The specific corrective action(s) which must be taken; 

              (c) The time period within which the contractor must complete the corrections; 

              (d) Notice that failure to make required corrections will result in termination of the contract or no offer of continued funding. 

              (e) If the contractor is placed on conditional status during the contract period: 

                            (1) A Conditional Status Addendum will be issued by the California Department of Education and 

                            (2) The Conditional Status Addendum shall be considered a part of the annual child development contract and binding on the contractor.

> NOTE: Authority cited: Section 8261, Education Code. Reference: Section 8406.6, 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/appeal-and-dispute-resolution-procedures/conditional-status-addendum.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.