Legislative intelligence / 90R
SESSION 2027View project ↗

Occupations Code § 1951.212: INTEGRATED PEST MANAGEMENT PROGRAMS FOR SCHOOL DISTRICTS

1 bill in the 90th Legislature would change this section

Part of Occupations Code Chapter 1951, 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. 1951.212. INTEGRATED PEST MANAGEMENT PROGRAMS FOR SCHOOL DISTRICTS. (a) The department shall establish standards for an integrated pest management program for the use of pesticides, herbicides, and other chemical agents to control pests, rodents, insects, and weeds at the school buildings and other facilities of school districts.

(b) The department shall use the structural pest control advisory committee to assist the department in developing the standards for the integrated pest management program. In developing the standards, the advisory committee shall consult with a person knowledgeable in the area of integrated pest management in schools.

(c) The department shall include in standards adopted under this section a requirement to use the least toxic methods available to control pests, rodents, insects, and weeds.

(d) The department by rule shall establish categories of pesticides that a school district is allowed to apply. For each category, the department shall specify:

(1) the minimum distance a school district must maintain between an area where pesticides are being applied and an area where students are present at the time of application;

(2) the minimum amount of time a school district is required to wait before allowing students to enter an indoor or outdoor area in a school building or on school grounds for normal academic instruction or organized extracurricular activities after pesticides have been applied;

(3) the requirements for posting notice of the indoor and outdoor use of pesticides;

(4) the requirements for obtaining approval before applying the pesticide; and

(5) the requirements for maintaining records of the application of pesticides.

(e) Each school district shall:

(1) adopt an integrated pest management program that incorporates the standards established by the department under this section;

(2) designate an integrated pest management coordinator for the district; and

(3) report to the department not later than the 90th day after the date the district designates or replaces an integrated pest management coordinator the name, address, telephone number, and e-mail address of the district's current coordinator.

(f) Each person who is designated as the integrated pest management coordinator for a school district shall successfully complete six hours of continuing education in integrated pest management every three years.

(g) The department shall inspect each school district at least once every five years for compliance with this section and may conduct additional inspections based on a schedule of risk-based inspections using the following criteria:

(1) whether there has been a prior violation by the school district;

(2) the inspection history of the school district;

(3) any history of complaints involving the school district; and

(4) any other factor determined by the department by rule.

Added by Acts 2001, 77th Leg., ch. 1421, Sec. 4, eff. June 1, 2003.

Amended by:

Acts 2007, 80th Leg., R.S., Ch. 8

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.