What to ask on the application before a crash write-up

A reason-for-leaving field will not tell you whether the last truck came back whole. If you ask why they left, you get a mood. If you ask where the unit was left, who recovered it, and whether it came back damaged, you get a scene — or a hole that is already the screen.

Among the reviews carriers left on CDLScan, 13.7% mention a crash or damage. 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.

That share is not a reason to reject every short stint. It is a reason to stop letting a home-time story do the work of a recovery. The write-ups keep repeating physical language: damaged truck, damaged trailer, left the truck, brand-new unit that did not stay that way. Pull that language out of the candidate before you issue a unit.

This is a screening playbook, not a legal memo. What you may ask, store, or decide is your counsel’s problem. If you need a rule, talk to yours.

Why a reason-for-leaving field fails

A reason-for-leaving field invites a story. Damaged trailer is an event. Those can diverge. A candidate can talk about home time, family, or a dispatcher and never name the unit. A previous carrier can later write that the trailer took a hit and someone had to go get the truck.

Verdict language in the reviews — stay away, waste your time, don’t hire — is not the event either. I do not put a stay-away box on an application. I ask for a location, a last dispatch, a recovery, and whether the equipment came back whole. The incident language is physical. How we separate incident from verdict is on the methodology page.

Official reports will not do all of this work for you. PSP can hold a filed crash. An MVR can hold a license action after a crash. The Clearinghouse does not hold a dented fender. Previous-employer forms often hold dates and a rehire box. A lot of damaged-truck write-ups never become a report. Hear the scene on the application, before you decide the packet is enough.

The share of reviews mentioning a crash or damage moved from 14.0% in 2018 to 15.1% in 2025. I stop that line at 2025. The wording stayed blunt, and the form still has to ask for it.

Five questions, on the form, in this order

1. When did you start, and when did you last dispatch?

Dates first, because a short stint is the skeleton of both a recovery and a no-show. If they never dispatched, you are in onboarding — a different screen. If they dispatched and the last day is a Tuesday in the middle of a run, you are in operations. Do not skip this to be polite. A hole between two carriers is not a finding by itself. An unexplained hole plus a last day that is not a yard day is.

2. Did the last truck come back whole, and who recovered it?

This is the question a reason-for-leaving field cannot absorb. People who had a filed crash they already disclosed can usually name a date and a report. People who put a unit into something and then walked often skip the recovery, talk about home time, or say they do not recall. You are not trying to trap them. You are trying to hear whether the equipment came back, and in what shape. Damaged truck, damaged trailer, damaged equipment belong here.

3. Where was the last truck left?

A crash-or-damage review often sits next to a recovery, not next to a clean resignation at the yard. An abandoned truck sits in 36.7% of those reviews. Left the truck and damaged truck are often one scene. If the candidate can name a yard, you have one kind of file. If they skip the location, you have another. Loaded-trailer language sits in 5.5% of crash-or-damage reviews and it changes the recovery.

4. Did anyone file anything — a crash, a police report, a claim — and what will the last carrier write anyway?

A filing is extra, not a substitute. Some write-ups sit next to a PSP hit. Many do not. Asking only about accidents on the record catches what the candidate already plans to disclose. Asking what the last carrier will write catches the sentence that never became a report.

5. When did you last answer the phone on that job, and who was trying to reach you?

Going unreachable sits in 6.0% of crash-or-damage reviews. Late or missed deliveries sit in 14.2%. Aggression sits in 17.2%. Silence and a late load are often the last step you hear about, not the first thing that happened. If the candidate can name the day the phone died, you have a timeline. If they jump to a mood, bring them back to a day and a unit.

I would not ask whether they were a safe driver. I would not ask for red flags. Both invite a mood. Mood is verdict language. You already know how that sounds, and it is not a fact about the driver.

Companions in the same reviews tell you which extra words to leave room for. In 36.7% of crash-or-damage reviews the carrier also mentions an abandoned truck. In 8.8% they also mention theft or money games. In 7.1% they also mention logbook and hours problems. Do not collapse all of those into one insult on the form. They are different files that happen to share a dent. What rides with late loads is in crash reviews and late deliveries. What rides with hours problems is in crash reviews and hours problems.

What was already visible on the packet

On an application the warning is rarely the word accident. It is a short stint, a hole, and a previous carrier who will not say whether the last truck came back whole. Ask the candidate to walk the last two exits before you dial the last desk.

Typical sequence, built from how these reviews cluster, not from one person’s file: two carriers in a year. They start. A load runs late. Answers get shorter. Then the language in the next review is damaged trailer, truck stop, left the truck. That sentence may never appear on the PSP you already pulled.

A no-show almost never sits in the same paragraph. Inside crash-or-damage reviews, only about 1.2% also mention a no-show — far below chance. If they never dispatched, switch to the empty-chair screen: ticket, orientation, never showed. Do not run a crash form and assume you covered both.

What to do with the answers

Look the name up before you treat a clean paragraph as a pass. The application is cheaper when you already know whether previous carriers used damaged-truck or left-the-truck. Asking a candidate to contradict a write-up you have not read is how you waste the only live conversation you will get.

If the last two exits are crisp — yard, day, unit came back whole, who took the keys — keep moving, and still read the name. If the last two exits skip the truck and jump to home time, stop. If they never dispatched, switch screens.

If the last carrier will only confirm dates, that is not a pass. It is a reason to read the rest of the name. Check it on CDLScan before you issue a truck. It takes less than a minute. The words you want on the application are already sitting there more often than the reason-for-leaving field will admit.

The longer call playbook is five reference questions that beat rehireable. Why the packet is a floor, not a character reference, is in truck driving background checks. This page is the form, not the phone.

This is not legal advice. It is a way to stop letting a reason-for-leaving field do a sentence’s job.

Frequently asked questions

Is a reason-for-leaving field useless here?

It is useful as a story and weak as an event. A reason can disagree with a write-up about a damaged trailer. Ask whether the last truck came back whole. Keep the reason field as extra, not as the screen.

Can I store these answers as a safety history?

That is a question for your counsel and your process, not for this page. I am talking about what to ask so you hear the event. What you store is a different job.

What if they refuse to say whether the unit came back whole?

That is information. Then read what other carriers already wrote about the name. A missing recovery is not a confession. It is a reason to stop treating the application as complete.

If PSP is clean, do I still need these questions?

Yes. Some damaged-truck write-ups sit next to a filing. Many do not. A clean packet means the filed items are clean. It does not mean nobody typed damaged trailer.

Why ask where the truck was left on a crash form?

Because an abandoned truck sits in 36.7% of crash-or-damage reviews. Left the truck and damaged truck are often one recovery. The location question is cheap and it belongs on this form.

Do official reports replace these questions?

No. PSP, an MVR, and the Clearinghouse hold filings. A dented fender that never became a report is usually not a filing. Keep the reports. Add the questions.

Where do I look the name up?

On CDLScan, before you issue the truck. The physical language — damaged truck, damaged trailer, left the truck — is already written down. Use the application to see if the candidate will say it out loud.