Truck Driver Application: Verify It Before You Hire

The truck driver application is filled out, signed, and sitting on your desk. Every line on it is a statement made by the person who wants the job, and not one of them has been checked yet.

That is the whole problem with the document. Under 49 CFR 391.21(b)(12) the applicant certifies that everything on the form is “true and complete to the best of my knowledge,” and that certification is the only thing standing between you and a rewritten timeline. Meanwhile a clock is running: the previous employer replies — or documented good faith efforts to get them — and your MVR both have to be in the file within 30 days of the date employment begins under 49 CFR 391.23(b) and (c)(1). That is not much room to discover on day 26 that two of the four employers listed do not exist.

This is not a guide to what the application must contain — for that, check your form against the twelve items in 391.21(b). This is what you do with it once signed.

What does a signed truck driver application actually prove?

It proves the applicant is willing to certify a version of the last decade in writing. That is genuinely useful, and it is not evidence. Read 49 CFR 391.21(b) and what you have is a structured set of assertions: identity and 3 years of addresses; each unexpired CMV license or permit; the nature and extent of driving experience; 3 years of accidents; 3 years of non-parking violations; and a statement detailing any denial, revocation or suspension of driving privileges, or that none occurred (49 CFR 391.21).

Notice what the regulation never says: that any of it is true. The form is furnished by you, completed and signed by the applicant, and it ends with the certification language in paragraph (b)(12). The verification apparatus in Part 391 sits downstream of it precisely because the document is self-reported. So read a completed application as a work queue: each block maps to a record elsewhere that can confirm or contradict it.

One field carries different weight. Paragraph (b)(10) is the only one paragraph (d) singles out: before the application is submitted you must inform the applicant that the (b)(10) information may be used and previous employers contacted to investigate safety performance history under 391.23(d) and (e), and you must notify the driver in writing of the due process rights in 391.23(i). If that language is not printed on your form, fix the form first.

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

Three years of all employment, plus seven additional years of CMV driving only. This is the most misquoted requirement in driver hiring, and it costs you in both directions: collect too little and fail an audit, or chase a decade of restaurant jobs no rule asks about.

Paragraph (b)(10) requires the names and addresses of the applicant’s employers during the 3 years preceding the date the application is submitted, the dates employed, the reason for leaving, and — after October 29, 2004 — whether the applicant was subject to the FMCSRs at that employer and whether the job was designated as a safety-sensitive function in any DOT-regulated mode subject to part 40 testing. No qualifier limits that list to driving jobs. If he stocked shelves for eight months, it belongs there.

Paragraph (b)(11) is narrower and longer. For drivers applying to operate a CMV as defined by part 383, it requires the names and addresses of employers during the 7-year period preceding the 3 years in (b)(10) — but only those “for which the applicant was an operator of a commercial motor vehicle,” together with dates of employment and reasons for leaving. Ten years total on the page, two different questions asked.

A second rule produces the same “10 years” from a different direction, and conflating the two is where the confusion starts. Under 49 CFR 383.35, any person applying for employment as a CMV operator must present 10 years of previous CMV employment history at the time of application, and paragraph (b) puts an affirmative duty on you: all employers “shall request” that information from all applicants. The driver owes you the 10-year CMV list; your driver employment application form is where you collect it.

Block on the form	Period	Scope	Where it comes from
Residence addresses	3 years	All addresses	391.21(b)(3)
Accidents	3 years	All motor vehicle accidents	391.21(b)(7)
Violations	3 years	All non-parking convictions and bond forfeitures	391.21(b)(8)
Employment history	3 years	All employers, driving or not	391.21(b)(10)
Employment history	7 more years	CMV driving only	391.21(b)(11)
CMV employment history	10 years	CMV driving only, requested by you	383.35(b), (c)

