What the ISM Code Actually Requires
The International Safety Management (ISM) Code, adopted by the IMO and mandatory under SOLAS for most commercially operating vessels, requires both the shipping company and each individual vessel to maintain a documented Safety Management System (SMS) — a structured set of policies, procedures, and responsibilities covering safety, pollution prevention, and emergency preparedness. This isn't a vague aspiration; it's an auditable, certifiable system, verified through periodic external audits and enforced through port state control inspection.
Compliance is evidenced by two linked certificates: the company holds a Document of Compliance (DOC), issued after audit of the company's shore-based safety management systems, and each vessel operating under that company holds a Safety Management Certificate (SMC), issued after audit confirming the vessel itself operates in accordance with the approved SMS. A vessel found operating without valid ISM certification, or with serious SMS deficiencies, faces genuine detention risk under port state control.
What a Safety Management System Actually Covers
A compliant SMS typically documents: safety and environmental protection policy, defined shipboard responsibilities and authority, procedures for reporting accidents and non-conformities, emergency preparedness procedures (drills, contingency plans), procedures for internal audits and management review, and maintenance procedures for the vessel and its equipment. This is a genuinely comprehensive system, not a single binder of generic policies — a well-implemented SMS is specific to the vessel type, trade, and company operating it.
How ISM Compliance Gets Verified at Port
Port state control inspectors routinely check ISM compliance as part of a broader inspection, reviewing the vessel's SMC and DOC validity, examining whether crew members can demonstrate familiarity with the SMS's actual procedures (not just its existence), checking records of internal audits, non-conformity reports, and corrective actions, and observing whether documented procedures — particularly around drills and emergency preparedness — appear to be genuinely followed in practice rather than existing only on paper.
This last point matters enormously in practice: inspectors are specifically trained to distinguish a genuinely functioning SMS from one that exists only as documentation, and a crew unable to demonstrate familiarity with their own vessel's procedures during questioning is a serious red flag that can trigger a much deeper inspection.
Where the Ship Agent's Role Fits In
While ISM compliance itself is fundamentally the company's and vessel's own responsibility, ship agents frequently play a genuine practical support role around SMS-related matters at port. This includes coordinating logistics for an external ISM audit taking place during a port call (arranging auditor access, coordinating timing with cargo operations), supporting documentation requests from port state control inspectors reviewing ISM-related records, and — in the event of an accident or non-conformity during the port call — supporting the accurate, prompt documentation that a well-functioning SMS itself requires.
This connects to the same documentation discipline theme running through much of ship agency work — see our guides on [laytime and demurrage documentation](/blog/laytime-demurrage-explained-ship-agent-documentation-role-2026) and the [Notice of Readiness](/blog/notice-of-readiness-nor-explained-ship-agent-role-2026) for related examples of how an agent's documentation competence has real, practical consequences beyond the immediate port call.
Why This Matters for Operators Choosing a Port-Level Provider
An agent genuinely familiar with ISM-related processes and port state control expectations is better equipped to support a smooth inspection, and to help coordinate effectively if an SMS-related audit or query arises unexpectedly during a call. This is a reasonable, specific question to ask an unfamiliar agent — not because the agent bears ISM responsibility themselves, but because their familiarity with the process reflects the broader operational competence covered in our [pre-arrival information checklist](/blog/vessel-pre-arrival-information-checklist-ship-agents-2026).
Conclusion
The ISM Code requires a genuine, auditable Safety Management System for both the company and each vessel, verified through certification and enforced through port state control inspection with real detention consequences for serious non-compliance. While ISM responsibility sits fundamentally with the company and vessel, a ship agent's practical familiarity with SMS-related logistics and documentation is a genuine, if often underappreciated, operational competence worth considering when evaluating a port-level provider.
Frequently Asked Questions
Q: What's the difference between a DOC and an SMC?
A: The Document of Compliance (DOC) is issued to the shipping company after audit of its shore-based safety management systems. The Safety Management Certificate (SMC) is issued to an individual vessel after audit confirming it operates according to the approved SMS — a vessel needs both a company holding a valid DOC and its own valid SMC to be ISM compliant.
Q: Can a vessel be detained for ISM non-compliance?
A: Yes — invalid or expired ISM certification, or serious SMS deficiencies identified during port state control inspection, are a recognized basis for detention, not merely an administrative note.
Q: Does the ship agent bear responsibility for a vessel's ISM compliance?
A: No — ISM compliance responsibility sits with the shipping company and vessel itself. The agent's role is practical support (logistics, documentation coordination) rather than compliance responsibility.
Q: What do port state control inspectors actually check regarding ISM?
A: Certificate validity, crew familiarity with actual SMS procedures (through questioning, not just document review), records of internal audits and corrective actions, and whether documented procedures appear genuinely followed in practice, particularly around emergency preparedness.
Q: How can operators find an agent familiar with ISM-related port processes?
A: A maritime services directory such as [PortServiceFinder](/ports) lets operators review verified agent profiles by port, and asking directly about experience supporting ISM audits or port state control inspections is a reasonable question before appointment.