> 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/duration-of-conditional-contract-status.md).

# Duration of Conditional Contract Status

18307

(a) A contractor shall remain on conditional contract status until the contractor has corrected deficiencies and/or has met requirements identified in the Conditional Status Addendum. 

(b) A contractor with a repayment plan shall remain on conditional contract status until full repayment is made. 

(c) A contractor on conditional contract status that is not on a repayment plan shall remain in that status until: 

              (1) the California Department of Education issues written notice to the contractor that the conditional status has been cleared; or 

              (2) the contractor is issued a clear contract; or 

              (3) the contract terminates according to its terms. 

(d) A contractor may request written verification from the Child Development Division that some of the deficiencies have been corrected even if the contractor will not be removed from conditional contract status.

> 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/duration-of-conditional-contract-status.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.