Driver Rehire Eligibility & "Do Not Rehire" Flags

A “not eligible for rehire” flag is the fastest yes/no signal in driver screening — and one of the easiest to misread. It can tell you a former carrier wouldn’t take a driver back, which feels decisive. But it’s one employer’s judgment, not a verified fact, and it almost never tells you why. Here’s what driver rehire eligibility actually means, where the flag shows up, how much weight it deserves, and what you need alongside it before you turn a candidate away.

What “eligible for rehire” means

Rehire eligibility is a former employer’s answer to one question: would we take this person back? In trucking it’s usually recorded as a simple code — Yes, No, or Review/Conditional — attached to a driver’s separation from a past carrier. “Eligible for rehire” means the carrier has no standing objection to working with the driver again. “Not eligible for rehire” — the flag recruiters react to — means that carrier has decided it would not.

The key thing to understand is that this is a judgment, not a fact. A driver doesn’t earn the flag by failing an objective test. A safety manager or HR coordinator assigns it based on how the driver’s tenure ended — a policy violation, a pattern of no-shows, an abandoned load, a bad attitude, or sometimes nothing more than a personality clash or a missed two-week notice. Two carriers could rate the identical separation differently. That’s why the flag is a starting point for questions, not the answer to them.

It also helps to separate rehire eligibility from the reason a driver left. “Reason for leaving” is descriptive — quit, terminated, laid off, mutual. Rehire eligibility is prescriptive — the carrier’s recommendation about the future. A driver can quit voluntarily on good terms and still be marked “not eligible” if their attendance was a problem, and the two fields don’t always line up cleanly.

Where the rehire flag shows up

For CDL (commercial driver’s license) hiring, driver rehire eligibility surfaces in two main places: the DAC report and direct reference checks. Each has different reliability.

The DAC report is the big one. DAC stands for Drive-A-Check, an employer-reported history file now run by HireRight that most mid-to-large carriers pull on applicants. Alongside employment dates, reason for leaving, and DOT-recordable accidents, the DAC report carries an eligibility-for-rehire field — and it’s the single line recruiters fixate on. Because it’s the most prominent place the flag lives, it’s worth understanding the full record: our DAC report explainer breaks down everything a DAC file shows and what it leaves out.

The second place is the reference check — the call or form you send to prior employers. In theory this is where a “would not rehire” gets explained. In practice, many carriers (on advice from HR or legal) confirm only dates of employment and job title, and answer the rehire question with a curt “no comment” or a bare “not eligible,” fearing a defamation claim. So the flag often arrives stripped of context from both sources at once: a coded “No” on the DAC, and a reference that won’t elaborate.

A practical note on weight: the same driver can carry an “eligible” flag from one carrier and a “not eligible” from another. Read the whole pattern, not a single line. One “no” among four “yes” results is a very different signal than three carriers in a row declining to rehire.

Why a “do not rehire” flag matters — and how reliable it is

A “do not rehire” flag matters because, treated correctly, it’s a cheap early warning — and because, treated carelessly, it’s a liability. On the upside, a pattern of “not eligible” results can flag the behaviors that sink most trucking hires before you spend a dollar on orientation: chronic no-shows, abandoned loads, repeated short stints. On the downside, a flag is only as reliable as the person who entered it and the reason behind it.

Here’s the reliability problem in plain terms. The flag is unverified, subjective, and sometimes retaliatory. It reflects one former employer’s view of a separation that may have been mutual, disputed, or about something that has nothing to do with how the driver performs for you. Entries get filed in anger — a truck returned in good condition and logged as “abandoned” is a documented failure mode. And many small and mid-size carriers don’t report to DAC at all, so the absence of a flag means little, and the presence of one says only that somebody chose to enter it.

There’s also a hard legal edge. Because the flag travels through a consumer reporting agency, rejecting a driver over it without following the rules creates exposure. Federal courts have heard FCRA disputes over exactly this kind of trucking safety-history entry — in Maiteki v. Marten Transport, a driver challenged the accuracy of his reported record and forced a reinvestigation. The lesson for employers: a rehire flag is evidence to weigh, not a verdict to rubber-stamp.

Disputing and contextualizing the flag (FCRA)

