The application before late loads and logbook trouble

The application that later shows late loads and logbook trouble has a recognisable shape: a thin recent year, miles that do not match the dates, and a last employer who will not say how they ran on time or how they ran logs. None of it is disqualifying on its own. Together it is the file worth a second call before you assign a live load.

This is a typical application, assembled from how late-delivery 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, 9.8% mention late or missed deliveries. 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, 8.2% also mention logbook and hours problems — 8.2% of late-delivery reviews, not of all reviews. Flip the pair and 17.6% of logbook reviews also mention late or missed deliveries. Logbook and hours problems are 4.6% of all reviews. Seeing them in 8.2% of late-delivery reviews is about 1.8 times the chance rate. Lift is that multiplier, not the odds on your next dispatch. 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. Miles look thin against the dates. 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 clock. They can start this week. They need miles. The first load is ready. Can you dispatch today.

Nothing on that page is disqualifying. Plenty of good hires start mid-week and have a messy year. The pattern is the combination: thin recent history, slow last employer, official packet quiet, and a live appointment pulled forward before anyone has read what previous carriers wrote about the clock or the logs.

The language that later shows up in the reviews is already sitting in that request: always late, late deliveries, first load, home time. The logbook language is not on the application yet. It arrives after you have dispatched — log book, disconnected ELD, ELD device, hos rules, how to use the ELD.

What happens after you say yes

Typical next step, still a composite: they take the truck. The first week has a late pick. Then the logs look wrong, or the ELD gets disconnected. Home time becomes the argument. Sometimes the next line is that they left the truck. Sometimes they stay and the clock just keeps missing.

In 35.7% of late-delivery reviews the carrier also mentions an abandoned truck. That is the ending you are trying not to buy. Aggression or threats sit in 21.0%. A crash or damage sits in 19.8%. Refused loads and low miles sit in 9.1%. Going unreachable sits in 8.8%. Walking off a loaded trailer sits in 7.3%. In 36.3% 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 clock because the packet you already buy is built for hours and inspections, not for always late. A disconnected ELD can leak into a filing. Always late usually cannot. The pairing itself is in late loads and logbook trouble. The late-delivery trend is in late loads as the week before a walk-off. Late loads with refused freight is a separate composite; that is in the application before late loads and refused freight. Aggression in the same history is what a threat in a carrier review actually means.

The share of reviews mentioning late or missed deliveries ran 12.8% in 2018, 7.2% in 2019, 11.4% in 2020, 9.6% in 2021, 8.9% in 2022, 8.6% in 2023, 9.9% in 2024, and 11.1% in 2025. I stop that line at 2025. Do not smooth 2019. It is the low in the completed series, 7.2%. Then the share climbed back, and 2025 is 11.1% — not the 2018 high, not the 2019 trough.

Logbook mentions 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. The late-delivery line eased, then came back. The logbook line fell. The application above did not get any rarer. The packet you run on it 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. Always late is usually not a filing. 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 driver was always late 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 Friday’s appointment holds.

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

What I would have done with that file

I would not reject it on sight. I would stop the first live load.

Look the name up first. If previous carriers already wrote about always late and a log book, the next dispatch is a decision, not a courtesy. If the last employer will not say how they ran on time, that is not a pass. Ask which loads ran late, how they ran logs at the last carrier, and what that desk will say about on-time performance. People who left cleanly can usually tell you. People who are about to walk often skip the freight and jump to home time.

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

Check the name on CDLScan before the first live load. 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 late-delivery 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 8.2% mean this application usually has logbook trouble?

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

Why is the other share 17.6%?

Because the base changed. 17.6% of logbook reviews also mention late or missed deliveries. Same overlap, counted from the other side. Always name the denominator.

Why didn’t PSP catch it?

Sometimes about the hours, if something was filed. Not about the clock. Always late is usually not a crash or an inspection. Official reports can still be useful for other things on the same person. They are silent on the appointments.

Should I stop assigning live loads on week one?

No. Stop assigning them before you have read what previous carriers wrote, and before the last employer has answered. The freight is the risk. The first load is not the crime.

What if the MVR is clean?

Then the recorded driving events are clean. In this composite the failure is the clock and the logs, which usually never become a query result. A clean MVR does not make Friday’s appointment hold.

What is the one question that changes the week?

Ask which loads ran late and how they ran logs at the last carrier. Combined with a name search, that question sorts a normal first week from a late-load week more honestly than a rehire box.

Where do I read the previous write-ups?

On CDLScan, before the first live load. The pairing is already on the record more often than chance. Read it while the truck is still yours.