How Do You Catch a Load Going Dark After Pickup Before It Turns Into Cargo Theft?
By Connor Miller, Founder and CEO, FreightScout. Last updated 13 November 2026.
Short answer: you won't catch it by looking at a map once an afternoon. You catch it by deciding ahead of time what "wrong" looks like on a rolling load (an unplanned stop, a stale ping, a truck off route, a truck behind pace) and making sure somebody hears about it within minutes, with the load in front of them. Most bad loads don't vanish at once. They go quiet first. The quiet is the window you've got.
Why does a load go dark in the first place?
Usually for boring reasons. A phone died. The driver's sleeping. The app logged out. A truck broke down in a dead zone. Most quiet loads turn out fine.
That's exactly the problem. Because most of them are fine, a floor learns to shrug at a stale ping. Somebody figures they'll check it after lunch, or first thing tomorrow. And the few loads that aren't fine look identical to the ones that are for the first couple of hours.
FreightWaves reported this week on a high-value load that investigators say made several multi-hour stops after pickup before they lost track of it entirely. Whatever the full story turns out to be, the pattern's familiar to anybody who's run a floor: the signs were on the load before anyone acted on them.
FreightScout comes from 12 years running a brokerage. The loads that hurt almost never went from fine to gone. They went from fine to quiet, and quiet sat too long.
What should count as a red flag on a rolling load?
Write it down before you need it, so a rep at 6 p.m. doesn't have to make a judgment call alone. A good starting list:
A stop nobody planned. A fuel stop or a break is normal. A loaded truck parked for hours somewhere that isn't the shipper, the receiver, a known yard or a sensible rest stop isn't.
A ping that stops updating. Not slow, stopped. Stale is different from "on pace and quiet."
Off route. A truck heading somewhere that doesn't get it closer to the receiver.
Behind pace for the appointment. If the math says it can't make delivery, you want to know now, not at the appointment time.
A driver who won't pick up. One missed call is a driver driving. A pattern of missed calls on a truck that's also stopped or off route is a different conversation.
For reefer loads, temperature out of range. That's its own kind of trouble, and it shouldn't wait either.
None of these alone proves anything. Two of them together on a high-value load should get a person's attention right away.
What do you do in the first hour?
Call, don't wait. A quiet truck gets a call. Same questions every time: where are you, are you still loaded, why are you stopped, what's your new ETA. If you get a clean answer, write it on the load and move on.
Call the carrier, not just the driver. If the driver doesn't answer, call dispatch at the number of record for that MC, not a number that showed up in a text or an email signature during the load.
Check what you confirmed at dispatch. Who did you book, which driver, which truck, which phone? If any of that changed after booking and nobody verified it, that matters a lot more now. We wrote up how to handle that in how to verify a driver or truck change before pickup.
Tell your customer early. A shipper who hears "your truck's been stopped for two hours, here's what we know and what we're doing" from you is a shipper who keeps working with you. One who hears it from the receiver isn't.
Hand it to a person who can make decisions. At some point this stops being a status question and starts being a judgment call: when to escalate inside the brokerage, when to bring in the shipper's security team, when to report it. That's a person's job. No software should be making that call for you.
Why is the next morning too late?
Because most of the cost of a bad load is time. A load that's been sitting quiet overnight gives everybody involved a long head start you don't get back.
The fix isn't heroics. It's making sure the watching doesn't depend on someone remembering to look. A rep working 40 loads can't refresh a map on every one of them all night, and they shouldn't have to.
How does FreightScout watch for a load going dark?
It watches every rolling load for the same signs listed above, and it sends the ones that need attention to a person.
| What happens on the load | What FreightScout does |
|---|---|
| Truck's on pace and the ping is current | The ping stands in for the call. Nobody gets dialed. |
| Unplanned stop, stale ping, off route or behind pace | Flags it as an exception on that load. |
| Truck goes quiet in transit | Calls for a spoken ETA and asks why it's quiet. |
| Driver is late | The reason and new ETA come back with the delay email to the customer drafted for one-click send. |
| No answer, detention, mechanical trouble, shipper heat | Escalates to a person. Those don't sit in voicemail. |
| Last check before an appointment | It's always a call, even when the ping looks fine. |
Every call and every status ends as a note on the load in McLeod, Aljex or Tai, so the next rep sees the history without asking around. By API where the TMS offers one, and by reading it in place where it doesn't, set up during implementation.
What it doesn't do: it isn't a tracking platform, it doesn't recover freight, and it can't promise a load won't get stolen. Nobody honestly can. What it does is shrink the time between "this load went quiet" and "a person who can act knows about it." Track runs supervised by default, every action is logged and reversible, and your TMS stays the system of record. It's not a TMS and not a load board.
The full list of what counts as an exception is on AI exception management for freight brokers, and how the ping and the call work together is on AI track and trace for freight brokers. If the problem is a tracking link that never worked in the first place, start with what to do when the tracking link won't work.
Questions brokers ask
How do I know if a long stop after pickup is a problem?
Look at where it is. What else is happening? A stop at a known yard or rest area with a driver who answers is usually fine. A long stop somewhere that makes no sense, with a stale ping or a driver who won't pick up, should go to a person right away.
How long should a load be quiet before a broker acts?
Set the rule before it happens, based on the load. A high-value load should get a call as soon as the ping goes stale or the truck stops somewhere unplanned. Waiting until the next scheduled check call is how a few quiet hours turn into a lost night.
Who should I call first when a driver goes dark?
Call the driver, then the carrier's dispatch at the number of record for that MC. Don't rely on a phone number that only showed up in texts or emails during the load.
Should I tell the shipper right away?
Yes, with what you know and what you're doing about it. Shippers forgive a problem they heard about early. They don't forgive hearing it from the receiver.
Does FreightScout prevent cargo theft?
No, and be wary of anyone who says their software does. FreightScout watches every rolling load for an unplanned stop, a stale ping, an off-route truck or a truck behind pace, calls when a truck goes quiet, and escalates to a person, so you find out sooner.
Does FreightScout replace my tracking provider?
No. It isn't a tracking platform. It reads the ping when the truck's on pace, calls when the truck goes quiet, writes the note back to the load, and escalates exceptions to a person.
Will this mean more calls to drivers whose trucks are fine?
It shouldn't. When the truck's on pace and the ping is current, the ping stands in for the call. A load earns a call when something changed, plus the last check before an appointment.
Related
- AI exception management for freight brokers
- AI track and trace for freight brokers
- how FreightScout automates check calls
- how to verify a driver or truck change before pickup
- what to do when the tracking link won't work