Bill Commons

TN HB 208

died on adjournment

Naming and Designating - As enacted, designates the National Guard Armory in Cheatham County as the "First Sergeant Charles Anderson Douglas National Guard Armory." -

Tennessee · 114S1 · lower

Quick answers

Did TN HB 208 pass?

No. TN HB 208 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-15): Comp. became Pub. Ch. 421

What is TN HB 208 about?

TN HB 208 is a bill in the 114S1 titled “Naming and Designating - As enacted, designates the National Guard Armory in Cheatham County as the "First Sergeant Charles Anderson Douglas National Guard Armory." -”.

Who sponsors TN HB 208?

Littleton is the primary sponsor of TN HB 208.

Introduced
2025-01-27
Latest action
2025-05-15 — Comp. became Pub. Ch. 421
Bill type
bill
Last updated
—

Subjects

Sponsors

  • Littletonprimary

Committees

Not provided by source.

Action timeline

  1. 2025-01-16

    Filed for introduction

    filing

  2. 2025-01-27

    Intro., P1C.

    introduction

  3. 2025-02-03

    P2C, ref. to Naming & Designating Committee - State & Local Government Committee

    referral-committee

  4. 2025-02-05

    Placed on cal. Naming & Designating Committee for 2/10/2025

  5. 2025-02-10

    Rec. for pass; ref to State & Local Government Committee

    committee-passage-favorable

  6. 2025-02-12

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

  7. 2025-02-19

    Placed on s/c cal Finance, Ways, and Means Subcommittee for 2/26/2025

  8. 2025-02-19

    Assigned to s/c Finance, Ways, and Means Subcommittee

    referral-committee

  9. 2025-02-19

    Rec. for pass; ref to Finance, Ways, and Means Committee

    committee-passage-favorable

  10. 2025-02-26

    Placed behind the budget

  11. 2025-03-19

    Placed on s/c cal Finance, Ways, and Means Subcommittee for 3/26/2025

  12. 2025-03-26

    Placed behind the budget

  13. 2025-04-09

    Placed on s/c cal Finance, Ways, and Means Subcommittee for 4/14/2025

  14. 2025-04-16

    Placed on s/c cal Finance, Ways, and Means Subcommittee for 4/17/2025

  15. 2025-04-17

    H. Placed on Regular Calendar for 4/21/2025

  16. 2025-04-17

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

  17. 2025-04-17

    Sponsor(s) Added.

    sponsorship

  18. 2025-04-17

    Rec. for pass; ref to Calendar & Rules Committee

    committee-passage-favorable

  19. 2025-04-17

    Rec. for pass by s/c ref. to Finance, Ways, and Means Committee

    committee-passage-favorable

  20. 2025-04-21

    Comp. SB subst.

  21. 2025-04-21

    Sponsor(s) Added.

    sponsorship

  22. 2025-05-15

    Comp. became Pub. Ch. 421

Versions

Documents

Votes

  • HOUSE NAMING & DESIGNATING COMMITTEE: Rec. for pass; ref to State & Local Government Committee 2/10/2025 Passed (5)

    2025-02-10 · pass · 9-0

  • HOUSE STATE & LOCAL GOVERNMENT COMMITTEE: Rec. for pass; ref to Finance, Ways, and Means Committee 2/19/2025 Passed (4)

    2025-02-19 · pass · 21-0

  • HOUSE FINANCE, WAYS, AND MEANS COMMITTEE: Rec. for pass; ref to Calendar & Rules Committee 4/17/2025 Passed (2)

    2025-04-17 · pass · 27-0

  • HOUSE FINANCE, WAYS, AND MEANS SUBCOMMITTEE: Rec. for pass by s/c ref. to Finance, Ways, and Means Committee 4/17/2025 Passed (3)

    2025-04-17 · pass · 11-0

  • HOUSE CALENDAR & RULES COMMITTEE: H. Placed on Regular Calendar for 4/21/2025 4/17/2025 (1)

    2025-04-21 · fail · 0-0

Related bills

Official source

Attribution

Data from openstates_bulk_csv, retrieved 2026-07-24T05:32:51.339172Z

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 208. 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.