Legislative intelligence / 90R
SESSION 2027View project ↗

Utilities Code § 121.2015: REQUIRED SAFETY RULES

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Utilities Code Chapter 121, 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. 121.2015. REQUIRED SAFETY RULES. (a) The railroad commission shall adopt rules regarding:

(1) public education and awareness relating to gas pipeline facilities;

(2) community liaison for responding to an emergency relating to a gas pipeline facility; and

(3) measures a gas pipeline facility operator must implement to prepare the gas pipeline facility to maintain service quality and reliability during extreme weather conditions if the gas pipeline facility:

(A) directly serves a natural gas electric generation facility operating solely to provide power to the electric grid for the ERCOT power region or for the ERCOT power region and an adjacent power region; and

(B) is included on the electricity supply chain map created under Section 38.203.

(a-1) In adopting rules under Subsection (a)(3), the railroad commission shall take into consideration weather predictions produced by the office of the state climatologist.

(b) The railroad commission shall require operators or their designated representatives to communicate and conduct liaison activities with fire, police, and other appropriate public emergency response officials. The liaison activities must be conducted by meetings in person except as provided by this section. An operator or the operator's representative may conduct required community liaison activities as provided by Subsection (c) only if the operator or the operator's representative has made an effort to conduct a community liaison meeting in person with the officials by one of the following methods:

(1) mailing a written request for a meeting in person to the appropriate officials by certified mail, return receipt requested;

(2) sending a request for a meeting in person to the appropriate officials by facsimile transmission; or

(3) making one or more telephone calls or e-mail message transmissions to the appropriate officials to request a meeting in person.

(c) If the operator or operator's representative cannot arrange a meeting in person after complying with Subsection (b), the operator or the operator's representative shall conduct community liaison activities by one of the following methods:

(1) holding a telephone conference with the appropriate officials; or

(2) delivering the community liaison information required to be conveyed by certified mail, return receipt requested.

(c-1) The railroad commission shall:

(1) inspect gas pipeline facilities described by Subsection (a)(3) for compliance with rules adopted under Subsection (a)(3);

(2) provide the owner of a facility described by Subsection (a)(3) with a reasonable period of time in which to remedy any violation the railroad commission discovers in an inspection; and

(3) report to the attorney general any violation that is not remedied in a reasonable period of time.

(c-2) The railroad commission shall prioritize inspections conducted under Subsection (c-1)(1) based on risk level, as determined by the railroad commission.

(d) The railroad commission by

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.