> 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/follow-up-visits-to-determine-compliance.md).

# Follow-up Visits to Determine Compliance

101194

(a) A follow-up visit shall be conducted to determine compliance with the plan of correction specified in the notice of deficiency. 

   (1) A follow-up visit shall be conducted within 10 working days following the date(s) of correction specified in the notice of deficiency unless the licensee has demonstrated that the deficiency was corrected as required. 

   (2) No penalty shall be assessed unless a follow- up visit is conducted. 

(b) If a follow-up visit indicates that a deficiency was not corrected on or before the date specified in the notice of deficiency, the evaluator shall issue a notice of penalty. 

(c) A notice of penalty shall be in writing and shall include: 

   (1) The amount of the penalty assessed and the date the payment is due. 

   (2) The name and address of the agency responsible for collecting of the penalty. 

(d) When an immediate penalty has been assessed pursuant to Sections 101195(c), (d) and (e), and correction is made when the evaluator is present, a follow-up visit is not required.

> NOTE: Authority cited: Sections 1596.81 and 1596.99, Health and Safety Code. Reference: Sections 1596.72, 1596.73, 1596.81, 1596.852, 1596.853, 1596.98 and 1596.99, 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/follow-up-visits-to-determine-compliance.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.