The TOS won't save you. Neither will the ERP.

If you're shortlisting companies offering workforce management systems for ports, here's the category error worth spotting early.

You've seen the shortlist. A TOS module bolted onto the cargo-handling system you already run. An HR or ERP module from the SaaS giant that already holds your master data. A "workforce" feature promised in the next release of whichever platform your head office standardised on five years ago. On paper, all three look like valid answers to the same question.

They aren't. Two of them were built for different problems entirely, and one was built thirty years ago for a world that didn't have smartphones, working time directives, or real-time vessel data.

Start with the ERP. ERPs are excellent systems of record for the 30% of a port's workforce who sit at a desk. They hold contracts, qualifications, and payroll accurately, and they integrate cleanly with finance. They do not know that the vessel arriving at 04:00 needs a specific gang composition, that the crane driver rostered for it did eleven hours yesterday, or that the stevedore's medical expires on Tuesday. ERPs answer who. Ports need who, where, when, and whether.

This isn't a failure of implementation effort. Multiple major UK port groups have tried it. One spent close to six years and a team of six architects trying to make a global ERP handle operational shift planning. Another has written off its first attempt and is now onto its second. Without exception, what they produce is a workable module for the office population. The dock, where 70% of the workforce actually earns its money, ends up back in Excel within months. That story is not unusual. It is the median experience.

The TOS story is different but lands in the same place. Terminal operating systems were built to move cargo, not to plan people. The workforce modules inside them tend to trace back to codebases written in the 1990s, when "scheduling" meant a printed weekly rota and "compliance" meant a binder of regulations read once a year. They were never reworked for the constraint-heavy, skills-dense, multi-jurisdictional world ports now operate in. The tell is in who is now asking whom for help: several of the largest TOS vendors have, in the last eighteen months, started approaching specialist workforce-planning providers about partnering. The vendors themselves know.

That leaves the category quietly admitted by both sides: a specialist layer that sits alongside the TOS and the ERP rather than inside them. One that understands operatives, qualifications, rest rules, rota patterns, vessel-driven demand, and multi-site coordination as first-class citizens, not as fields retrofitted into software designed for a warehouse or a finance department.

For a port CIO evaluating companies offering workforce management systems for maritime ports, the question to ask isn't "can this platform do scheduling?" Every platform says yes to that question. The question worth asking is this: what was this platform originally built to do, and what percentage of our workforce does that actually serve?

If the answer is "it was built for the 30%", you already know where the other 70% will end up.