If you asked your import ops team to track how they spend their day, the split would look something like this: 60-70% reactive firefighting, 30-40% proactive work. That ratio is backwards, and everyone knows it.
The reactive work looks like this:
Checking carrier portals one by one to see if releases dropped. Logging into terminal websites to check availability. Scrolling through email looking for customs release notifications. Calling the drayman to confirm they're actually going to make the pickup. Explaining to a client why their container has been sitting for three days.
Why the ratio is so bad
The root cause isn't laziness or understaffing. It's system fragmentation. The information your team needs to do their job proactively lives in 6-10 different places:
- Carrier portals (Maersk, MSC, CMA CGM — each with their own login)
- Terminal websites and appointment systems
- TMS (CargoWise, Magaya, GoFreight)
- Customs broker status feeds
- Email inboxes (individual, not shared)
- Spreadsheet trackers built by whoever was here before you
Nobody has a unified view of "which containers can actually move right now, and which ones are about to cost us money." So the team builds that view manually every morning, and it's outdated by lunchtime.
What proactive actually looks like
A proactive ops team starts the day knowing: which containers are actionable right now, which are approaching free-time expiry, which are blocked and why, and who needs to do what to unblock them.
That doesn't require replacing your TMS or buying a new platform. It requires connecting the status information that already exists into a single prioritized queue — ranked by cost exposure, not by who happens to yell loudest.
The shift from reactive to proactive typically saves 15-25 hours per week across a 4-6 person ops team. Not because the work disappears, but because the team stops rebuilding the same picture from scratch every day.
See how a regional forwarder shifted to proactive exception detection — catching 85% of problems before they became charges.
If this sounds familiar, the logistics operations AI agents use case shows exactly how to implement this, and the demurrage leak breakdown explains where the money is slipping today.
