Your Carrier Book Has Rot In It — Here's How to Find It Fast

You already vet carriers. That's not the problem. The problem is that a vet is a snapshot, and the carrier keeps moving after you take it. The operating authority you confirmed in the spring can be revoked by summer. The insurance on the COI can lapse the month after they hand it to you. An out-of-service order can land on a carrier you've run fifty loads with. None of that sends you a notice — it just sits there in your book, looking exactly as safe as the day you cleared it, until the load you tender on it is the one that goes wrong.

So the real question isn't whether you vet — it's whether you know the current status of every carrier you'd still tender to right now. If your book lives in a spreadsheet or your head, you don't. The fix is fast: pull the list into one place, run it against the live federal record in a single pass, and let the ones that changed surface themselves. Minutes of work to find the problem carrier before it finds you.

Nothing about carrier status is static, and none of the changes are announced to the brokers relying on the carrier:

Everyone knows they should re-check carriers. Almost nobody does it at any real cadence, because doing it by hand means pulling up the FMCSA record for each carrier, one at a time, reading the authority and insurance fields, and remembering to do it again next month. At ten carriers it's tedious. At a hundred it's a job nobody has time for, so it silently doesn't get done — and the book drifts out of date one quiet revocation at a time.

That gap isn't a discipline problem; it's a tooling problem. The check itself is simple. Doing it across your whole book, repeatedly, without it eating a day — that's the part that needs to be automatic.

Take the list you already have — the spreadsheet, the CSV export from your TMS, whatever holds your carriers — and bring it into one place. In Draylo that's a direct import: upload a .csv or .xlsx, the columns map themselves (USDOT, MC, name, contact), and every carrier lands in your book. Then one action re-checks all of them against the live FMCSA record at once and returns a red/yellow/green on each. The carriers that quietly changed since you last looked don't hide — they surface at the top as the ones to deal with.

You're not re-doing the vetting you already did. You're getting the current federal status of your entire book in the time it takes to export a spreadsheet — and turning "I think these carriers are fine" into "here's the live status of every one, and here are the three that aren't."

Importing and re-checking closes the gap once. Keeping it closed is the part that actually protects you. After the book is in, the federal record is monitored daily — a revoked authority, a dropped insurance filing, an out-of-service order, or an insurer's advance notice that a policy is about to cancel surfaces as an alert, on the specific carrier, without you re-pulling anything. The pending-cancellation warning matters most: it flags the lapse before the coverage is actually gone, which is the window where you can still act.

That's the difference between vetting as an event and vetting as a state. An event is a snapshot you took once; a state is a book that tells you the moment one of your carriers stops being safe to tender to.

There's a second reason to get your book out of a spreadsheet, and it isn't about efficiency. After the Supreme Court's 2026 Montgomery decision, a broker can be sued for negligently selecting an unsafe carrier, and the defense is evidence: a dated record showing what you checked and when. A process that works is not the same as a process you can prove — and a text thread or a mental note is not a defense exhibit.

When your book is checked in one system, every re-check and decision is on the record automatically, time-stamped, without you keeping a separate log. You keep running your process the way you already do; it just stops being invisible the day someone asks you to show it.