Legislative intelligence / 90R
SESSION 2027View project ↗

Civil Practice and Remedies Code § 145.003: PRESUMPTION OF NO NEGLIGENCE

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 Civil Practice and Remedies Code Chapter 145, 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. 145.003. PRESUMPTION OF NO NEGLIGENCE. (a) This section applies only to an action against an in-home service company or residential delivery company that:

(1) arises out of a criminal act or omission by an officer or employee of the company as to whom the company has obtained criminal history record information under Section 145.002(1);

(2) is brought by or on behalf of a person whose home the officer or employee entered while in the performance of the employee's job duties, without regard to where the criminal act or omission occurred; and

(3) seeks damages from the company for the negligent hiring of the officer or employee.

(b) In an action to which this section applies, an in-home service company or residential delivery company is rebuttably presumed to have not acted negligently if:

(1) at the time a person was hired, the company obtained criminal history record information regarding the officer or employee under Section 145.002(1); and

(2) the criminal history record information shows that, in the 20 years preceding the date the information was obtained for a felony or in the 10 years preceding the date the information was obtained for a Class A or Class B misdemeanor, the officer or employee had not been convicted of, or placed on deferred adjudication for:

(A) an offense in this state classified as:

(i) an offense against the person or the family;

(ii) an offense against property; or

(iii) public indecency; or

(B) an offense in another jurisdiction that would be classified in a category described by Paragraph (A) if the offense had occurred in this state.

(c) A residential delivery company or an in-home service company that sends two or more employees together into a residence shall be deemed to have complied with the requirement in Section 145.002 as long as at least one of those employees has been checked as described in Section 145.002 and, while they are in the residence, that employee accompanies and directly supervises any employee who has not been checked, and the residential delivery company or in-home service company maintains a record of the identity of any such nonchecked employee for at least two years.

Added by Acts 2003, 78th Leg., ch. 228, Sec. 1, eff. Sept. 1, 2003.

Amended by:

Acts 2009, 81st Leg., R.S., Ch. 751 (S.B. 627), Sec. 4, eff. September 1, 2009.

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.