
The MVR Check Doesn't Match His Application. Which State Are You Missing?
ON THIS PAGE7 sections
- Why does the MVR disagree with what the driver wrote?
- Which states does an MVR check for CDL drivers have to cover?
- How do you close a multi-state gap, step by step?
- How do you run the annual review as a process, not a fire drill?
- What does a complete set of MVRs still not tell you?
- How do you know the file will hold up?
- Frequently asked questions
The application says six years driving: four in Texas, two in Oklahoma. The record you ordered came back from Oklahoma, starts nineteen months ago, and is spotless.
That is not a clean driver. That is a clean state, and you are looking at a quarter of his history. An MVR check for CDL drivers is a per-jurisdiction pull: one licensing authority, one record, one slice of time. Move the driver across a state line and the slice moves with him, which is why the federal rule is written in the plural. 49 CFR 391.23(a)(1) requires an inquiry “to each State where the driver held or holds a motor vehicle operator’s license or permit during the preceding 3 years” (eCFR). Each. Not the current one.
This is not a walkthrough of what an MVR contains. It is what you do when the record and the claimed history do not line up, and how to build the annual review so the gap stays closed.
Why does the MVR disagree with what the driver wrote?
Because the driving record follows the license, and the license moves when the driver does. There is no federal MVR. There are state and jurisdictional licensing authorities, each keeping its own record, and the machinery stitching them together is a pointer system, not a merged file. What makes any of it work is one sentence at 49 CFR 383.21: no person who operates a commercial motor vehicle may at any time hold more than one driver’s license. One authoritative record at any moment, not one forever.
Three mechanisms move history across state lines, and each is a place your file can spring a leak.
The transfer at issuance. When a driver applies in a new state, 49 CFR 383.73(b)(3) requires that state to check his record in the current state of licensure, query CDLIS, check the Problem Driver Pointer System, and request “the applicant’s complete driving record from all States where the applicant was previously licensed over the last 10 years to drive any type of motor vehicle.” Read the exception: that full 10-year request is only required for initial issuance of a CLP, transfer of a CDL from another state, or a first renewal after September 30, 2002 (eCFR). It is a DMV compliance event, not a promise that ten years of detail will render on the report you buy.
The conviction posting chain. 49 CFR 384.225(a)(1) requires the state to post to the CDLIS driver record all convictions, disqualifications and licensing actions for traffic-law violations “committed in any type of vehicle,” excepting parking, weight and vehicle defect violations — the provision that pulls a personal-car ticket onto a CDL holder’s record. Paragraph (c) sets a 10-day posting clock; paragraph (d) requires retention of at least three years (eCFR).
The driver’s own duty, now narrower. Under 49 CFR 383.31, a CDL holder convicted of a traffic violation in any type of motor vehicle, parking excepted, must notify his current employer within 30 days of the conviction date. The parallel duty to self-report the conviction to the issuing State was removed by FMCSA effective July 22, 2026 (91 FR 37047, published June 22, 2026), on the reasoning that electronic exchange of violations between State licensing agencies had made it unnecessary (Federal Register). An intake script that still asks whether he reported a ticket to his home state is asking about a duty that no longer exists.
The mismatch usually resolves into one of four diagnoses.
| What you are seeing | Most likely cause | What closes it |
|---|---|---|
| Record starts recently, no prior history | You pulled the current state only; the history sits with a prior authority | Pull the prior state directly |
| Claimed employment period with no license activity | Driver was licensed in a state you did not list, or off a CDL for a stretch | Rebuild the license timeline, then pull |
| A violation the driver disclosed is not there | Posting lag, or a conviction not yet forwarded between states | Re-pull after the 10-day window |
| A violation appears the driver never disclosed | Possible failure to notify you within 30 days under 49 CFR 383.31, or an entry on the wrong driver | Ask in writing before deciding |
Note what is not on that list: the driver’s own annual list of violations. That requirement lived at 49 CFR 391.27, and FMCSA rescinded it effective May 9, 2022 (87 FR 13192, published March 9, 2022), reasoning that it duplicated the carrier’s existing obligation to obtain the MVR (Federal Register). If your process still leans on a signed driver certification to catch what the MVR misses, it leans on a form with no regulatory weight.
Which states does an MVR check for CDL drivers have to cover?
Two rules, two scopes, and carriers conflate them constantly. The hire inquiry and the annual inquiry are not one pull run twice.
| At hire — 49 CFR 391.23 | Annual — 49 CFR 391.25 | |
|---|---|---|
| Cycle | Once, at hire | At least once every 12 months |
| Which authorities | Each State where the driver held a license or permit in the preceding 3 years | Each licensing authority where he held a CDL or permit during the period covered |
| Period covered | The driver’s prior 3-year driving history | At least the preceding 12 months |
| Deadline | In the qualification file within 30 days of the date employment begins | Within the 12-month cycle |
| If nothing comes back | Document a good faith effort (391.23(b)) | Document the attempt |
| What goes in the file | Copy of the MVR from each authority (391.51(b)(2)) | The MVR and a note naming reviewer and date (391.25(c); 391.51(b)(4)–(5)) |
One consequence drives most of the findings: “each State” tracks license history, not employment history. Three carriers inside one state on one license is one inquiry; one job while relocating twice is three. Pull only the current state and the gap stays invisible until an investigator asks why the file has a single MVR.
How do you close a multi-state gap, step by step?
| Step | What you do | Status |
|---|---|---|
| 1 | Rebuild the license timeline first | Smart |
| 2 | Pull the CDLIS MVR from the licensing state | Required in effect |
| 3 | Order a record from every jurisdiction on it | Required |
| 4 | Reconcile the application against the records | Smart |
| 5 | Put discrepancies to the driver in writing | Smart |
| 6 | Document good faith where nothing comes | Required |
Rebuild the license timeline before ordering anything
What you do: build a license history separate from the employment history. Take the 10-year employment list that 49 CFR 383.35(c) requires the applicant to furnish — previous CMV employers, dates, reason for leaving — and beside it write every state the driver was domiciled in, with dates. Then ask which state issued his CDL in each period, and whether he ever surrendered one license to get another.
Status: smart practice. The 383.35 request is required; deriving a license timeline from it is your own discipline.
The gotcha: the two columns diverge more often than people expect. Drivers who ran out of a terminal in a neighboring state, kept a home-state license through a stint elsewhere, or let a CDL lapse and re-tested somewhere new all produce timelines whose edges do not match. Order against the license column; ordering against the employment column is how a state gets skipped.
Pull the CDLIS MVR from the current state of licensure
What you do: request the CDLIS motor vehicle record, not a generic state abstract. 49 CFR 384.105(b) defines it as a report generated from the CDLIS driver record and provided by states to authorized users, subject to the Driver Privacy Protection Act at 18 U.S.C. 2721–2725. Motor carriers are authorized users under 49 CFR 384.225(e)(4), and that access runs “after notification to a driver.”
Status: required in effect. 49 CFR 391.51(b)(6)(ii) makes the CDLIS MVR from the current licensing state the mechanism for the medical certification file requirement, so most carriers obtain it anyway.
The gotcha: it tells you which jurisdictions matter; it is not a merged national history. Use it to confirm the Step 1 timeline and catch a state the driver forgot. Treating it as the complete record is the mirror image of the mistake you are fixing.
Order a record from every jurisdiction on the timeline
What you do: submit an inquiry to each state on the timeline, in that state’s prescribed form and manner. At hire you want the prior 3-year driving history from each state where a license or permit was held in that window. Log the order date, state, requested period and response date for every one, including the ones still open.
Status: required. 49 CFR 391.23(a)(1) is unambiguous about “each State,” and 391.23(b) sets the 30-day file deadline from the date employment begins.
The gotcha: the lookback a state actually returns is a matter of state law and it varies. A state returning seven years is not handing you seven years of decision material — 49 CFR 384.225(d) only requires convictions to stay on the CDLIS driver record for three years, so anything beyond that window is inconsistent between jurisdictions. Score the three-year window the regulation defines and read the rest for context.
Reconcile the application against the records
What you do: lay three documents side by side and walk them month by month — the 391.21 application, your Step 1 license timeline, and the stack of MVRs. Mark every month covered by an actual state record and every month covered by nothing. You are not producing a verdict but a map: what you know, what you do not, and which of the four causes above explains each gap.
Status: smart practice, and the step that makes the rest defensible.
The gotcha: an uncovered month is not an adverse fact and must never be scored as one. Carriers err in both directions: treating a gap as a red flag, which is unfair and hard to defend, or treating a clean partial record as a clean full record, the failure this procedure exists to prevent. Our 391.21 driver application walkthrough covers what the application should capture.
Put every discrepancy to the driver in writing
What you do: list the specific items — a violation he did not disclose, a claimed period with no license activity, a state on CDLIS that is not on his application — and ask him to respond in writing, not a vague “we found something.” Most discrepancies have ordinary explanations, and the exchange turns his into a document rather than a recruiter’s recollection.
Status: smart practice. It becomes a legal question the moment your answer turns into a no.
The gotcha: if the record came from a consumer reporting agency and contributes in whole or in part to an adverse decision, the FCRA sequence attaches — the report and A Summary of Your Rights Under the Fair Credit Reporting Act before you reject him, then a notice naming the reporting company and telling him he may dispute the information (FTC). Trucking has a shortened alternative at 15 U.S.C. 1681b(b)(3)(B) for applicants who only ever dealt with you by mail, telephone or computer, with its own three business day clock. Decide which route applies before you send anything, and confirm with counsel.
Document good faith where a record will not come
What you do: when a state does not respond, write down what you did. 49 CFR 391.23(b) says it plainly: if no record is received from a licensing authority required to respond, the carrier must document a good faith effort. Keep the request date, channel, reference number, follow-ups and outcome.
Status: required.
The gotcha: good faith is a documented sequence, not an adjective, and it does not suspend the clock. What you received goes in the qualification file within 30 days of the date employment begins either way.
How do you run the annual review as a process, not a fire drill?
By putting the calendar on the driver rather than the fleet, and treating the note as a deliverable. 49 CFR 391.25 has two halves carriers staff differently: the inquiry in paragraph (a), a purchasing task, and the review in paragraph (b), a judgment task. Both run on an “at least once every 12 months” cycle.
The review has defined content. Paragraph (b) requires you to review each driver’s MVR to determine whether he meets minimum requirements for safe driving or is disqualified under 49 CFR 391.15. Paragraph (b)(1) covers evidence of violations of the applicable Federal Motor Carrier Safety Regulations or the Hazardous Materials Regulations. Paragraph (b)(2) covers the driver’s accident record and violations of laws governing the operation of motor vehicles, and requires giving “great weight to violations, such as speeding, reckless driving, and operating while under the influence of alcohol or drugs, that indicate that the driver has exhibited a disregard for the safety of the public” (eCFR). That is a standard, not a scoring formula. It tells you which items outweigh the rest; it does not draw your line for you.
One arithmetic check belongs in every review, because it is where a multi-state driver quietly crosses a threshold. Under Table 2 to 49 CFR 383.51, a second conviction for any combination of the listed serious traffic violations, in separate incidents within a 3-year period, carries a 60-day disqualification; a third or subsequent conviction in that window carries 120 days. Those offenses include excessive speeding at 15 mph or more over the limit, reckless driving, improper or erratic lane changes, following too closely, and texting or hand-held phone use while driving a CMV. Convictions from separate incidents count toward the tally whether committed in a CMV or a non-CMV (49 CFR 383.51(a)(4)); where the qualifying conviction happened in a non-CMV, the disqualification attaches only if it results in revocation, cancellation or suspension of the license or non-CMV driving privileges (eCFR). Two 62-in-a-45 tickets in different states, eighteen months apart, are two records you have to have pulled in order to see as one pattern.
Then close the paperwork. 49 CFR 391.25(c) requires a copy of the MVR obtained under paragraph (a) in the qualification file, plus a note with the name of the person who performed the review and the date of it; both are separately listed at 49 CFR 391.51(b)(4) and (b)(5). On retention, 391.51(c) holds the qualification file for as long as the driver is employed and three years after, while paragraph (d) lets the annual MVR and the review note come out three years after the date of execution (eCFR). Keep three cycles and you are at the retention floor; keep four and you have margin.
In practice: a per-driver anniversary date, a queue built from license jurisdictions rather than one default state, and a named reviewer who is not also running dispatch. Someone has to own the call.
What does a complete set of MVRs still not tell you?
Whether he shows up. You can execute every step above perfectly — CDLIS confirmed, four states pulled, reconciliation clean, good-faith log tight — and still know almost nothing about what the driver was like to employ. The MVR is a record of adjudicated traffic outcomes, narrow by design.
The multi-state case makes the limit obvious. Consider what generates no conviction anywhere: leaving a load, going dark on dispatch for two days, returning equipment with damage nobody wrote up, quitting after the first pay cycle three times running. None of it reaches a DMV, and 49 CFR 384.225(a) obligates the state to post convictions, disqualifications and other licensing actions plus medical certification status — there is no field where behavioral information could land even in principle.
That is the gap a behavioral layer is built for. Carrier-written reviews on cdlscan come from employers rather than a state agency, so they are not bounded by jurisdiction: a driver who relocated three times leaves one continuous trail instead of four disconnected ones. Where the MVR answers “was he convicted,” carrier-submitted feedback speaks to whether other carriers found him workable — look him up last, after the required inquiries.
Be exact about the boundary. This is an additional layer of evidence and nothing more: it does not satisfy 49 CFR 391.23 or 391.25 and does not substitute for a state motor vehicle record. Nor is its legal status something a guide can settle. If you intend to rely on any third-party information in a hiring decision, ask the provider which category of report the data falls under, and confirm with your own counsel which FCRA obligations attach. The same argument applies to the DAC report and its blind spots.
How do you know the file will hold up?
Test the coverage, not the outcome. Before you sign the review note, two things should hold. Every jurisdiction where the driver held a license or permit in the window appears in the file, either as a record or as a documented good-faith effort with dates. And the serious-violation tally under 383.51 was run across all the records, not state by state.
A file failing the first test has an upstream problem in how records get ordered, and it repeats across every driver you hire. For how these decisions surface in your scores, see the CSA methodology walkthrough; for roadside data an MVR does not carry, our PSP report walkthrough.
Frequently asked questions
If my driver moved states last year, do I have to pull an MVR from both?
Yes. 49 CFR 391.25(a) requires the annual inquiry to go to each licensing authority where the driver held a CDL or permit during the period the record must cover. A mid-year relocation means two records for that cycle. Pulling only the current state is a common audit finding.
Is a CDLIS MVR the same thing as a state MVR?
No. 49 CFR 384.105(b) defines the CDLIS MVR as a report generated from the CDLIS driver record and provided by a state to authorized users. It tells you which jurisdictions are in play and carries medical certification status, but it is issued by one state and does not replace the inquiry to each prior licensing authority under 391.23(a)(1).
What do I do when a state will not produce the record?
Document the effort. 49 CFR 391.23(b) requires a documented good faith effort where no motor vehicle record is received from a licensing authority required to respond. Keep the request date, channel, reference number, follow-ups and outcome. The 30-day deadline still runs.
Can I use the driver’s own list of violations instead of pulling the MVR?
No, and the form it came from is gone. FMCSA rescinded 49 CFR 391.27, the record-of-violations requirement, effective May 9, 2022, reasoning that it duplicated the carrier’s obligation to obtain the MVR. The driver’s duty to report convictions to his employer within 30 days survives at 49 CFR 383.31 — redesignated as paragraph (a) effective July 22, 2026, when FMCSA removed the parallel duty to self-report to the issuing State (91 FR 37047). It supplements the MVR rather than replacing it.
How long do I keep the annual MVR and the review note?
49 CFR 391.51(d) permits both the annual MVR under 391.25(a) and the review note under 391.25(c)(2) to be removed from the qualification file three years after the date of execution. The file as a whole is kept as long as the driver is employed, plus three years (391.51(c)).
A violation the driver disclosed is not on the record. Should I worry?
Usually not yet. Under 49 CFR 384.225(c) a state must make conviction information available within 10 days of receiving it from another state, or within 10 days of an in-state conviction date, so a recent out-of-state citation can legitimately be absent when you pull. Ask for the citation and disposition, and re-pull rather than treating the absence as a clearance or a lie.
This article is general information for motor carrier hiring and safety staff, not legal advice. Federal regulations and their interpretations change, and state record practices vary. Verify the current text of any section on ecfr.gov and consult counsel before building a screening policy on it. Last reviewed 2026-07.