Now the part that governs your workload. The mandatory outbound contacts do not follow the 10-year list. Under 49 CFR 391.23(d) you must investigate, at a minimum, general driver identification and employment verification information plus the accident data elements specified in 49 CFR 390.15(b)(1), from all previous employers that employed the driver to operate a CMV within the previous three years. The narrower drug and alcohol items in paragraph (e) go only to previous DOT-regulated employers from those same 3 years where the job was safety-sensitive under part 40. Nothing in 391.23 sends you into years four through ten. Read the 7-year block anyway: it is free context on how long this driver stays anywhere, and it is where a carrier he would rather you not call quietly disappears.

How do you work a completed application, step by step?

Step	What you do	Status
1	Check the form for completeness before anything else	Required
2	Rebuild the timeline as dates and count the holes	Smart
3	Split the employer list into the mandatory 3-year set and the rest	Required
4	Test the self-reported records against the government ones	Required
5	Read the reasons for leaving against what came back	Smart
6	File the application and the investigation in the right two places	Required

Check the form for completeness before anything else

What you do: run the application against the paragraph (b) list line by line before you spend a minute on verification. Missing license expiration date, a blank reason for leaving, an accident block left empty instead of marked “none,” an unsigned certification. Send it back the same day with the specific gaps named.

Status: required. 49 CFR 391.51(b)(1) requires the driver qualification file to contain the application for employment “completed in accordance with § 391.21.”

The gotcha: paragraph (b)(9) is the one people leave blank. It requires either a detailed statement of the facts and circumstances of any denial, revocation or suspension of a license, permit or privilege to operate a motor vehicle, or an affirmative statement that no such event occurred. A blank is not “no.” It is an incomplete application, and it is also the field the MVR is about to contradict if the applicant was hoping you would skip it.

Rebuild the timeline as dates and count the holes

What you do: ignore the employer names and lay the dates out as a line running back from today through the 3-year window. Mark every month not covered by an entry, then every month covered by two entries at once. Both are questions.

Status: smart practice. No FMCSA rule sets a maximum unexplained gap or requires a gap explanation form, so the threshold you use is your policy, not a federal one. Write it down and apply it to every applicant identically.

The gotcha: the gap is not the finding. A driver laid off for five months, or out after surgery, has an ordinary hole in the line. What you are looking for is a gap that moves — an end date at one carrier stretched forward and a start date at the next slid backward, so a three-month job in between never has to be listed. Ask for the month and year of each start and end, not just the year, and the overlap becomes visible immediately.

Split the employer list into the mandatory 3-year set and the rest

What you do: take the (b)(10) list and pull out every employer that put this driver in a commercial motor vehicle during the preceding 3 years. That subset is your 391.23(d) call list. Note the tension in the section: 391.23(a)(2) frames the underlying inquiry as covering DOT-regulated employers, and (c)(4) is written around that same universe, so whether a purely intrastate, non-DOT-regulated employer sits inside the mandatory set is not settled on the face of the rule. Contacting them anyway is the conservative call; confirm your policy with counsel. Build the written contact log before the first letter goes out, with a row per employer: name, address, date contacted or attempted, what came back. Then send requests containing specific contact information telling the previous employer where to send the response, which 391.23(d) requires on its face.

Status: required. The investigation may be interviews, phone calls, letters or any other method you deem appropriate under 391.23(c)(2) — but the written record of each contact and attempt is not optional, and failures to reach an employer must be documented.

The gotcha: you are about to wait. Previous employers must respond within 30 days of receiving the request under 391.23(g)(1), including a response confirming there is nothing to report. That is a long time to sit on a decision, so work the list informally on day one. A look at carrier-written driver reviews while the formal requests are in flight tells you which of those names other carriers have written about, and whether it lines up with the reason for leaving on your form. That is triage for sequencing your calls, not a substitute — the 391.23(d) requests still go to every one of them.

Test the self-reported records against the government ones

What you do: order the records the applicant did not write, and read them against the matching blocks on the form. The MVR inquiry goes to each state where the driver held a license during the preceding 3 years and must be in the driver qualification file within 30 days of the date employment begins, covering the prior 3-year driving history (391.23(a)(1) and (b)). The Drug and Alcohol Clearinghouse pre-employment full query, with the driver’s specific consent, must happen before the driver performs any safety-sensitive function (49 CFR 382.701(a)). PSP adds FMCSA roadside inspection and crash data under its own separate written consent.

