Driver mobile app alongside Geotab Drive

What Geotab’s mobile surface covers today

Geotab’s mobile surface is built for telematics, compliance and driver safety, not for delivery execution. The rest of the delivery workflow comes from elsewhere.

• Geotab Drive. Driver-side iOS and Android app: HOS / ELD logging, DVIR pre-trip and post-trip inspections, in-cab compliance workflow, dispatcher messaging, document scanning. Built for the long-haul or service-vehicle compliance workflow, not for multi-stop delivery with POD capture at every door.
• MyGeotab mobile / web. Fleet manager / dispatcher view: vehicle locations on a map, exception alerts, driver safety scores, custom reports. Internal-facing, not a driver surface.
• Geotab Marketplace add-ins. Third-party driver, dispatch and TMS apps that ride on Geotab’s vehicle data via the MyGeotab API. Useful when an operator already has Geotab and wants a routing or execution layer alongside.

None of those is the working surface a delivery or field-service driver opens at every stop. Geotab wasn’t built to be one.

What an on-road delivery driver app actually needs to do

The driver workflow on the road is a different problem from HOS / DVIR compliance or ERP record access. The app has to be the driver’s whole working surface for the day.

• Turn-by-turn navigation. Native or integrated with Apple Maps, Google Maps and Waze. The driver shouldn’t need a second device.
• Route view with live re-sequencing. The day’s plan laid out by stop, with the next stop highlighted. If dispatch adds or cancels a stop, the app updates in place.
• Proof of delivery capture. Photos, e-signatures, configurable form fields per stop or task type.
• Conditional outcomes. Delivered, refused, partial, failed and the reason. Different outcomes trigger different follow-ups.
• Offline operation. Captures, photos, signatures all queue locally and sync when signal returns. A basement, a rural route or a dead zone can’t block the workflow.
• Barcode and asset scanning. Camera-based scanning for items, pallets, serial numbers, asset tags.
• Vehicle inspections. Start-of-shift pre-trip checklist; end-of-shift sign-off.
• Live GPS. Streams back to dispatch and to the customer-facing tracking page so ETAs stay accurate.

That’s the working surface for a delivery driver or field-service technician. None of it is what Geotab Drive (a compliance and safety app) was built to do.

Where Geotab users land today without a dedicated delivery driver app

Two patterns are common in fleets running Geotab that haven’t yet added a dedicated delivery driver app. Both create friction at scale.

• Paper route sheets plus phone camera and signature. Driver prints the route at the depot, drives stops, captures photos and signatures on a personal phone or a basic camera. Manual reconciliation at the end of the day; POD evidence sits in someone’s camera roll, not against the order record. Cycle-time on AR invoicing stretches because POD takes a day or two to arrive.
• Generic delivery app, manual sync. A point-tool delivery app captures POD, but data flow back into the order system is manual: a CSV export, a copy-paste. The driver workflow works, the data flow doesn’t, and the AR team waits.

The path forward is a driver app that lives in the same data flow as the route plan: same source for the route, same destination for the captures.

How eLogii’s driver app works

Native iOS and Android, built specifically for delivery and field-service execution. The driver opens the app at the start of their shift and lives in it for the day.

• Daily route view. Today’s plan laid out by stop, with the next stop highlighted, ETA shown, and contact details for the customer.
• Turn-by-turn navigation. Native handoff to Apple Maps, Google Maps or Waze; or in-app navigation depending on configuration.
• Configurable POD per stop. Photos, e-signature, conditional outcomes, custom form fields. Configured at the route or task-type level so different stops capture the right evidence.
• Offline-first. Drivers can complete the whole day with no signal. Captures queue on the device and sync automatically when connectivity returns.
• Barcode scan. Camera-based scanning for items, pallets, asset serials.
• Custom forms. Temperature checks for cold-chain, gate access codes, hazmat handling forms, safety attestations, NPS micro-surveys, vehicle inspections.
• Live GPS. Streams back to dispatch and to the customer-facing tracking page so ETAs update live.
• Multi-language. Interface localized so drivers work in their own language.

How the integration sits alongside Geotab

The driver carries one phone with both apps installed. Geotab Drive stays open for HOS, DVIR and ELD logging. The eLogii driver app is the surface the driver works in for the route. eLogii reads vehicle and driver data from the MyGeotab API and writes completion to the upstream order system.

1. Route into the eLogii app. Open delivery orders pulled from the upstream order system become routable tasks in eLogii. Vehicles, drivers and remaining HOS hours pulled from the MyGeotab API feed the optimizer. The driver’s daily route lands in the app at the start of their shift.
2. Driver completes stops. Navigation, POD capture, photos, signatures, custom forms, conditional outcomes. All offline-capable. Geotab Drive continues to capture HOS events and DVIR in parallel.
3. Sync to eLogii. Captures land in eLogii in real time when signal is available, or on the next sync when it returns. Live GPS streams via webhook (Driver/Task Tracking Update) for dispatch and customer-facing visibility.
4. Write back to the order system. Completion status, POD references (photo IDs, signature image references), timestamps, driver-collected payments and custom form data write back to the upstream order system for invoicing and inventory. The Geotab side stays read-only on eLogii’s part.

End to end: the driver experience is built for the road, Geotab stays the telematics and compliance system of record, AR gets the POD reference the moment the driver completes the stop.

Frequently asked questions

Does Geotab have a driver mobile app?

Yes, but for a different job. Geotab Drive handles HOS / ELD logging, DVIR pre-trip and post-trip inspections, in-cab compliance workflow and dispatcher messaging. It is the driver-side compliance and safety surface. It is not built for the delivery and field-service execution workflow: turn-by-turn navigation to each stop, offline-capable proof of delivery, photos, e-signatures, conditional outcomes for failed visits, custom forms per job type. That is the gap eLogii fills with its own driver app.

What does an on-road delivery driver app actually need to do?

The driver gets a daily route, drives between stops, completes the work and captures the evidence. The app has to handle: turn-by-turn navigation to each stop; the route view with the day’s plan and live re-sequencing if a stop is added or canceled; proof of delivery capture (photos, signatures, configurable form fields); conditional outcomes (delivered, refused, partial, failed and the reason); offline operation so the driver isn’t blocked by patchy signal; barcode scanning for items or assets; live GPS streaming back to dispatch so ETAs can update; secure handoff of the captures back into the system of record.

How does the eLogii driver app run alongside Geotab Drive?

Both apps run on the same phone, side by side. Geotab Drive stays open in the background for HOS, DVIR, ELD logging and dispatcher messaging. The eLogii driver app is the surface the driver works in for the route: navigation, POD, photos, signatures, custom forms. eLogii reads vehicle and driver records (and remaining HOS) from the MyGeotab API so the route plan respects compliance limits. Completion data flows from eLogii back to the upstream order system; nothing is written into Geotab.

Is the eLogii driver app offline-capable?

Yes. Drivers can complete stops, capture POD, photos and signatures with no signal. Captures queue on the device and sync automatically when connectivity returns. Built for rural routes, basement deliveries and dead zones.

Can the driver app capture custom forms per job type?

Yes. Form fields are configurable per route, per stop or per task type: temperature checks for cold-chain, gate access codes, asset serials, hazmat handling forms, safety attestations, NPS micro-surveys. Custom form data flows through to the upstream order system against the matching record.