MVR schedules, expiration tracking, and Part 391 files

Motor vehicle records anchor both hire and annual qualification tasks. They support investigations under 49 CFR 391.23, annual reviews under § 391.25, and day-to-day checks that licensing still matches the application on file. When pull dates drift, everything else looks finished while the record underneath is stale.

A safety manager preparing for a review often discovers the gap late: the folder includes a license copy and medical evidence, but the last MVR is thirteen months old—or the initial request went out on day thirty-one. Scheduling pulls and the dates your team tracks on the file turns those surprises into visible tasks instead of audit-night panic. Treat hire and annual MVR work as one queue with two rule citations, not as separate projects one terminal forgets until FMCSA calls.

Key takeaways

• Request initial MVRs within 30 days of hire and file responses within that window under § 391.23.
• Pull motor vehicle records at least every 12 months for each employed driver and note who reviewed them under § 391.25.
• CDL holders may need licensing state medical status updates when certification changes, not only on the annual anniversary.
• Expiration alerts flag dates your team enters; they do not replace MVR pulls or reviewer notes.

Initial hire MVR requests under § 391.23

Initial hire work starts when employment begins. § 391.23(a) requires motor carriers to request records from each state that issued a license or permit during the past three years, within 30 days of the start date. File each response with the request date and source state so auditors can match timing to the rule. Same-week hires still require structured timing—sequence initial requests with applications and inquiries as described in same-day driver onboarding records, and keep MVR tasks open on the workflow until responses land inside regulatory windows.

When a state is slow, log follow-up attempts on the file so the gap shows intentional pursuit, not neglect. Dispatch should see open MVR tasks alongside other hire steps, not a green status copied from a vendor email that never reached the qualification folder. The 30-day window in § 391.23(a) applies to the request, not to your hope that the state responds—your file should show you requested on time even when the reply lands on day twenty-eight. Rehires and transfers from sister terminals still need hire-window requests when the new employment relationship starts; reusing an old MVR without a fresh request dated to this start date is one of the fastest ways to fail a hire sample even when the driving record itself looks clean.

Annual MVR pulls and reviewer notes under § 391.25

Annual cycles run on employment, not calendar-year convenience. At least every 12 months, obtain a fresh MVR and review it. Store the reviewer’s name and date on the qualification file per § 391.25(c)(2). Many carriers anchor anniversaries to hire date or last review date—pick one method, document it in your safety manual, and apply it fleet-wide. Pair schedules with annual driver record review reminders so reviewers receive tasks before anniversaries slip.

An MVR without a reviewer note is paperwork; an MVR with a dated note is the annual review the rule describes.

Close tasks only after the note is filed, not when the vendor email arrives. If your tool separates motor vehicle record tasks from expiration alerts, use both: pulls satisfy inquiry rules; alerts remind you about license or medical dates your policy tracks—they do not replace pulls or notes. Picture an annual review where the safety manager can point to a note dated two days after the MVR run date—that is the story § 391.25(c)(2) expects. A note dated months after the printout looks like paperwork added for the audit, not a review performed when the record arrived. When the MVR shows a serious event your policy names, the annual note should still describe what appeared and who reviewed it—even if follow-up MVRs or supervisor memos come later under separate policy steps.

Medical certification changes alongside MVR cycles

Commercial driver’s license holders often rely on state licensing system medical status. § 391.43 describes examination requirements and how certification interacts with qualification. When a driver reports a downgrade or presents a new certificate, refresh the licensing state record your policy requires—even if the annual MVR anniversary is months away. Non-CDL interstate drivers may need medical examiner certificates and National Registry verification on file instead; see FMCSA medical certification guide for fleets when clinic and state updates diverge.

Wallet certificates and MVR data should tell the same story before dispatch assigns the next load. Treating an expiration alert as an automatic MVR pull is a common mistake—alerts flag dates you entered; they do not satisfy § 391.25 by themselves. When a CDL holder reports a medical downgrade, the licensing state record may change before your next annual anniversary; refreshing that record is part of keeping the qualification file aligned with § 391.43, not an optional extra step you defer until annual season.

Multi-state drivers and pending jurisdiction responses

Drivers licensed in more than one jurisdiction during the lookback period need records from each state your process covers under § 391.23 and § 391.25. Track pending state responses separately so one completed pull does not hide a missing reply elsewhere. File metadata auditors expect: request date, receipt date, and state source on each PDF.

Drivers who transfer between terminals still need one anniversary calendar—see managing driver compliance across regulated operations for keeping MVR dates carrier-centralized. When employment ends, MVR and review notes remain subject to § 391.51(d) retention like other qualification records. Multi-state drivers are where single-state “complete” statuses lie: one Colorado reply does not excuse a missing Texas request when both states issued licenses during the lookback period. Track pending jurisdictions explicitly on the workflow so reviewers cannot close the driver until each required state response—or documented follow-up—is on the file. If your vendor batches pulls monthly, adjust internal due dates so requests still leave within regulatory windows rather than waiting for the batch run to coincide with day thirty-one.

What to do this week

Export drivers whose hire date plus 30 days is approaching and confirm initial requests went out. List every driver more than eleven months from the last dated review note and schedule pulls before the anniversary passes, not after a customer asks for samples. Filing MVRs without reviewer notes, batching annual pulls by calendar year while ignoring hire anniversaries, and marking complete when one state responds but others remain pending are the gaps auditors find first.

Publish your anniversary method to all terminals, assign a named backup reviewer for vacation weeks, and map hire and annual tasks using the motor vehicle record glossary entry so MVR work stays a visible queue—not a fire drill before each sample request.

Sources

• 49 CFR 391.23 — Investigation and inquiries
• 49 CFR 391.25 — Annual inquiry and review of driving record
• 49 CFR 391.43 — Medical examination; medical examiner’s certificate
• FMCSA — Driver qualification regulations