> 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-imposed-during-the-contract-period.md). # Conditional Status Imposed During the Contract Period 18304 (a) If the contractor demonstrates fiscal or programmatic noncompliance during the contract period, based on such information as an annual audit report, a contract compliance review, a program quality review, or a change in licensing status, the Child Development Division may place the contract on conditional contract status for the remainder of the contract period. (b) The contractor shall receive notice and may request an administrative review of the proposed action as set forth in Section 18303 of this Division, in the event such a change in contract status is recommended by staff of the Child Development Division. (c) if the contract is placed on conditional status during the last ninety (90) days of the contract period and the contractor is offered continued funding, the contract for the subsequent contract period will also be on conditional 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/conditional-status-imposed-during-the-contract-period.md?ask=&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.