What counts as unplanned
Every load has stops you planned: the pickup, the delivery, any drop in between. Every trip also has stops you did not plan but should expect. Fuel takes ten minutes. A weigh station takes five. Federal hours of service rules require a 30-minute break once a driver has driven eight cumulative hours, and ten consecutive hours off duty before the next shift, so a truck that leaves a pickup at 7 a.m. is going to sit still for half an hour around mid-afternoon and for most of the night after that. None of those is a problem, and a dispatcher who treats them as one trains drivers to turn tracking off.
An unplanned stop is what is left: a truck that is not at one of the load's stops, is not on a break the rules account for, and has been still for longer than fuel or a scale explains. A breakdown, a detour to a home address, a trailer swap nobody mentioned and the stop that ends in a cargo theft report all start the same way on a map: the pin stops moving. A truck that stopped reporting is a different problem, a pin that is gone rather than still, and the guide on a carrier that stops tracking covers it.
Where the signal comes from
You cannot detect a stop you are not watching. A check call every four hours finds the stops the driver tells you about, and a driver stopped somewhere they should not be will not mention it. Detection needs positions arriving without anyone asking: from the driver's phone through a driver app or a browser tracking link, from the carrier's ELD share link (Samsara, Motive and most other vendors let a carrier share one truck's live position by link, and the page usually shows speed, the fastest way to see a stop), or from a connected ELD that reads the carrier's trucks directly. How to ask for a share link. A driver tapping arrived and departed is a second opinion, never the only one, because a tapped time is a claim and a GPS time is evidence.
How often a position arrives sets how fast you can detect anything: one a minute from a share link shows a stop within minutes, one an hour cannot tell a 50-minute stop from a moving truck. ELD connections and phone tracking on the same load mean a dead phone is not a blind spot.
The three questions
When the pin has not moved, answer these in order. The numbers are a reasoned default, not measured industry practice: they are what LoadSignal ships with, set per organization, and your most experienced dispatcher should check them before a customer sees an alert built on them.
| Question | Answer that ends it | Answer that keeps it open |
|---|---|---|
| How long? | Under 30 minutes: fuel, a scale, the mandated break. | Past 30 minutes, mark the load so a glance shows it. Past 60, a person looks. |
| Where? | At one of the load's stops, a truck stop, a rest area, a weigh station. | A residential street, a lot that is not on the rate confirmation, the shoulder of a highway, or more than about 20 miles off the planned route. |
| When in the driver's day? | A half hour around the eighth hour of driving, or a long stop that begins late in the day and runs ten hours or more. | A long stop at 10 a.m. on the day of delivery, two hours after leaving the pickup. |
The first question does most of the work, which is why the threshold matters. Set it at ten minutes and a brokerage running a couple of hundred trucks gets a message for every coffee. Set it at two hours and a breakdown an hour from the receiver is found by the receiver. A position at one of the load's stops is dwell rather than an unplanned stop, and dwell has its own clock: free time, then detention, which the detention guide covers.
Doing it by hand
None of this needs software. It needs a position source, a cadence and a habit of writing things down.
- Get a live source on every load before the truck moves. Share link from the carrier, a tracking link to the driver, or both, and put the requirement in the rate confirmation.
- Pick a review cadence and keep it. Every 30 minutes on loads delivering today, every hour on the rest. The first time the pin is where it was last time, write the time and the place on the load, then check the place against the rate confirmation: at a stop on the load, start the dwell clock; anywhere else, ask the three questions.
- Ask the carrier before the driver. The carrier's dispatcher sees the hours clock, knows about the breakdown, and prefers a question to a complaint. Note the time and the answer.
- If the carrier cannot explain it, text the driver one specific question. “Load 4471: tracking shows the truck stopped near Cookeville since 1:40. Everything OK, and when do you expect to roll?” A text, because a driver on the road cannot take a call. Call once if there is no reply in fifteen minutes.
- Write it on the load. Who you contacted, when, by what channel, what they said, and what you decided, so the dispatcher who takes the load at shift change does not start over.
At twenty loads a day one person can do this. At two hundred the cadence slips to whenever someone has a minute, and the stop that mattered was the one in the gap.
What to do with one
Once a stop is unplanned and unexplained, the job changes from detecting to deciding. First, is the appointment at risk? Take the remaining distance, the driver's remaining hours and the stop so far, and compare with the delivery window. A truck 90 minutes from the receiver with a 6 a.m. appointment tomorrow has slack; the same truck with a 4 p.m. appointment today does not. Late load detection is this arithmetic run on every position.
Second, does the customer need to know? Only if the window is at risk, and then before they ask. “Load 4471: the truck has been stopped near Cookeville since 1:40 p.m. The carrier reports a tire repair and expects to roll by 3:30. The 6 a.m. delivery tomorrow is still on. We will update you by 5 p.m. either way.” Where, since when, what the carrier said, and when the next update comes.
Third, does anyone else need to act? A stop that neither the carrier nor the driver can explain, in a place nobody can account for, with a high-value load, is a security question before it is a customer-service one. Have the carrier call the driver directly, and if the truck is still unaccounted for, follow your theft procedure. Minutes matter there, and the detection threshold is what buys them.
After delivery
Every stop on the trip, planned or not, is worth a line in the load's record: where, GPS arrival, GPS departure, duration. For the planned stops that record is your detention evidence. For the unplanned ones it is your answer when the receiver asks why the truck was two hours later than the ETA you gave at noon. A record built from positions only knows what it saw: if the share link was dead for ninety minutes, it should say the truck was not observed, not that it did not stop.
Where software helps
Everything in the by-hand section except the judgement is a clock on a position stream, and clocks are what software is for. LoadSignal checks active loads on a five-minute schedule and on relevant events, and polls a share link every minute. When a truck has sat still for the stationary threshold while tracking is live and it is not inside a stop's geofence, the load gets a “shipment stationary” exception with where and for how long; at twice the threshold it becomes high priority, and it clears itself when the truck moves. The default is 30 minutes, set per organization, a reasoned default rather than a measured one. A position more than 20 miles from the planned route raises its own exception, and a truck inside a stop's fence runs the dwell and detention clocks instead.
The exception goes to the people watching the load and escalates if nobody acknowledges it on a timer you set. Rules your team turns on can text the driver the check-in above and read the reply against the GPS; a customer message is drafted with the facts filled in and waits for a person to send it. After delivery the trip record lists every stop with its GPS times and a place name, marked “observed only” with the share of the trip that was tracked. The exception management page describes the whole set of conditions, and track and trace is the queue they land in. The three questions, like the call to the carrier, are still a person's.
Questions dispatchers ask
How long should a truck be stopped before a broker does anything?
A reasoned default is 30 minutes away from any planned stop before the load is marked for a look, and 60 minutes before a person acts. Under 30 minutes covers fuel, a weigh station and the mandated break. Set it for your own operation, and have a dispatcher check it.
How can I tell a mandated break from a problem?
Look at the driver's day, not the clock on the wall. A 30-minute stop around the eighth hour of driving is the break the rule requires, and a stop of ten hours or more that starts late in the day is the reset. The carrier's dispatcher can see the hours of service clock and will tell you.
Can I detect an unplanned stop from a carrier's ELD share link?
Yes. A Samsara or Motive share link shows the position and usually the speed. Open it at set intervals, note the time and place the first time the pin has not moved, and compare it with the stops on the rate confirmation. Software can poll the same link every minute and start the clock for you.
Should I tell the customer the truck has stopped?
Only when the stop puts the delivery window at risk, and only with the evidence in the message: where, since when, what the carrier said, and when you will update them next. A stop that does not threaten the appointment is a note on the load, not a customer email.
How LoadSignal flags a stationary truck and the other exceptions