How often does a motor carrier have to pull and review a driver's MVR?

For FMCSA-regulated carriers, at least once every 12 months. Under 49 CFR 391.25, each motor carrier must obtain each driver's motor vehicle record and review it to determine whether the driver still meets the qualification standards — at least annually. The carrier also keeps the MVR plus a dated review note identifying the reviewer in the driver-qualification file. Continuous MVR monitoring is widely treated as best practice on top of that annual minimum.

Is continuous MVR monitoring required by federal law?

No. The federal requirement for FMCSA-regulated carriers is the annual review under 49 CFR 391.25 — that's the floor. Continuous monitoring (getting alerted to violations between annual pulls) is a strong best practice rather than a federal mandate. It closes the blind spot between annual reviews, but it's something safety-minded fleets adopt voluntarily, not a rule the FMCSRs impose.

Do non-CDL company drivers need MVR monitoring?

Federal Part 391 driver-qualification rules — including the annual 391.25 review — apply to motor carriers operating commercial motor vehicles in interstate commerce. Many corporate 'gray fleet' drivers in ordinary lighter vehicles fall outside Part 391, so the federal annual-review mandate doesn't reach them. But screening and monitoring their records is best practice: it's one of the highest-ROI things a safety program does, and OSHA's General Duty Clause expects employers to address recognized hazards.

What should I do when an MVR flags a driver?

Don't just file it. A flag — a new violation, a suspension, or an at-fault crash — is the trigger to act. First confirm the driver still meets the qualification standards (for FMCSA carriers, the 391.15 disqualification rules). Then assign targeted training or remediation so the behavior is corrected before the next incident. Routing a flagged driver into a defensive driving course is the layer that turns monitoring from a paperwork exercise into actual risk reduction.

What's the difference between MVR screening and MVR monitoring?

Screening is a point-in-time check — usually at hire and again at each annual review. Monitoring is ongoing visibility, so a violation that lands between scheduled pulls surfaces in days rather than waiting up to a year. FMCSA-regulated carriers must at minimum screen annually under 391.25; continuous monitoring is the best-practice upgrade that removes the gap between pulls.

MVR Monitoring for Fleets: A Practical Guide

MVR monitoring for fleet drivers: the annual 49 CFR 391.25 review, why continuous monitoring is best practice, a cadence policy, and what to do on a flag.

A motor vehicle record (MVR) is the most direct window you have into how your drivers actually drive. It's the state-maintained history of a driver's license status, violations, suspensions, and crashes — and for a fleet, it's both a compliance obligation and a risk-management tool. This guide covers what an MVR is, the federal review requirement that applies to regulated carriers, why continuous monitoring is the smart best practice on top of that floor, a cadence you can actually run, and — most importantly — what to do when a record flags a driver.

What an MVR is (and what it tells you)

An MVR is pulled from the state that issued the driver's license. It typically shows license class and status, moving violations, at-fault crashes, license suspensions or revocations, and disqualifying events. For a safety lead, the MVR is the single best leading indicator you have: a pattern of violations almost always precedes a serious crash. Catch it early and you can intervene; miss it and you find out at claim time.

The federal requirement: the annual MVR review (49 CFR 391.25)

If you operate commercial motor vehicles in interstate commerce, the FMCSA driver-qualification rules in 49 CFR Part 391 apply — and that includes a specific MVR rule.

Under 49 CFR 391.25, each motor carrier must, at least once every 12 months:

