> 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/general-requirements/subcontracts-excluded-from-scope-of-this-article.md). # Subcontracts Excluded from Scope of This Article 18026 The following types of relationships are not subject to the regulations contained in this Article: (a) Employment agreements; (b) Facility rental or lease agreements; (c) Payment arrangements with family child care homes; (d) Payment arrangements with child care providers for Alternative Payment programs; (e) Medical or dental service agreements; (f) Bookkeeping/auditing agreements, except for Section 18027; (g) Food services agreements; (h) Janitorial and groundkeeping agreements; (i) A subcontract with a public agency; and (j) Subcontracts with an individual for less than ten thousand dollars ($10,000.00), except for Section 18027. > NOTE: Authority cited: Section 8261, Education Code. Reference: Section 8261, 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/general-requirements/subcontracts-excluded-from-scope-of-this-article.md?ask=&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.