What the Deposition Looks Like When You Did the Vetting Right

Most of what I write about negligent-selection depositions starts with the broker who didn't have the answer. The one who pulled up the MC number and called it vetting. The one whose carrier file had a COI from 14 months ago and a handwritten note that said "driver sounds good."

I want to flip that. I want to tell you what the other deposition looks like.

I know what it looks like because I've helped build tools designed to produce exactly that kind of file — the one where, when opposing counsel works through the standard question sequence, the answers are specific, dated, and supported by evidence. Here's what that deposition sounds like, question by question, and what's sitting in the file behind each answer.

The load and the lawsuit

MC-1247893 / DOT-3567102. A carrier out of Atlanta. Three years of authority, 14 power units, a flatbed and van mixed fleet, operating mostly in the Southeast. The broker — I'll call her Cara — had moved seven loads with them over 11 months without incident. Then in October, one of their drivers ran a red light in Spartanburg, South Carolina. Two vehicles involved. Injuries. A fatality in the other car.

Plaintiff's attorneys filed against the carrier, the driver, and Cara's brokerage. Standard negligent-selection theory. Cara got deposed six months later.

Here's how it went.

Q: "How did you find MC-1247893 originally?"

Cara's answer: "We found them through the DOTScreener Find Carrier tool, which surfaces carriers filtered by active authority, safety scores, and inspection history for specific lanes. I was looking for van capacity on the Atlanta-Charlotte corridor. The system returned a ranked list. MC-1247893 came up in the top results. I pulled their SAFER snapshot that same day — I have the timestamp — and reviewed the complete profile before adding them to our approved list."

What's in the file behind that answer: A timestamped record from DOTScreener showing the date and time of the initial lookup, the SAFER snapshot at that moment, and the specific filters applied when searching. Not "I found them on a load board." A documented sourcing method with a safety-filtered starting point.

Plaintiff's question trying to undercut it: "But you didn't know them personally. You'd never used them before." Correct. But Cara started with safety signals, not price. That's the difference between a sourced carrier and a random carrier.

Q: "What did their BASIC scores show at the time you approved them?"

Cara's answer: "At the time of approval, their Unsafe Driving BASIC was at the 34th percentile. Vehicle Maintenance was at the 41st. Crash Indicator was not percentiled — insufficient data at that time, which actually worried me a little, so I looked at the actual inspection history. Fourteen Level I and II inspections over 26 months, one minor defect citation on lighting equipment that was corrected on-scene. No OOS violations. I documented my review of each BASIC category in the approval record."

What's in the file: A snapshot of the BASIC scores at approval, the actual inspection records, and a written note on the Crash Indicator status explaining why insufficient data wasn't automatically treated as a pass. Most brokers don't document the reasoning. Cara did.

Plaintiff's attempted hook: "But their scores changed before the accident." Yes, they did. We'll get to that. That's where continuous monitoring comes in.

Q: "How did you verify their insurance?"

Cara's answer: "I verified through the FMCSA Licensing and Insurance database, not through the ACORD 25 they sent us. I pulled their L&I record on the day of onboarding — that's the primary source FMCSA maintains for active policy filings. The ACORD 25 went in the file as supplemental documentation. I also pulled L&I again 48 hours before every load for the first three loads, and then relied on continuous monitoring after that — which flags any change to the L&I filing within 24 hours."

What's in the file: Three timestamped L&I pulls during the probationary period, then the monitoring log showing every check after that. When plaintiff's counsel asks "how did you know their insurance was active the day of the accident?" — Cara has an answer. The monitoring system had pulled L&I two days before the load. Active. Same policy. No lapse.

This matters. A lot of negligent-selection cases that look like "bad carrier" cases actually turn on whether the broker had current insurance confirmation. If Cara had only the COI from 11 months ago, the answer to "how did you know they were insured on October 14th?" is "I assumed." That's not an answer you want to give under oath.

Q: "Did you have a signed carrier agreement with MC-1247893?"

Cara's answer: "Yes. We use a standardized carrier agreement that they completed through our onboarding system. They e-signed it on [date]. The system required them to confirm their operating authority, their insurance coverage, and their compliance with federal safety regulations. I have the timestamp of the signature, the IP address, and a verifiable record of their identity tied to the person who signed — they submitted a government ID as part of the onboarding process."

What's in the file: A timestamped e-signature with identity verification. Not a PDF that arrived by email with a scanned signature from someone whose name might be "Operations Coordinator." The person who signed is tied to a verified government ID. If you're wondering why that matters — if the crash had involved a double-brokered load and the "carrier" who signed turned out to be a freight forwarder operating through someone else's authority, that identity record would be the thread that unravels the fraud.

Q: "After you initially approved this carrier, did you do any ongoing monitoring?"

This is the question that separates brokers who got lucky from brokers who were prepared.

Cara's answer: "Yes. We enrolled them in continuous monitoring on the date of approval. The monitoring system checks for changes to operating authority status, insurance filings, and BASIC score changes daily. I have a monitoring log for the full period from approval through the date of the accident. Between approval and October 14th, there were two alerts — one when their Vehicle Maintenance BASIC rose to the 62nd percentile in March, and one in August when the same score crossed the 75th percentile."

