Most captains and chief engineers know the ISM Code exists. Many can recite the high-level structure of it. Far fewer can answer the question that actually matters: when the auditor walks aboard tomorrow, what do they want to see, and is it ready?
This article is about the practical reality of ISM compliance on superyachts — what the Code actually requires, where audits typically find problems, and what separates vessels where compliance is routine from those where every audit is a fire drill.
It's written for captains, chief engineers, DPAs, and management company staff who deal with this regularly. It's not a substitute for reading the Code itself, and it's not legal advice. It's the practical view from years of watching how ISM compliance actually plays out on superyachts.
What the ISM Code actually is
The International Safety Management Code is a chapter of SOLAS — the International Convention for the Safety of Life at Sea — that requires shipping companies to establish a Safety Management System (SMS) for their vessels. The Code was adopted by the IMO in 1993 and has been amended several times since.
For superyachts, ISM applies to:
- All commercially operated yachts of 500 GT and above
- All passenger yachts (carrying more than 12 paying passengers) regardless of size
- Some smaller yachts under specific Flag State requirements
Many private yachts that aren't strictly required to comply still operate under ISM-style systems voluntarily, because the discipline it imposes is genuinely useful and because many owners want their vessels run to commercial standards regardless of registration.
If your yacht is ISM-coded, you have two certificates that matter: the Document of Compliance (DOC) held by the company that operates the vessel, and the Safety Management Certificate (SMC) issued to the vessel itself. Losing either is the kind of event that ends careers.
What the Code actually requires
The Code is structured around principles rather than checklists, which is part of why people find it confusing. It doesn't tell you exactly what to do — it tells you what outcomes you have to achieve, and leaves the implementation to the company.
The core obligations include:
A documented Safety Management System (SMS). This is the master document that describes how the company manages safety across its fleet. Every vessel operates under the SMS of its company.
Designated Person Ashore (DPA). Every ISM-compliant company must have a DPA who provides a direct link between the vessel and the highest level of management ashore. The DPA is supposed to have authority to investigate incidents, allocate resources, and ensure the SMS is being implemented.
Defined responsibilities and authorities. Roles and responsibilities for safety must be documented, both for shoreside staff and for crew aboard each vessel.
Procedures for key shipboard operations. The SMS must include procedures for how critical operations are carried out — anchoring, bunkering, hot work, navigation in restricted visibility, dozens of others.
Procedures for emergencies. Defined response plans for fire, flooding, collision, grounding, medical emergencies, and other foreseeable events. Crews must drill these regularly.
Reports and analysis of non-conformities, accidents, and hazardous occurrences. When something goes wrong, the company must document what happened, investigate root causes, and implement corrective actions.
Maintenance of the ship and equipment. This is the section that intersects most directly with planned maintenance systems. The Code requires the company to "establish procedures to ensure that the ship is maintained in conformity with the provisions of the relevant rules and regulations" and that "appropriate records of these activities are maintained."
Documentation control. The SMS itself must be maintained, controlled, and kept current. Old versions of procedures need to be archived. New versions need to be distributed and acknowledged.
Internal audits and management reviews. The company must audit itself regularly and conduct management reviews of the SMS.
That's the high-level structure. The actual implementation is where it gets interesting.
What auditors actually look at
External ISM audits — performed by Flag State or a recognized organization on the Flag's behalf — are where compliance gets tested. Auditors look for evidence that the SMS isn't just a document on a shelf. They want to see it being lived.
Here's where they typically focus.
The Safety Management Manual itself
The first thing the auditor looks at is the SMS document. Is it current? Is it controlled? Does the version on the vessel match the version held by the company? Are the procedures actually applicable to this specific yacht, or did someone copy a generic template that mentions equipment the boat doesn't have?
A surprising number of audit findings come from SMS documents that don't match the actual operational reality of the vessel. A procedure that references a control system that was replaced two refits ago. An emergency response plan that lists a crew structure that no longer exists. These are unforced errors.
Maintenance records
This is where the equipment register and maintenance history come under direct scrutiny. The auditor will pick a piece of critical equipment — main engines, life rafts, fixed firefighting systems — and ask to see the complete maintenance history. They want to see:
- The manufacturer's recommended service intervals
- Evidence that those intervals have been met
- Records of who performed each service
- Documentation of any deficiencies and how they were addressed
If the records are in a paper file, that's acceptable but slow. If they're in a system that can produce a complete history in two clicks, the audit moves faster and the vessel looks better managed.
The other failure mode here is partial records — a maintenance log that has entries for the first six months and then trails off, or one that has dates but no signatures, or one where the dates don't quite line up with the actual service intervals. Auditors notice all of this.
Certifications
Every certificate that should be valid needs to be valid. Class certificates, statutory certificates, equipment-specific certificates (life rafts, EPIRBs, fire detection systems), crew certificates — all of it needs to be current and producible on demand.
This is where proper certification tracking earns its place. Manual systems lose track of expiries. The certificate that was renewed nine months ago and put in a folder somewhere is fine — until the audit, when you can't find it. The certificate that quietly expired last week is worse — you've been operating without valid coverage and didn't know.
A maintenance system with automated expiry reminders catches both problems. The auditor doesn't need to see the reminder system, but they see the result: every certificate is current, every renewal is documented, the answer to "can I see your X certificate?" is always yes.
Drill records
The Code requires regular drills — fire, abandon ship, man overboard, oil spill, others depending on the operational profile. Drill records must show that they happened, who participated, what was practiced, and what was learned.
Audits frequently find:
- Drills logged but with no detail about what was actually practiced
- Drill schedules that show drills happening on dates the vessel was in transit (and obviously couldn't have run them)
- Crew rotations where new joiners haven't been drilled before going on watch
- Drills logged but with no evidence of debrief or lessons learned
The fix is the same as the fix for maintenance records: a system that makes proper documentation easier than improper documentation, and that makes the records retrievable on demand.
Non-conformity reports
When something doesn't go to plan — equipment fails, a procedure isn't followed, a near-miss occurs — the SMS requires this to be documented as a non-conformity, investigated, and addressed.
The audit failure here usually isn't the absence of non-conformities. It's the suspicious absence of non-conformities. If a 70-meter yacht has run for two years without recording a single non-conformity, the auditor's question isn't "great safety culture?" — it's "what aren't they reporting?"
Vessels that document non-conformities openly and consistently are easier to audit than vessels that pretend nothing ever goes wrong. The Code expects you to find problems and address them. It penalizes hiding them.
Crew familiarization records
When a new crew member joins, they must be familiarized with the SMS, the vessel, and their role. This needs to be documented. Auditors will sometimes interview a recent joiner and ask what their familiarization included — if the answer is "I just kind of figured it out," the audit finding writes itself.
The findings that come up most often
Across superyacht ISM audits, a handful of findings appear repeatedly:
Maintenance overdue or undocumented. A planned interval has passed without service, or the service happened but wasn't logged properly. This is the single most common category of finding and the one a working planned maintenance system prevents.
Certificates expired or about to expire. Often discovered during the audit itself. A platform with automated certification tracking and reminders eliminates this category entirely.
SMS document out of date. A procedure references equipment that's been replaced, or a crew structure that's changed, or a regulation that's been superseded. The fix is document control discipline — knowing which version is current and pushing updates to the vessel.
Drill records incomplete or missing. Drills happened but weren't documented, or drills are scheduled but weren't actually run, or the documentation lacks the detail to demonstrate what was practiced.
Non-conformity reports missing or sanitized. No reports filed for incidents that clearly happened, or reports that are so vague they don't serve their purpose.
Familiarization records missing. New crew joined and went on watch without documented familiarization.
Every one of these findings is preventable. None of them are dramatic individually. In aggregate, they paint a picture of a vessel where the SMS exists on paper but isn't being lived.
What "compliance is routine" actually looks like
The vessels where ISM audits go smoothly aren't the ones where the crew prepares intensively for two weeks before the auditor arrives. They're the ones where the audit is a Tuesday in April that doesn't disrupt operations.
Here's what that looks like in practice:
The SMS lives in current use. Crew refer to procedures, not because they're told to, but because the procedures are useful. Updates flow from the company to the vessel and back without friction.
Maintenance is on schedule because the system says so. Tasks generate themselves at the right intervals. Completion is logged at the time of completion, not the night before the audit. The full history of any piece of equipment is two clicks away.
Certificates renew on autopilot. Reminders fire 60 and 30 days before expiry. The renewal happens, the new certificate gets uploaded, and the system updates. The captain doesn't need to track this manually.
Drills happen on schedule and get documented thoroughly. The crew knows what they're practicing and why. Debriefs surface real lessons that get logged.
Non-conformities get reported as they happen. Not weekly, not monthly — immediately, while the details are fresh. The pattern of reports is honest, which makes the pattern of resolutions credible.
The auditor's questions have answers ready. "Show me the maintenance history for the port main." Two clicks. "Show me the latest fire drill record." Two clicks. "Show me the certificate for the inflatable life rafts." Two clicks.
The compounding effect of all of this is that ISM compliance stops being a performance and starts being a description of how the vessel actually operates. That's the goal.
Where most yachts fall short
The gap between vessels where compliance is routine and vessels where it's a fire drill usually comes down to one variable: whether the SMS is supported by systems that make compliance easier than non-compliance, or whether it depends on individual humans remembering to do everything correctly.
Spreadsheets, paper logs, and disconnected file folders make compliance dependent on human discipline. The discipline is real, but it's fragile. Crew turnover, busy seasons, equipment changes, and simple human attention all create gaps.
A purpose-built operational platform closes those gaps by making the right action the easiest action. Tasks generate automatically. Records create themselves as a byproduct of work being completed. Reports run on demand. Certificates remind themselves.
This is exactly what YMS360 was built to do. It was designed by a team that's been supporting ISM-coded superyachts since 1999, with the audit experience to know what auditors actually want to see and the operational experience to know what makes documentation routine instead of burdensome.
If your next ISM audit is coming up and you're already worried about it, that's a signal worth listening to. We'd be glad to show you what compliance looks like when the system is doing the work.