When ship managers ask me what a SIRE 2.0 compliant SMS looks like, the honest answer is that the question itself reveals the problem. Most companies are still treating the SMS as a document to be inspected rather than a system to be demonstrated. SIRE 2.0 has changed what inspectors are looking for — and a lot of SMS documents written under the previous regime are not equipped to show it.
The Inspector Is Tracing a Thread
The shift in SIRE 2.0 is not subtle once you understand what the inspector is actually doing. They are not checking whether a procedure exists. They are tracing a thread — from the regulatory or manufacturer requirement, through the SMS, through the planned maintenance system, to the crew member responsible, and finally to the record that proves it was done correctly.
Every link in that thread has to hold. If the SMS has a procedure but the officer standing in front of the inspector cannot explain it, that is a finding. If the record exists but the process it was supposed to follow is not defined in the SMS, that is a finding. If the SMS procedure is correct but the PMS entry does not reflect it, that is a finding.
The procedure existing is no longer sufficient. The thread has to be complete. That is the standard a SIRE 2.0 compliant SMS is now held to.
What a Fire Extinguisher Check Reveals
Take fire extinguisher servicing — monthly checks, quarterly checks, six-monthly checks. Most ships have entries for all of these. What the SIRE 2.0 inspector is tracing is whether the SMS reflects what the manufacturer actually specifies, whether the PMS intervals align with the SMS, whether the officer conducting the check knows what they are looking for at each interval, and whether the record produced at the end demonstrates that specific checks were carried out — not simply that the item was inspected and found satisfactory.
That last point matters more than most ships appreciate. Inspected — satisfactory is a record of an outcome. SIRE 2.0 wants evidence of a process. Those are not the same thing.
I have sat in interviews with competent, experienced officers who could not tell me the difference between what they were checking at the monthly interval versus the six-monthly one. Not because they were not doing the job, but because the SMS had never drawn that distinction clearly, and the PMS had never prompted them to think in those terms. The thread was broken at the SMS-to-knowledge link, and no amount of completed records could repair it during the inspection.
Why Clubbed Entries Fail
The ballast tank vent is a second example that is a small item but works well to explain the issue. Some PMS’s still have a single PMS entry — inspect all ballast tank vents — with work done recorded as: checked, satisfactory.
Under SIRE 2.0, that entry fails on two levels. First, the process is not defined. What constitutes a satisfactory inspection of a ballast tank vent? What is the inspecting officer’s reference point? What condition are they looking for, and what are they looking to rule out? If the SMS does not define this, the inspector cannot conclude that the check was done correctly — only that it was done.
Second, individual items cannot be meaningfully assessed from a grouped record. Ballast tank vents vary in condition, location, and exposure. Clubbing them into a single entry means a deficiency in one vent can pass undetected beneath a satisfactory record for the group. SIRE 2.0 treats each item as a discrete inspection — with its own process, its own record, and its own criteria.
This is not bureaucracy for its own sake. It is the difference between a maintenance system that catches deterioration early and one that produces records of compliance without producing evidence of condition.
The Two Failure Modes
In practice, the observations that come out of SIRE 2.0 inspections cluster into two categories.
The first is process-related: the procedure is missing, incomplete, or does not reflect current regulatory or manufacturer guidance. The SMS was written to satisfy an inspection rather than to guide a crew, and the gaps show under direct scrutiny.
The second is knowledge-related: the process exists on paper but the officer responsible cannot explain it. They know the task. They do not know the system behind it. That gap between doing and understanding is exactly what SIRE 2.0 is designed to surface — through direct crew interviews and through the consistency check between what the SMS says and what the crew describes.
Both failure modes point to the same underlying problem. A SIRE 2.0 compliant SMS is not just more thorough than a compliance document — it is differently constructed. An SMS built for compliance tells a crew what to do. It tells them why the process is structured the way it is, what they are specifically looking for, and how the record they produce demonstrates it.
What a SIRE 2.0 Compliant SMS Has to Demonstrate
A SIRE 2.0 compliant SMS is not a more detailed version of a traditional compliance document. It is a differently constructed one.
The distinction is this: a traditional compliance SMS is written to demonstrate that requirements have been acknowledged. A SIRE 2.0 SMS is written to demonstrate that requirements are understood, applied, and current. The inspector is not reading the SMS to confirm that a requirement has been listed. They are using it as a reference against which to test what they see on the ship and hear from the crew.
That means the SMS has to be operationally coherent. The procedures have to reflect how the ship actually works. The intervals have to match the PMS. The terminology has to be consistent with what the crew uses. Any gap between the document and the operation becomes visible under SIRE 2.0 scrutiny.
The Quick Fix Problem
When an inspection is approaching, the instinct is to find and close gaps quickly. Add the missing procedure, update the PMS entry, brief the officers. That approach worked well enough under previous inspection regimes because the inspection was primarily checking existence — whether the procedure was there.
SIRE 2.0 does not inspect existence. It inspects coherence. A procedure added a week before an inspection, in isolation from the PMS and without crew familiarisation, does not produce a coherent thread — it produces a document with a recent date. The inspector will find the thread broken at exactly the point the quick fix was applied.
Building a SIRE 2.0 compliant SMS is substantive work. It requires reviewing every significant procedure against current regulatory and manufacturer requirements, restructuring PMS entries to reflect individual items and defined processes, and ensuring the language and logic of the SMS is consistent with what the crew has been trained to do. That is not a pre-inspection task. It is an ongoing one.
Most companies understand this in principle. The difficulty is finding the time and the expertise to execute it without disrupting fleet operations — and accepting that the SMS is no longer a background document but an active inspection deliverable, one that has to be maintained with the same rigour as any other critical system on board.
