ELD, location, and the driver apps
The log, the truck, and the office.
Hours come off the engine. Drivers work from the iOS or Android app. Dispatch watches the same fleet on the web, without a second system and without another phone call.
Engine-connected logs
Hours recorded from the truck
Live location
The truck on a map
IFTA miles
Distance by jurisdiction
Inspections
DVIR on the driver phone
The desk a dispatcher can run.
Logs, location, inspections, and the miles that used to live in three tools. The sample card above is a sketch, not a customer fleet.
Live location
See where the truck is and replay the recent route, instead of calling the driver to ask.
Hours of service
Driving time comes off the engine. The log follows the trip instead of a paper grid.
Geofences
Mark the yard and the customer. Get an alert when a truck crosses the line.
IFTA
Miles sort themselves by jurisdiction so quarter-end is an export, not a spreadsheet rebuild.
Inspections
Pre-trip and post-trip reports stay with the vehicle, timestamped and ready for an audit.
Safety signals
Harsh driving, idle time, and fatigue risk show up before they turn into a violation.
Yard moves
Geofences can separate yard moves and unassigned driving from a normal trip.
One record
The phone and the office read the same hours, location, and inspections. Nothing is retyped.
From the box to the first log.
01
Plug in the device
It connects to the truck’s ECM port. Hours and location leave the cab from there.
02
Open the driver app
The driver signs in on iOS or Android. Hours and location stay in sync with the cab.
03
Run it from the office
Dispatch watches the map, reviews logs, and pulls IFTA and inspection reports.
Four surfaces. One fleet.
A cab device, a driver app for each phone, a web dashboard, and the API they share.
01
On the truck
Cab device
Plugs into the ECM port and sends hours and location to the same API the apps use.
02
iOS and Android
Driver apps
Duty status, inspections, and the log, on the driver’s own iPhone or Android phone.
03
In the office
Fleet web
The map, the hours, IFTA, and inspection reports for the person running dispatch.
04
Underneath
API
One service behind the dashboard and both phone apps, so a truck does not have three copies of the truth.
Built for fleets that still feel small.
Owner-operators
One truck, one log, and a phone app that is the whole back office.
Small carriers
A handful of trucks on one map, with logs the office can open without a second system.
Growing fleets
The same device, the same apps, and the same dashboard as trucks get added.
| Job | Paper | TimeTrack |
|---|---|---|
| Hours | Written by hand | Read from the engine |
| Where is the truck | A phone call | On the map |
| IFTA | A spreadsheet | Miles by jurisdiction |
| Inspection | A clipboard | On the phone, stored with the truck |
Questions from the first call.
How does a truck get onto TimeTrack?
The device plugs into the ECM port. The driver signs into the iOS or Android app. The office then sees that truck on the web dashboard.
Do drivers need their own phone?
Yes. The driver app is the screen for duty status, inspections, and the log. It runs on current iOS and Android phones.
What does dispatch actually open?
A web dashboard: live location, recent route, hours, IFTA miles, and inspection reports. It reads the same API as the driver apps.
Is location a separate product?
No. Hours and location come from the same cab device and show up in the same apps. Geofences, route history, and IFTA sit on that feed.
Tell us about the fleet.
These questions start a conversation. They are not a quote and they are not an order.
- 01
How many trucks are in the fleet?
- 02
Owner-operator, or a carrier with an office?
- 03
Logs only, or logs and live tracking?