Legislative intelligence / 90R
SESSION 2027View project ↗

Education Code § 51.217: MULTIHAZARD EMERGENCY OPERATIONS PLAN; SAFETY AND SECURITY AUDIT

1 bill in the 90th Legislature would change this section

Part of Education Code Chapter 51, 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. 51.217. MULTIHAZARD EMERGENCY OPERATIONS PLAN; SAFETY AND SECURITY AUDIT. (a) In this section, "institution" means a general academic teaching institution, a medical and dental unit, or other agency of higher education, as those terms are defined by Section 61.003.

(b) An institution shall adopt and implement a multihazard emergency operations plan for use at the institution. The plan must address mitigation, preparedness, response, and recovery, including the prompt recovery of services provided by the institution. The plan must provide for:

(1) employee training in responding to an emergency;

(2) mandatory drills to prepare students, faculty, and employees for responding to an emergency;

(3) measures to ensure coordination with the Department of State Health Services, local emergency management agencies, law enforcement, health departments, and fire departments in the event of an emergency; and

(4) the implementation of a safety and security audit as required by Subsection (c).

(c) At least once every three years, an institution shall conduct a safety and security audit of the institution's facilities. To the extent possible, an institution shall follow safety and security audit procedures developed in consultation with the division of emergency management of the office of the governor.

(d) An institution shall report the results of the safety and security audit conducted under Subsection (c) to the institution's board of regents and the division of emergency management of the office of the governor.

(e) Except as provided by Subsection (f), any document or information collected, developed, or produced during a safety and security audit conducted under Subsection (c) is not subject to disclosure under Chapter 552, Government Code.

(f) A document relating to an institution's multihazard emergency operations plan is subject to disclosure if the document enables a person to:

(1) verify that the institution has established a plan and determine the agencies involved in the development of the plan and the agencies coordinating with the institution to respond to an emergency, including the Department of State Health Services, local emergency services agencies, law enforcement agencies, health departments, and fire departments;

(2) verify that the institution's plan was reviewed within the last 12 months and determine the specific review dates;

(3) verify that the plan addresses the four phases of emergency management under Subsection (b);

(4) verify that institution employees have been trained to respond to an emergency and determine the types of training, the number of employees trained, and the person conducting the training;

(5) verify that each campus has conducted mandatory emergency drills and exercises in accordance with the plan and determine the frequency of the drills;

(6) verify that the institution has completed a safety and security audit under Subsection (c) and determine the date the audit was conducted, the person c

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.