Working without a signal

What the app can do offline, what it queues, and how the catch-up appears to dispatch.

Written for
Drivers
Reading time
1 min
Last reviewed
August 2, 2026

Parking structures, rural routes and hospital basements are normal parts of the job, so the app assumes connectivity will be lost rather than treating it as an error state.

What still works

  • Your trip list and trip details, which are held on the device.
  • Marking arrival, loading, and completing a trip.
  • Capturing signatures, photos and odometer readings.
  • Recording a no-show.

What waits

  • Anything that needs the server right now: new assignments, messages, and live position updates to dispatch.
  • Turn-by-turn guidance for a route not already loaded.

Actions taken offline are queued in order and submitted when the connection returns. Dispatch sees them arrive as a catch-up with their original timestamps, not as though everything happened at the moment you came back into coverage.

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator