Exception queues that hide missed deliveries
A green dashboard can still sit on top of a queue nobody owns. Last-mile and TMS exceptions only matter if someone is required to close them.
Most transport and last-mile applications we review have an exception screen. Failed geocode, customer not in, gate closed, POD photo unreadable, COD variance. The screen exists. The ownership often does not. Exceptions age, get bulk-closed before month-end, or sit with a supervisor who already has a full outbound.
We treat the exception queue as a primary artefact. Who is assigned. What the SLA is, if any. Whether closing an item updates the customer-facing status. Whether a bulk close is possible without a reason code. In one Klang Valley last-mile review, more than a third of ‘delivered’ stops in a sample week had passed through a failed-attempt state that the buyer app never showed. The rider app and the dispatcher console agreed with each other. The customer did not.
TMS queues hide a different class of miss: the appointment that moved, the detention that never flagged, the POD that arrived as a WhatsApp image and was never attached. If finance later disputes a carrier invoice, the application may have no file to stand on. That is an audit finding even when operations ‘already know’ the carrier.
Before we arrive, export the queue. Do not tidy it. A cleaned queue is a less useful document than an honest one. We would rather read two hundred ageing tickets than a demonstration of an empty inbox.