Prevention FAQ — FMCSR 391.25: Annual Driving Record Review

Operational guidance for fleet safety managers on preventing 391.25 citations through documented annual reviews, driver fitness tracking, and audit procedures.

Severity Weight
3
OOS Eligible
No
BASIC Category
Driver Fitness
Code System
FMCSR
Code:
391.25
Code System:
FMCSR
BASIC Category:
Driver Fitness
OOS Eligible:
No
Severity Weight:
3
Violation Group:
BASIC 3

Ranks #3,037 of 3,146 FMCSR codes by citation frequency.

Violation Description

Motor carrier failing to review the driving record of each driver at least once every 12 months.

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What exactly do inspectors look for when they audit for 391.25 compliance?

Inspectors verify that your carrier maintains a documented annual review of each driver's Motor Vehicle Record (MVR) or state driving history. They will request your MVR files, review dates, and sign-off records during a roadside or facility inspection. The inspector checks for:

  • A dated record showing when the review was completed
  • Evidence the review occurred within the prior 12 months
  • Documentation that identifies which driver was reviewed
  • Any notes or action taken based on unsafe violations or license suspensions found

Keep these records organized by driver and indexed by review date. Digital systems with timestamp logs are stronger than manual spreadsheets, because they create an auditable trail that satisfies inspector expectations.

What should our annual MVR review pre-work checklist include?

Before your team orders the MVR or accesses state records, confirm:

  1. Driver identity — legal name, date of birth, and current CDL number match your employment file
  2. License status — the CDL is current and not suspended or revoked
  3. Review window — last review date is within the past 12 months; if not, flag for immediate action
  4. Order method — you are using an authorized service (your state DMV, a licensed MVR vendor) to avoid data integrity issues
  5. Retention plan — you will file the result in a designated folder (physical or digital) with the date and reviewer's name
  6. Action triggers — you have a written policy defining what findings require immediate follow-up (DUI convictions, reckless driving, multiple moving violations)

Enforce a calendar reminder 11 months after each review to prevent lapses.

What documents must drivers carry and what must the carrier retain?

Drivers are not required to carry proof of the annual review. However, they should know the review was done and be prepared to confirm it in conversation with an inspector.

Carriers must retain:

  • A copy of each driver's MVR or official driving record printout (typically valid for 30 days from order date)
  • A cover sheet or log entry dated and signed by the person who reviewed it
  • Your written policy describing how you handle violations found during review (e.g., unsafe driver letters, retraining, or termination thresholds)
  • The record must be accessible within your driver qualification file and held for at least 3 years

Store these in a consistent location — either a physical filing cabinet organized alphabetically by driver, or a cloud system indexed by driver ID and review date. Inspectors expect to retrieve any driver's file in under 5 minutes.

What root causes should we investigate after identifying a lapsed review?

A 391.25 lapse usually stems from one of these systemic issues:

  1. Administrative turnover — The person responsible for ordering MVRs or tracking due dates left the company, and the responsibility wasn't reassigned. Solution: Assign reviews to at least two people with written backup procedures.

  2. Lack of calendar reminders — No system flags the 12-month anniversary. Solution: Use your fleet management software, Google Calendar, or a dedicated compliance tracking spreadsheet with email alerts set to trigger 60 days before expiration.

  3. Cost avoidance — Carriers skip reviews to save on MVR order fees ($15–50 per record). Solution: Budget the annual cost upfront and include it in your safety program expenses; the fine far exceeds the cost of compliance.

  4. Driver turnover masking — New hires were added, but the review schedule wasn't updated. Solution: Integrate the MVR review requirement into your onboarding checklist so reviews are ordered immediately for new drivers, not on a calendar date.

How do we verify and document the review before closing out the annual cycle?

After receiving the MVR from your vendor or state, follow this closure workflow:

  1. Compare to file — Verify the driver name, DOB, and CDL number on the printout match your employment records
  2. Flag violations — Highlight any moving violations, suspensions, or convictions discovered during the review period
  3. Apply your policy — If your policy requires an unsafe driver letter or retraining for specific violations, issue it and retain the copy
  4. Sign and date — The safety manager or HR personnel who reviewed it must print their name, date, and title on the MVR or a cover sheet
  5. File immediately — Do not leave the MVR in an inbox. File it in the driver's qualification folder that same day
  6. Update your log — Mark the driver as "reviewed – [date]" in your master MVR tracking spreadsheet

