Package Vertex Base
Long warehouse aisle with packed shelves and pallet traffic

Field notes ·

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.

Failed-attempt arguments on a dispatch floor have a familiar shape. The rider says the guard would not let the van in. The customer desk says the recipient was downstairs with the IC. Both people can be telling the truth about different stops, and the code on the screen will not settle it.

In May we counted one week of “no access” marks for a hub that covers Seri Kembangan and parts of Puchong. Of the 118 marks, 41 sat inside a forty-minute window after 12:15 p.m. on two shop-lot streets. Those stops share a pattern: the rider can see the unit, cannot park, and would rather close the stop than circle. That is not a guardhouse story.

Another cluster sat on a gated street in Bandar Puteri after 7 p.m., where the access code on the waybill was blank. That cluster deserved a different briefing: fill the access field at booking, or stop promising an evening drop you cannot enter.

The point of a pattern study is not to catch riders out. It is to stop treating every fail code as a moral event. Once the week is counted, a supervisor can change the lunch-hour sequence on two streets without writing a memo about professionalism.

Bring a de-identified extract with timestamps, codes, and locality if you have it. Without locality we can still read hours and codes, and we will say in the note that the streets remain unnamed. A note that admits what it cannot see is more use than a tidy chart that invents a map.

All field notes