The Fair Credit Reporting Act (FCRA) is the federal law governing consumer reports used for employment, and it puts real duties on both the driver and you. When a DAC entry — including a rehire flag — is wrong, the driver can dispute it: they flag the entry with HireRight, submit documentation, and the agency must conduct a reasonable reinvestigation, generally within 30 days, then correct or delete anything it can’t verify. (That window can extend up to 15 additional days if the driver supplies more information mid-investigation.) The full driver-side and employer-side process is laid out in our guide on how to get and dispute a DAC report.

Your obligations as the employer are just as concrete. Before you decline a candidate because of a consumer report:

• Get written consent before pulling the report.
• Send a pre-adverse-action notice with a copy of the report and a summary of the driver’s FCRA rights, and give them a reasonable window to respond.
• Send a final adverse-action notice if you proceed.

This isn’t optional paperwork. In 2012 the FTC fined HireRight $2.6 million for failing to assure accuracy, give consumers their reports, and reinvestigate disputes — a reminder that the data behind these flags isn’t infallible. So when a candidate tells you a “not eligible” flag is wrong and is actively disputing it, that’s not automatically a red flag. Inaccurate and contested entries are common enough that the dispute process exists for a reason.

Filling in the “why”: peer-review context

The structural weakness of a rehire flag is that it’s a verdict with the evidence removed. “Not eligible” — but for what? An abandoned load tells you to slow down; a personality clash with one dispatcher tells you almost nothing. The flag can’t distinguish the two, and the carrier that set it usually won’t.

That’s the gap peer reviews fill. Where a rehire flag is a single coded decision, a peer-driver-review database lets you read what multiple previous carriers actually said about a driver’s reliability — whether they showed up, how they treated equipment, whether the separation was about safety or about something that won’t follow them to your fleet. It turns a binary flag into a narrative you can actually evaluate. This is the same reputation layer that formal records miss across the board, which our pillar guide on truck driver reviews covers in full, and that prior-employer feedback closes specifically in our breakdown of previous-carrier driver reviews.

Where cdlscan fits

A rehire flag is one data point. Peer reviews give you the context that makes it usable — and together they sit alongside your required checks, never in place of them. That’s the gap a peer-sourced platform like cdlscan.com is built to close. When a DAC report comes back with a bare “not eligible for rehire,” you can search a driver by name and read what previous carriers said — the reliability signals and the why the flag leaves out.

To be clear about the boundary: this doesn’t replace your MVR, PSP, DAC, or Clearinghouse work, all of which stay mandatory. It adds the reputation read those records miss, so a single unexplained flag doesn’t either sink a good driver or wave through a bad one. The peer driver-review database is free to search, and one search takes about a minute — cheap insurance against a bad hire that runs $8,000 to $50,000.

Frequently asked questions

What does “eligible for rehire” mean for a truck driver? It’s a former employer’s coded answer — usually Yes, No, or Review — to whether they’d take the driver back. It reflects how the driver’s tenure ended, not an objective test, and it’s a judgment call rather than a regulatory fact.

Where does a “not eligible for rehire” flag show up? Mainly on the DAC (Drive-A-Check) report run by HireRight, in the eligibility-for-rehire field. It can also surface in a direct reference check, though many carriers will only confirm dates and job title.

Is a “do not rehire” flag the same as the reason for leaving? No. Reason for leaving describes how the driver separated (quit, terminated, laid off). Rehire eligibility is the carrier’s recommendation about the future. A driver can quit on good terms and still be marked “not eligible,” and vice versa.

How reliable is a rehire-eligibility flag? It’s unverified and subjective — one employer’s view, sometimes filed in anger or over a personality conflict. Many small carriers don’t report at all. Treat a flag as a prompt to investigate, not as proof of a problem.

Can a driver dispute a “not eligible for rehire” flag? Yes. Under the FCRA, the driver disputes the entry with HireRight, which must conduct a reasonable reinvestigation — generally within 30 days — and correct or delete anything it can’t verify.

What do I owe a driver if I reject them over a rehire flag? The FCRA adverse-action process: written consent before pulling the report, a pre-adverse-action notice with a copy of the report and the driver’s FCRA rights, a chance to respond, and a final adverse-action notice if you proceed.

Should one “not eligible” flag disqualify a driver? Not on its own. Read the whole pattern across carriers, get the context behind the flag, and pair it with peer reviews. A single unexplained “no” among several “yes” results is a weak signal; three in a row is a strong one.

How do I find out why a driver was marked “not eligible for rehire”? The flag itself rarely explains the why. Combine the reference attempt (documented for compliance), the rest of the DAC record, and peer reviews from a driver-review database, where previous carriers describe what actually happened.