Legislative intelligence / 90R
SESSION 2027View project ↗

Education Code § 37.0814: ARMED SECURITY OFFICER REQUIRED

1 bill in the 90th Legislature would change this section

Part of Education Code Chapter 37, 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. 37.0814. ARMED SECURITY OFFICER REQUIRED. (a) The board of trustees of each school district shall determine the appropriate number of armed security officers for each district campus. The board must ensure that at least one armed security officer is present during regular school hours at each district campus.

(b) A security officer described by Subsection (a) must be:

(1) a school district peace officer;

(2) a school resource officer;

(3) a commissioned peace officer employed as security personnel under Section 37.081;

(4) a reserve deputy sheriff appointed under Section 85.004, Local Government Code, who is a peace officer as described by Article 2A.001, Code of Criminal Procedure;

(5) a reserve police officer appointed under Section 37.0816 who is a peace officer as described by Article 2A.001, Code of Criminal Procedure; or

(6) an honorably retired peace officer, as that term is defined by Section 614.121, Government Code, who has:

(A) kept their commission as a peace officer in active status; and

(B) fulfilled all applicable requirements under Sections 1701.351, 1701.3525, and 1701.357, Occupations Code.

(c) If the board of trustees of a school district is unable to comply with this section, the board may claim a good cause exception from the requirement to comply with this section if the district's noncompliance is due to the availability of:

(1) funding; or

(2) personnel who qualify to serve as a security officer described by Subsection (a).

(d) The board of trustees of a school district that claims a good cause exception under Subsection (c) must develop an alternative standard with which the district is able to comply, which may include providing a person to act as a security officer who is:

(1) a school marshal; or

(2) a school district employee or a person with whom the district contracts who:

(A) either:

(i) has completed school safety training provided by a qualified handgun instructor certified in school safety under Section 411.1901, Government Code; or

(ii) not later than the 90th day after the date on which the employee or person begins duties as a security officer, completes training deemed appropriate by the district, in consultation with the district's police department, or, if the district does not have a police department, a local law enforcement agency, in:

(a) active shooter response, which must be provided by an instructor certified by the Advanced Law Enforcement Rapid Response Training Center at Texas State University--San Marcos;

(b) school safety and emergency management;

(c) crisis intervention;

(d) incident command;

(e) first aid administration;

(f) mental health; and

(g) qualifications relating to the carrying or use of a firearm; and

(B) carries a handgun on school premises in accordance with written regulations or written authorization of the district under Section 46.03(a)(1)(A), Penal Code.

(d-1) A good cause exception claimed by the board of trustees of a school district under Su

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.