Legislative intelligence / 90R
SESSION 2027View project ↗

Utilities Code § 37.051: CERTIFICATE REQUIRED

1 bill in the 90th Legislature would change this section

Part of Utilities 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.051. CERTIFICATE REQUIRED. (a) An electric utility may not directly or indirectly provide service to the public under a franchise or permit unless the utility first obtains from the commission a certificate that states that the public convenience and necessity requires or will require the installation, operation, or extension of the service.

(b) Except as otherwise provided by this chapter, a retail electric utility may not furnish or make available retail electric utility service to an area in which retail electric utility service is being lawfully furnished by another retail electric utility unless the utility first obtains a certificate that includes the area in which the consuming facility is located.

(c) Notwithstanding any other provision of this chapter, including Subsection (a), an electric cooperative is not required to obtain a certificate of public convenience and necessity for the construction, installation, operation, or extension of any generating facilities or necessary interconnection facilities.

(c-1) Notwithstanding any other provision of this title except Section 11.009, and except as provided by Subsection (c-2), a person, including an electric utility or municipally owned utility, may not interconnect a facility to the ERCOT transmission grid that enables additional power to be imported into or exported out of the ERCOT power grid unless the person obtains a certificate from the commission stating that public convenience and necessity requires or will require the interconnection. The person must apply for the certificate not later than the 180th day before the date the person seeks any order from the Federal Energy Regulatory Commission related to the interconnection. The commission shall apply Section 37.056 in considering an application under this subsection. In addition, the commission must determine that the application is consistent with the public interest before granting the certificate. The commission may adopt rules necessary to implement this subsection. This subsection does not apply to a facility that is in service on December 31, 2014.

(c-2) The commission, not later than the 185th day after the date the application is filed, shall approve an application filed under Subsection (c-1) for a facility that is to be constructed under an interconnection agreement appended to an offer of settlement approved in a final order of the Federal Energy Regulatory Commission that was issued in Docket No. TX11-01-001 on or before December 31, 2014, directing physical connection between the ERCOT and SERC regions under Sections 210, 211, and 212 of the Federal Power Act (16 U.S.C. Sections 824i, 824j, and 824k). In approving the application, the commission may prescribe reasonable conditions to protect the public interest that are consistent with the final order of the Federal Energy Regulatory Commission.

(c-3) Nothing in Subsection (c-1) or (c-2) is intended to restrict the authority of the commission or the indepe

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.