Obtain each driver's motor vehicle record, and
Review it to determine whether the driver still meets the qualification standards (and isn't disqualified under §391.15).

The carrier then keeps the MVR plus a dated review note — identifying the person who did the review — in the driver-qualification file. That dated note is what proves the review actually happened; an MVR sitting in a folder with no review record isn't compliance.

A few boundaries worth getting right:

This annual requirement applies to FMCSA-regulated carriers — operations running commercial motor vehicles in interstate commerce. CDL-level rules (Part 383) layer in at higher thresholds and reach both interstate and intrastate operations. Purely intrastate operations are governed by state law, and most states adopt the federal rules by reference — so confirm your state's posture.
Many corporate "gray fleet" drivers — employees in ordinary, lighter, non-commercial vehicles — fall outside Part 391 entirely. For them, the annual 391.25 review isn't a federal mandate.

Compliance obligations depend on your vehicles, your operations, and whether you cross state lines. The annual MVR review under 49 CFR 391.25 applies to commercial motor vehicles in interstate commerce; intrastate and non-CMV operations vary by state. Confirm what applies to your operation with the FMCSA (fmcsa.dot.gov) and the regulation text at ecfr.gov before relying on any summary — including this one.

Continuous monitoring: best practice, not a mandate

Here's the gap the annual review leaves: a driver can pick up a speeding conviction, a DUI, or a suspension the day after their annual pull, and under the bare minimum you wouldn't know for nearly a year. That's a long time to keep a newly high-risk driver on the road.

Continuous MVR monitoring closes that gap. Instead of one snapshot a year, you subscribe to alerts so a new violation, suspension, or status change surfaces within days. It's the difference between an annual photograph and a live feed.

To be clear about what this is: continuous monitoring is a best practice, not a federal requirement. The federal floor for regulated carriers is the annual 391.25 review. Continuous monitoring is something safety-minded fleets adopt voluntarily because it reduces risk — and for non-DOT gray fleets, where there's no federal review mandate at all, ongoing monitoring is simply good risk management. (OSHA doesn't impose a specific driver-monitoring standard either; its General Duty Clause obligates employers to address recognized hazards, and a driver with a deteriorating record is exactly that.)

A monitoring cadence you can actually run

A workable policy has four moving parts. Adapt the specifics to your operation.

Pre-hire. Pull and review an MVR on every driver before they get behind the wheel. Set a clear hiring standard (e.g., no recent major violations).
Annual review (the floor). For FMCSA-regulated drivers, complete the 391.25 obtain-and-review cycle at least once every 12 months, and file the dated review note. Run the same annual check on gray-fleet drivers as a best practice.
Continuous monitoring (the upgrade). Enroll drivers in a monitoring service so new activity alerts you between annual pulls. This is where you catch problems early.
Event-triggered review. Any alert — a violation, suspension, or at-fault crash — triggers an immediate review, regardless of where you are in the annual cycle.

Write this down. A one-page MVR policy that names the cadence, the standard, and who reviews and files the records is what turns "we check MVRs" into a program you can defend.

What to do when an MVR flags a driver

This is the step fleets most often skip — and it's the one that actually reduces crashes. Pulling and reviewing records does nothing on its own; the value is in what you do with a flag.

When monitoring surfaces a problem:

Confirm continued qualification. For FMCSA-regulated drivers, check the record against the §391.15 disqualification standards. A disqualifying event means the driver can't operate the CMV — full stop.
Triage by severity. A single minor violation is a coaching conversation; a pattern, a serious violation, or an at-fault crash is a remediation trigger.
Assign targeted training. Route the flagged driver into a defensive driving course built for the behavior at issue — now, not at the next renewal. This is the layer that completes the monitoring loop: monitoring tells you who and when, and training is the what you do about it.
Document everything. Record the flag, the review, the action you assigned, and completion. That paper trail is your due-diligence evidence if a crash ever becomes a claim or litigation.

A course that supports bulk assignment and completion tracking is what makes this practical — you can route a flagged driver into the right course in minutes and prove they finished. (We'll go deeper on what to assign after a crash in a forthcoming post-accident remediation guide.) For the broader picture of how training slots into screening and incident review, see our companion guide on building a fleet driver safety program that lowers your insurance, and for picking the course itself, choosing an online corporate defensive driving course.

The bottom line

MVR monitoring runs on two levels: the annual review required of FMCSA-regulated carriers under 49 CFR 391.25 is the floor, and continuous monitoring is the best-practice upgrade that removes the year-long blind spot between pulls. But neither one reduces a single crash by itself. The payoff comes when a flag triggers action — confirming qualification and assigning training that actually corrects the behavior. Build the cadence, write the policy, and make sure you can route a flagged driver into a course the same day. Explore more in our fleet and corporate safety guide.