Introduction to the ISM Code

Every DOC and SMC certificate on a vessel's bridge traces back to the same origin: a string of avoidable accidents in the 1980s that made regulators conclude technical standards alone weren't enough — the way ships were managed, ashore and on board, had to become part of the rulebook too. That conclusion became the ISM Code, and it's still the foundation every safety management system on every vessel operates under today.

Why the ISM Code Exists

The Code's origins go back to the late 1980s, a period when a string of serious maritime accidents — including the capsize of the ro-ro ferry Herald of Free Enterprise in 1987 — exposed a consistent pattern: the ships involved were often technically seaworthy, but the way they were managed, both ashore and on board, had failed. In 1987, the IMO Assembly adopted Resolution A.596(15), calling for guidelines on shipboard and shore management specifically for ro-ro passenger ferries. That effort evolved through two rounds of guidelines before reaching its current form.

The International Safety Management Code was adopted by the IMO in 1993 as Resolution A.741(18). It became mandatory through a new SOLAS Chapter IX, entering into force on 1 July 1998 for passenger ships and certain tanker and bulk carrier types, and extending to most other cargo ships and mobile offshore drilling units by 1 July 2002.

The reasoning behind treating management as a safety issue, not just an operational one, is blunt: investigations consistently found that a large majority of maritime accidents trace back to human and organisational error, not equipment failure alone. If most accidents come from how people and companies operate, then regulating only the equipment misses most of the risk.

DOC and SMC: What the Two Certificates Actually Mean

The ISM Code produces two linked but distinct certificates:

• Document of Compliance (DOC) — issued to a company, confirming its shore-based Safety Management System meets ISM Code requirements. One DOC can cover a whole fleet.
• Safety Management Certificate (SMC) — issued to an individual vessel, confirming it operates under a company's approved SMS and that the DOC-holding company's system is genuinely being applied on board that specific ship.

A vessel cannot hold a valid SMC unless its managing company holds a valid DOC — the two certificates are structurally linked, one at the company level and one at the vessel level, and an audit finding serious enough can put either at risk.

The ISM Code's Definition of "Company"

One detail that surprises people new to the ISM Code: it doesn't define "Company" as simply "the registered owner." The Code's definition covers the owner, or any other organisation or person — such as a manager or a bareboat charterer — who has assumed responsibility for the vessel's operation. Whoever that is in practice is who the ISM Code holds accountable, regardless of who technically owns the vessel on paper.

This matters operationally because it determines exactly who is legally answerable when an auditor raises a finding: the entity that has actually assumed operational responsibility, not necessarily whoever's name is on the registry.

The Three Objectives Every SMS Must Serve

The ISM Code states its objectives plainly, and every Safety Management System is built to serve exactly these three:

• Safety at sea — the core operational objective.
• Prevention of human injury or loss of life — the objective aimed squarely at crew welfare.
• Avoidance of damage to the environment, particularly the marine environment, and to property — the pollution-prevention and asset-protection objective.

Every subsequent lesson in this Learning Path — the SMS structure itself, the DPA role, how non-conformities are classified, how audits run — exists to serve one or more of these three objectives. When a requirement in the Code seems bureaucratic in isolation, tracing it back to one of these three objectives usually clarifies why it exists.

Common Misunderstandings

• Assuming the DOC alone is sufficient — a vessel still needs its own valid SMC, confirming the system is genuinely applied on board.
• Treating "Company" as synonymous with "registered owner" — the ISM Code's definition can include a manager or bareboat charterer instead.
• Viewing the ISM Code as paperwork rather than a response to real, well-documented accident patterns from the 1980s.
• Assuming ISM compliance is a one-time achievement rather than an ongoing system, verified through recurring audits covered later in this Learning Path.

Frequently Asked Questions