> 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/continuing-requirements/staffing-for-water-activities.md).

# Staffing for Water Activities

101216.6

(a) There shall be at least one adult who has a valid water-safety certificate on file at the center present during water activities in or near any of the following bodies of water:&#x20;

&#x20;  (1) Swimming pool.&#x20;

&#x20;  (2) Any portable pool with sides so high that children using the pool cannot step out unassisted by a person or device (including a ladder).&#x20;

&#x20;  (3) Potentially dangerous natural bodies of water including, but not limited to, oceans, lakes, rivers and streams.&#x20;

(b) A ratio of not less than one adult, including teachers, to every six children, or fraction thereof, shall be maintained during water activities in or near any of the bodies of water specified in (a)(1) through   (3) above.&#x20;

&#x20;  (1) Lifeguards or personnel supervising anyone other than center children at the water activity site shall not be included in this ratio.

> NOTE: Authority cited: Section 1596.81, Health and Safety Code. Reference: Sections 1596.72, 1596.73, 1596.81, 1596.87 and 1597.05, 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/continuing-requirements/staffing-for-water-activities.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.
