What Employers See on a Commercial Driver DAC Report

The PDF is open on the second monitor. Three carriers. The application listed two. The middle job ends in “job abandonment.” Rehire on the last one is “no.” The candidate is in the lobby, and the offer letter is sitting in the ATS with a cursor in the start-date field.

This is not another explainer of what the file is, how a driver pulls a copy, or how a dispute works. Those live in our DAC report overview and in how to get a free DAC report. This page is the desk view: what an employer sees on a commercial driver DAC report, and how to read dates, reason for leaving, and rehire without turning one coded line into a verdict.

Rules change. Verify current requirements at fmcsa.dot.gov before you act on anything in this guide.

What an employer actually sees on the employment block

Open a commercial driver DAC report the way a recruiter opens it: skip the product branding and go to the prior-employer rows. Each contributing carrier typically gives you who the employer was, the window they reported, how the job ended, whether they would take the driver back, and optional work-record comments.

That is the block this article is about. Accidents and drug-and-alcohol lines may sit on the same PDF. Do not let them steal the first pass. Employment history is where most bad reads happen, because it looks simple and it is not.

Two framing facts before you mark anything in red. The rows are employer-reported: a carrier that never contributed will not appear, and a thin file is not proof of a thin career. And the rows are not the investigation. 49 CFR §391.23 still requires you to investigate safety-performance history with prior DOT-regulated employers. A commercial driver DAC report can help you see who those employers were. It does not close the check. If you need the product definition or the driver-side copy-and-dispute path, use the two guides linked above.

How to read employment dates

Dates are the least dramatic field and the most useful. Read them as a timeline, not as a list of stamps.

Line the DAC dates against the application. A missing job on the application that appears on the DAC is not automatically fraud — people forget a short lease-on — but it is a question you ask before you issue a number. A job on the application that never appears on the DAC is even more common: that carrier may not report. Do not treat silence as confirmation.

Measure tenure, not just calendar years. A long run at one fleet with a clean exit is not the same as the same span split across six fleets. One short stint is a conversation. A staircase of short stints with the same exit code is a pattern. Watch the seams: a short gap after a resignation can be a truck ride home; a long dark gap after “job abandonment” is a different shape. Overlapping dates can be a second job, a lease that was never closed, or two carriers reporting the same contract. Overlap is a prompt to ask who actually controlled the dispatch, not a verdict.

End dates lie in small ways. Some contributors report the last dispatch, the last paid day, or the day the truck was recovered. If the candidate says they turned the truck on a Friday and the DAC ends later, you may be looking at a yard date, not a walk-off. And “still employed” is a field, not a vibe: if a row says the driver is still there and the candidate is in your lobby, get the leave story before you call.

What you do: build a single timeline — application on the left, DAC dates on the right, gaps and overlaps circled. Do not score the file until the timeline exists. The gotcha: recruiters skip dates because rehire is louder, and then they reject a driver for one angry supervisor while missing the stable years on either side.

How to read reason for leaving

Reason for leaving is a label a former employer chose. It is not a police report. Read the label, then read it against the dates.

Resigned or voluntary quit is the ordinary exit — ask why, and whether notice was given. Terminated or discharged is the one people over-read: fired after a preventable crash is a safety conversation; fired after a dispatch argument is a management conversation; the DAC line will not tell you which. Layoff or end of contract is common with dedicated accounts; pair it with tenure. Job abandonment is the code to take seriously and still verify — it is used for a dumped load, a missed check-in, and, in ugly files, a truck that was returned and logged as missing. Ask where the truck was and whether freight moved. Blank or “other” is not clean. Treat it as unknown, not as fine.

Never let a single reason-for-leaving code hire or kill the candidate by itself. Compare it to the application. Matching stories help. Vague matching stories (“better opportunity”) help less. Conflicting stories are the work. Drivers who want to see or correct their own file should use HireRight’s consumer process — covered in how to get a free DAC report. Your job is narrower: do not treat an unexamined code as a fact.

How to read rehire eligibility

Rehire is the line most recruiters stare at, and it is the line most likely to be someone’s mood. Typical values cluster around eligible, not eligible, and some flavor of “review.”

“No” is a question, not a disqualification. A former carrier can mark a driver ineligible because of a crash, a policy, a pay issue, a personality clash, or a blanket no-rehire rule. Those are not the same risk. “Yes” is not a character reference — it can mean “we would take them tomorrow” or “we rehire almost everyone.” A yes next to a very short tenure is a weak compliment. “Review” means someone wants a phone call. Do not translate it as “probably fine.” Call. If they will not talk, document the attempt as part of your §391.23 investigation. Silence is a result you record, not a pass you invent.

Watch for pattern versus spike. One “do not rehire” in a long file is often a single relationship that ended badly. Several in a row is a different file. Weight a mega-carrier code differently from a small-fleet owner’s.

