Status: Delivered. Described from our own delivery records. Client identity, brand and commercial terms are withheld. Figures, where given, cover the period stated and nothing beyond it.
Context
A business-to-business supply-chain vendor operating its own delivery-truck fleet. Tours were planned manually on a weekly cycle.
Once a truck left, information came back by phone or at the end of the day, and returns were handled on paper.
The problem
- Planning happened weekly, so any change during the week was handled by improvisation.
- Dispatchers had no view of where a tour had got to or what had gone wrong.
- Drivers recorded deliveries, exceptions and B2B returns on paper, which someone re-keyed later.
- Coordination between office and driver ran over phone calls, leaving no record.
- The delay between work performed and work recorded made every downstream process late.
What we built
A driver mobile application
Connected to the operational system, carrying the day's tour, delivery confirmation, exception capture and B2B returns — designed for a cab, not a desk.
A management-facing tour-planning capability
In the operational system, so vehicles, drivers and routes are coordinated in the same place the orders live.
A continuous feedback loop
What the driver records updates the plan and the operational record immediately, rather than at the end of a shift.
A delivery pipeline for the mobile application
So app releases are a routine, repeatable step rather than an event.
How we delivered it
- 1
Ride along with the process
Map how planning, dispatch and return handling actually work before designing either half.
- 2
Foundation
Environments, source control, an automated build and release pipeline for the app.
- 3
Planning side first
So there was something for the app to connect to.
- 4
Mobile application
Tested by real drivers on real routes, with the offline and glove-friendly constraints treated as design requirements.
- 5
Pilot with one depot
Through a full week.
- 6
Roll-out
Depot by depot.
How it was phased
Indicative phasing for work of this shape. Actual duration varies with data quality, access and decision speed.
What the client keeps
- The mobile application source in their own repository and developer accounts
- The planning configuration
- The build and release pipeline
- Integration documentation