Screening
DOT-Compliant CDL Driver Vetting Services: What You Actually Get
By Editorial Team · Updated August 24, 2026 · 13 min read · Editorial standards
On this page 9 sections
Three vendors just walked you through the same demo. Each one called the product a DOT-compliant CDL driver vetting service. Each one showed a dashboard, a green check, and a promise that the file will survive an audit. None of them opened the actual packet you would hand a compliance officer. That is the buying problem: you are shopping for a service, and they are selling a portal.
This page is the buyer’s brief. It is not a ranked vendor list, and it is not another walkthrough of every screening layer. If you need the layer map, use driver screening services. If you need the hire-day order, use the new-hire vetting checklist. Here you decide what a service must produce, how to tell a real DOT package from a relabeled background check, and what belongs in the driver vetting file template you keep even when the vendor changes.
Rules change. Verify current requirements at fmcsa.dot.gov before you act on anything in this guide.
What “DOT-compliant” means when a vendor says it
On a sales call, “DOT-compliant” usually means “we have a trucking logo and a checklist.” In the file, it means something narrower: the service can collect, retrieve, and store the documents FMCSA expects a motor carrier to have when it puts a commercial driver in a CMV.
The core of that file lives in 49 CFR §391.51. The application the driver signs is set out in 49 CFR §391.21. The investigation of the driving record and safety performance history is 49 CFR §391.23. The annual driving-record review is 49 CFR §391.25. Pre-employment drug testing sits in 49 CFR §382.301. Clearinghouse queries sit in 49 CFR §382.701. Medical qualification is 49 CFR §391.41 and the examiner’s certificate process is 49 CFR §391.43.
A service that cannot name those jobs in plain English is not selling driver vetting. It is selling a background check with a CDL field.
Two more tests, both boring and both decisive:
- Can the vendor produce an employer-facing packet that a stranger on your safety team can read without logging into their portal?
- Can they show you, on one sample file, which items they pulled, which items they only stored after you uploaded them, and which items they never touch?
If the answer to either question is a slide instead of a PDF, keep shopping.
Driver vetting vs. a background check vs. a screening package
Recruiters mash three products together because vendors mash the names.
Driver vetting is the whole pre-hire and first-year qualification job: identity, license, driving record, federal safety history, drug and alcohol status, medical card, prior-employer contact, and the folder that proves you did the work. That is the job DOT-compliant CDL driver vetting services claim to take off your desk.
A background check is usually a criminal and identity product built for offices, warehouses, and retail. Useful. Not a substitute. It will not put an MVR in the DQ file and it will not run a Clearinghouse query.
A screening package is a vendor SKU. It may cover two layers or five. The name on the invoice does not tell you which. Our driver screening services page is the layer map; this page is the purchase decision that sits on top of that map.
PSP, DAC, and a criminal search are common add-ons. They are not the definition of compliant. Treating a PSP as “the vetting” is how a file looks busy and still fails the parts FMCSA actually wrote down. For the report itself, see what a PSP report is. For how it sits next to DAC and the MVR, see PSP vs DAC vs MVR.
What the service must produce, not what it must demo
Ignore the dashboard for a minute. A CDL driver vetting service earns the “DOT-compliant” label only if it can hand you these outputs for an interstate hire:
- A completed employment application that collects the license and employer history 49 CFR §391.21 requires.
- Proof the CDL is real, current, and classed for the equipment, with endorsements that match the lane.
- A driving-record inquiry from every state the application and CDLIS pointed at, plus a dated company review. That is 49 CFR §391.23 at hire and 49 CFR §391.25 every year after.
- A documented safety-performance-history investigation of prior DOT-regulated employers — requests sent, answers received, and a written note when a former carrier stays silent.
- A pre-employment Clearinghouse full query, with the driver’s electronic consent inside the Clearinghouse, under 49 CFR §382.701.
- A verified-negative pre-employment drug test under 49 CFR §382.301, or a documented exception the rule actually allows.
- A current medical examiner’s certificate that matches the person in the seat (49 CFR §391.41, 49 CFR §391.43).
- A driver qualification file that holds the copies and the review notes (49 CFR §391.51).
Optional, and still worth buying if the vendor does them well: a PSP, an employment-history report such as DAC, and a criminal search where your lane or insurer asks for one. None of those three close the required list.
If a sales engineer cannot walk a sample file down that list, you are not looking at DOT-compliant CDL driver vetting services. You are looking at a recruiting CRM with a screening tab.
Driver vetting file template
Print this. Put it in the first sleeve of every new DQ file. Make the vendor map their product to the rows. Empty rows are the negotiation.
| File item | Required or optional | What “done” looks like | Who usually pulls it |
|---|---|---|---|
| Standalone FCRA disclosure and written authorization | Required if a CRA pulls consumer reports | Signed forms, dated before the first report | You, or the vendor’s workflow |
| Employment application | Required | Complete license and employer history, signed | Vendor application or your ATS |
| CDL / CDLIS verification | Required | Class, endorsements, one-license check | Vendor or state channel |
| MVR from each relevant state | Required | Record plus a named official’s dated review | Vendor or DMV |
| Safety performance history | Required | Requests, replies, and good-faith notes | Vendor letters or your safety desk |
| Clearinghouse pre-employment full query | Required | Query result in the file before safety-sensitive work | Vendor as your C/TPA, or you |
| Pre-employment drug test | Required | Verified negative, or a documented exception | Clinic / C/TPA |
| Medical examiner’s certificate | Required | Current card that matches the driver | Examiner; you verify |
| Road test or accepted equivalent | Required unless the rule lets you accept another carrier’s | Certificate in the file | You, or a previous qualified employer |
| Annual MVR review | Required after hire | Fresh inquiry and signed review | Vendor reminder plus your official |
| PSP report | Optional | Crash and inspection extract, read against volume | FMCSA or vendor |
| DAC / employment database | Optional | Dates, reason for leaving, rehire flag — treated as testimony | HireRight or similar |
| Criminal / Hazmat check | Optional except where your lane demands it | Report plus adverse-action file if you say no | CRA |
| Peer driver reviews | Optional | Notes from past carriers on no-shows and dumped loads | CDLScan |
That table is the product. A portal is only useful if it fills the table and exports it.
Two rows get skipped more than any others. The first is the signed review of the MVR. Vendors love to deliver the PDF and call the layer closed. An unread MVR is not a review under 49 CFR §391.23 or 49 CFR §391.25. The second is the silent prior employer. A blank “we called” line is not an investigation. Write the name, the address, the date, and what came back — including nothing.
The rest of the DQ file — medical follow-up, random testing under 49 CFR §382.305, accident register notes — is operations after the hire. Do not let a vetting vendor sell you those as if they were the pre-hire package. For the folder itself, use DOT driver qualification file.
How to score a vendor without a beauty contest
You do not need a ranked list. You need seven answers in writing. Ask every bidder the same questions and keep the replies next to the template.
Make them itemize the layers
What you do: send the template above and ask which rows they pull, which they only store, and which stay on you.
The gotcha: a single line item called “DOT package.” That is a price, not a scope.
Separate data they own from data they broker
What you do: ask who the source is for the MVR, the PSP, the Clearinghouse query, and the employment history. Same DMV, same FMCSA systems, same Clearinghouse. The vendor is selling access and workflow.
The gotcha: marketing that sounds like they invented the federal databases. They did not.
Watch the FCRA workflow
What you do: if the service is a consumer reporting agency, confirm standalone disclosure, written authorization, and a complete adverse-action sequence when a report is why you decline. The FTC employer guidance is the public reference. A Clearinghouse query runs on its own consent rules; do not treat that consent as FCRA coverage for the rest of the stack.
The gotcha: a disclosure buried inside the employment application. That is how class actions start.
Demand an export you can keep if you fire them
What you do: have them generate one redacted sample file as a zip or PDF packet: application, MVRs, investigation notes, query result, drug-test result, medical card, review signatures.
The gotcha: “everything lives in the portal.” Portals get cancelled. Audits do not.
Check who still has to click
What you do: list the actions that still require a company official — MVR review, hire / no-hire, adverse action, Clearinghouse registration, medical-card follow-up. A honest vendor will leave those on you.
The gotcha: language that says the service “keeps you compliant.” It keeps documents. You stay compliant.
Look for double-pulls
What you do: compare the quote to your insurance program and your C/TPA. MVRs are the usual duplicate.
The gotcha: paying two intermediaries for the same state record and calling both of them vetting.
Names you will hear — HireRight, Foley, Cisive, First Advantage, CDLSuite, and a long tail of MVR shops and C/TPAs — overlap on some layers and not others. We do not rank them here. Rank the file they produce against the template. The how to run a CDL background check walkthrough is the DIY version of the same stack if the quote is really just charging you for work you already do.
What even a good service cannot sell you
A finished template means no institution has recorded a problem. That is a high bar, and it is still not a prediction.
License data does not know the driver ghosted after orientation. A PSP does not know they sat on a load. A Clearinghouse query does not know they quit mid-route. A DAC is only as complete as the carriers who bother to report. Prior-employer letters often come back with dates of employment and nothing else because counsel told the last safety manager to stop talking.
That silence is not a vendor failure. It is what records are. Records appear when a state, a roadside inspector, a medical examiner, or a lab writes something down. Walking away from a truck never becomes a line on those systems.
So you run every required check, you file every required copy, and then you look up the driver on CDLScan for the peer layer: no-shows, abandoned loads, quit-on-dispatch, equipment condition, whether a past carrier would take them back. Search is the cheap pass; a full report starts at $2.75. It does not satisfy 49 CFR §391.23. It is not a Clearinghouse query. It will not put an MVR in the DQ file. Read it as a lead for the interview, the same way you read a DAC.
A working buy for a small safety desk
You do not need the most expensive package to be legal. You need the required rows closed before the driver performs a safety-sensitive function, and you need a file someone else can reconstruct.
A lean, still-compliant buy usually looks like this:
- Your own Clearinghouse registration, or a C/TPA that queries as your agent
- MVRs and a CDLIS pointer through one vendor you already trust
- Prior-employer letters you send on your letterhead even if the vendor drafts them
- Medical card and drug test through the clinic / C/TPA you already use
- PSP when the lane or the insurer cares about roadside history
- A peer-review search after the required stack, not instead of it
That split is how a ten-truck fleet stays honest. A hundred-truck fleet may still want one portal — not because the data is different, but because the labor and the FCRA letters are. Either way, keep the template. The service is a contractor. The file is yours.
If a bidder cannot fill the template, keep the money and run the trucking new-hire vetting checklist yourself until one can.
Frequently asked questions
What are DOT-compliant CDL driver vetting services?
They are vendors that collect, retrieve, and store the documents a motor carrier needs to qualify a CDL driver under FMCSA hiring rules — application, license check, MVRs, prior-employer safety history, Clearinghouse query, drug test, medical card, and the DQ file that holds them. A dashboard without that packet is recruiting software, not vetting.
Do I have to hire a vetting service to be DOT compliant?
No. The rules sit on the carrier, not on a contractor. You can pull MVRs, run Clearinghouse queries, send prior-employer letters, and keep the DQ file yourself. A service is worth it when the volume, the FCRA workflow, or the reminder system costs less than the mistakes you make by hand.
What belongs in a driver vetting file template?
The required DQ items first: application, CDL verification, MVRs with a signed review, safety-performance history, Clearinghouse query, pre-employment drug test, medical certificate, and road-test proof. Then the optional rows — PSP, DAC, criminal, peer reviews — so nobody pretends an add-on closed a required line.
How is a CDL driver vetting service different from a background check company?
A background check company is built around criminal and civil records. A CDL driver vetting service is built around FMCSA hiring work: state driving records, safety performance history, Clearinghouse queries, and a file an auditor can read. Using only a general screener leaves the federal rows empty.
Can a vendor make us DOT compliant by contract?
No. They can pull data, store documents, generate letters, and remind you about annual reviews. A company official still has to review the driving record, decide the hire, and keep the file. “We keep you compliant” on a website is marketing.
Is a PSP enough driver vetting?
No. A PSP is an optional extract of federal crash and roadside-inspection data. It does not replace the MVR, the prior-employer investigation, the Clearinghouse query, or the medical card. Useful. Not the stack.
Where does CDLScan fit next to a vetting service?
After the required checks. Vetting services sell records. CDLScan collects peer reports on how the driver actually worked — the no-shows and dumped loads that never become a conviction or a lab result. It does not replace any FMCSA step.
What should I ask before I sign?
Which rows of the file template they pull, which they only store, whether you can export a complete packet if you leave, who reviews the MVR, and whether your insurer or C/TPA already buys the same MVR. If they will not itemize, do not sign.