Legislative intelligence / 90R
SESSION 2027View project ↗

Local Government Code § 143.089: PERSONNEL FILE

1 bill in the 90th Legislature would change this section

Part of Local Government Code Chapter 143, 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. 143.089. PERSONNEL FILE. (a) The director or the director's designee shall maintain a personnel file on each fire fighter and police officer. The personnel file must contain any letter, memorandum, or document relating to:

(1) a commendation, congratulation, or honor bestowed on the fire fighter or police officer by a member of the public or by the employing department for an action, duty, or activity that relates to the person's official duties;

(2) any misconduct by the fire fighter or police officer if the letter, memorandum, or document is from the employing department and if the misconduct resulted in disciplinary action by the employing department in accordance with this chapter; and

(3) the periodic evaluation of the fire fighter or police officer by a supervisor.

(b) A letter, memorandum, or document relating to alleged misconduct by the fire fighter or police officer may not be placed in the person's personnel file if the employing department determines that there is insufficient evidence to sustain the charge of misconduct.

(c) A letter, memorandum, or document relating to disciplinary action taken against the fire fighter or police officer or to alleged misconduct by the fire fighter or police officer that is placed in the person's personnel file as provided by Subsection (a)(2) shall be removed from the employee's file if the commission finds that:

(1) the disciplinary action was taken without just cause; or

(2) the charge of misconduct was not supported by sufficient evidence.

(d) If a negative letter, memorandum, document, or other notation of negative impact is included in a fire fighter's or police officer's personnel file, the director or the director's designee shall, within 30 days after the date of the inclusion, notify the affected fire fighter or police officer. The fire fighter or police officer may, on or before the 15th day after the date of receipt of the notification, file a written response to the negative letter, memorandum, document, or other notation.

(e) The fire fighter or police officer is entitled, on request, to a copy of any letter, memorandum, or document placed in the person's personnel file. The municipality may charge the fire fighter or police officer a reasonable fee not to exceed actual cost for any copies provided under this subsection.

(f) The director or the director's designee may not release any information contained in a fire fighter's or police officer's personnel file without first obtaining the person's written permission, unless the release of the information is required by law.

(g) A fire or police department may maintain a personnel file on a fire fighter or police officer employed by the department for the department's use. Except as provided by Subsection (h), the department may not release any information contained in the department file to any agency or person requesting information relating to a fire fighter or police officer. The department shall refer to the director o

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.