• Continuous MVR overview
  • Continuous MVR driver license monitoring
  • Continuous MVR prerequisites
• Enrolling and un-enrolling drivers in Continuous MVR
  • Using the Continuous API
  • Using the Checkr Dashboard
  • Using a CSV upload
    • CSV upload for both Continuous MVR and Continuous Criminal
• Continuous and Adverse Action
• Continuous MVR rules
• Delayed rejections and error handling
• Billing
• Driver License updates: Verifying PII
  • Rejection notifications
• Re-enrolling drivers

Continuous MVR overview

From the moment a new driver completes their screening, your knowledge about their background starts to fade. Continuous MVR (C-MVR) helps fill in that gap so you can find incidents as they happen.

Continuous MVR mitigates risk by continually monitoring your workers’ driver’s licenses for new violations and license status changes. When Continuous MVR detects a new incident, it automatically runs a full MVR for the driver in question and applies your adjudication criteria. This is why Continuous MVR is the newest standard of driving safety and finds incidents 4+ months sooner than even an MVR rerun program.

Please note: Continuous MVR will surface records from the time of driver enrollment forward. Continuous MVR will not surface records prior to the driver’s enrollment.

Continuous MVR driver license monitoring

Once a driver is enrolled in Continuous MVR, their PII will be used for routine monitoring of any driving-related incidents. Continuous MVR checks for new reported records at least once a month (source databases may be updated according to different timelines). Checkr uses two data sources to monitor licensing information:

• State-sponsored: State-sponsored notification programs offer a monitoring service that provides driver related information based on that state's permissible purpose requirements.
• Non-state sponsored: In states that do not have a state-sponsored notification program Checkr monitors criminal and civil traffic court records or other pointer sources.

If any change in licensing history is detected, Continuous will generate an MVR report.

Not all states are the same and coverage can vary by state. States may include two different types of coverage:

• Violation monitoring: Continuous MVR may find violations such as DUIs, speeding, failure to obey a traffic signal, failure to appear for court, failure to pay a fine, driving with a suspended license, and more. Some states also provide data on at-fault accidents.
• Status monitoring: Continuous MVR looks for suspended or revoked licenses. In many instances, you’ll see the reason for the suspension/revocation as well. Note: A license expiration may not trigger Continuous MVR to run an MVR. This depends on the state. In states without this capability you would only see a license expiration if Continuous MVR notices a different violation or status change and runs an MVR as a result.

Continuous MVR prerequisites

You must have run a completed MVR on a driver before enrolling them in Continuous MVR. Checkr will use the licensing information obtained from this initial MVR report to enroll the driver in Continuous MVR. Invalid licenses are not eligible for continuous monitoring. Licenses that are or later become invalid for any reason will be rejected, and your driver will be automatically un-enrolled from Continuous MVR.

Rejections may occur at any time for reasons including:

• Mismatch of PII (For example: The date of birth (DOB) provided by your candidate for their initial background check does not match the DOB on their driver license.)
• Driver License no longer exists (For example: Your driver recently moved to a new state and obtained a new driver license.)

To minimize outdated PII and reduce the number of rejections, we recommend you enroll drivers in Continuous MVR as soon as possible after their most recent MVR report is completed.

See Delayed rejections and error handling below for more information on potential rejections and notifications post-enrollment.

Enrolling and un-enrolling drivers in Continuous MVR

Continuous MVR enrollments and un-enrollments follow the patterns set by Continuous Criminal.

Continuous MVR provides three methods to enroll and un-enroll drivers:

• Checkr API
• Checkr Dashboard
• CSV upload

When possible, we recommend that customers manage their Continuous enrollments using the Checkr API. The API provides full control over Continuous workflows and enables seamless onboarding and offboarding. Once configured, use the Continuous API (or an uploaded CSV) to bulk enroll and un-enroll candidates, and to retrieve the list of enrolled candidates. Use the Checkr Dashboard to enroll or un-enroll individual candidates, if you like.

Drivers may be enrolled in or un-enrolled from Continuous MVR at any time.

Using the Continuous API

To enroll and un-enroll drivers through the API, use the Continuous Checks resource in the Checkr API documentation, with type: `mvr`. For more information, including authorizations, path parameters, and responses, see the Cancel an existing Continuous in the Checkr API documentation.

Using the Checkr Dashboard

To enroll drivers through the Checkr dashboard, select a driver from the Candidates page in the Checkr Dashboard. Then, select the toggle for Continuous MVR, certify that you have obtained evergreen consent, and click Enable.

To un-enroll drivers, return to the candidates page in the Dashboard and deselect the Continuous MVR toggle. 

For more information, see Enroll a Candidate in Checkr Continuous in the Dashboard User Guides.

Using a CSV upload

To enroll or un-enroll drivers, submit a formatted CSV document to your Checkr Customer Success Manager. You may submit multiple enrollment CSVs per month. Checkr suggests that you submit only one un-enrollment CSV per month, as that CSV must be uploaded prior to month’s end to prevent those drivers’ Continuous enrollments from being carried into the next month.

