The application before theft and logbook trouble

The application that later shows theft and logbook trouble has a recognisable shape: a short recent stint nobody explains, a request for a fuel card or an advance 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 a unit.

This is a typical application, assembled from how theft and logbook 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, 8.8% mention theft or money games. 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.9% also mention logbook and hours problems — 7.9% of theft reviews, not of all reviews. Flip the pair and 15.3% of logbook reviews also mention theft. Logbook and hours problems are 4.6% of all reviews. Seeing them in 7.9% of theft reviews is about 1.7 times the chance rate. Lift is that multiplier, not the odds on your next hire. 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 theft language is not on the application yet. It arrives after you have issued the card — stole fuel, stole tablet, stole equipment, truck stole.

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 stole fuel. Sometimes the next line is that they left the truck.

In 35.5% of theft reviews the carrier also mentions an abandoned truck. That is the ending you are trying not to buy. A crash or damage sits in 13.7%. Aggression or threats sit in 10.8%. Drugs or alcohol sit in 9.2%. Equipment or a fuel card that never returned sits in 8.7%. Paid travel with no arrival sits in 7.2%. In 37.4% 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 logbook side, an abandoned truck sits in 36.2%. Aggression sits in 22.3%. A crash or damage sits in 21.3%. Late or missed deliveries sit in 17.6%. Theft sits in 15.3%. Going unreachable sits in 9.5%. Equipment or a fuel card that never returned sits in 7.4%. Always name which base you are standing on.

I keep the logs next to the theft because the packet you already buy is built for hours and inspections, not for stole fuel. A disconnected ELD can leak into a filing. A missing tablet usually cannot. The pairing itself is in theft and logbook hours. A missing card in the same history is theft and a missing fuel card. The theft trend is in theft in a carrier review. Logbook trouble next to a missing card is logbook hours and missing equipment.

The share of reviews mentioning theft or money games ran 6.6% in 2018, 9.0% in 2019, 10.5% in 2020, 7.8% in 2021, 9.1% in 2022, 9.4% in 2023, 9.5% in 2024, and 9.0% in 2025. I stop that line at 2025. 2020 is the high you should not smooth over. Then the share sat near nine percent. 2025 is higher than 2018, not a spike.

Logbook-and-hours mentions ran 5.0% in 2018, then 3.7% in 2025. The theft line held. The logbook line fell. 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. Stole fuel is usually not a filing unless someone called the police. 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 they stole fuel and disconnected the ELD. 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, and it does not mean the logs will match the trip.

I am not going to pretend this is an independent study. CDLScan is the source, and I write from the data they share. Theft is common enough in what carriers bother to write down, logbook trouble rides along above chance, and the packet you already run is designed for hours, not for the missing 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 stole fuel and a log book, the next unit is a decision, not a courtesy. If the last employer will not say how they ran logs, that is not a pass. Ask what equipment they had, how they ran logs at the last carrier, and what that desk will say about the card. People who left cleanly can usually tell you. People who are about to walk often skip the freight and jump to the card.

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 theft and logbook reviews cluster. No name, no carrier, no date. If your current file matches it, that is the pattern talking, not a biography.

Does 7.9% mean this application usually has hours trouble?

No. 7.9% is the share of theft reviews that also mention logbook and hours problems, among reviews carriers left on CDLScan. Most theft write-ups do not include that companion. The pairing is above chance. It is not a majority.

Why is the other share 15.3%?

Because the base changed. 15.3% of logbook reviews also mention theft. Same overlap, counted from the other side. Always name the denominator.

Why didn’t PSP catch it?

There was usually nothing to file. Stole fuel is not a crash or an inspection. A disconnected ELD can leak into a filing. Most of this pairing never becomes a query result.

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 how they ran logs. The spend is the risk.

What if the MVR is clean?

Then the recorded driving events are clean. In this composite the failure is the money and the logs, 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 ran logs at the last carrier and what that desk will say about the fuel card. Combined with a name search, that question sorts a normal day-one issue from a money-games 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.