Line-art sketch of a fuel gauge on a truck dashboard

Read the three fields as one sentence, then act

The mistake is scoring fields in isolation. The useful unit is one prior job, spoken as a sentence: a long run, resigned, eligible; three weeks, job abandonment, do not rehire; years on a dedicated account, layoff, eligible.

A long tenure, ordinary resignation, and eligible rehire is a stable chapter — still screen, but do not hold the offer hostage to that row. A short tenure plus abandonment plus do-not-rehire is a chapter you unpack: last load, last check-call, where the truck went — asked of the candidate and of the carrier. If the stories match, you have a fact. If they do not, you have a dispute, and a commercial driver DAC report is not where you resolve it. When the fields argue with each other — long tenure, termination, still eligible — believe none of them until a human explains the argument.

Build the side-by-side before you judge

Split-screen the application and the commercial driver DAC report. Mark every DAC row as matches, missing on application, missing on DAC, or dates disagree. Matches move on. Missing-on-DAC means the carrier may not report. Missing-on-application means ask why it was left off. Date disagreements mean whose end date is this. Do not start the rehire debate until this grid exists.

Interrogate the ugly rows, then finish §391.23

Pick the rows that change the decision: short tenure, abandonment, termination, do-not-rehire, comments that sound like a fight. Ask the candidate those rows first, then use them as the agenda for prior-employer contacts. Keep the questions operational: last load, who had the truck, whether the driver was paid through the reported end date, and whether that carrier would put them in a truck tomorrow.

Then finish the line recruiters skip when the DAC looks “complete.” A commercial driver DAC report is a consumer report from participating employers. §391.23 is a federal investigation of driving record and safety-performance history. They are not the same work. DAC does not replace 391.23. Use the DAC rows as a map of who to contact. Document what came back, including “no response.” Accident history still has to be asked of prior FMCSA-regulated employers. Drug-and-alcohol program history is its own channel through the Clearinghouse. If you need the wider stack, use PSP vs DAC vs MVR. If the DAC is thin, you have more investigation to do, not less.

What the employment block still will not tell you

Even a dense commercial driver DAC report is silent on the behaviors that wreck a first week: no-show for orientation, ghosting after the first dispatch, attitude toward customers, and whether other recruiters would actually take the driver back. Former dispatchers know those things. They almost never type them into a DAC field.

That is the gap a peer-sourced driver-review database is built to fill. After you have read the dates, the exit, and the rehire code, search the driver on CDLScan by name. It does not replace HireRight, the MVR, PSP, or the Clearinghouse. It adds the reputation layer those records miss. Search is available without buying a full report; the full report is the paid layer.

You read the file instead of reacting to it if your ATS note can answer four questions: which DAC jobs match the application, which single row changes the hire, what the candidate and the prior employer said about that row, and what you still had to complete under §391.23. If your note says only “DAC no-rehire — pass,” you flinched at a code. Required checks first. Then look up what prior carriers actually said on cdlscan.com.

Frequently asked questions

What does an employer see on a commercial driver DAC report?

The employment-history block shows contributing carriers, employment dates, reason for leaving, and rehire eligibility, often with optional comments. Accidents and drug-and-alcohol items may sit on the same PDF, but the hire decision usually turns on those three fields.

How should I read employment dates on a DAC?

Build a timeline against the application. Mark gaps, overlaps, short tenures, and end dates that do not match the driver’s story. Dates tell you where to ask questions, not whether to hire.

What does “not eligible for rehire” actually mean?

It means one former employer coded that they would not take the driver back. It can reflect a safety event, a policy, a money issue, or a personality clash. Treat it as a question, not as a federal ban.

Can I reject a driver because of one DAC exit code?

You can make a hiring decision, but you should not treat a single reason-for-leaving label as a proven fact. Ask the driver, contact the prior employer, and finish screening.

Does a commercial driver DAC report replace the 391.23 investigation?

No. 49 CFR §391.23 still requires a safety-history investigation of prior DOT-regulated employers. A DAC pull can help you see who those employers were. It does not complete the investigation.

What if the DAC is missing a job the driver listed?

Many carriers do not contribute. A missing row is a prompt to verify that employer another way, not proof the job was fake. Call, write, and document the attempt.

What if the DAC shows a job the driver left off the application?

Ask why it is missing. It may be a short lease-on they forgot, or a job they hoped you would not see. Compare dates and the exit code.

Where do I send a driver who says the DAC is wrong?

Point them to the consumer process in how to get a free DAC report. Do not become their dispute agent. Keep investigating the employment facts on your side.

What should I check after I finish reading the DAC employment history?

Finish the required federal pieces, then look for the behavior the codes omit. CDLScan is the reputation layer — prior carriers describing no-shows and dumped loads that never became a DAC field.