The ISM Code Explained: Why It Exists and What It Actually Requires (2026)

The Document of Compliance is issued to the company, verifying its shore-side management system meets ISM requirements across its fleet. The Safety Management Certificate is issued to the individual ship, verifying that vessel is operating in accordance with the approved system. Holding both is necessary for a ship to trade legally — but neither certificate, by itself, verifies the system is being followed in practice day to day, only that it exists and was compliant at the time of certification.

This distinction is the source of most confusion about what ISM certification actually guarantees: a valid SMC confirms a ship's SMS was found compliant at its last audit, not that every procedure in it is being genuinely followed on the specific day an inspector or auditor next steps aboard.

The Code requires a documented system covering, at minimum: a safety and environmental protection policy, defined levels of authority and communication between ship and shore, procedures for reporting accidents and non-conformities, procedures for emergency preparedness, and a structure for internal audits and management review. None of this is optional detail — each element is a specific, checkable requirement, not general guidance.

The company is also specifically required to designate a Designated Person Ashore with direct access to the highest level of management, providing a link between ship and shore that exists independently of the normal operational chain of command — precisely so that a safety concern can reach senior management without depending on the same operational reporting line that might have contributed to the concern in the first place.

The gap ISM was built to close was never really about companies lacking any safety procedures — it was about procedures existing on paper without a genuine mechanism ensuring they were followed, checked, and improved based on what actually happened at sea. A Safety Management System that is comprehensive on paper but not genuinely used day to day satisfies the letter of the Code while missing its entire purpose.

This is exactly what internal and external ISM auditors are trained to probe: not simply whether a procedure document exists for a given operation, but whether crew members can demonstrate they actually follow it, understand why it exists, and know how to report when it doesn't work as written — the same substantive, understanding-based questioning that SIRE 2.0's human factor questions independently converged on for a related reason.

Non-conformities found during ISM audits cluster around a consistent set of categories: near-miss and non-conformity reporting that technically exists but is rarely used in practice, because crew perceive reporting as generating blame rather than genuine system improvement; internal audits that are completed as a formality rather than a genuine review; and management review meetings ashore that don't demonstrably act on issues raised from ships.

The common thread across all of these is the same one running through the Code's original purpose: a system that looks complete in documentation but where the actual feedback loop between what happens at sea and what changes ashore has quietly broken down, often without anyone deciding to break it — it simply atrophies when reporting isn't genuinely encouraged and acted on.

The DPA role is one of the Code's more distinctive requirements, and one of the most underused in practice. Its entire value depends on crew actually knowing who holds the role, how to reach them directly, and genuinely believing that route exists independent of the normal chain of command — not simply knowing the position exists somewhere in the company's organisational chart.

A DPA relationship that only activates after a serious incident, rather than being a genuinely known and used channel for raising concerns before they escalate, is functioning as a compliance formality rather than the safety mechanism the Code intended.

For officers and crew, the practical difference between a ship that merely holds ISM certification and one genuinely operating under it comes down to a few observable habits: near misses actually get reported, not just discussed informally and left there; procedures get followed because crew understand the reasoning behind them, not just because they're documented; and internal audits surface real findings rather than confirming everything is already fine.

None of this requires more paperwork than a well-run ship already generates — it requires the paperwork to reflect what's actually happening, which is the same underlying discipline that keeps every record covered elsewhere in this series, from the Oil Record Book to the Ballast Water Record Book, genuinely inspection-ready rather than reconstructed after the fact.