> 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/parent-fees/fee-assessment-explanation-to-parents.md).

# Fee Assessment: Explanation to Parents

18109

(a) The contractor shall utilize the following factors in determining the fee to be assessed for each family:&#x20;

&#x20;             (1) The adjusted monthly family income;&#x20;

&#x20;             (2) Family size; families having fewer than three&#x20;

&#x20;             (3) members shall be regarded as a family of three (3). (3) The fee shall be assessed and collected based on the family's child who is enrolled for the longest period.&#x20;

&#x20;             (4) The fee assessed and collected shall be either the fee indicated on the fee schedule, the actual costs of services or the contract maximum daily/hourly rate, whichever is least.&#x20;

&#x20;             (5) No adjustment shall be made for excused or unexcused absences.&#x20;

&#x20;             (6) The fee shall be the full portion of the family's cost for services.&#x20;

(b) The contractor shall maintain a record of each family's fee assessment, the effective date(s) of each fee increase or decrease, the dates and amounts of fees collected and any amounts which are delinquent.&#x20;

(c) The contractor shall explain to the parent(s) the contractor's policies regarding fee assessment and collection and the possible consequences for delinquent payment of fees.

> NOTE: Authority cited: Section 8263, Education Code. Reference: Sections 8263 and 8265, 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/parent-fees/fee-assessment-explanation-to-parents.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.
