Why official reports miss aggression or threats

A clean PSP does not mean the last week was quiet. Yelling at a dispatcher is not a filing. A bad attitude is not a roadside inspection. The packet comes back quiet because nothing in it was ever designed to make a noise about this.

Among the reviews carriers left on CDLScan, 13.9% mention aggression or threats. 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. It is one of the larger incident slices in the set CDLScan shared with me. And it is one your standard packet is least built to hold.

A recruiter who has already pulled PSP, an MVR, and a Clearinghouse query can still be looking at a dull file. That is not a failure of those reports. It is what they were designed to do.

What those reports actually hold

PSP is a crash-and-inspection product. It gives you about five years of crash data and about three years of roadside inspections. If the driver put the truck into a wall and it was recorded, you may see it. If a trooper wrote a violation, you may see that too. A shouting match with dispatch is not a roadside inspection. It is not a crash unless someone also filed one.

An MVR is a state driving record. Tickets, suspensions, license actions. It is useful for the thing it is. It will not tell you that the last week ended in a hard conversation and then the truck sat at a stop.

The Clearinghouse holds drug and alcohol program events: positives, refusals, actual knowledge, return-to-duty status. A bad attitude is not a test result. A clean query answers a real question. It does not answer how the last week sounded.

Previous-employer history — the DAC-style employment check, the safety-performance request — is the closest official place this should appear. Sometimes it does. Often it does not. The last carrier answers what they are required to answer, or they answer slowly, or they answer “eligible for rehire” with a blank where the scene actually is. A hard last week is usually treated as an employment mess, not as a filing. Nobody sends it to FMCSA. How we treat these shares is on the methodology page.

So a clean packet is not a lie. It is an incomplete sentence. The missing clause is what previous carriers bothered to write when they were no longer being polite.

Why aggression stays off the page

The language in those reviews is a scene, not a code. Bad attitude. Always late. Left the truck. First load. Truck stop. Abandoned equipment. None of that maps onto a violation you can buy.

The companions in the same write-ups tell you why the official systems stay quiet. In 29.7% of aggression reviews the carrier also mentions an abandoned truck — so a shouting match and a recovery often share a paragraph. In 17.0% they also mention a crash or damage, and that slice is the one most likely to leave a mark on PSP. The rest often will not. In 14.9% they also mention late or missed deliveries. In 7.3% they also mention logbook and hours problems. In 6.9% they also mention theft or money games. In 6.3% they also mention drugs or alcohol. In 6.1% they also mention refused loads and low miles. Those are operational facts. They live in dispatch notes and in the next recruiter’s phone call, not in a state record.

Stay away and waste your time are a different register. In 37.2% of these reviews the carrier also writes a verdict. That is heat at the end of the write-up, not a filing. Read the scene. Do not hire off the temperature of the last sentence.

The share of reviews mentioning aggression or threats moved from 13.2% in 2018 to 15.1% in 2025. I stop that line at 2025. A problem that common in what carriers write down, and that rarely becomes a filing, is exactly the gap a clean packet hides.

I would not drop PSP because of this. I would stop treating a quiet PSP as a character reference.

What was visible before you spent

The pattern I’d watch for is not a code on a report. It is a short stint, a hole between two carriers, and a previous desk that already used the same words: bad attitude, always late, left the truck. Those words show up in carrier write-ups. They do not show up as “aggression” on an MVR.

Ask the candidate to walk the last two exits without help. How did the last week run. Where was the truck left. Who recovered it. What will the previous carrier say if you call. People who had a hard conversation they already disclosed can usually name a day and a dispatcher. People who yelled and then walked often skip the recovery and jump to home time.

Typical sequence, built from how these reviews cluster, not from one person’s file: the application is thin. References are slow. Official reports are dull. You assign a truck. A load runs late. Answers get shorter. Then the language in the next review is bad attitude, always late, left the truck. That sequence does not generate a Clearinghouse hit.

The words carriers actually reach for are in how they write about aggression. The form that pulls a last week out of a candidate is in what to ask before an aggression write-up. The climb in the share is in driver aggression screening.

What to do with a clean packet

Keep running the reports. They catch the class of problem they were built for. Then add the check they cannot do: what previous carriers already wrote about this name.

If the last carrier will only confirm dates, that is not a pass. It is a reason to read what other carriers put on the record when they were not filling out a form. Check the name on CDLScan before you issue a unit. It takes less than a minute.

A clean PSP means the filed crashes and inspections are clean. A shouting match is usually not filed. Those are different claims. Only one of them is in the packet you already buy.

I am not going to pretend this is an independent study. CDLScan is the source, and I write from the data they share. An aggression mention is common enough in what carriers bother to write down, and a quiet packet is not a substitute for reading that sentence.

Frequently asked questions

If PSP, MVR, and Clearinghouse are clean, is the driver safe to hire?

They are clean on the items those systems store. Aggression mentions are in 13.9% of the reviews carriers left on CDLScan, and that behavior is rarely filed. A quiet packet is necessary. It is not sufficient.

Is a DAC or previous-employer check enough?

It is the right official place to look, and it still misses a lot. Carriers answer slowly, narrowly, or not at all. The same desk that returns “eligible for rehire” will later write that it ended in a shouting match.

Does a clean PSP mean no aggression ever happened?

No. PSP holds recorded crashes and roadside inspections. A hard last week is usually an employment event. It becomes a PSP item only if someone also recorded a crash or a roadside violation.

Should I skip official reports and only read carrier reviews?

No. Reviews do not replace a license check, a crash history, or a Clearinghouse query. They cover the class of problem those reports were never built to hold.

What should I ask the previous carrier if they will not give a story?

Ask how the last week ran and whether the truck came home. If they will only confirm dates, go read what other carriers already wrote about the name.

Why do so many aggression write-ups never become a record?

Because nobody is required to file “the last week went loud” the way they file a crash or a positive test. The next employer only sees it if the last one bothers to say it.

Where do I look first if the packet is already clean?

The name, in what previous carriers wrote. Start on CDLScan, then call. Do not issue the truck first and look later.