DOT Employment Verification: Which of Those Ten Employers Must You Call?

The application on your desk lists eleven employers going back ten years. The rules make the driver disclose all eleven. They do not make you investigate all eleven.

FMCSA states the mismatch in its own words: an applicant for a CDL position “must provide the driver’s employment history for the preceding 10 years, rather than 3 years (49 CFR 391.21(b)(11)). In contrast, the motor carrier is required to investigate the driver’s safety performance history for only the preceding 3 years (49 CFR 391.23(a)(2))” (91 FR 5554, 5555).

That sentence explains most of what goes wrong in DOT employment verification. Carriers either work the whole ten-year list and burn a week they did not have, or they call the current employer and stop. This article is the middle: whom you have to contact, what you have to ask, what you have to tell the driver first, and what the file must contain when nobody writes back.

What does DOT employment verification actually require?

Two inquiries, both keyed to the date employment begins, both due in 30 days. 49 CFR 391.23(a) sets them out: an MVR inquiry, and an investigation of the driver’s safety performance history “with Department of Transportation regulated employers during the preceding three years.” Everything below hangs off those two sentences.

One wording change matters if you built your process from older text. Paragraph (a)(1) now requires the inquiry to go to “each driver’s licensing authority” where the driver held a license or permit during the preceding 3 years. It read “each State” until FMCSA restored the broader term in a technical amendments rule effective July 21, 2026 (91 FR 45653). Running that inquiry across jurisdictions is its own job — see the MVR check walkthrough.

The employment side starts on the application. 49 CFR 391.21(b)(10) requires the names and addresses of the applicant’s employers for the 3 years preceding the application date, the dates of each, and the reason for leaving. Subparagraph (iv) adds two flags for employment after October 29, 2004: whether the applicant was subject to the FMCSRs at that employer, and whether the job was a safety-sensitive function in a DOT-regulated mode subject to part 40 testing. Those checkboxes are how you build the call list. Treat them as required fields.

The ten years is a statutory floor, not an agency preference: 49 U.S.C. 31303(c)(2) lets the Secretary set the notice period by rule, but “the period may not be less than the 10-year period ending on the date of the application.”

Where does the 3-year window stop and the 7-year window start?

At the boundary between what you read and what you chase. The seven-year block is disclosure. You read it, check it for arithmetic that does not work, and ask about it in the interview. It generates no mandatory contacts.

Do not confuse the DOT seven years with the seven years from general background screening. That one comes from the Fair Credit Reporting Act at 15 U.S.C. 1681c(a), limits what a consumer reporting agency may report rather than what an applicant must disclose, and is switched off for paragraphs (a)(1) through (a)(5) by 15 U.S.C. 1681c(b)(3) where the position pays an annual salary of $75,000 or more. Two regimes, one number, no relationship. Reading both blocks for gaps is covered in our 391.21 application walkthrough; this article picks up where the call list starts.

Whom are you actually required to contact?

Previous employers that put the driver in a CMV in the last three years, plus DOT-regulated employers for the drug and alcohol piece. 49 CFR 391.23(d) is explicit: investigate, at a minimum, “from all previous employers of the applicant that employed the driver to operate a CMV within the previous three years.”

The current-employer row is the one that gets skipped, for the obvious human reason: nobody wants to call a man’s boss while he still works there. The definition does not care. Tell the driver the call is coming — that is what the notices below are for.

If the applicant has no DOT-regulated employment in the last three years, you still do not get an empty step. 391.23(c)(4) requires documentation that no investigation was possible, filed within the same 30 days. A blank section is a finding; a dated memo explaining the blank is compliance.

Note what is not on the list: nothing in 391.23 names a commercial employment-history database, and no DOT regulation requires you to buy one. Those products have their uses — see what carriers see in a DAC report — but buying one does not discharge the investigation.

What must you tell the driver before you contact anybody?

Two separate notices, both in writing, both before the application is submitted. 49 CFR 391.21(d) requires you to inform the applicant, before submission, that the (b)(10) information may be used and that previous employers will be contacted for the safety performance history investigation. The same paragraph requires you to “notify the driver in writing of his/her due process rights as specified in § 391.23(i).”

Those rights are three: to review the information you received, to have erroneous information corrected, and to have a rebuttal attached where the previous employer will not correct it. 391.23(i)(1) requires the notice to reach drivers with DOT-regulated employment in the preceding three years “via the application form or other written document prior to any hiring decision.” FMCSA was blunter in the preamble: the notification “must be made in writing to all applicants, including those not hired” (69 FR 16684, 16694).

Carriers routinely ship only one of the two, and losing the due process notice is the expensive omission: the rest of paragraph (i) runs on clocks that start only when the driver asks, and he cannot ask for something he was never told about. Print both into the application packet.

How do you run the verification, step by step?

What counts as a good-faith effort when nobody answers?

Nobody will tell you, and that is the honest answer. “Good faith effort” runs through Part 391 and is defined nowhere in it. In the 2004 rulemaking an industry association asked FMCSA directly for examples. FMCSA declined, saying only that “the most appropriate guidance it can give in the context of this rule is that employers document in the driver investigation history file their efforts to comply with the requirements to obtain the background investigation information” (69 FR 16684, 16690–91).

