Hub exceptions
Hub exception desk for broken seals, audit holds, and ambiguous inbound
This is where non-routine hub work gets isolated and resolved. The goal is a decisive desk that makes cause, severity, and the next corrective action obvious in one scan.
Critical queue
Separate abnormal inbound from the normal lane
Exception work should be triaged fast, with enough context to decide whether a pouch can be released or must stay isolated.
Queue pressure
0 exceptions need attention
This number should feel operationally sharp: if it rises, the desk should still stay readable rather than devolving into a wall of warnings.
0 shipment0 pouch
Pouch review
No pouch currently waits for re-review
Seal integrity and actual weight should be enough to either release the pouch back into flow or keep it on hold without ambiguity.
Review stays localNo hidden side workflow
Return path
Clear exceptions back into the main hub flow
Once an issue is resolved, operators should be able to return to the regular receive, scan, and dispatch lanes immediately.
Back to hubNo duplicated work
Review desk
Review the next pouch under hold
The desk should always present one clear corrective action rather than forcing operators to interpret a generic status table.
Review exception pouch
Most recent exception activity
Exception queue is clearNo abnormal inbound work is active right now.
Queue detail
Shipment and pouch issues stay separate
Operators should be able to see whether the problem is with the whole shipment or with a specific pouch before they take action.
No shipment-level exceptions are active right now.
No pouch-level exceptions are active right now.