Bill Commons

UT HB 355

died on adjournment

Nuisance Modifications

Utah · 2026 Regular Session · lower

Quick answers

Did UT HB 355 pass?

No. UT HB 355 died when the 2026 Regular Session adjourned without final action on it. Bills that die this way are sometimes reintroduced in a later session. Latest recorded action (2026-03-07): House/ filed

What is UT HB 355 about?

UT HB 355 is a bill in the 2026 Regular Session titled “Nuisance Modifications”.

Who sponsors UT HB 355?

Clancy, Tyler is the primary sponsor of UT HB 355, joined by 1 cosponsor.

Introduced
Latest action
2026-03-07 — House/ filed
Bill type
bill
Last updated

Subjects

Sponsors

  • Clancy, Tylerprimary
  • Brammer, Bradycosponsor

Committees

Not provided by source.

Action timeline

  1. 2026-01-23

    Bill Numbered but not Distributed

  2. 2026-01-23

    Numbered Bill Publicly Distributed

  3. 2026-01-23

    LFA/ bill assigned to staff for fiscal analysis for HB0355

  4. 2026-01-23

    LFA/ bill sent to agencies for fiscal input for HB0355

  5. 2026-01-23

    House/ received bill from Legislative Research

    receipt

  6. 2026-01-23

    House/ 1st reading (Introduced)

  7. 2026-01-28

    LFA/ fiscal note sent to sponsor for HB0355

  8. 2026-01-28

    LFA/ fiscal note publicly available for HB0355

  9. 2026-01-28

    House/ received fiscal note from Fiscal Analyst

    receipt

  10. 2026-03-07

    House/ strike enacting clause

  11. 2026-03-07

    House/ filed

    filing

Versions

Documents

Votes

Not provided by source.

Related bills

No related bills recorded for this bill.

Official source

Attribution

Data from openstates_bulk_csv, retrieved 2026-07-24T05:35:26.931453Z

Inspect retained evidence for changes recorded after evidence tracking began:

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=UT&identifier=HB 355. 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.

See the methodology page for data sources and limitations.