Your Checkr CSM will upload submitted CSVs for you. CSV enrollments and un-enrollments occur once a month. Un-enrollments are performed at the end of the month and enrollments are performed at the beginning of the following month.

Submitted enrollment and un-enrollment CSVs should include changes to your current enrollments. Do not submit your account’s entire pool of enrolled (or un-enrolled) drivers with each CSV.

When creating the CSV, please date and specify the Continuous type in the filename. For example: AccountName_CMVR_July2021.csv.

Both enrollment and un-enrollment CSVs must adhere to the following format:

• Cell A1 (the first row and column of your CSV) must say candidate_id
• Every cell in the first column below this cell must include a 24-digit candidate ID
  • Please note: This must be the candidate ID. Not a custom ID or report ID.

CSV upload for both Continuous MVR and Continuous Check (Criminal)

If you use Continuous Check (Criminal) as well as Continuous MVR, please tell your CSM when you send your CSVs whether that list is for Continuous Check (Criminal), Continuous MVR, or both. The filename pattern defined above (AccountName_CMVR_July2021.csv) will help serve this purpose.

Continuous and Adverse Action

When Continuous MVR finds an incident and runs an MVR, based on that MVR you may decide to process an Adverse Action against that worker and remove them from your workforce. If you use Checkr to process an Adverse Action against any driver based on any Continuous Checkr background check report (including an MVR report triggered by Continuous MVR), Continuous will automatically un-enroll the driver from all Continuous services for your account. If that worker is also enrolled in Continuous Check (Criminal), they will be automatically un-enrolled from Continuous Check (Criminal) as well.

For example: If you initiate an Adverse Action against a driver based on a report generated from Continuous MVR, Checkr will automatically un-enroll that driver from both Continuous MVR and from Continuous Criminal (if the driver is enrolled in both features). If you initiate an Adverse Action against a driver based on a report generated from Continuous Check (Criminal) enrollment, they will also be un-enrolled from Continuous MVR.

Note: If you have a custom Adverse Action process within your company, and do not use Checkr’s automated Adverse Action functionality, you must un-enroll any applicable drivers to maintain compliance with FCRA obligations.

Continuous MVR rules

Continuous MVR allows you to define post-hire MVR rules by which your Continuous MVR reports will be adjudicated.

To configure your (post-hire) Continuous MVR rules, you may either:

• Use a copy of your existing MVR rules. (Default)
• Create custom rules for your Continuous MVR. (Contact your Checkr Account Manager to create custom rules for your account.)

For more information on MVR Rules, see Creating Custom MVR Filters in the Checkr Help Center.

Delayed rejections and error handling

When a driver is enrolled in Continuous MVR, the driver's license information is obtained from a previously completed MVR report (see Continuous MVR prerequisites above). Invalid or stale PII may lead to enrollment rejections by the state. Continuous MVR errors can occur immediately after enrollment or up to 30 days after enrollment.

Checkr will surface rejected drivers once a month on the Checkr dashboard (regardless of enrollment method) to facilitate subscription management.

For more information, see Continuous Services in the Checkr Dashboard User Guides.

Billing

Once Checkr receives your Continuous MVR order, Continuous MVR will be added automatically to your monthly Checkr invoice. Your invoice might include several lines for Continuous MVR, including any pass through fees.

Checkr collects a monthly service fee for each enrolled driver, beginning the first month of their enrollment. Some states also collect a service fee upon driver enrollment. Some of these states also collect a service fee annually on the anniversary of the driver’s enrollment.

Your account will be billed for each MVR triggered by Continuous MVR. Some states collect an additional fee for each MVR triggered by Continuous MVR.

Most states take from 1-31 days to process a Continuous MVR enrollment. In some cases, an enrolled driver may be rejected by the state for driver license, PII, or other data mismatch. (See Delayed rejections and error handling for more information.) If a driver is rejected, that driver will be un-enrolled from Continuous MVR and you will no longer pay for their enrollment.

To help reduce the number of rejected drivers, Checkr recommends you enroll drivers in Continuous MVR immediately after a standard MVR report completes for the driver. This will help to ensure that the information passed to the DMV for that driver’s enrollment is up to date and accurate.

Driver License updates: Verifying PII

Continuous MVR offers customers the ability to edit a driver’s PII in the event the PII becomes invalid. Examples of this may include when a DMV rejects a driver’s license because of PII mismatch or a driver’s license no longer exists (such as if a driver moves out of state and surrenders their license).

Rejection notifications

When a driver is rejected by the DMV, they will be automatically unsubscribed from Continuous MVR. Checkr will notify the customer of the rejection and attempt to obtain updated information from the driver through the standard Checkr exception process. When the driver has submitted the requested information, Checkr will issue a webhook notifying customers that the PII was updated. The updated driver PII will also be applied to all future reports for this driver.

Checkr will redirect all driver inquiries around why updated PII is being requested to the customer. Customers should prepare a response to inform drivers why this information is being requested, and a process by which they communicate to drivers who do not resolve these exceptions upon request.

Re-enrolling drivers

When driver PII has been updated, customers must re-enroll the driver into Continuous MVR; Checkr will not automatically enroll drivers on behalf of our customers.