Failed-attempt pattern study
A focused reading of “unable to deliver” events: which codes repeat, which streets and time windows they cluster on, and whether a second knock was ever recorded.
We sit with dispatch and trace how parcels actually move through the tracking app.
On the trail
What a review actually looks at
-
01
Scan gaps between pickup and first hub
A bag can sit on a feeder van in Jalan Puchong traffic while the app already says “at hub.” We name the event that flipped the status and the station that never scanned.
-
02
Fail codes that hide a second knock
“Recipient not in” may be a locked lobby in Bandar Puteri or a tap from the next street. We count a week before anyone argues about professionalism.
-
03
Notices that leave after the rider has gone
We put three clocks beside each other: rider mark, SMS or WhatsApp send, proof of delivery. A notice that documents a miss is not a notice the recipient can act on.
Flagship engagement
Tracking App Performance Review
For courier firms, last-mile operators, and in-house e-commerce desks that already run a tracking app and need a written account of how it behaves on real consignments. Ten to fifteen working days. One hub. A sample week. A closing workshop on the floor or in the dispatch room.
From RM 8,400 for a single Klang Valley hub. Quoted after a short intake — hub address, typical volume, and the week you want read.
Read the review in full
Related work
Other readings we take
Recipient notice timing review
A comparison of when the rider marked a stop against when the SMS, WhatsApp, or in-app notice actually went out — and whether the recipient still had time to come down.
Hub scan walkthrough
A half-day on the sort floor watching inbound, outbound, and exception scans, followed by a short note on stations that parcels pass without a scan.
Peak-season tracking check
A heavier sample of tracking trails taken before 11.11, Chinese New Year, or Hari Raya, so the desk knows which statuses collapse first when volume rises.
From a hub in Shah Alam
More client storiesThey asked for the exception cage before they asked for a login. We spent a morning in Shah Alam walking inbound bags, then they sent a report that named the exact hour our “at hub” status was jumping ahead of the belt. I still wish the closing workshop had been shorter — two hours on a Friday sort was a lot — but the numbered gaps were things my supervisors could brief the next day.
Field notes
Notes from the trail
When “out for delivery” sits still on a Klang Valley route
The status can turn at 8:10 a.m. while the van is still waiting for a bay in Shah Alam. Here is how we read that pause without blaming the rider first.
Failed-attempt codes that hide a knock that never happened
A code named “no access” can be a genuine guardhouse, or a tap made from the next street. Counting is the only way to stop the argument.
How to sample consignments when you cannot read every bag
A peak week in Cheras will outrun any full reading. A disciplined sample still tells a supervisor where the trail breaks.
Bring a week of consignments. We will tell you if a visit is worth making.
Write with the hub location and the week you want read. We reply within two working days, and we confirm a hub visit window within five working days of a complete brief.