STCW, MLC, ISM: turning frameworks into workflows

Every maritime operator knows the acronyms by heart. STCW governs the certification and watchkeeping standards your crew must hold. MLC sets the baseline for their working and living conditions. ISM defines how the vessel itself is managed safely. On paper, they read like three separate rulebooks. In practice, they describe a single reality: the right people, properly rested and properly certified, running a well-managed ship. The gap between the frameworks and the deck is where compliance quietly fails.

That gap is almost never caused by ignorance of the rules. It is caused by the distance between a requirement written in a manual and a check that actually runs against live crew data. A certificate expires. A rest-hour pattern drifts out of tolerance. A drill falls off the schedule. Each of these is a known obligation, yet each becomes a finding because nothing was watching the moment it slipped.

From clauses to checks

The work of turning a framework into a workflow starts by treating each clause as a testable condition rather than a paragraph to reread before an audit. A certification requirement becomes a rule that compares a seafarer's held documents against the matrix for their rank and vessel type. A rest-hour provision becomes a continuous calculation over recorded hours, not a spreadsheet reconstructed the night before an inspection. A management-system procedure becomes a scheduled task with an owner and a due date.

Once a requirement is expressed this way, it stops being something you remember and becomes something the system enforces. CruiseControl is built around that shift. The point is not to replace the judgement of a compliance officer but to remove the manual watching, so attention goes to the exceptions that actually need a human decision.

"A rule you have to remember is a rule you will eventually forget. A rule the system runs is a rule that closes the gap before anyone notices it opened."

Where the three frameworks converge

The real value appears when the checks stop living in separate silos. A single crew change touches all three frameworks at once, and a workflow that understands the overlap catches problems a single-framework view would miss:

• The joining seafarer holds valid, unexpired certificates for the assigned rank — the STCW question.
• Their contract length, wage terms, and repatriation entitlements sit inside the agreed limits — the MLC question.
• The change leaves the vessel with a compliant manning table and no watchkeeping shortfall — the ISM question.

Handled as three isolated reviews, those questions get asked at three different times by three different people, and the connections between them go unchecked. Handled as one workflow, they resolve together, and a conflict in any one surfaces before the crew member ever boards.

Closing gaps before they open

The phrase matters. A compliance gap that is caught during an inspection has already been open, sometimes for weeks. The goal of mapping frameworks to automated checks is to move detection upstream, to the moment a condition first drifts out of tolerance rather than the moment an auditor asks about it. An expiring certificate should raise its hand while there is still time to arrange training or a replacement, not after the seafarer is already at sea with a lapsed document.

None of this removes the frameworks or the professional accountability behind them. What it changes is the posture. Instead of periodically proving compliance after the fact, operators maintain it continuously, with the tedious watching handled by workflows and the meaningful decisions left to the people who understand the vessel. That is the difference between reading the rules and running them.