Legislative intelligence / 90R
SESSION 2027View project ↗

Local Government Code § 252.021: COMPETITIVE REQUIREMENTS FOR PURCHASES

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 Local Government Code Chapter 252, 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. 252.021. COMPETITIVE REQUIREMENTS FOR PURCHASES. (a) Before a municipality may enter into a contract that requires an expenditure of more than $100,000 from one or more municipal funds, the municipality must:

(1) comply with the procedure prescribed by this subchapter and Subchapter C for competitive sealed bidding or competitive sealed proposals;

(2) use the reverse auction procedure, as defined by Section 2155.062(d), Government Code, for purchasing; or

(3) comply with a method described by Chapter 2269, Government Code.

(b) A municipality may use the competitive sealed proposal procedure for the purchase of goods or services, including high technology items and insurance.

(c) The governing body of a municipality that is considering using a method other than competitive sealed bidding must determine before notice is given the method of purchase that provides the best value for the municipality. The governing body may delegate, as appropriate, its authority under this subsection to a designated representative. If the competitive sealed proposals requirement applies to the contract, the municipality shall consider the criteria described by Section 252.043(b) and the discussions conducted under Section 252.042 to determine the best value for the municipality.

(d) This chapter does not apply to the expenditure of municipal funds that are derived from an appropriation, loan, or grant received by a municipality from the federal or state government for conducting a community development program established under Chapter 373 if under the program items are purchased under the request-for-proposal process described by Section 252.042. A municipality using a request-for-proposal process under this subsection shall also comply with the requirements of Section 252.0215.

Acts 1987, 70th Leg., ch. 149, Sec. 1, eff. Sept. 1, 1987. Amended by Acts 1989, 71st Leg., ch. 1, Sec. 56(b), eff. Aug. 28, 1989; Acts 1993, 73rd Leg., ch. 749, Sec. 1, eff. Sept. 1, 1993; Acts 1993, 73rd Leg., ch. 757, Sec. 11, eff. Sept. 1, 1993; Acts 1995, 74th Leg., ch. 45, Sec. 1, eff. May 5, 1995; Acts 1997, 75th Leg., ch. 790, Sec. 1, eff. June 17, 1997; Acts 1999, 76th Leg., ch. 571, Sec. 1, eff. June 18, 1999; Acts 2001, 77th Leg., ch. 115, Sec. 1, eff. Sept. 1, 2001; Acts 2001, 77th Leg., ch. 436, Sec. 2, eff. May 28, 2001; Acts 2001, 77th Leg., ch. 436, Sec. 3, eff. May 28, 2001; Acts 2001, 77th Leg., ch. 1409, Sec. 1, eff. Sept. 1, 2001; Acts 2003, 78th Leg., ch. 217, Sec. 1, eff. June 18, 2003; Acts 2003, 78th Leg., ch. 1276, Sec. 12.003, eff. Sept. 1, 2003.

Amended by:

Acts 2007, 80th Leg., R.S., Ch. 434 (S.B. 1765), Sec. 1, eff. September 1, 2007.

Acts 2007, 80th Leg., R.S., Ch. 1213 (H.B. 1886), Sec. 1, eff. September 1, 2007.

Acts 2007, 80th Leg., R.S., Ch. 1272 (H.B. 3517), Sec. 1, eff. September 1, 2007.

Acts 2007, 80th Leg., R.S., Ch. 1272 (H.B. 3517), Sec. 2, eff. September 1, 2007.

Acts 2011, 82nd Leg., R.S., Ch. 1129 (H.B. 628), Sec. 4.01, eff. Septe

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.