Where visibility breaks
Visibility does not fail on the loads you would expect. Your own drivers with the app installed and your big carriers on an ELD integration are fine. It fails in the middle: the one-truck carrier you booked off a load board this morning, the owner-operator whose phone died at the fuel island, the driver who turned off location because the app was draining the battery. Those loads are a third to a half of most brokerage boards, and they are exactly the loads where something goes wrong.
The second place it breaks is time. A carrier that answers a check call at 9 a.m. has told you where the truck was at 9 a.m. By the time the receiver calls at 2 p.m. asking where their freight is, that position is five hours stale and the dispatcher is back on the phone. Visibility that arrives on request is not visibility. It is a faster check call.
The four ways a position reaches you
A truck's position can get to your board four ways. They are not interchangeable, and a brokerage that wants every load covered usually needs three of them.
The driver's phone, through an app. The most reliable source when it works, because the app keeps reporting with the screen locked and the phone in a pocket. It needs the driver to install something and grant background location, which is a real ask of a driver you will never meet. It is the right answer for your own fleet and for carriers you use every week.
The driver's phone, through a text link. A link the driver taps once that opens a page and shares location from the browser. No install, so the take-up is far higher. The catch is that browsers stop reporting when the tab goes to the background or the phone locks, so what you get is a burst of positions while the driver is looking at it, then silence. Good for a one-off carrier; not something to build an ETA on.
The carrier's ELD. Every interstate carrier has one, and the bigger platforms offer an API. When the carrier grants access you get a position every minute or so with speed and heading, with nobody touching a phone. The limit is the granting: it takes a carrier with an admin who knows how, and most small carriers will not do it for a broker they have hauled two loads for.
A live-sharing link from the carrier. The one most brokers already have and most tools ignore. Samsara and Motive both let a carrier send a link to a page that shows one truck live, and carriers hand them out freely because it costs them nothing. Read automatically, that link is as good as the API. How to track a load from a carrier share link covers what those links contain and how long they last.
| Source | Asks the driver to | Keeps reporting when | Typical cadence |
|---|---|---|---|
| Driver app | Install, grant background location | Phone is locked, app is closed | Every 20 to 30 seconds while moving |
| Text link | Tap once | The page is open on screen | Seconds, then nothing |
| ELD API | Nothing | Truck is on | About a minute |
| Share link | Nothing | The link has not expired | Seconds, read once a minute |
What real-time should mean
Vendors use the phrase loosely. Here is a working definition: a position no older than five minutes on any load in transit, without anyone asking for it, and a warning the moment that stops being true. The five minutes is not arbitrary. A truck at highway speed covers about five miles in that time, which is close enough for an ETA and for telling whether it has left the corridor. Tighter than that is nice on a map and changes no decision. Looser than that and the position is a memory, not a location.
The second half of the definition is the one that matters. A board that shows a position without showing its age lets a dispatcher trust a dot that stopped moving two hours ago. Every position should carry a timestamp, and the board should say plainly when the last one is older than the threshold you set, so that a truck that has gone quiet looks different from one that is fine.
From a position to knowing
A position on its own tells a dispatcher almost nothing. The work is turning it into an answer to the questions they actually have: is this load going to make its appointment, is the truck where it should be, and has anything changed since I last looked. That takes four pieces.
A route. The road distance from the truck to the next stop, planned for a real truck rather than a car. A 53-foot trailer does not take the road a sedan takes, and an ETA built on a straight line between two dots is wrong by an hour on a long lane. The route should be labelled a planning estimate, because the driver follows the signs and their own navigation, not your map.
An ETA that accounts for the driver. Distance divided by speed ignores the eleven-hour drive limit and the thirty-minute break. A truck four hundred miles out at 4 p.m. with three hours left on the clock is not arriving tonight, and an ETA that says it is will be wrong in the most expensive way, confidently.
Geofences at the stops. A radius around each facility so arrival and departure are recorded from the position rather than from a driver remembering to tap a button. This is what makes detention a fact rather than an argument.
A check against the plan, on a schedule. Every active load re-evaluated on a fixed cadence against a fixed list: tracking gone stale, stopped mid-transit longer than it should, off the corridor, running late for the window, still at a stop past free time, no proof of delivery after leaving the receiver. LoadSignal checks active loads on a five-minute schedule and on relevant load events. That cadence, and the list, are what most people mean when they ask for automated track and trace without quite saying it.
What the customer sees
The point of tracking shipments this closely is not the map on your wall. It is that the customer stops emailing. Give them a link to a page that shows the stops, the appointment windows, the truck's last position and the current ETA, so they can check progress themselves. The page should make position freshness clear and keep the driver's name and phone number private. In LoadSignal, the position appears only while tracking is active.
Where to start
If you are running on check calls today, the first move is not the driver app. It is asking for the share link on every rate confirmation and reading it automatically, because it costs the carrier nothing and covers the loads that are hardest to see. Add the app for your own drivers and your regulars, keep the text link for the one-offs, and let the board tell you which loads have gone quiet instead of finding out from the receiver.
LoadSignal takes all four sources into one board and checks active loads on a five-minute schedule and on relevant events. It is in early access for brokerages moving roughly a hundred to a couple of thousand loads a month. The track and trace page describes the function it replaces, and early access starts with a call where your thresholds are set up with us.