Plaintiff's counsel: "And what did you do when you received those alerts?"

Cara's answer: "Each alert triggered a file review. For the March alert, I pulled their current inspection data. The percentile increase was driven by two citation violations from the same inspection event — both minor, both corrected on-scene. I reviewed the underlying violations, documented my reasoning that they didn't meet our stop-use threshold, and noted the file with a re-review date 60 days out. For the August alert, same process — but the August review flagged a pattern I didn't like. Their Vehicle Maintenance BASIC had moved from the 41st to the 75th percentile in five months. I put them on conditional status and flagged them for supervisor review before any further loads."

Plaintiff's counsel, looking for a hook: "But you still used them in September — one month before the accident."

Cara's answer: "The conditional designation triggered an additional manual review. I pulled their current SAFER snapshot, verified insurance, reviewed their inspection history for the preceding 90 days. The September review showed two inspections with no violations. Based on that, we approved one load — with a notation in the file. I did not re-authorize an unlimited number of loads. Each load after the conditional flag required individual review."

What's in the file: The monitoring log, both alert events, the written reasoning at each review, and the conditional-status notation. When plaintiff's counsel implies that the elevated Vehicle Maintenance BASIC should have been a permanent stop — Cara has an answer for why it wasn't, and that answer is documented with specific references to what the underlying inspections showed.

She might not win every argument on the merits. But she's not sitting there saying "I just trusted them" while opposing counsel reads elevated BASIC percentiles back to her from SAFER.

Q: "At the time of the load on October 14th, what was the status of their authority?"

Cara's answer: "Active. I have a monitoring record showing their authority was confirmed active October 12th — two days before the load. Our monitoring system checks operating authority status daily."

Q: "Did you have any reason to believe this carrier was unsafe?"

Cara's answer: "Based on my file at the time of tender, no. I had reviewed their BASIC scores, I had monitoring alerts that I'd responded to and documented, I had active insurance confirmed, a signed carrier agreement with identity verification, and a carrier file going back 11 months. The September manual review was my most recent documentation. I found no indication of imminent safety concern."

This is the line that matters. Not "I didn't know anything was wrong." Not "they looked fine to me." "Based on my file" — four words that anchor the answer to a documented process rather than a feeling.

What made Cara's deposition different

It wasn't that she had perfect information. She didn't. A driver for MC-1247893 ran a red light and someone died. That is tragic and nothing in Cara's file stops it from happening.

What Cara had was a documented decision process: how she found the carrier, what she reviewed at approval, what monitoring she maintained, what she did when monitoring flagged a problem, and what her file showed on the date of the load. Opposing counsel could challenge each of those decisions — the choice to approve after the August alert, the September re-approval — but they couldn't challenge the fact that decisions were made, documented, and tied to specific data at specific times.

The broker who loses a negligent-selection case post-Montgomery usually loses not because they made a wrong call, but because they can't show they made any call at all. "We checked their MC" isn't a decision. It's a reflex.

49 CFR § 371.3 requires brokers to maintain records of carrier name, MC number, shipper name, and load details. That's it. The regulatory floor is close to useless as a defense document. What Cara had was the floor plus everything above it: the reasoning, the BASIC data, the monitoring log, the alert responses, the identity-verified carrier agreement.

That's what survives a deposition.

How I document this

For every carrier we approve: I generate a timestamped carrier profile snapshot at the point of approval, including BASIC scores, inspection summary, L&I confirmation, and authority status. That snapshot is the "approval record" — it captures what I knew and when I knew it.

For ongoing monitoring: every alert generates a file note. The note records what the alert was, what I reviewed in response, and what decision I made. If I continued using the carrier, the note says why. If I put them on conditional, the note says what the condition is. If I stopped using them, the note says what triggered the stop.

For load-day: L&I confirmation and authority status check, timestamped within 48 hours. The file doesn't just show they were active at approval. It shows they were active before the load.

If I'm ever deposed, that's what I'm walking in with.

The deposition you're preparing for right now

You probably think you're not preparing for a deposition. You're just moving freight. Maybe.

But every load you tender without documentation is a gap in the file you'll wish you had if something goes wrong. The carrier who has a perfect record until they don't. The driver who's been compliant until the day he isn't. The load that looks like every other load until it doesn't.

Most brokers won't get sued. But the ones who do — and the ones who survive it — look like Cara, not like the broker who said "they seemed fine" while opposing counsel read their inadequate file back to them line by line.

How I document this

The documentation trail I described above isn't theoretical. It's what DOTScreener builds for every carrier approval: timestamped SAFER snapshots, FMCSA L&I pulls, a continuous monitoring log with alert events and responses, an e-signed carrier agreement with identity verification, and a carrier file that accumulates a datable record from first approval through every load.

When the deposition question is "walk me through how you selected this carrier," that file is what you're reading from.

— Mason Lavallet

Founder, DOTScreener.com