Status: Enacted — Signed by Tennessee Governor Bill Lee on April 23, 2026. Effective date: April 23, 2026.

Bill Number: Tennessee SB 837 (companion HB sponsored by Rep. Michelle Reneau, R-Hixson; Senate version sponsored by Sen. Mark Pody, R-Lebanon) — “Statutes and Codification” amendments to TCA Title 1

Jurisdiction: Tennessee

Category: AI Governance / Statutory Construction

Industries: All Tennessee-regulated industries; AI vendors operating in Tennessee; legal counsel evaluating AI liability exposure

Enacted Date: April 23, 2026

Effective Date: April 23, 2026

Summary: Tennessee SB 837 amends Title 1 of the Tennessee Code Annotated — the chapter governing statutory construction and definitions used throughout Tennessee law — to explicitly exclude artificial intelligence, computer algorithms, software programs, computer hardware, and any type of machine from the statutory definitions of “person,” “natural person,” “human being,” and “life.” The statute is preemptive and prospective: it does not respond to any pending litigation, but it forecloses future legal theories that might attempt to argue an AI system has standing, rights, or personhood under Tennessee law.

While the bill's framing is futuristic — Senator Pody publicly described it as a contingency against the prospect of advanced humanoid robotics — the practical near-term effect is to definitively answer a question that has surfaced in academic AI law literature: can an AI system be a “person” for purposes of statutory rights, liability, or capacity? Under Tennessee law, the answer is now an unambiguous no, foreclosing both rights-claiming theories and rights-evading theories (e.g., an AI operator arguing the AI itself is the responsible “person” for a tortious act).

Key Provisions:

Definitional Exclusion: “Person,” “natural person,” “human being,” and “life,” as used throughout the Tennessee Code Annotated, expressly do not include artificial intelligence, a computer algorithm, a software program, computer hardware, or any type of machine.
Statutory Construction Anchor: The definitional change is placed in Title 1 (Statutes and Codification), making it the default interpretive rule across every other title of the Tennessee Code unless a more specific definition is provided in another chapter.
Forward-Looking Scope: The statute is intentionally drafted to address future AI development scenarios, including conscious or quasi-conscious AI systems and humanoid robotics.
No Liability Shield Created: The exclusion does not relieve AI operators, developers, or deployers from liability for harms caused by AI systems — liability continues to attach to the human and corporate persons behind the AI.

Affected Entities: All AI developers, deployers, and operators with operations, customers, or potential liability exposure in Tennessee. Legal counsel advising on AI deployment, AI procurement, and AI-related litigation in Tennessee. The statute also has cross-jurisdictional persuasive value as the first explicit state-level AI personhood exclusion of its kind.

Legal and Operational Context: SB 837 sits in an emerging genre of state-level “AI clarification” statutes that address foundational questions other AI legislation (e.g., consumer-protection disclosure laws, biometric privacy laws, high-risk system regulations) does not resolve. The Tennessee approach is narrow and definitional rather than substantive: it does not regulate AI use, mandate disclosures, or restrict deployment. It simply forecloses one specific theoretical doctrine.

For physical security and AI video analytics operators, the practical effect is that liability for AI-driven decisions — including missed detections, false detections, downstream response actions, and any harms arising from AI-system operation — will continue to attach to the human and corporate entities responsible for the system, with no statutory ambiguity about whether the AI itself might be a party to the analysis. This matters most in litigation hypothesis-testing and in vendor contract risk allocation.

IntelliSee Relevance: Adjacent. SB 837 does not directly regulate IntelliSee's deployment, data processing, or operations in Tennessee. The law does, however, reinforce a baseline IntelliSee already operationalizes: every detection, every alert, and every downstream response is attributable to identifiable human decision-makers (the operator, the security director, the responding personnel) and to IntelliSee Corporation as the platform provider. The statute eliminates any future legal argument that an AI system itself bears responsibility for outcomes, which aligns with IntelliSee's human-in-the-loop deployment framework for physical security.

Tennessee customers and prospects evaluating AI security platforms should note that the statute creates no new compliance burden on AI vendors operating in Tennessee — it is a definitional clarification, not a regulatory regime. Customers focused on operational AI governance should look instead to the Texas Responsible AI Governance Act (TRIAGA), the Colorado AI Act, and the EU AI Act, all of which impose substantive obligations rather than definitional clarifications.

Tennessee AI Personhood Clarification Act (SB 837, 2026)

Related Legislation & Resources

Turn Legislative Mandates Into a Working Safety Program