Case study / Logistics
Dispatch software for a national freight network
An offline-first dispatch and tracking product for 12,000 drivers moving between coverage gaps, loading docks, and paper manifests.
- Client
- Atlas
- Sector
- Logistics
- Year
- 2025
- Scope
- 3 services
- Services
- Mobile apps / Cloud & APIs / Product design
Atlas / Logistics
Case study / 2025
01
38%
Faster dispatch
02
12k
Drivers on the platform
03
0
Shifts lost to sync
Context
The problem we found
Drivers worked in warehouses and mountain routes with no usable connection. Dispatch ran on radio and spreadsheets, so the operations team learned about failed pickups hours after they happened.
Method
How we worked
Four decisions that shaped the build.
- 01
Designed an offline-first sync model with deterministic conflict resolution for stops and signatures.
- 02
Built native iOS and Android apps from what drivers do at the depot each day.
- 03
Replaced radio dispatch with an event stream the operations room could act on.
- 04
Ran a six-week pilot with 300 drivers before a staged national rollout.
What the client said
“The app works in a basement loading dock. That sounds small until you have watched a dispatch team lose a day to a dead tablet.”