Legislative intelligence / 90R
SESSION 2027View project ↗

Local Government Code § 22.073: POWERS AND DUTIES OF SECRETARY

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 22, 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. 22.073. POWERS AND DUTIES OF SECRETARY. (a) The secretary of the municipality shall attend each meeting of the governing body of the municipality and shall keep, in a record provided for that purpose, accurate minutes of the governing body's proceedings.

(b) The secretary shall:

(1) engross and enroll all laws, resolutions, and ordinances of the governing body;

(2) keep the corporate seal;

(3) take charge of, arrange, and maintain the records of the governing body;

(4) countersign all commissions issued to municipal officers and all licenses issued by the mayor, and keep a record of those commissions and licenses; and

(5) prepare all notices required under any regulation or ordinance of the municipality.

(c) Repealed by Acts 2011, 82nd Leg., R.S., Ch. 1324, Sec. 5(2), eff. June 17, 2011.

(d) The secretary shall draw all the warrants on the treasurer, countersign the warrants, and keep, in a record provided for that purpose, an accurate account of the warrants.

(e) The secretary serves as the general accountant of the municipality and shall keep regular accounts of the municipal receipts and disbursements. The secretary shall keep each cause of receipt and disbursement separately and under proper headings. The secretary shall also keep separate accounts with each person, including each officer, who has monetary transactions with the municipality. The secretary shall credit accounts allowed by proper authority and shall specify the particular transaction to which each entry applies. The secretary shall keep records of the accounts and other information covered by this subsection.

(f) The secretary shall keep a register of bonds and bills issued by the municipality and all evidence of debt due and payable to the municipality, noting the relevant particulars and facts as they occur.

(g) The secretary shall carefully keep all contracts made by the governing body.

(h) The secretary shall perform all other duties required by law, ordinance, resolution, or order of the governing body.

Acts 1987, 70th Leg., ch. 149, Sec. 1, eff. Sept. 1, 1987. Amended by Acts 1989, 71st Leg., ch. 1248, Sec. 47, eff. Sept. 1, 1989.

Amended by:

Acts 2011, 82nd Leg., R.S., Ch. 1184 (H.B. 3475), Sec. 3(2), eff. September 1, 2011.

Acts 2011, 82nd Leg., R.S., Ch. 1324 (S.B. 480), Sec. 5(2), eff. June 17, 2011.

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.