Legislative intelligence / 90R
SESSION 2027View project ↗

Occupations Code § 1702.282: CRIMINAL HISTORY CHECK

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 Occupations Code Chapter 1702, 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. 1702.282. CRIMINAL HISTORY CHECK. (a) The department shall conduct a criminal history check, including a check of any criminal history record information maintained by the Federal Bureau of Investigation, in the manner provided by Subchapter F, Chapter 411, Government Code, on each applicant for a license or security officer commission issued under this chapter. As part of its criminal history check, the department may request that the applicant provide certified copies of relevant court documents or other records. The failure to provide the requested records within a reasonable time as determined by the department may result in the application being considered incomplete. An applicant is not eligible for a license or security officer commission issued under this chapter if the check reveals that the applicant has committed an act that constitutes grounds for the denial of the license or commission. Except as provided by Subsection (d), each applicant shall submit at the time of application, including an application for the renewal of a license or security officer commission issued under this chapter, fingerprints in the manner prescribed by the department accompanied by the fee set by the commission.

(b) Before beginning employment as a commissioned security officer, the applicant must be approved by the department based on the results of the check under Subsection (a). To continue employment in a capacity regulated under this chapter other than as a commissioned security officer, the applicant must be approved by the department based on the results of the check under Subsection (a) not later than the 120th day after the date the applicant begins employment in that capacity.

(c) A license or security officer commission issued by the department is conditional on the department's review of criminal history record information.

(d) An applicant who is a peace officer is not required to submit fingerprints with the applicant's application. On request, the law enforcement agency or other entity that employs the peace officer or the entity that maintains the peace officer's fingerprints shall provide the fingerprints for the peace officer to the department. The applicant shall provide sufficient information to the department to enable the department to obtain the fingerprints under this subsection.

(e) On receipt of notice that a check of the applicant's criminal record has uncovered an unresolved and potentially disqualifying arrest that occurred before the 10th anniversary of the date the application is filed, the applicant must provide a letter of reference from the county sheriff, prosecuting attorney, or judge of the county in which the applicant was arrested stating that a record of a disposition related to the arrest does not exist, and to the best of the county sheriff's, prosecuting attorney's, or judge's knowledge the applicant is free of any disqualifying convictions. If the applicant fails to provide either the letter of reference

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.