Legislative intelligence / 90R
SESSION 2027View project ↗

Utilities Code § 37.056: GRANT OR DENIAL OF CERTIFICATE

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.056. GRANT OR DENIAL OF CERTIFICATE. (a) The commission may approve an application and grant a certificate only if the commission finds that the certificate is necessary for the service, accommodation, convenience, or safety of the public.

(b) The commission may:

(1) grant the certificate as requested;

(2) grant the certificate for the construction of a portion of the requested system, facility, or extension or the partial exercise of the requested right or privilege; or

(3) refuse to grant the certificate.

(c) The commission shall grant each certificate on a nondiscriminatory basis after considering:

(1) the adequacy of existing service;

(2) the need for additional service;

(3) the effect of granting the certificate on the recipient of the certificate and any electric utility serving the proximate area; and

(4) other factors, such as:

(A) community values;

(B) recreational and park areas;

(C) historical and aesthetic values;

(D) environmental integrity;

(E) the probable improvement of service or lowering of cost to consumers in the area if the certificate is granted, including any potential economic or reliability benefits associated with dual fuel and fuel storage capabilities in areas outside the ERCOT power region; and

(F) the need for extending transmission service where existing or projected electrical loads will be underserved, including where:

(i) the existing transmission service is unreasonably remote;

(ii) the available capacity is unreasonably limited at transmission or distribution voltage level; or

(iii) the electrical load cannot be interconnected in a timely manner.

(c-1) In considering the need for additional service under Subsection (c)(2) for a reliability transmission project that serves the ERCOT power region or under Subsection (c)(4)(F), the commission must consider the historical load, forecasted load growth, and additional load currently seeking interconnection, including load for which the electric utility has yet to sign an interconnection agreement, as determined by the electric utility with the responsibility for serving the load.

(d) The commission by rule shall establish criteria, in addition to the criteria described by Subsection (c), for granting a certificate for a transmission project that serves the ERCOT power region and that is not necessary to meet state or federal reliability standards. The criteria must include a comparison of the estimated cost of the transmission project for consumers and the estimated congestion cost savings for consumers that may result from the transmission project, considering both current and future expected congestion levels and the transmission project's ability to reduce those congestion levels. The commission shall include with its decision on an application for a certificate to which this subsection applies findings on the criteria.

(e) A certificate to build, own, or operate a new transmission facility that directly interconnects with an existing

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.