Nusantara Logistics

An operations dashboard for a regional fleet

Placeholder — invented project, stock photo

Live fleet visibility for dispatchers who previously worked from phone calls.

Client
Nusantara Logistics
Type
Internal System
Role
Product design, full-stack build
Duration
14 weeks
Year
2025
Status enquiries
−68%Status enquiries
Vehicles tracked live
40Vehicles tracked live
Overtime hours added
0Overtime hours added

The challenge

Dispatchers tracked forty vehicles by calling drivers. Delivery status reached customers late and often wrong.

Our approach

We built a dashboard around the dispatcher's actual routine rather than the data model, surfacing exceptions first and keeping routine trips quiet.

  1. Watching a dispatch shift

    We spent two days beside the dispatch desk before designing anything. The pattern was immediate: almost every call was a routine trip confirming it was routine, and the trips that had actually gone wrong surfaced last.

  2. Exceptions first

    So the dashboard inverts the list. Delayed, stalled, and off-route vehicles hold the top of the screen; everything running to plan collapses into a single count. A dispatcher's attention goes where it is needed without being asked to search for it.

  3. Handing it over

    Dispatchers had no appetite for training. We shipped in stages beside the phone-call routine and let the desk drop the calls on its own once the screen proved faster — which took about three weeks.

The screen tells me what is wrong before a customer does. That never used to be true.
Dispatch lead, Nusantara Logistics

The outcome

Status enquiries fell by roughly two thirds, and dispatchers now handle the same fleet without overtime.

Built with

  • Next.js
  • TypeScript
  • Mapbox

Have a problem shaped like this one?

Tell us what you're working on. We'll tell you honestly whether we're the right fit.