A ship safety management system is mandatory under the ISM Code, and in most of the fleets I review the document is technically compliant and still hard to use. It has grown after every observation, with nothing taken out. It was written by one group of people and is read by another. And whether a procedure exists is a different test from whether anyone can find it in time.
This guide to the ship safety management system collects the articles in the SMS Series in one place, grouped by the problem they deal with, along with the related articles on how an SMS is found, controlled and kept current once it is on board.
Why the SMS Grows, and How to Rationalise It
The SMS Keeps Growing. No One Has a Mandate to Cut It Back. — why ISM SMS requirements tell you what to add and never what to remove, the four pressures that add, and what that means for the crew who have to use the result.
Before You Rationalise Your SMS — why volume is the symptom and not the problem, the shadow SMS of circulars, alerts and Master’s reviews, and why the inventory has to come before the mapping.
Why SMS Rationalisation Stalls — who actually owns the work, three patterns that kill the exercise halfway, and why a half-finished rationalisation can be worse than not starting.
Your Crew Can Find the Procedure. That Doesn’t Mean They Can Trust It. — the three structural models in use, what a digital SMS adds, and why documents that agree with each other matter more than which model you pick.
What Vetting Inspectors Test in the SMS
What a SIRE 2.0 Compliant SMS Actually Has to Prove — why inspectors trace a thread from the requirement through the SMS to the record, why clubbed entries fail, and why quick fixes do not hold up.
For the wider picture, How the Vetting System Actually Works explains how SIRE, RightShip and PSC fit together, and What a RightShip RISQ Inspection Actually Tests covers the RISQ side.
Where the SMS Meets the Ship
Your SMS Is in English. That Doesn’t Mean the Crew Read It in English. — SMS language neutrality, and the three places the gap between the people who write the procedures and the people who read them shows up in an audit.
Your Near-Miss Reporting Looks Healthy — whether near-miss data is telling you something real, what a mature reporting culture produces, and why a flat line is a warning.
Who Receives the Pilot — where the SMS answers a question in a single line and the ship answers it differently: what SOLAS requires, three scenarios, and the decision the OOW is left with.
Two related pieces sit nearby. Root Cause Analysis in Shipping looks at what happens after a finding is raised, and The Officer Wrote It Correctly looks at the language problem from the closeout side.
Finding, Controlling and Keeping the SMS Current
These five articles look at the ship safety management system from the other direction: not how it is written, but how it is found, controlled and kept current once it is on the ship. They were written around Wayfinder, VragaMarine’s own SMS search tool, but each one is grounded in what the ISM Code requires.
Your SMS Passed the Gap Analysis. SMS Search Wasn’t Part of the Test. — a gap analysis checks whether a procedure exists, not whether anyone can find it in time.
Objective Evidence Is the Bar — the ISM Code’s own definition of objective evidence is verifiable fact, not a plausible answer, and what that means for AI-assisted search.
Your Working Language Policy Covers the Manual — ISM 6.6 covers the language the SMS reaches the crew in, and says nothing about the language a crew member has to search in.
A Wrong Answer Doesn’t Fix Itself — when an AI search answer is wrong, document control means someone with authority has to approve the fix first.
The Manual Got Sent — ISM 11.2 requires valid documents everywhere and obsolete ones removed, and “sent” is not the same as “current”.
How to Use This Ship Safety Management System Guide
If the SMS has simply grown too large, start with the first group and read the review article before touching a single document. If an inspection is the immediate pressure, start with the SIRE 2.0 article. If the document is fine and the problem is that nobody can find or trust what is in it, the last two groups are the place to begin. For an independent read on whether your SMS is usable as well as compliant, an SMS gap analysis is where that starts, or you can get in touch with a question first.
Two companion guides: the TMSA compliance guide covers the TMSA and DryBMS frameworks an SMS is measured against, and the VDR audit guide covers what recorded bridge data shows about how the SMS is followed at sea.
More from the SMS Series
→ Explore our SMS Gap Analysis Service — Get an SMS Gap Analysis
- Who Receives the Pilot — What the SMS Says and What the Ship Does
- Your Near-Miss Reporting Looks Healthy. But What Is It Actually Telling You?
- Your SMS Is in English. That Doesn’t Mean the Crew Read It in English.
- What a SIRE 2.0 Compliant SMS Actually Has to Prove
- Why SMS Rationalisation Stalls — and What It Leaves Behind
- Your Crew Can Find the Procedure. That Doesn’t Mean They Can Trust It.
- Before You Rationalise Your SMS, You Need to Know What It’s Actually Doing
- The SMS Keeps Growing. No One Has a Mandate to Cut It Back.
