Annual MVR reviews: dates your fleet should track now

It is the first Monday of the month, and your safety manager opens three spreadsheets: license expirations, medical dates, and a dispatch list. Somewhere in that stack is the annual motor vehicle record review—easy to defer because nothing looks broken until an auditor asks for reviewer names and dates.

Every employed driver needs an MVR pull at least every 12 months under 49 CFR 391.25. The regulation expects both the record and a note showing who reviewed it. Fleets that track only “MVR received” without “MVR reviewed by Jane on 3/14” still fail samples even when the underlying driving record is clean.

If you manage a mid-size fleet, you already feel the tension: safety staff are thin, terminals want drivers rolling, and state MVR vendors move at their own pace. Annual reviews fail quietly in that gap—until a compliance sample asks for ten reviewer names you cannot produce. Treating anniversaries as payroll-grade deadlines prevents those surprises without inventing new bureaucracy.

Key takeaways

• Request MVRs covering at least three years from each licensing state that issued the driver a license during the review period, per § 391.25(a).
• Document who performed the review and the date on the qualification file under § 391.25(c)(2).
• Track next due date from the review or pull—not from memory or dispatch’s gut feeling.
• Annual MVR work runs on its own calendar alongside medical updates and Clearinghouse queries.

An MVR sitting in email is not an annual review until a named reviewer dates it on the file.

Why the annual MVR cycle breaks in mid-size fleets

Drivers stay employed for years; reviewers change roles; states delay responses. Many carriers pull MVRs reliably at hire under § 391.23 but treat the 12-month review as optional until someone asks. Compliance samples target continuing qualification, not onboarding alone.

Expiration alerts help start work, but alerts do not satisfy § 391.25(c)(2)—you still need a named reviewer and date on the qualification file. Tie reminders to lists you already use: Monday safety stand-up, active driver roster, or dispatch readiness reports. Export anyone whose last review is older than eleven months and assign a pull before the meeting ends. Our annual review guide for carriers separates “pull the MVR” from “write the note” for new staff.

Calendar invites alone fail when reviewers ignore them. Better triggers attach to workflows that already exist—payroll active lists, dispatch sheets for Monday departures, or the same report that tracks expiration alerts for licenses. Configure alerts to fire before the twelfth month ends, not after. A late alert recreates the panic you wanted to avoid.

Imagine a driver hired in March 2023 whose last review note shows April 2024 but no 2025 entry. The MVR vendor delivered a PDF in May; it sits in a shared folder because the reviewer was on vacation. By October, dispatch still shows “current” because nobody closed the loop on the file. That pattern is invisible until a sample asks for ten consecutive anniversary dates. Fixing it means tying vendor delivery to a review task with an owner, not treating the PDF as the finished obligation.

Pull the MVR, review it, and file it under Part 391

§ 391.25 requires inquiry and review. Step one is obtaining a record covering at least three years from each licensing state in scope. Step two is reading it against Part 391 disqualification rules and your written policy. Step three is documenting who reviewed and when on the § 391.51 file—thin notes like “reviewed” alone invite follow-up questions.

When an MVR shows crashes or serious violations your policy flags, follow escalation paths and file supervisor notes with dates. Multi-state history means tracking pending responses separately so one slow state does not hide a missing pull from another. Medical certification and Clearinghouse query anniversaries belong on the same dashboard as MVR dates, but each obligation keeps its own schedule—do not treat one green flag as covering another.

A useful review note names the reviewer, the review date, the MVR source date, and a plain statement that the record was evaluated against Part 391 and carrier policy. “Reviewed” alone is thin. Train backup reviewers before PTO season so anniversaries do not stall when one person is out. If two reviewers split the fleet, document who owns escalations when the MVR shows a crash pattern your policy requires supervisor sign-off.

Serious MVR findings and common annual review gaps

Annual reviews are not only quiet renewals. When a record triggers your policy, document who decided the driver could continue in a safety-sensitive role and whether additional pulls were ordered. Future investigators should read a chain on the file, not a lone PDF with no context.

Common failures: MVRs filed without review notes, notes dated on the wrong pull when multiple MVRs exist in one year, and anniversary dates tied to internal transfers without a clear employment story. Spreadsheet reminders that never reach the official file create false confidence—if the note is not on the qualification file, the program failed.

When a driver returns after a leave or rehire, decide which prior reviews remain valid under your policy and which steps repeat under § 391.23. Do not assume an old annual note covers a new employment period without a documented decision. Serious findings on the MVR may require extra pulls or supervisor memos—link those habits to extra review after MVR events without inventing scores FMCSA does not publish.

For a concrete escalation, suppose the annual MVR shows an out-of-state DUI conviction your policy flags as disqualifying unless mitigated. The reviewer should not silently file the PDF. Document who reviewed, what policy section applied, whether a supervisor signed off on continued employment, and whether you ordered a follow-up pull after a waiting period. Investigators reading the file months later should see a decision trail, not a mystery attachment. That discipline turns annual reviews from checkbox work into the continuing qualification program Part 391 expects.

Common mistakes and this week's anniversary sweep

This week, export last MVR review date and reviewer name for every employed driver. Sort oldest first; schedule pulls and assigned reviewers for anyone past eleven months. Spot-check five files from your last external sample—do note dates match PDF dates? Update one SOP sentence to cite § 391.25(c)(2) so language stays precise.

Make annual reviews boring in a good way

When MVR anniversaries behave like payroll—predictable, assigned, dated—you spend less time explaining gaps and more time fixing real driving-record issues. Use driver qualification files to keep review status visible, and deepen process with our annual review guide for carriers when you rewrite SOPs this quarter.

Sources

• 49 CFR 391.25 — Annual inquiry and review of driving record
• 49 CFR 391.51 — General requirements for driver qualification files
• 49 CFR 391.23 — Investigation and inquiries
• FMCSA — Driver qualification regulations (Part 391)