Status: required for the MVR and the Clearinghouse query. PSP is optional and it is the fastest independent test of the accident and violation blocks.

The gotcha: these records answer the form’s questions imperfectly, and the mismatch is informative rather than damning. The MVR shows convictions the state recorded, not everything the driver was cited for; PSP shows roadside inspections and DOT-recordable crashes, which is not the same universe as the “all motor vehicle accidents” that (b)(7) asks about. A fender-bender in a personal car belongs on the application and appears in neither system. Our walkthroughs on running the MVR check and pulling a PSP report cover what each one carries. And if you order any of this through a background screening company, the FTC is explicit that the written disclosure must be stand-alone and cannot be in the employment application (FTC).

Read the reasons for leaving against what came back

What you do: put the applicant’s stated reason for leaving each carrier next to that employer’s response for the same period, and treat every divergence as a question for the driver rather than a verdict. Ask it directly and write down the answer.

Status: smart practice, and where most of the decision quality actually lives.

The gotcha: a previous employer’s answer to 391.23(d) is narrow by design — identification, employment verification and accident data, not a performance review. A carrier that thought the driver was a headache but had nothing recordable will send a clean, honest response. A purchased screening report, meanwhile, may carry a “not eligible for rehire” flag that no federal rule defines; our breakdown of DAC report flags covers how to work one. If the reason for leaving involves a load left somewhere, the first 24 hours of an abandonment explains what the other carrier’s file looks like.

File the application and the investigation in the right two places

What you do: the signed application goes in the driver qualification file under 49 CFR 391.51(b)(1). The investigation material — the driver’s written authorization for the alcohol and controlled substances inquiry required by 391.23(f)(1), every previous employer response, and the contact log documenting attempts and non-responses — goes in the driver investigation history file, a separate file under 49 CFR 391.53.

Status: required, and so is the separation. Under 391.53(a) the investigation file must be kept in a secure location with controlled access, limited to people involved in the hiring decision or who control access, and used only for that decision.

The gotcha: the retention clocks are long and there is more than one. The qualification file is kept as long as the driver is employed and 3 years afterward (391.51(c)), with a carve-out in 391.51(d) letting certain medical and annual-review records come out three years after execution; the safety performance histories carry the same rule (391.53(c)); Clearinghouse query records run 3 years (382.701(e)). And if the driver was never hired, the FTC still expects secure disposal of any consumer report you ordered and the information gathered from it.

What does a rewritten timeline look like on the page?

It looks like arithmetic that almost works. Here is the same 3-year block, filled out two ways.

The version that should stop you. Carrier A: “2023 to 2024, reason for leaving: better opportunity.” Self-employed owner-operator: “2024 to 2025, reason for leaving: n/a.” Carrier B: “2025 to present.” No months anywhere. The self-employed block covers the exact window a fourth carrier would sit in, and because there is no employer to contact, there is nothing to request.

The version you can work. The same driver, asked for month and year: Carrier A, March 2023 to August 2024. Owner-operator under his own authority, September 2024 to January 2025, with a DOT number he can name. Carrier B, February 2025 to present. Now the self-employed period is checkable — operating authority is a public record, and a driver leased to a carrier in that window was operating that carrier’s CMV, which puts it inside your 391.23(d) list.

The lesson is not that self-employment is suspicious. A period with no named employer is the only block that generates no outbound request, which makes it the cheapest place to hide a job. Ask what equipment, under whose authority, and hauling for whom.

What is still missing after the form, the calls, and the queries?

Everything about how the driver actually worked. Complete the procedure above and you have verified identity, dates, licensure, crashes, convictions and drug and alcohol status. You have not learned whether this driver answers the phone, brings the truck back in one piece, or is still with you in ninety days. None of it is a reportable event, and the previous employer who found him exhausting will still send an accurate, unremarkable response.

There is a second structural hole: the mandatory contacts only reach employers the applicant listed. An omitted carrier generates no request, and the route when a listed employer ignores you is a complaint to FMCSA under 49 CFR 386.12 — useful for showing good faith at audit, useless for deciding this candidate today.

