Field notes
When exceptions pile on the same lane
Short-ships, refused trailers, and claims often share a corridor. Treating each ticket as a unique accident hides the lane that keeps producing them.
A claims clerk can spend a month treating each short-ship as a new story. The floor already knows the story: the same lane, the same door, the same hour when the wave is borrowed from the afternoon. Exceptions cluster. They are allowed to look random because the tickets are filed by date, not by corridor.
When we map exceptions during a performance review we pin them to a lane and a door before we pin them to a person. A refused trailer at dusk is often the child of a morning dwell, not a sudden act of spite by the receiver. A customs hold that repeats on one SKU family is a bonded-cage problem wearing a warehouse costume.
The mild version of this work is a wall of tickets. The useful version is a single page: this lane, these three exception types, this shift. That page is uncomfortable. It is also short enough to survive a Monday meeting.
Do not wait for a full review if you already suspect the cluster. Pull thirty days of exception codes and mark the destination yard. If one corridor owns half the pile, you have a logistics performance question, not a coincidence. Write to the desk if you want that pile drawn; keep it in the spreadsheet if you prefer the comfort of isolated tickets.