So ignore the three-attempts folklore. There is no numeric threshold, and an auditor holding your file is not counting calls. Work the standard that does exist — the content standard at 391.23(c)(2). Each carrier “must make a written record with respect to each previous employer contacted, or good faith efforts to do so,” showing the employer’s name and address, the date contacted or the attempts made, and the information received. Failures must be documented. Then add the escalation the regulation itself endorses: 391.23(c)(3) says prospective employers “should report failures of previous employers to respond to an investigation to the FMCSA and use the complaint procedures specified at § 386.12,” and “keep a copy of the reports in the driver investigation history file as part of documenting a good faith effort.”

The record is the deliverable, not the answer. A file with four documented non-responses and one reply is compliant. A file with five phone calls nobody wrote down is not, even if all five employers answered.

It helps that the other side is on a clock. 391.23(g)(1) requires a previous employer to respond within 30 days of receiving the request — and to respond even with nothing to report: “previous motor carrier employers are nonetheless required to send a response confirming the non-existence of any such data, including the driver identification information and dates of employment.” Silence is not a permitted answer. When the request lands on your desk instead, paragraph (g) runs the duties the other way: respond in 30 days, take the precautions reasonably necessary to ensure the records are accurate, provide contact information in case the driver seeks correction or rebuttal, and keep a record of each request and response for one year (391.23(g)(2)–(4)).

Which clocks are running, and where do the records live?

The due process clocks do not eat your 30 days. 391.23(c)(1) says any period required to exercise the driver’s rights to review, correct or rebut “is separate and apart from this 30-day requirement.” You do not get to file late because he disputed something.

Two frequent errors sit around that table. The driver qualification file has exactly eight enumerated items at 391.51(b)(1) through (b)(8), and safety performance history is not one of them. And 49 CFR 391.27, the annual list of violations many checklists still carry, is currently [Reserved] — FMCSA rescinded it in the Record of Violations final rule, effective May 9, 2022 (87 FR 13192). The agency kept 391.21 and 391.23 in place and noted that removal “does not preclude employers from requiring their drivers to provide a list of their traffic convictions as a condition of employment.” Keep collecting it if it is useful. Stop calling it a federal requirement.

What is your exposure if the file is short?

Direct, and not measured by the acute/critical list. 391.53(d) requires you to make everything in the investigation file available to an FMCSA representative or special agent, a State or local enforcement representative, or an authorized third party, “upon request or as part of any inquiry within the time period specified by the requesting representative.” Whatever window they name is your window.

Be precise about severity. On FMCSA’s List of Acute and Critical Regulations in 49 CFR part 385, appendix B, the driver-file items scored critical are 391.51(a), 391.51(b)(2) and 391.51(b)(6). Neither 391.23 nor 391.53 appears anywhere in part 385, so the investigation carries no acute or critical weight in the safety management controls calculation. That is not the same as free: it is still a violation, still producible on demand, and still the document plaintiff’s counsel asks for first after a crash. Penalty amounts are adjusted for inflation on a recurring schedule, so pull the current figure from FMCSA’s published penalty schedule rather than from any article, including this one.

Doing it properly also buys something. 391.23(l) bars actions for defamation, invasion of privacy or interference with a contract based on furnishing or using information in accordance with the section, protecting both the carrier investigating and the carrier furnishing — but paragraph (l)(2) withdraws that protection from anyone who knowingly furnishes false information “or who are not in compliance with the procedures specified for these investigations.” Answer reference calls off the cuff, outside the framework, and you have given up the shield.

One absolute limit on use: under 391.23(k) the information from the (d) and (e) investigations may be used “only as part of deciding whether to hire the driver,” and you “may not provide any alcohol or controlled substances information to the prospective motor carrier employer’s insurer.” Underwriters ask. On that category the answer is no: 391.53(a)(1) lets your insurer reach the investigation file, “except the alcohol and controlled substances data.”

What does a complete verification file still not tell you?

Whether the driver was any good to employ. Work every step above perfectly and look at what you hold: identity confirmed, dates confirmed, accident register entries for three years, drug and alcohol history, a driving record. 391.23(d) lists two items and 390.15(b)(1) lists six data fields, and none of the eight describes behavior.

Consider what generates no entry anywhere in that file. A driver who left a loaded trailer at a truck stop and stopped answering the phone — the scenario in our first 24 hours of a truck abandonment piece. A driver who no-showed three dispatches in his last month. A driver who quit inside the first pay cycle at four carriers running, visible as a pattern of dates and invisible as a reason, because “reason for leaving” is whatever he wrote.

That is the layer carrier-written reviews are for. A driver reputation search returns what other carriers wrote about employing the same person, tied to the period they employed him. Where the 391.23 response says he was employed March to November with one recordable accident, peer-submitted feedback speaks to why November was the end of it. Our notes on reading truck driver reviews cover how to weigh them, and what a bad hire actually costs covers why it is worth five minutes.

State the boundary plainly, because it matters more here than anywhere else in the process. This is an additional layer on top of the mandatory record, not a substitute for any part of it. It does not satisfy 49 CFR 391.23(a)(2), does not replace a previous-employer investigation, and does not discharge a single deadline in the table above. Run it after the required inquiries are out the door, use it to shape the questions on the next call, and 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 obligations attach.

Frequently asked questions