That is the gap a first-party behavioral layer is built for. Any carrier can leave a review on cdlscan, not only companies that subscribe to a screening database or answer their mail, so a carrier missing from the application can still leave a trace you can read. When the employment history is thin and every response comes back neutral, looking the driver up is often the only independent signal available.

Say the boundary plainly. This is an additional layer of evidence, not a replacement. It does not satisfy 49 CFR 391.23 and it does not substitute for the previous employer investigation, the MVR, or the Clearinghouse query. If you rely on any third-party information in a hiring decision, ask the provider which category of data it believes it is supplying, and confirm with counsel which FCRA obligations attach. Run the required checks exactly as written, then use the behavioral layer for the questions those checks were never designed to answer — our overview of how carrier-written driver reviews work explains what it does and does not contain.

How do you know the application file will hold up?

Test the file, not the hire. Before you sign off on a driver employment application, six things should be true.

Every paragraph (b) field is filled in, including an affirmative “none” where nothing occurred, and the certification carries a date and a signature.
The 3-year employment block reconciles month by month, with every gap and overlap either explained in writing or converted into a named employer you contacted.
Every employer that put the driver in a CMV in the last 3 years appears in the written contact log with a date and an outcome, including the ones that never answered.
The MVR and the Clearinghouse query are in the file, dated, and read against the accident, violation and license blocks on the form.
The 391.23(i) due process notice reached the driver in writing before any hiring decision.
The application sits in the driver qualification file and the investigation material sits in the separate, access-controlled driver investigation history file.

If the file fails on the second or third line, the problem is your intake process rather than this applicant, and it repeats on the next one.

Frequently asked questions

Do I have to contact every employer listed in the 7-year CMV section?

No. 49 CFR 391.23(d) requires you to investigate all previous employers that employed the driver to operate a CMV within the previous 3 years. The additional 7 years collected under 391.21(b)(11) and 383.35 is history you must obtain and read, not a mandatory call list. You may contact those employers voluntarily; Part 391 does not require it.

How big an employment gap do I have to explain?

There is no federal threshold. FMCSA does not define an unexplained gap or set a maximum, so any number you use is your own policy. Set one in writing, apply it to every applicant the same way, and document how each gap was resolved. What matters at audit is that the 3-year employment history required by 391.21(b)(10) is complete, not that the driver was continuously employed.

Can I let the driver start before the previous employer responses come back?

Yes. 49 CFR 391.23(c)(1) gives you 30 days from the date employment begins to place the responses, or documentation of good faith efforts, in the driver investigation history file. The Clearinghouse pre-employment full query under 49 CFR 382.701(a) is different: it must be completed before the driver performs any safety-sensitive function, with no grace period — and neither does 391.23(m)(1), which requires the medical examiner’s certificate and National Registry verification in the file before the driver operates a CMV.

What do I do when a previous employer never answers?

Document the attempts and keep going. 391.23(g)(1) obligates previous employers to respond within 30 days, including confirming there is no data to report. When one does not, 391.23(c)(3) says you should report the failure to FMCSA using the complaint procedures at 49 CFR 386.12 and keep a copy in the driver investigation history file as evidence of good faith.

Does the application satisfy the FCRA disclosure if I add the authorization language to it?

No, and this is a common and expensive mistake. The FTC states that the notice telling an applicant you may use a consumer report must be in a stand-alone format and cannot be in the employment application. Written permission may be part of that same stand-alone disclosure document, but not part of the truck driver application form itself.

Do I need a new application if a former driver comes back a year later?

Treat a returning driver as a new applicant unless counsel advises otherwise. A driver application is time-anchored: 391.21(b)(3), (b)(7), (b)(8) and (b)(10) measure their windows from the date the application is submitted, so a year-old form no longer covers the required periods, and the 391.23 and MVR clocks restart with the new employment date.

This article is general information for motor carrier hiring and safety staff, not legal advice. Federal regulations and their interpretations change. Verify the current text of any section on ecfr.gov and consult counsel before building a hiring policy on it. Last reviewed 2026-07.