This article gives you a tour of polt.ai driver app — what it is, how to access it, and what each part of the interface does. Use this as a map; once you know where things are, the other polt.ai driver app articles walk you through specific tasks step by step.
What polt.ai driver app is: polt.ai driver app is the driver tracking app that pairs with polt.ai. The driver installs polt.ai driver app on their phone, and from your side you see real-time location data, geofence-based pickup and delivery events, and a map of the route — all of which feed status updates back into the shipment in polt.ai.
Drivers use the polt.ai driver app mobile app on their phone.
Two ways to access polt.ai driver app:
The polt.ai driver app dashboard
When you open polt.ai driver app, you land on the main dashboard, which lists every shipment that has tracking active or has had tracking active in the past.
Dashboard mechanics work the same way as polt.ai:
Favorite filters — see Pinning frequently used filters in the polt.ai help center for the same workflow
Saved filters — for filter combinations you want to reuse
The tracking request page
Once a tracking request has been sent to a driver but not yet accepted, the shipment shows up here with:
polt.ai load ID
Checkpoint frequency (how often the driver's location pings)
Driver's name
Pickup and delivery locations
See Sending a tracking request to a driver for how to send one, and Reviewing tracking sent to a driver for monitoring status.
The shipment detail page
Click any shipment from the polt.ai driver app dashboard to open its detail page. The page has several components:
Header information:
polt.ai driver app load ID and shipment status
Driver name and the option to re-send the tracking message if they haven't accepted yet
Pickup and delivery locations
Checkpoints: time of the most recent ping from the driver's tracker, plus a history of past pings.
Documents: drivers can upload documents (e.g., PODs) directly from the polt.ai driver app (mobile). See Uploading a POD to polt.ai driver app.
Events log: a back-end record of everything happening with the driver's tracker — when tracking was accepted, when the load status changed (e.g., "At pickup"), when signal was lost and for how long, and so on.
The right-side map shows the driver's current location, the route, and the pickup and delivery geofences.
Hover over a pin or checkpoint to see the exact location and time of that ping.
Map legend options (click Show map legend to expand):
Status colors:
🔵 Blue = ahead of schedule
🟢 Green = on time
🟡 Yellow = slightly delayed
🔴 Red = late
Follow driver pins — auto-centers the map on the driver's current location
Predict route — shows the route we expect the driver to take based on polt.ai driver app's data
Show predictive value — shows ETA estimates at upcoming geofences
Geofences: pickup and delivery locations have geofence boundaries. When the driver enters or exits a geofence, polt.ai driver app logs the event automatically and updates the corresponding shipment status in polt.ai.
If a geofence doesn't fire (signal issue, GPS error, driver forgot to start tracking, etc.), you can manually add arrival or departure times on the polt.ai driver app shipment page.
These sync back to polt.ai the same way automatic events do.
Click the "..." menu on any tracked shipment to access:
Edit — change the ping frequency or add rep IDs
Watch — add the shipment to your watchlist
Archive — remove the shipment from your active list
Share — send tracking access to your customer
Available ping frequencies: 10 minutes, 20 minutes, or 30 minutes. Choose based on how closely you need to track the load — more frequent pings drain the driver's phone battery faster.