The application before logbook trouble and a missing fuel card

The application that later shows logbook trouble and a fuel card that never came back has a recognisable shape: a short recent stint nobody explains, a request for a card before the first load is even named, and a last employer who will not say how they ran logs. None of it is disqualifying on its own. Together it is the file worth a second call before you issue either.

This is a typical application, assembled from how logbook and missing-equipment reviews cluster together. It is not one person’s file. There is no name, no carrier, no state, and no week attached to it. If it feels familiar, that is the point of a pattern.

Among the reviews carriers left on CDLScan, 4.6% mention logbook and hours problems. That figure describes those reviews, not drivers in general: carriers write after a bad run, so the share tells you what shows up once someone bothers to report it. Inside that slice, 7.4% also mention equipment or a fuel card that never returned — 7.4% of logbook reviews, not of all reviews. Flip the pair and 9.0% of missing-equipment reviews also mention logbook trouble. Equipment or a fuel card never returned is 3.7% of all reviews. Seeing it in 7.4% of logbook reviews is about 2.0 times the chance rate. Lift is that multiplier, not the odds on your next card. How those shares are counted is on the methodology page.

Here is the application that pairing keeps producing.

What the file looks like on Monday

Two employers in the last year, maybe three. One stint is short enough that you would want a sentence about it and you do not get one. There is a hole of a few months. References are listed. They are slow. The MVR is dull. PSP is dull. Clearinghouse is clear.

The urgency is not in the reports. It is in the wallet. They can start this week. They need a fuel card on day one. Sometimes a cash advance sits in the same sentence. The truck is ready. Can you issue today.

Nothing on that page is disqualifying. Plenty of good hires need a card on day one and have a messy year. The pattern is the combination: thin recent history, slow last employer, official packet quiet, and company money pulled forward before anyone has read what previous carriers wrote about the logs.

The language that later shows up in the reviews is already sitting in that request: fuel card, cash advance, log book, ELD device, first load. The missing-equipment language is not on the application yet. It arrives after you have issued the card — return truck, return equipment, left equipment, didn’t return, refused return.

What happens after you say yes

Typical next step, still a composite: the card is issued. They take the truck. Then the logs look wrong, or the ELD gets disconnected. Sometimes they went home with the equipment. Sometimes the next line is that they left the truck.

In 36.2% of logbook reviews the carrier also mentions an abandoned truck. That is the ending you are trying not to buy. Aggression or threats sit in 22.3%. A crash or damage sits in 21.3%. Late or missed deliveries sit in 17.6%. Theft or money games sit in 15.3%. Going unreachable sits in 9.5%. In 32.7% of those same reviews the carrier also writes a verdict. Stay away and waste your time are that register — the author’s recommendation to the next recruiter, not a description of what the driver did. Read the scene. Do not hire off the temperature of the last sentence.

From the missing-equipment side, an abandoned truck sits in 36.6%. Theft sits in 20.6%. Aggression sits in 16.2%. A crash or damage sits in 14.4%. Late or missed deliveries sit in 11.4%. Logbook trouble sits in 9.0%. Going unreachable sits in 8.1%. Always name which base you are standing on.

I keep the missing card next to the logs because the card is the spend you can still stop. A disconnected ELD can leak into a filing. A fuel card that never came back usually cannot. The pairing itself is in logbook hours and missing equipment. The logbook trend is in logbook mentions that are falling, not gone. Theft in the same history is theft and logbook hours. Equipment that never returns as its own category is in a fuel card that never came back.

The share of reviews mentioning logbook and hours problems ran 5.0% in 2018, 5.8% in 2019, 6.5% in 2020, 5.5% in 2021, 5.5% in 2022, 4.6% in 2023, 4.3% in 2024, and 3.7% in 2025. I stop that line at 2025. 2020 is the high you should not smooth over. Then the share fell. 2025 is lower than 2018, not gone.

Equipment-return mentions ran 2.3% in 2018, 1.6% in 2019, 3.2% in 2020, 2.6% in 2021, 3.8% in 2022, 4.5% in 2023, 4.5% in 2024, and 3.8% in 2025. The card line did not fall with the logs. The packet you run on this application did not get any better at describing it.

Why the packet stayed quiet

PSP, an MVR, and the Clearinghouse hold what someone filed: a roadside inspection, a recorded crash, a failed test, a license action. A fuel card that never came back is an accounts-payable problem. A disconnected ELD can leak into that packet. Most of this pairing will not.

Previous-employer forms are not much better. Eligible for rehire can come back blank while the same desk will later write that the logs were wrong and the card never returned. The behavior lives in carrier-to-carrier memory. Most of that memory never becomes a query result.

A clean packet on this application means the filed items are clean. It does not mean the card will come back.

I am not going to pretend this is an independent study. CDLScan is the source, and I write from the data they share. Logbook trouble is common enough in what carriers bother to write down, a missing card rides along far above chance, and the packet you already run is designed for hours, not for the card.

What I would have done with that file

I would not reject it on sight. I would stop the issue.

Look the name up first. If previous carriers already wrote about a log book and a fuel card that never returned, the next card is a decision, not a courtesy. If the last employer will not say how they ran logs, that is not a pass. Ask how they returned equipment at the last carrier and what that desk will say about the ELD. People who left cleanly can usually tell you. People who are about to walk often skip the equipment and jump to home time.

If you already assigned a unit, freeze the next card limit until someone has looked. Then, if the write-ups are clean and the last employer talks, issue it. The point of a composite is not to make you cruel. It is to put the spend after the read.

Check the name on CDLScan before you issue the card. It takes less than a minute. On this pattern, that minute is the job.

Frequently asked questions

Is this a real driver?

No. It is a typical application built from how logbook and missing-equipment reviews cluster. No name, no carrier, no date. If your current file matches it, that is the pattern talking, not a biography.

Does 7.4% mean this application usually loses a fuel card?

No. 7.4% is the share of logbook reviews that also mention equipment or a fuel card that never returned, among reviews carriers left on CDLScan. Most logbook write-ups do not include that companion. The pairing is far above chance. It is not a majority.

Why is the other share 9.0%?

Because the base changed. 9.0% of missing-equipment reviews also mention logbook and hours problems. Same overlap, counted from the other side. Always name the denominator.

Why didn’t PSP catch it?

There was usually nothing to file. A missing fuel card is not a crash or an inspection. A disconnected ELD can leak into a filing. Most of this pairing does not. Official reports can still be useful for other things on the same person. They are silent on the card.

Should I stop issuing fuel cards?

No. Stop issuing them before you have read what previous carriers wrote, and before the last employer has answered. The spend is the risk. The card is not the crime.

What if the MVR is clean?

Then the recorded driving events are clean. In this composite the failure is the logs and the card, which usually never become a query result. A clean MVR does not make the card free.

What is the one question that changes the week?

Ask how they returned equipment at the last carrier and what that desk will say about the logs. Combined with a name search, that question sorts a normal day-one issue from a missing-card week more honestly than a rehire box.

Where do I read the previous write-ups?

On CDLScan, before you issue the card. The pairing is already on the record more often than chance. Read it while the money is still yours.