Utah Admin. Code R907-63-2 - Procedure to Collect for Damage to Department Property

(1) Upon notification of damage to department property, the department will repair or replace the damaged property.
(2)
(a) After the department repairs or replaces the damaged property described under Subsection (1), the department will invoice the owner of the vehicle or object causing the damage for the total costs of repairing or replacing the damaged property.
(b) If the person directly responsible for causing the damage does not own the vehicle or object causing the damage, the department will invoice both the owner and the person responsible for causing the damage for the total cost of repairing or replacing the damaged property.
(c) The owner and operator are jointly and severally liable under this Subsection (2) for any damage caused to department property by the operation or movement of the vehicle or object.
(3) If a vehicle damages department property, the owner of the vehicle or object causing the damage, or the person directly responsible for causing the damage must reimburse the department for the total cost of repairing the damage.
(4) If the department does not receive the total amount invoiced under Subsection (2) within 120 days of the date of the invoice, the department may pursue reimbursement by one of the following means:
(a) collection of a delinquent account as provided in Title 63A, Chapter 3, Part 3, Accounts Receivable Collection; or
(b) collection through a collection agency.
(5) In cases where the full payment of an invoice will cause undue financial pressure, the owner of the vehicle or person responsible for the damage may arrange to make installment payments on the debt.

Notes

Utah Admin. Code R907-63-2
Amended by Utah State Bulletin Number 2016-18, effective 8/23/2016 Amended by Utah State Bulletin Number 2022-04, effective 2/7/2022 Amended by Utah State Bulletin Number 2025-03, effective 1/23/2025

State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.


No prior version found.