This step-by-step process creates an unbroken audit trail and ensures no reviews fall through the cracks.

What post-citation analysis should we run if an inspector finds a lapsed review?

If cited for 391.25, conduct a full-fleet audit within 5 days:

  1. Identify scope — Pull your master driver list and the date each driver's MVR was last reviewed
  2. Calculate gaps — Determine how many drivers have reviews older than 12 months
  3. Order replacements immediately — For any driver with a gap, order a current MVR the same day
  4. Root-cause interview — Meet with the person responsible for tracking reviews. Document what broke (missed deadline, staff absence, budget freeze)
  5. Policy revision — If your current system allowed a lapse, revise it. For example, switch from manual tracking to automated reminders in your fleet software
  6. Complete all delinquent reviews — Do not wait for a deadline. Treat all overdue reviews as urgent and order/file them within 7 days
  7. Document the corrective action — Keep a dated memo in your compliance file describing what you changed

This shows the FMCSA that you took the citation seriously and have a credible prevention plan.

Does 391.25 affect our CSA score or driver fitness ratings?

Yes. FMCSR 391.25 carries a CSA Severity Weight of 3, which means each citation contributes to your Driver Fitness BASIC. While a single citation typically does not trigger immediate intervention, repeated citations signal to auditors and the FMCSA that your driver qualification process is weak.

Multiple 391.25 citations over time will increase your Driver Fitness percentile, making you a higher priority for:

  • Roadside inspection frequency
  • Safety audits and off-site reviews
  • Mandatory corrective action plans
  • Potential Out-of-Service directives if your entire safety culture appears broken

Prevent this by implementing the annual MVR review as a non-negotiable, automated process. One well-documented citation is recoverable; a pattern suggests systemic non-compliance that regulators will target.

What training should we require for drivers and office staff on this code?

For drivers: Include in your annual safety briefing that the carrier reviews their driving record at least once per year. Explain that your policy may require retraining or disciplinary action if serious violations are found. Drivers should understand this is not surveillance but a way to identify performance issues early and keep unsafe habits off the road.

For office/HR staff: Require training on:

  • How to order an MVR (your state's process and any licensed vendor partnerships you use)
  • What documents to request and how to verify authenticity
  • Your internal filing structure and retention timeline
  • Red flags in an MVR (suspended licenses, DUI convictions, at-fault accidents) and escalation procedures
  • Calendar and reminder systems specific to your fleet size (e.g., "every driver's review date + 11 months = order new MVR")

For safety managers: Annual training on FMCSR 391.25 requirements, recent FMCSA guidance on driver fitness, and best practices from peer carriers. This ensures your program stays current as regulations evolve.

When should we challenge a 391.25 citation using DataQs?

Submit a DataQs challenge only if you have documentary proof that:

  1. The review was completed within 12 months of the inspection date, and the date was recorded accurately
  2. The inspector did not ask for the file, or you provided it and the officer noted it on the inspection report
  3. The citation reflects a data-entry error (e.g., the officer cited the wrong driver or wrong date)

Do not challenge if:

  • The review was genuinely overdue
  • You cannot locate the MVR file to prove the review occurred
  • The officer's narrative is accurate

If you do challenge, submit the signed MVR cover sheet, your policy document, and a dated memo explaining the timing. Include a screenshot of your compliance log showing the review date. FMCSA typically resolves DataQs challenges within 30–60 days.

How often should we audit our fleet for 391.25 compliance, and what cadence works best?

Conduct a full audit every 90 days as part of your preventive compliance program. Here's why: enforcement data shows that lapses occur slowly—a driver's review might slip from "due next month" to "3 months overdue" before anyone notices. A quarterly check catches these gaps before an inspector does.

Audit checklist:

  • Pull your master MVR tracking log
  • For each driver, calculate days since last review
  • Flag anyone over 12 months
  • Flag anyone approaching 11 months (order their new MVR immediately)
  • Verify filed copies are in the correct folder with legible dates
  • Test your reminder system—did it trigger for anyone this quarter?

Additionally, conduct an annual review (every 12 months) to assess the entire program: Are drivers being reviewed on time? Is your vendor reliable? Do you need a better software tool? Are staff trained?

This dual cadence—quarterly spot checks plus annual program review—aligns with industry best practice and creates a strong defense against citations.

Last updated: 2026-04-20T18:15:38.340Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.