Safety Management System (SMS)
A Safety Management System (SMS) is the documented set of policies, procedures, and practices required by the ISM Code for the safe operation of a ship and environmental protection. It covers emergency procedures, maintenance, crew training, and incident reporting. Flag state and class surveyors inspect the SMS.
Definition
Semantic definition
- Subject
- Safety Management System (SMS)
- Predicate
- is the ISM-required document that
- Object
- defines all policies, procedures, and practices for safe ship operation and environmental protection.
Safety Management System (SMS) is the ISM-required document that defines all policies, procedures, and practices for safe ship operation and environmental protection.
What is a Safety Management System?
A Safety Management System (SMS) is the documented set of policies, procedures, and practices that an ISM-certified shipping company and its vessels must operate under. Required by chapter IX of SOLAS, the SMS defines how the company manages safety and environmental protection at sea and ashore. It covers every aspect of vessel operation: emergency procedures, maintenance management, crew training, voyage planning, accident and near-miss reporting, and continuous improvement. The SMS is not a binder on a shelf — it is the living operational framework that flag state auditors, classification societies, and Port State Control inspectors assess.
Required Elements of an SMS
ISM Code section 1.4 defines the minimum elements the SMS must address. These are not optional; every item must be documented, implemented, and verifiably functional.
Safety and environmental policy
A clearly stated commitment to safety and environmental protection, signed by the highest level of management and communicated to all personnel.
Company responsibilities and authority
Clear definition of who is responsible for what — ashore and on board — with documented lines of authority and communication.
Resources and personnel
Procedures for manning vessels with qualified crew, providing training, and ensuring crew familiarisation with the SMS. The company must verify that crew are competent for their duties.
Plans for shipboard operations
Documented procedures for all key shipboard operations: port approach and departure, mooring, anchoring, cargo and passenger operations, bunkering, and any identified high-risk activities.
Emergency preparedness
Procedures for identifying, responding to, and recovering from emergency situations on board. Muster lists, emergency contact chains, DPA contact, and drill schedules.
Non-conformities, accidents, and hazardous occurrences
A formal process for reporting, investigating, and learning from nonconformities, near-misses, and incidents. Root cause analysis and corrective action records are required.
Maintenance of ship and equipment
Procedures for identifying critical equipment, planned maintenance intervals (PMS), defect identification and rectification, and inspection by class societies.
Documentation
The SMS itself must be documented and version-controlled. All records required by the SMS (drills, maintenance, audits, incident reports) must be retained for the required period.
SMS Audits and Certification
The SMS is audited by the flag state or recognised organisation during the ISM certification cycle. An initial audit covers shore company and vessel. Subsequent audits (intermediate and renewal) verify that the SMS remains functional and updated. Internal audits by the DPA are also required annually. Auditors look for implementation evidence — signed drill records, completed PMS tasks, nonconformity close-out reports — not just documentation of intent.
Common SMS Failures
The most common SMS failures found in PSC inspections and ISM audits are: the SMS documentation exists but crew do not follow it in practice; drills are recorded but crew cannot demonstrate competency; maintenance records have gaps or are not signed; nonconformities and near-misses are not reported; the SMS is not updated when operations, crew, or equipment change; and DPA is unreachable or role is not understood by crew. Each of these indicates a gap between the documented system and operational reality.
The 12 Elements of an ISM-Compliant SMS
An ISM-compliant Safety Management System must cover the full management cycle of a vessel, not only emergency procedures or maintenance checklists. The commonly used twelve-element structure gives auditors, masters, DPAs, and yacht managers a practical way to test whether the system is complete. 1. Safety and environmental protection policy: the company must state its commitment to safe operation, pollution prevention, continuous improvement, and compliance with mandatory rules. This policy should be signed by senior management and understood by crew, not hidden in the first pages of a manual. 2. Company responsibilities and authority: the SMS must identify who owns each safety management duty ashore and on board. It should define reporting lines, authority to allocate resources, authority to stop unsafe work, and the relationship between owner, manager, master, DPA, and technical support. 3. Designated persons ashore: the SMS must name or clearly identify the DPA function, explain how the DPA is contacted, and show how the DPA has direct access to the highest level of management. This is the shore-side link that makes the system accountable. 4. Master's responsibility and authority: the SMS must confirm the master's overriding authority for safety, pollution prevention, and requesting company assistance. It should make clear that commercial pressure, guest preference, or schedule commitments do not override the master's safety decisions. 5. Resources and personnel: the company must provide qualified crew, training, familiarisation, medical fitness verification, and adequate shore support. For yachts, this includes seasonal crew changes, charter turnaround pressure, language comprehension, and role-specific induction. 6. Development of plans for shipboard operations: key operations must be planned, documented, and carried out under controlled procedures. Examples include bunkering, anchoring, tender operations, enclosed space entry, passage planning, mooring, guest embarkation, lifting operations, hot work, waste handling, and heavy weather preparation. 7. Emergency preparedness: the SMS must identify likely emergencies, define response procedures, schedule drills, test communications, and ensure the crew can perform under stress. Fire, flooding, man overboard, medical emergency, pollution, grounding, collision, and loss of propulsion are core yacht scenarios. 8. Reporting and analysis of nonconformities, accidents, and hazardous occurrences: the system must make it easy to report incidents and near-misses, investigate root causes, assign corrective actions, and verify close-out. A yacht that never records near-misses is usually not safer; it is usually under-reporting. 9. Maintenance of the ship and equipment: the SMS must connect planned maintenance, defect reporting, critical equipment, spare parts, class survey items, and verification records. Maintenance records should prove that safety-critical systems are inspected and defects are not allowed to disappear informally. 10. Documentation: the SMS itself must be controlled, current, accessible, and understandable. Forms, checklists, manuals, certificates, drill records, risk assessments, and maintenance logs must be retained and protected from uncontrolled revision. 11. Company verification, review, and evaluation: the company must audit its own system, review performance, measure whether procedures work, and make improvements. Internal audits, DPA reviews, management reviews, and corrective action registers are the evidence. 12. Certification, verification, and control: the company and vessel must maintain the required ISM certificates where applicable, including external audits by the flag state or recognised organisation. Certification is the formal output, but the functioning system is what inspectors test.
SMS Documentation: The Living Document Problem
The most dangerous SMS is often not the missing SMS. It is the beautifully written SMS that no longer matches the yacht. Many operators create a manual during initial certification, pass the first audit, and then let the document freeze while the vessel, crew, equipment, cruising pattern, and operating risks change. A yacht may install new tenders, change stabiliser systems, add lithium battery equipment, adopt new waste handling practices, move from private use to charter, or change management company, while the SMS still describes the old operation. That mismatch is exactly what auditors call a gap between documented procedure and operational reality. Crew training exposes the problem quickly. If new crew are familiarised using outdated procedures, they learn the wrong emergency contacts, wrong maintenance responsibilities, wrong reporting routes, or wrong equipment locations. If the deck team is trained on one tender launch procedure while the SMS describes another, the vessel has created a compliance defect and an operational hazard at the same time. The same issue appears in maintenance. If the SMS says that critical equipment must be inspected at a defined interval but the PMS uses a different interval, or if maintenance records are stored outside the controlled system and cannot be reconciled with SMS requirements, an auditor will question whether the company is actually controlling maintenance. A living SMS changes when the operation teaches the company something. After a drill, the SMS may need a clearer muster instruction or a revised checklist. After a near-miss, it may need a new risk control or a better permit-to-work step. After a Port State Control finding, it may need a corrected procedure and evidence that crew were briefed. After an equipment change, it may need updated manuals, emergency isolation instructions, spare parts references, and planned maintenance tasks. The point is not to rewrite the SMS after every minor event. The point is to have a disciplined review process that asks whether the event revealed a weakness in the documented system. Document control is therefore part of the SMS, not an administrative add-on. A controlled SMS should show version numbers, issue dates, review dates, approval authority, document owner, distribution list, and a method for removing obsolete copies from the vessel. If the captain has version 3 on the bridge, the engineer has version 2 in the engine room, and the management office uses version 4, the company cannot prove which procedure is authoritative. Digital systems help only if they control access, versioning, and acknowledgement. A PDF emailed to crew without a read receipt, change summary, or archive policy can create the same confusion as an old paper binder. For yachts, the best SMS documentation is practical, concise, and visibly connected to daily work. It should generate the forms crew actually use: drill reports, risk assessments, permits, maintenance records, defect reports, near-miss reports, and audit checklists. If the SMS requires records that crew never complete, the system is over-designed or badly implemented. If crew complete records but nobody ashore reviews them, the system is performative. A living SMS closes the loop: procedure, action, record, review, corrective action, verification, and controlled update where needed.
SMS for Private Yachts: When Is It Required?
The ISM Code requirement for a certified Safety Management System applies to internationally trading commercial vessels at the relevant convention thresholds, including commercial ships of 500 GT and above. Commercial yachts operating internationally and falling within the ISM scope must hold the appropriate company and vessel certification and operate under an audited SMS. Private yachts that are not engaged in trade are generally outside mandatory ISM certification, even when they are large and professionally crewed. That distinction is important: private use may remove the formal certification requirement, but it does not remove the operational risk that the SMS is designed to manage. Many large private yachts voluntarily operate under an SMS or an SMS-equivalent management system. Flag states often encourage safety management practices below the mandatory threshold, especially for complex yachts with professional crew, long-range cruising, helicopters, large tenders, advanced engineering systems, or frequent guest operations. Some flag administrations and yacht codes also introduce safety management expectations for vessels that are below full ISM scope but still operate commercially or carry higher risk. The exact requirement depends on flag, size, tonnage, use, certification route, and trading area, so operators should verify the vessel's actual flag state position rather than assuming that "private" automatically means "no SMS needed". The private-versus-commercial distinction can change during the vessel's life. A yacht built for private family use may later be offered for charter, placed under a different flag, moved into a commercial yacht code, sold into a managed fleet, or used for promotional, corporate, or event activity that changes the compliance analysis. The SMS question should therefore be reviewed whenever ownership, management, flag, charter status, guest model, operating area, or tonnage certification changes. Waiting until the first charter booking to build a safety system usually creates rushed documentation and weak crew familiarisation. Insurance is another driver. Hull underwriters, P&I providers, lenders, marina operators, and yacht managers increasingly expect evidence that a large private yacht has structured safety management, even where the law does not demand ISM certification. For an insurer, the practical question is whether the vessel can prove competent operation, planned maintenance, crew training, emergency preparedness, and incident reporting. A voluntary SMS can support that evidence. It can also reduce claim friction after a casualty because the owner can show that the vessel had documented procedures, qualified crew, maintenance records, and a functioning shore support chain. A private yacht SMS should be scaled to the vessel. Copying a commercial ship manual into a 35-metre private yacht produces paperwork that crew will ignore. A useful private yacht SMS focuses on the real risk profile: bridge procedures, passage planning, anchoring, tender and toy operations, bunkering, waste handling, guest safety, medical response, fire and flooding response, maintenance control, contractor control, crew familiarisation, and emergency contacts. It should also define who ashore supports the master, even if the person is not formally called a DPA. The voluntary system should still have ownership. Someone must approve procedures, review incidents, track corrective actions, and make sure the yacht does not keep using obsolete documents. On a privately managed yacht, that person may be the captain with support from a yacht manager, technical superintendent, family office, or external safety consultant. On a managed yacht, the management company may provide a DPA-like function even when formal ISM certification is not required. Without named responsibility, a voluntary SMS becomes a folder of templates rather than a working management system. Private yachts also benefit from SMS discipline because they often operate with informal owner involvement. Owners may request last-minute itinerary changes, late-night departures, tender transfers in marginal weather, unusual guest activities, or compressed maintenance windows. A lightweight SMS gives the master a neutral framework for explaining risk and documenting decisions. It turns safety from a personal disagreement into a managed process: identify the hazard, assess the risk, apply controls, record the decision, and escalate where needed. That process protects the owner as much as it protects the crew. For sale and purchase, a well-maintained SMS can also support vessel value. Buyers, surveyors, and insurers want to see that maintenance, defects, drills, incidents, certificates, and crew familiarisation were controlled over time. A yacht with coherent records is easier to diligence than a yacht whose history lives in personal email accounts and crew memory. Even where a voluntary SMS is not legally required, it can make the vessel easier to insure, manage, charter in the future, and transfer to a new owner. The operational case is simple. A yacht does not become safer because a regulation applies to it; it becomes safer because the crew have clear procedures, current records, competent support, and a habit of learning from defects and near-misses. For private yachts, a well-scaled SMS is often the bridge between informal owner operations and the professional standard expected by crew, insurers, marinas, surveyors, and future buyers.
Frequently Asked Questions
Manage Safety Management System (SMS) with HelmOps
Purpose-built for yacht operations — offline-first, compliance-ready.
Track certificates, crew documents, and deadlines in one place
30-day free trial. No credit card required.
Start Free TrialRelated terms
Last updated: