Freight tracking software
Tracking that shows the six loads that need you, out of 126 moving.
Roadmark turns the ELD, the driver's app, EDI status and check calls into one ETA per load. When one slips, it drafts the reason, the new time and the message, so your morning goes to the loads with a problem, not the ones without one.
Each exception comes with the reason and a drafted next step.
- 120
- On time
- 3
- At risk
- 2
- Late
- 1
- No signal
- 48226At riskNorthgate HomeBrampton ON → Cleveland OHSnow squall on the 401 near Tilbury ON16:10 ETwas 14:30
- 48231LateKeel Building SupplyHamilton ON → Rochester NYDriver nears the 11-hour limit before deliveryTomorrow 08:00was today 18:00
- 48239No signalLakeshore GrocersMississauga ON → Erie PANo ELD ping for 2 hoursHoldinglast seen 09:40
- 48244At riskPrairie FoodsBrampton ON → Grand Rapids MIMissed the 13:00 dock slot at pickup18:30 ETwas 16:00
- 48248At riskNorthgate HomeMississauga ON → Buffalo NYReefer running 41°F against a 34°F set point15:20 ETon time
- 48252LateKeel Building SupplyWindsor ON → Detroit MIHeld at the border crossing17:45 ETwas 14:45
Five sources feed one ETA.
ELD
Position, speed and hours of service, straight from the truck.
Driver app
Stop and dock events the driver confirms on the phone, like a pickup or a POD.
Carrier app or EDI 214
Status codes an outside carrier's own system sends automatically.
Visibility networks
A location feed for carriers who already share through a network.
Check calls
A call or text, logged by a person or the Tracking agent, when nothing else is reporting.
One load, explained
Every ETA shows its math, in plain words.
Not a black-box prediction: the distance left, the driver's hours, the delays on the road, and the appointment it has to land inside.
- The delivery window is 14:00 to 17:00 ET, so 16:10 still lands inside it
- 4 h 00 m of driving fits inside the 4 h 10 m of hours left
- The estimate was 14:30 before the squall cut the pace to 38 mph
Check calls without the calls
When nothing else is reporting, Roadmark asks.
- Tracking agent · for Ashgrove LogisticsHi B. Ruiz, quick check on load 48258: how far out are you from Rochester?
- B. Ruiz · Harrow Lane TruckingJust past the exit, maybe 45 more minutes.
- ETA updated to 15:05 ET from this reply
The customer's view
They see the same ETA, and the reason for it.
No map to squint at: a stop timeline, the current ETA, and the documents for the load, updated the moment Roadmark's own view changes.
- The reason travels with the ETA, so "running late" always comes with why.
- Documents show up as they're ready, not after someone remembers to email them.
Running 1 h 40 m behind: snow on the 401
Questions
What dispatch asks about tracking.
Where does Roadmark get a load's ETA?
From five sources: the ELD, the driver app, a carrier's own app or EDI 214, visibility networks and check calls. Roadmark knows which one is reporting for each load and turns them into one ETA.
How is an ETA calculated?
Every ETA shows its math in plain words: the distance left, the driver's remaining hours of service, delays on the road, and the appointment window it has to land inside. It isn't a black-box prediction.
What happens when a load starts running late?
It becomes an exception on the board with the reason, an updated ETA and a drafted next step, such as updating the customer, rescheduling the appointment or calling the carrier. Loads that are on time stay off your screen.
Can you track a carrier with no ELD feed?
Yes. When nothing else is reporting, the Tracking agent texts the driver directly on behalf of the brokerage that booked the load, and the reply updates the ETA. Nobody has to dial the carrier for a check call.
Can our customers see the ETA?
Yes. The customer portal shows a stop timeline, the current ETA with the reason for any delay, and the load's documents as they're ready, updated the moment Roadmark's own view changes.
Which ELDs and visibility networks does tracking work with?
Samsara, Motive, Geotab and Omnitracs for ELD data, and project44 and FourKites for carriers who share location through a network, and Terminal49 for containers at ports and rail ramps. Roadmark connects to any system with an API, so if yours isn't in the integrations directory, tell us what you run and we set it up with you.
Bring today's board. We'll show you the six that need you.
Connect a day of your loads and we'll show you the exceptions Roadmark would have surfaced, with the reasons and the drafted next steps.
- Your loads and your carriers
- Your ELD or visibility provider, if you have one
- Beside your current TMS