> For the complete documentation index, see [llms.txt](https://t22.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t22.caqualityearlylearning.org/enforcement-provisions/review-of-licensing-decisions.md).

# Review of Licensing Decisions

101196

(a) Any person may request a review of a licensing decision against him/her within 10 working days of receipt of the written decision unless an administrative action pursuant to the California Administrative Procedure Act has commenced against the person. 

   (1) "Licensing decision" means a decision that applies to notices of deficiency, civil penalties, and waivers and exceptions. 

   (2) If the review is of a deficiency that has not been corrected, civil penalties continue to accrue during the review process. 

(b) The review specified in (a) above shall be conducted by a higher-level staff person than the person who made the licensing decision and issued the related notice of deficiency, civil penalty, or waiver or exception. 

(c) The reviewer may uphold, amend or dismiss the licensing decision; or may extend the date specified for the correction of a deficiency.

> NOTE: Authority cited: Section 1596.81, Health and Safety Code. Reference: Sections 1596.72, 1596.73, 1596.81 and 1596.842, Health and Safety 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://t22.caqualityearlylearning.org/enforcement-provisions/review-of-licensing-decisions.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.