UtahPolice must check driver records before impounding vehicles
Police must check a state database before impounding a vehicle from a driver without a credential, and must take quick fingerprints in some cases.
What it does
If a driver lacks a credential in hand, police must check a state law enforcement database before impounding the vehicle. Listed safety and practical exceptions apply.
Police must take a quick fingerprint from some lawfully stopped people without a driving credential when they cannot verify one and the person lacks usable identification. Exceptions apply.
Law enforcement agencies must provide portable fingerprint devices to officers working outside their facilities.
Argument forQuick fingerprints could help officers identify some stopped drivers who lack a credential and usable identification, while listed safety and equipment exceptions limit when officers must take them.
Argument againstA driver could lose access to a vehicle after a stop over a missing credential, even though police can skip impoundment in listed circumstances.
More detail
Before impounding a vehicle because its driver lacks a credential in hand, an officer must check a state law enforcement database. This applies when the driver lacks a driver license, driving privilege card, or learner permit in their possession, unless an officer can verify that a credential was issued. An officer need not impound the vehicle if the officer reasonably finds a listed exception, including a safety concern, a driver under 18, or another credentialed person available to drive or collect it. An officer may release the vehicle at the scene to its registered owner if that owner is not the person arrested and is immediately available. This provision takes effect May 6, 2026.
An officer must take a quick fingerprint from certain lawfully stopped people who lack a driving credential. This applies to a person lawfully stopped by police who lacks a driver license, driving privilege card, or learner permit. The fingerprint is checked against a fingerprint database, is not added to or stored in that database, and is taken in about 15 minutes or less. An officer need not take it if doing so raises a safety concern, prevents attention to other public safety needs, equipment or cell service is unavailable, or the person is under 18. This provision takes effect May 6, 2026.
Law enforcement agencies must provide portable fingerprint devices to officers working outside agency facilities. This duty applies to each law enforcement agency and its officers on duty outside the agency's facility. The device requirement begins on January 1, but the text shows both 2027 and 2028 as the year, so the start year is unclear.
Where do you stand?
Choose your position
Tell your reps
Take a position to see your representatives and ways to contact them.
Where it stands
- Introduced
- Passed House
- Passed Senate
- To Governor
- Became Law
Looking ahead
No hearings or votes scheduled.
History
- 2026
- Mar 26Governor Spencer Cox SignedBecame Law
- Mar 12House/ to GovernorTo Governor
- Mar 12House/ received enrolled bill from PrintingMinor
- Mar 11House/ enrolled bill to Printing
- Mar 11Enrolled Bill Returned to House or SenateMinor
- Mar 7Draft of Enrolled Bill Prepared
- Mar 7Bill Received from House for EnrollingMinor
- Mar 6House/ signed by Speaker/ sent for enrollingMajor
- Vote recorded House Conference Committee - Final Passage. Result: pass.Lower
- Vote recorded Senate Conference Committee - Final Passage. Result: pass.Upper
- Mar 6House/ received from SenateMinor
- Mar 6Senate/ to House
- Mar 6Senate/ signed by President/ returned to HouseMajor
- Mar 6Senate/ received from HouseMinor
- Mar 6House/ to Senate
- Mar 6House Conference Committee - Final Passage [Senate President]Major
- Mar 6House Motion to Adopt Joint Conference Comm Rpt [Conference Committee]
- Mar 6House/ received from SenateMinor
- Mar 6Senate/ to House
- Mar 6Senate Conference Committee - Final Passage [Conference Committee]Major
- Mar 6Senate Motion to Adopt Joint Conference Comm Rpt [Conference Committee]
- Mar 6Senate/ received from HouseMinor
- Mar 6Conference Committee Report [Conference Committee]
- Mar 6Bill amended by Conference Committee [Conference Committee]Major
- Mar 6Bill Substituted by Conference Committee [Conference Committee]Major
- Mar 6House/ to Senate
- Mar 6House Conference Committee Appointed [Conference Committee]Minor
- Mar 6House/ received from SenateMinor
- Mar 6Senate/ to House
- Mar 6Senate Conference Committee Appointed [Conference Committee]Minor
- Mar 6Senate/ refused to recede from Senate amendments
- Mar 6House/ to Senate
- Mar 6House/ refuse to concur with Senate amendment
- Mar 5House/ placed on Concurrence Calendar
- Vote recorded Senate/ passed 2nd & 3rd readings/ suspension. Result: pass.Upper
- Mar 5House/ received from SenateMinor
- Mar 5Senate/ to House with amendments
- Mar 5Senate/ passed 2nd & 3rd readings/ suspensionPassed Senate
- Mar 5Senate/ uncircled
- Mar 5Senate/ circled
- Mar 5Senate/ uncircled
- Mar 5Senate/ circled
- Mar 5Senate/ 2nd & 3rd readings/ suspensionMinor
- Mar 5Senate/ Rules to 2nd Reading Calendar
- Mar 5Senate/ 2nd Reading Calendar to Rules [Senate Rules Committee]Minor
- Mar 3LFA/ fiscal note publicly available for HB0136S05
- Mar 2LFA/ fiscal note sent to sponsor for HB0136S05
- Feb 27LFA/ bill sent to agencies for fiscal input for HB0136S05
- Feb 27LFA/ bill assigned to staff for fiscal analysis for HB0136S05
- Feb 26LFA/ fiscal note publicly available for HB0136S04
- Feb 26LFA/ fiscal note sent to sponsor for HB0136S04
- Feb 25Senate/ placed on 2nd Reading Calendar
- Feb 25Senate/ comm rpt/ substituted/ amended [Senate Transportation, Public Utilities, Energy, and Technology Committee]Major
- Feb 25Senate Comm - Favorable Recommendation [Senate Transportation, Public Utilities, Energy, and Technology Committee]Minor
- Feb 25Senate Comm - Amendment Recommendation [Senate Transportation, Public Utilities, Energy, and Technology Committee]Minor
- Feb 25Senate Comm - Substitute Recommendation [Senate Transportation, Public Utilities, Energy, and Technology Committee]Major
- Feb 24LFA/ bill sent to agencies for fiscal input for HB0136S04
- Feb 24LFA/ bill assigned to staff for fiscal analysis for HB0136S04
- Feb 23Senate/ to standing committee [Senate Transportation, Public Utilities, Energy, and Technology Committee]Minor
- Feb 13LFA/ fiscal note publicly available for HB0136S03
- Feb 12LFA/ fiscal note sent to sponsor for HB0136S03
- Feb 12LFA/ fiscal note publicly available for HB0136S02
- Feb 12LFA/ fiscal note sent to sponsor for HB0136S02
- Feb 10Senate/ 1st reading (Introduced)Minor
- Feb 9Senate/ received from HouseMinor
- Vote recorded House/ passed 3rd reading. Result: pass.Lower
- Vote recorded House/ substitute adoption failed. Result: fail.Lower
- Feb 9House/ to Senate
- Feb 9House/ passed 3rd readingPassed House
- Feb 9House/ substitute adoption failedMajor
- Feb 9LFA/ bill sent to agencies for fiscal input for HB0136S03
- Feb 9LFA/ bill assigned to staff for fiscal analysis for HB0136S03
- Feb 9House/ substituted
- Feb 9House/ uncircled
- Feb 9LFA/ bill sent to agencies for fiscal input for HB0136S02
- Feb 9LFA/ bill assigned to staff for fiscal analysis for HB0136S02
- Feb 5LFA/ fiscal note publicly available for HB0136S01
- Feb 5LFA/ fiscal note sent to sponsor for HB0136S01
- Feb 4House/ circled
- Feb 4House/ 3rd readingMinor
- Feb 3LFA/ bill sent to agencies for fiscal input for HB0136S01
- Feb 3LFA/ bill assigned to staff for fiscal analysis for HB0136S01
- Jan 29LFA/ fiscal note publicly available for HB0136
- Jan 28LFA/ fiscal note sent to sponsor for HB0136
- Jan 26House/ 2nd readingMinor
- Jan 26House/ comm rpt/ amended [House Transportation Committee]Major
- Jan 23House Comm - Favorable Recommendation [House Transportation Committee]Minor
- Jan 23House Comm - Amendment Recommendation [House Transportation Committee]Minor
- Jan 22House/ to standing committee [House Transportation Committee]Minor
- Jan 20House/ 1st reading (Introduced)Minor
- Jan 20House/ received fiscal note from Fiscal AnalystMinor
- Jan 18LFA/ fiscal note publicly available for HB0136
- Jan 18LFA/ fiscal note sent to sponsor for HB0136
- Jan 14House/ received bill from Legislative ResearchMinor
- Jan 5LFA/ bill sent to agencies for fiscal input for HB0136
- Jan 5LFA/ bill assigned to staff for fiscal analysis for HB0136
- Jan 5Numbered Bill Publicly Distributed
- Jan 5Bill Numbered but not DistributedIntroduced
Criminal JusticePublic Safety