> 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/selection-of-contractors/appeals-for-request-for-applications.md).

# Appeals for Request for Applications

18003

After receiving the written notification of its score as described in section 18002(e) above, an applicant may review its application, the criteria used to score the application, and any reader comments on its application. An applicant may appeal its score. If the applicant intends to appeal, the following appeal process shall apply: 

              (a) An applicant shall send a notice of appeal to the CDE's Child Development Division within ten business days of receipt of the notice of its score issued pursuant to section 18002(e). 

              (b) The notice to appeal shall contain the following information: 

                            (1) the appellant's name, mailing address, and telephone number; 

                            (2) the name(s) of the person(s) who will represent the appellant at the appeal hearing; 

                            (3) whether the representative(s) will attend the appeal hearing in person or communicate through a telephone conference call. 

              (c) Within ten days of receipt of the notice of appeal, the CDE will notify the appellant of the date, time and place of the appeal hearing in writing to the address provided pursuant to subdivision (b)(1). 

              (d) The appeal will be limited to the application submitted in response to the RFA. 

              (e) The CDE shall notify the appellant in writing of the results of the appeal within ten business days of the appeal hearing.

> NOTE: Authority cited: Section 8261, Education Code. Reference: Sections 8261 and 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/selection-of-contractors/appeals-for-request-for-applications.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.