Legislative intelligence / 90R
SESSION 2027View project ↗

Election Code § 63.001: REGULAR PROCEDURE FOR ACCEPTING VOTER

1 bill in the 90th Legislature would change this section

Part of Election Code Chapter 63, 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. 63.001. REGULAR PROCEDURE FOR ACCEPTING VOTER. (a) Except as otherwise provided by this code, acceptance of voters shall be conducted as provided by this section and Section 63.0011.

(b) Except as provided by Subsection (h), on offering to vote, a voter must present to an election officer at the polling place:

(1) one form of photo identification listed in Section 63.0101(a); or

(2) one form of identification listed in Section 63.0101(b) accompanied by the declaration described by Subsection (i).

(c) On presentation of the documentation required under Subsection (b), an election officer shall determine whether the voter's name on the documentation is on the list of registered voters for the precinct. If in making a determination under this subsection the election officer determines under standards adopted by the secretary of state that the voter's name on the documentation is substantially similar to but does not match exactly with the name on the list, the voter shall be accepted for voting under Subsection (d) if the voter submits an affidavit stating that the voter is the person on the list of registered voters.

(c-1) An election officer may not refuse to accept documentation presented to meet the requirements of Subsection (b) solely because the address on the documentation does not match the address on the list of registered voters.

(d) If, as determined under Subsection (c), the voter's name is on the precinct list of registered voters and the voter's identity can be verified from the documentation presented under Subsection (b), the voter shall be accepted for voting. An election officer may not question the reasonableness of an impediment sworn to by a voter in a declaration described by Subsection (i).

(e) On accepting a voter, an election officer shall indicate beside the voter's name on the list of registered voters that the voter is accepted for voting. If the voter executes a declaration of reasonable impediment to meet the requirement for identification under Subsection (b), the election officer must affix the voter's voter registration number to the declaration either in numeric or bar code form.

(f) After determining whether to accept a voter, an election officer shall return the voter's documentation to the voter.

(g) If the requirements for identification prescribed by Subsection (b) are not met, the voter may be accepted for provisional voting only under Section 63.011. For a voter who is not accepted for voting under this section, an election officer shall:

(1) inform the voter of the voter's right to cast a provisional ballot under Section 63.011; and

(2) provide the voter with written information, in a form prescribed by the secretary of state, that:

(A) lists the requirements for identification;

(B) states the procedure for presenting identification under Section 65.0541;

(C) includes a map showing the location where identification must be presented; and

(D) includes notice that if all procedures are fol

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.