Legislative intelligence / 90R
SESSION 2027View project ↗

Business Organizations Code § 6.202: ACTION BY LESS THAN UNANIMOUS WRITTEN CONSENT

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 Business Organizations Code Chapter 6, 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. 6.202. ACTION BY LESS THAN UNANIMOUS WRITTEN CONSENT. (a) This section applies to any action required or authorized to be taken under this code or the governing documents of a filing entity at an annual or special meeting of the owners or members of the entity.

(b) Except as provided by this code, the certificate of formation of a filing entity may authorize the owners or members of the entity to take action without holding a meeting, providing prior notice, or taking a vote if owners or members of the entity having at least the minimum number of votes that would be necessary to take the action that is the subject of the consent at a meeting, in which each owner or member entitled to vote on the action is present and votes, sign a written consent or consents stating the action taken.

(c) A written consent or consents described by Subsection (b) must include:

(1) the date each owner or member signed the consent; and

(2) the date of signing of the latest dated consent satisfying the minimum number of owners or members necessary to approve the action that is the subject of the consent.

(c-1) The date described by Subsection (c)(2) must be not later than the 60th day after the date of the signing of the earliest dated consent of the owners or members signing the consent or consents. If a consent does not contain the date that an owner or member signed the consent, the date that the owner or member signed the consent is considered to be the date that the consent is received by the filing entity. A written consent or consents described by Subsection (b) that are not solicited by or on behalf of a filing entity or the filing entity's governing authority must be delivered to the entity as required by Section 6.203 to take effect.

(c-2) By a provision in the written consent or consents or by a written instruction to an agent of the filing entity from one or more persons granting the written consent or consents, a written consent or consents described by Subsection (b) may be made to take effect at a future time, which must be not later than the 60th day after the date the last of the minimum number of owners or members necessary to sign the consent or consents as required by Subsection (b) have signed the consent or consents. If the written consent or consents described by this subsection are to take effect at a future time, all of the written consent or consents take effect at that future effective time.

(c-3) If two or more of the written consents described by Subsection (c-2) have different future effective times, the latest future effective time of those consents applies to all of the consents. The written consent or consents are considered to have been given for purposes of this section at the applicable effective time so long as owners or members satisfying the minimum requirements in Subsection (b):

(1) are determined to be owners or members, as applicable, as of:

(A) that effective time; or

(B) if applicable, the record date establi

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.