Bill Commons

TN HB 672

died on adjournment

Industrial Development - As enacted, redefines "remediation site" to include a 501(c)(3) nonprofit entity whose main purpose is to promote industrial development and new nuclear development upon dissolution of the existing nonprofit entity. - Amends TCA Title 7, Chapter 53, Part 3.

Tennessee · 114S1 · lower

Follow this bill’s action updates (Atom)

Subscribe in a feed reader. The feed covers recorded actions from the last 30 days; Bill Commons may record an action after it happened at the legislature.

Quick answers

Did TN HB 672 pass?

No. TN HB 672 died when the 114S1 session adjourned without final action on it. Bills that die this way are sometimes reintroduced in a later session. Latest recorded action (2025-05-13): Comp. became Pub. Ch. 379

What is TN HB 672 about?

TN HB 672 is a bill in the 114S1 titled “Industrial Development - As enacted, redefines "remediation site" to include a 501(c)(3) nonprofit entity whose main purpose is to promote industrial development and new nuclear development upon dissolution of the existing nonprofit entity. - Amends TCA Title 7, Chapter 53, Part 3.”.

Who sponsors TN HB 672?

Scarbrough is the primary sponsor of TN HB 672.

Introduced
2025-02-05
Latest action
2025-05-13 — Comp. became Pub. Ch. 379
Bill type
bill
Last updated
—

Subjects

Sponsors

  • Scarbroughprimary

Committees

Not provided by source.

Action timeline

Newest first

  1. 2025-05-13

    Comp. became Pub. Ch. 379

  2. 2025-04-16

    Comp. SB subst.

  3. 2025-04-14

    Objected to on Consent Calendar.

  4. 2025-04-14

    H. Placed on Regular Calendar 4/16/2025

  5. 2025-04-10

    H. Placed on Consent Calendar for 4/14/2025

  6. 2025-04-09

    Placed on cal. Calendar & Rules Committee for 4/10/2025

  7. 2025-04-08

    Rec. for pass; ref to Calendar & Rules Committee

    committee-passage-favorable

  8. 2025-04-02

    Action def. in State & Local Government Committee to 4/9/2025

  9. 2025-04-02

    Placed on cal. State & Local Government Committee for 4/9/2025

  10. 2025-03-26

    Action def. in State & Local Government Committee to 4/2/2025

  11. 2025-03-26

    Placed on cal. State & Local Government Committee for 4/2/2025

  12. 2025-03-19

    Action def. in State & Local Government Committee to 3/26/2025

  13. 2025-03-19

    Placed on cal. State & Local Government Committee for 3/26/2025

  14. 2025-03-12

    Rec. for pass by s/c ref. to State & Local Government Committee

    committee-passage-favorable

  15. 2025-03-12

    Placed on cal. State & Local Government Committee for 3/19/2025

  16. 2025-03-05

    Placed on s/c cal Cities & Counties Subcommittee for 3/12/2025

  17. 2025-02-06

    P2C, ref. to State & Local Government Committee

    referral-committee

  18. 2025-02-06

    Assigned to s/c Cities & Counties Subcommittee

    referral-committee

  19. 2025-02-05

    Intro., P1C.

    introduction

  20. 2025-02-03

    Filed for introduction

    filing

Versions

Documents

Votes

  • HOUSE CITIES & COUNTIES SUBCOMMITTEE: Rec. for pass by s/c ref. to State & Local Government Committee 3/12/2025 Passed (3)

    2025-03-12 · pass · 7-0

  • HOUSE STATE & LOCAL GOVERNMENT COMMITTEE: Rec. for pass; ref to Calendar & Rules Committee 4/8/2025 Passed (2)

    2025-04-08 · pass · 19-0

    Member-level votes (2)
    • Powell: not voting
    • Salinas: not voting
  • HOUSE CALENDAR & RULES COMMITTEE: H. Placed on Consent Calendar for 4/14/2025 4/10/2025 (1)

    2025-04-14 · fail · 0-0

Related bills

Official source

Attribution

Data from openstates_api_sync, retrieved 2026-10-29T07:27:12.101716Z

Inspect retained evidence for changes recorded after evidence tracking began:

Session-wide evidence can include changes to other bills:

Use this data

Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=TN&identifier=HB 672. See the API docs or the MCP server for AI assistants.

Known limitations

  • Sponsor party and chamber affiliation are not yet captured by this API.
  • Committee referrals are not yet captured.
  • Some documents have no extracted text yet, so version comparison may be limited.

See the methodology page for data sources and limitations.