Legislative intelligence / 90R
SESSION 2027View project ↗

Local Government Code § 176.003: CONFLICTS DISCLOSURE STATEMENT REQUIRED

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 176, 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. 176.003. CONFLICTS DISCLOSURE STATEMENT REQUIRED. (a) A local government officer shall file a conflicts disclosure statement with respect to a vendor if:

(1) the vendor enters into a contract with the local governmental entity or the local governmental entity is considering entering into a contract with the vendor; and

(2) the vendor:

(A) has an employment or other business relationship with the local government officer or a family member of the officer that results in the officer or family member receiving taxable income, other than investment income, that exceeds $2,500 during the 12-month period preceding the date that the officer becomes aware that:

(i) a contract between the local governmental entity and vendor has been executed; or

(ii) the local governmental entity is considering entering into a contract with the vendor;

(B) has given to the local government officer or a family member of the officer one or more gifts that have an aggregate value of more than $100 in the 12-month period preceding the date the officer becomes aware that:

(i) a contract between the local governmental entity and vendor has been executed; or

(ii) the local governmental entity is considering entering into a contract with the vendor; or

(C) has a family relationship with the local government officer.

(a-1) A local government officer is not required to file a conflicts disclosure statement in relation to a gift accepted by the officer or a family member of the officer if the gift is:

(1) a political contribution as defined by Title 15, Election Code; or

(2) food accepted as a guest.

(a-2) A local government officer is not required to file a conflicts disclosure statement under Subsection (a) if the local governmental entity or vendor described by that subsection is an administrative agency created under Section 791.013, Government Code.

(b) A local government officer shall file the conflicts disclosure statement with the records administrator of the local governmental entity not later than 5 p.m. on the seventh business day after the date on which the officer becomes aware of the facts that require the filing of the statement under Subsection (a).

(c) Repealed by Acts 2015, 84th Leg., R.S., Ch. 989 , Sec. 9(1), eff. September 1, 2015.

(d) Repealed by Acts 2015, 84th Leg., R.S., Ch. 989 , Sec. 9(1), eff. September 1, 2015.

(e) The commission shall adopt the conflicts disclosure statement for local government officers for use under this section. The conflicts disclosure statement must include:

(1) a requirement that each local government officer disclose:

(A) an employment or other business relationship described by Subsection (a)(2)(A), including the nature and extent of the relationship; and

(B) gifts accepted by the local government officer and any family member of the officer from a vendor during the 12-month period described by Subsection (a)(2)(B) if the aggregate value of the gifts accepted by the officer or a family member from that

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.