> 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/utilization-of-the-regional-market-rate-ceiling/adjustment-for-children-with-exceptional-needs.md).

# Adjustment for Children with Exceptional Needs

18075.2

(a) When child care and development services are provided to a child with exceptional needs, the contractor shall multiply the lesser of the regional market rate ceiling or the rate determined pursuant to Section 18074.3 or 18074.4, whichever is lower, by only one of the following:

&#x20;            (1) By 1.2, when the child has exceptional needs as defined in Education Code Section 8208(*l*).

&#x20;            (2) By 1.5, when the child is severely disabled as defined in Education Code Section 8208(x).

(b) Contractors shall apply this adjustment only when there is documentation that additional services and/or accommodations for that particular child are being provided, and such services and/or accommodations result in an on-going financial impact on the provider.

> NOTE: Authority cited: Sections 8222, 8265, 8265.5 and 8269, Education Code. Reference: Sections 8208(*l*) and 8208(x), 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/utilization-of-the-regional-market-rate-ceiling/adjustment-for-children-with-exceptional-needs.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.
