Key takeaways
- Track by exception; assume shipments are fine unless something flags otherwise.
- Let completed shipments leave the active view so the exceptions stand out.
- Alert on the milestones that carry cost or a decision, not every event.
- Normalize identifiers on entry and keep one shared, exportable shipment record.
Track by exception, not by roll-call
The biggest mistake is checking every container every day. It does not scale and it trains the team to skim. Flip the model: assume shipments are fine unless something says otherwise, and let the exceptions come to you. The container that changed, slipped, or stalled is the only one that needs attention today.
Let completed shipments disappear
An active view cluttered with delivered containers hides the ones that still need work. Completed shipments should drop out of the working list automatically. If your active tab shows boxes that were emptied last week, you are paying attention tax on shipments that no longer need it.
Watch the money milestones
Not all milestones deserve equal attention. The ones that carry cost or a decision are the ones to alert on:
- Discharge and availability — the window when free time is burning and pickup must be arranged.
- Last Free Day approaching — the deadline before demurrage begins.
- ETA changes past a commitment — when a slip threatens a delivery promise.
- Discharged-but-not-moving — the classic sign of a hold or a bottleneck.
Standardize how a shipment is entered
Tracking is only as good as the identifiers going in. Normalize container numbers (remove spaces, uppercase), confirm the carrier, and enter shipments consistently so nothing silently fails to track. A mistyped container number is a shipment you think you are watching but are not.
Make the whole team read one record
Tracking that lives in one person's spreadsheet is a single point of failure. When the shipment record is shared, anyone can answer a customer, cover a colleague, or pick up an exception. The goal is that the status does not depend on who is at their desk.
Keep an audit trail
For disputes — a demurrage charge, a delivery claim — the timeline is the evidence. Exportable event history with timestamps turns 'we think it arrived Tuesday' into a defensible record. It costs nothing to keep and occasionally saves a great deal.
Frequently asked
How many containers can one coordinator realistically track?
Far more with exception-based tracking than with daily roll-call. When only the containers that changed surface for attention and completed ones drop off, a coordinator's capacity is limited by the number of exceptions, not the size of the portfolio.
Should I track every container or just the important ones?
Track them all, but do not look at them all. Monitor the whole portfolio so nothing slips through, and rely on alerts and exception views so your attention goes only to the boxes that need it.