Legislative intelligence / 90R
SESSION 2027View project ↗

Utilities Code § 38.079: TRANSMISSION AND DISTRIBUTION SYSTEM RESILIENCY PLAN AND COST RECOVERY

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 38, 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. 38.079. TRANSMISSION AND DISTRIBUTION SYSTEM RESILIENCY PLAN AND COST RECOVERY. (a) In this section, "plan" means a transmission and distribution system resiliency plan described by Subsection (b).

(b) An electric utility may file, in a manner authorized by commission rule, a plan to enhance the resiliency of the utility's transmission and distribution system through at least one of the following methods:

(1) hardening electrical transmission and distribution facilities;

(2) modernizing electrical transmission and distribution facilities;

(3) undergrounding certain electrical distribution lines;

(4) lightning mitigation measures;

(5) flood mitigation measures;

(6) information technology;

(7) cybersecurity measures;

(8) physical security measures;

(9) vegetation management; or

(10) wildfire mitigation and response.

(c) A plan must explain the systematic approach the electric utility will use to carry out the plan during at least a three-year period.

(d) In determining whether to approve a plan filed under this section, the commission shall consider:

(1) the extent to which the plan is expected to enhance system resiliency, including whether the plan prioritizes areas of lower performance; and

(2) the estimated costs of implementing the measures proposed in the plan.

(e) The commission shall issue an order to approve, modify, or deny a plan filed under Subsection (b) and any associated rider described by Subsection (i) not later than the 180th day after the plan is filed with the commission. The commission may approve a plan only if the commission determines that approving the plan is in the public interest.

(f) For a plan approved by the commission, with or without modification, an electric utility may request a good cause exception on implementing all or some of the measures in the plan if operational needs, business needs, financial conditions, or supply chain or labor conditions dictate the exception. The commission's denial of a plan is not considered to be a finding of the prudence or imprudence of a measure or cost in the plan for the purposes of Chapter 36 or this chapter.

(g) An electric utility for which the commission has approved a plan under this section may request that the commission review an updated plan submitted by the electric utility. The updated plan must comply with any applicable commission rules and take effect on a date that is not earlier than the third anniversary of the approval date of the utility's most recently approved plan. The commission shall review and approve, modify, or deny the updated plan in the manner provided by Subsections (d), (e), and (f).

(h) An electric utility's implementation of a plan approved under this section may be reviewed for the purposes of Chapter 36 or this chapter. If the commission determines that the costs to implement an approved plan were imprudently incurred or otherwise unreasonable, those costs are subject to disallowance.

(i) Notwithstanding any other law

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.