Wisconsin Legislation

Year of last legislative change: Awaiting data
Year of last revision to administrative code: 1993
Most challenging aspects associated with introducing and passing interlock legislation:
The Department of Transportation is unable to propose legislation changes and there is currently a lack of a champion.
Changes for program improvement being pursued:
Administrative code requires updating
Who is eligible for an interlock in your state according to legislation (Data provided by CIIM):
Repeat impaired drivers, High BAC (.10-.18) impaired drivers
Can impaired drivers 'wait out' their interlock requirement:
Is an interlock required on test refusal:

Program Authority

Type of program: Judicial
Agency/agencies with authority over the interlock program:
State Patrol
Agency/agencies with authority over participant monitoring:
Department of Motor Vehicles Courts, Probation, Department of Health
Agency/agencies with authority over sanctioning interlock program participants:
Courts, Probation
Agency/agencies with authority to approve devices:
Courts, Probation
Training available for judges, law enforcement, and lawyers:
Law enforcement are trained to use the evidential breath testing devices, which is has an interlock component. Using the TIRF grant the state plans to create education materials and conduct educational outreach to stakeholders.

Program Features

Hardship license available to first offenders: Yes
Hardship license available to repeat offenders: Yes
Hardship license (First offenders, Repeat offenders, All): All
Lookback period: 10 years
Source of funding: Awaiting data
Indigent funding is available to participants: Yes
Qualification requirements for indigent funding: Court decision
Frequency of interlock device service: 60 days


Participation Rate: Awaiting data
Number of interlock program participants in 2019: >2,000
Indicator used to determine the number of participants in the interlock program (e.g., certificate of device installation, certificate of device removal):
Track court orders and issuance of sanction driving privilege
Indicator(s) used in state as the best measure(s) of the eligible population of offenders for the interlock program to determine the program participation rate:
Number of court/probation orders for interlock
Penalties for non-compliance: Awaiting data

Program Length

Length of Hard Suspension

1st offenders: 6 months
2nd offenders: 6-18 months
3rd offenders: 24-36 months
4th and subsequent offenders: Awaiting data

Interlock Program Length

1st offenders: 12 months
2nd offenders: 12 months
3rd offenders: 24-36 months
4th and subsequent offenders: Awaiting data


Program length is extended for non-compliance: No
Length of extension for non-compliance: Awaiting data
Program length is reduced for compliance: No
Length of reduction for compliance: Awaiting data
Frequency of sanctions imposed for non-compliance: Rarely
Program exit requirements: Awaiting data


Treatment is required for the interlock program: Yes
Components applied to treatment: Yes

Data Collection & Management

Agency responsible for collecting data: DMV
Overview of Data Management: DMV collects data regarding installations, removals, and exemptions (i.e., medical or employer). The offender status (i.e., first, second, third, etc. offense) is captured and contained within the driving record abstract. There is currently an ongoing development of a data warehouse to make data more usable. The data system would specifically be for the interlock program and housed within the DMV. The DMV has partnered with UW Traffic Safety for the development of the data system. The users of this data system will be DMV staff, treatment providers, and law enforcement
Barriers to data collection: Violation reports are not usable
Vendors in State

Vendor Oversight

Number of Vendors in State: 6
Agency responsible for vendor oversight: Department of Transportation
Approval process for new vendors: Awaiting data
Vendor recertification: Awaiting data
Interlock technology features (Data provided by CIIM): None
Radius requirement for service centers: Awaiting data
Radius requirement: Awaiting data