Legislative intelligence / 90R
SESSION 2027View project ↗

Human Resources Code § 42.252: PROPOSED OPERATIONAL PLAN; LICENSING PROCEDURES

1 bill in the 90th Legislature would change this section

Part of Human Resources Code Chapter 42, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 42.252. PROPOSED OPERATIONAL PLAN; LICENSING PROCEDURES. (a) In addition to the applicable requirements to obtain a license under Subchapter C, a person applying for a license to operate a general residential operation shall submit to the commission a proposed operational plan.

(b) The executive commissioner shall adopt rules regarding:

(1) the information that must be included in the operational plan;

(2) the commission's review of the operational plan; and

(3) the basis of the commission's determination on whether:

(A) the plan is complete or incomplete; and

(B) to deny or approve the plan.

(c) The operational plan must include:

(1) a community engagement plan to develop and, if necessary, improve relations between the general residential operation and the community in which the operation is located that includes:

(A) a summary of any discussions the operation had with:

(i) local law enforcement; and

(ii) local health, therapeutic, and recreational resources available to support children at the operation; and

(B) a summary of the opportunities the children at the operation will have for social interaction in the community;

(2) an educational plan describing the applicant's plan to provide for the educational needs of the children at the general residential operation that:

(A) identifies whether the proposed operation will provide for the public or private education of school-age children at the operation;

(B) identifies whether the proposed operation will provide for the education of school-age children through a local school, off-site charter school, or on-site charter school;

(C) includes any discussions, plans, and agreements with the local school district, private school, or local charter school that will be providing education to the school-age children at the operation; and

(D) if the children are to be enrolled in a public school, includes either:

(i) a statement from the local independent school district on the impact of the proposed child-care services on the local school district; or

(ii) an explanation of the reasons the operation was unable to obtain a statement described by Subparagraph (i) and a discussion of other alternative educational services that the operation could offer;

(3) a trauma-informed plan to address unauthorized absences of children from the general residential operation;

(4) a suicide prevention, intervention, and postvention plan that meets the requirements of Section 42.0433; and

(5) the qualifications, background, and history, including any compliance history, of each individual who is proposed to be involved in:

(A) the management of the operation; and

(B) the educational leadership of the operation if the operation will be using an on-site charter school.

(d) A person applying for a license to operate a general residential operation shall state in the application if the proposed operation will provide services to children who are victims of human trafficking but is not required

The section continues: whole chapter.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.