Legislative intelligence / 90R
SESSION 2027View project ↗

Local Government Code § 141.005: ELECTED OFFICERS IN POPULOUS MUNICIPALITIES

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 141, 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. 141.005. ELECTED OFFICERS IN POPULOUS MUNICIPALITIES. (a) In a municipality with a population of 1.9 million or more, the governing body may set the amount of salary and expenses to be paid to elected officers by ordinance adopted in accordance with this section.

(b) The salary of a state district court judge of the county in which the municipality is located is the comparative salary for the ordinance. In the ordinance:

(1) the salary of the municipal comptroller may not exceed the comparative salary;

(2) the salary of a member of the governing body may not exceed 40 percent of the comparative salary; and

(3) the salary of the mayor may not exceed 150 percent of the comparative salary.

(c) The governing body shall publish notice of the proposed ordinance in a newspaper of general circulation in the municipality for two consecutive weeks immediately preceding the week in which the meeting is to be held at which the proposed ordinance is to be considered. The notice must include:

(1) a general description of the proposed ordinance;

(2) a statement that a public hearing will be held before the ordinance is adopted;

(3) a statement of the time and place of the public hearing; and

(4) a statement that any interested person may appear and testify at the hearing.

(d) The governing body must hold a public hearing before considering the adoption of the proposed ordinance. The ordinance must be approved by a majority vote of the membership of the governing body.

(e) A certified copy of an ordinance adopted under this section must be filed with the municipal secretary within 10 days after the date the ordinance is enacted. The ordinance takes effect on the first day of the next term of office for the officer to whom the ordinance applies, unless the ordinance prescribes a later effective date.

(f) The governing body may submit an ordinance proposed under this section to the voters for their approval in the same manner that charter amendments are submitted under Chapter 9. When an election is held under this subsection, another election on the same proposition may not be called until two years have elapsed after the date of the election.

Acts 1987, 70th Leg., ch. 149, Sec. 1, eff. Sept. 1, 1987. Amended by Acts 2001, 77th Leg., ch. 669, Sec. 59, 60, eff. Sept. 1, 2001.

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.