# Tracking that shows the six loads that need you, out of 126 moving. > Freight tracking software that turns ELD, driver app, EDI and check calls into one ETA per load, and drafts the reason, new time and message when one slips. URL: https://roadmark.ai/tracking Language: en 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. Everything else is quietly on time and stays off your screen. These six have a reason attached, an updated ETA, and a drafted next step already waiting. - **48226** (Northgate Home, Brampton ON → Cleveland OH): Snow squall on the 401 near Tilbury ON. ETA 16:10 ET, was 14:30. Next step: Update customer. - **48231** (Keel Building Supply, Hamilton ON → Rochester NY): Driver nears the 11-hour limit before delivery. ETA Tomorrow 08:00, was today 18:00. Next step: Reschedule appointment. - **48239** (Lakeshore Grocers, Mississauga ON → Erie PA): No ELD ping for 2 hours. ETA Holding, last seen 09:40. Next step: Call carrier. - **48244** (Prairie Foods, Brampton ON → Grand Rapids MI): Missed the 13:00 dock slot at pickup. ETA 18:30 ET, was 16:00. Next step: Reschedule appointment. - **48248** (Northgate Home, Mississauga ON → Buffalo NY): Reefer running 41°F against a 34°F set point. ETA 15:20 ET, on time. Next step: Call carrier. - **48252** (Keel Building Supply, Windsor ON → Detroit MI): Held at the border crossing. ETA 17:45 ET, was 14:45. Next step: Update customer. ## Five sources feed one ETA. Roadmark doesn't ask which system to check. It already knows which source is reporting for each load, and falls back to a check call when nothing else is. - **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. ## 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. - **Distance left:** 203 mi - **Through the squall, 38 mi at 38 mph:** 1 h 00 m - **Ambassador Bridge, current wait:** 0 h 30 m - **Detroit to Cleveland, 165 mi at 55 mph:** 3 h 00 m - **Hours of service left:** 4 h 10 m - **ETA:** 16:10 ET - 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 ## When nothing else is reporting, Roadmark asks. Load 48258 has no ELD feed sharing with Roadmark. Instead of a dispatcher dialling the carrier, the Tracking agent texts the driver directly, on behalf of the brokerage that booked the load. ## 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. ## 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. ## Related pages - [Samsara integration: hours of service and ETAs](https://roadmark.ai/integrations/samsara): Samsara feeds Roadmark hours of service, location and engine data every few minutes, so tracking ETAs, dispatch planning and detention all use current data. - [Motive integration: hours of service and DVIR](https://roadmark.ai/integrations/motive): Motive feeds Roadmark hours of service, location, inspections and diagnostics, so tracking, dispatch planning and detention billing use current ELD data. - [project44 integration: location and predictive ETAs](https://roadmark.ai/integrations/project44): project44 feeds Roadmark real-time location and predictive ETAs for carriers already sharing through its network, keeping tracking and the portal current. - [Terminal49 integration: container availability and holds](https://roadmark.ai/integrations/terminal49): Roadmark reads container availability, holds, last free day, fees, appointments and rail events from Terminal49 onto each drayage and intermodal load. - [EDI X12 integration: 204, 990, 214 and 210 explained](https://roadmark.ai/integrations/edi): What EDI 204, 990, 214 and 210 mean, which way each goes and when it's sent, how trading partners are set up, and how tracking status becomes 214s. - [Detention calculator](https://roadmark.ai/tools/detention): What a truck's time at the dock past its free time comes to, on the invoice and on the driver's pay. Companies, people and shipment figures in product examples are fictional. They illustrate workflows and are not customer testimonials or measured results.