Building a Safety Management System from a blank page is a different problem from maintaining one. A yacht that has operated under ISM for years has procedures shaped by real incidents, drills that have been run enough times to be routine, and a DPA who already knows where the gaps are. A new owner crossing the 500 GT threshold, a management company picking up its first commercial yacht, or a first-time DPA staring at a folder of templates has none of that — and the ISM Code does not hand you a checklist in the order you need to act on it.
This guide is that order: what to write first, how DOC and SMC certification actually sequence for a company or ship with no prior ISM history, what a realistic timeline looks like, and where the setup process most commonly goes wrong. For what the SMS must contain once it exists and how ongoing DOC/SMC certification works, the ISM Code compliance guide covers that in full — this piece is about the build, not the maintenance.
Step 1: Confirm Scope and Appoint the DPA Before Writing Anything
Before a single procedure gets drafted, two things need to be settled and put in writing.
Scope. Does the vessel actually require ISM certification, or is this a voluntary SMS being built ahead of a flag state or insurer expectation? Vessels of 500 GT or more on international voyages carrying passengers or cargo commercially fall under mandatory ISM. Below that threshold, a private yacht or a smaller commercial vessel may still need an SMS to satisfy its flag state's large yacht code, its insurer, or a charter broker's listing requirements — but the certification path and the surveyor's expectations differ. Get this confirmed with the flag state or the chosen Recognized Organization before drafting starts, not after.
The Designated Person Ashore. The DPA appointment is not a line in an org chart — it is a formal, documented designation with a direct link to the highest level of company management, and it is the single point every other part of the SMS refers back to. Who is the DPA, what is the scope of their authority, and how does the Master escalate to them. If this appointment is not written down and signed before procedures reference "the DPA" throughout, you will be rewriting cross-references later. For what the DPA role actually does once the SMS is running, see the DPA glossary entry.
A new DPA appointed only in title, with no defined authority to intervene in safety matters or no real line to top management, is a finding waiting to happen. Surveyors ask the DPA direct questions about incidents and escalation — a hesitant answer about their own authority undermines the entire SMS faster than a missing procedure does.
Who Actually Needs to Be in the Room
An SMS built entirely by one person — usually the newly appointed DPA, working alone at a desk — is a common failure pattern, and it produces a system that looks complete on paper but was never stress-tested against how the vessel actually runs. A first-time build works better with four inputs, not one:
- The Master or captain, who knows the vessel's actual operating pattern, equipment quirks, and crew rhythm — the details a DPA working from a template will get wrong.
- The DPA, coordinating the documentation, holding the authority to sign off on procedures, and acting as the fixed point of contact once certification starts.
- The owner or management company's decision-maker, who signs the safety policy and needs to understand, before the survey is booked, that a genuine SMS changes how the vessel operates day to day — not just what paperwork exists.
- The Recognized Organization, engaged early rather than only at survey time. ROs will often review draft documentation informally before a formal submission, and that early conversation catches structural problems — wrong scope, missing DPA authority, mismatched vessel details — before they become a failed survey.
Skipping the Master's input is the version of this mistake that surfaces latest and costs the most: a beautifully written procedure that describes a watch system or tender operation the crew does not actually follow gets caught the moment a surveyor asks a deckhand to explain it.
Step 2: Write the SMS Documents in an Order That Actually Works
The ISM Code does not mandate a drafting sequence, but building the documentation set in the wrong order is how first-time SMS projects stall. A workable build order looks like this:
- Safety and Environmental Protection Policy — the board-signed statement everything else derives from.
- Company Safety Management Manual — roles, responsibilities, DPA authority, resources and personnel management, document control rules.
- Ship Safety Management Manual and critical operations procedures — written for this specific vessel's equipment, crew complement, and operating pattern, not adapted from a sister ship or a generic template.
- Emergency preparedness plans — fire, flooding, man overboard, severe weather, medical emergency, evacuation — each with a drill schedule attached.
- Forms and record templates — maintenance logs, drill records, near-miss reports, document registers — built before they are needed, not improvised the first time a drill happens.
Writing emergency plans before the company manual exists, or building ship-specific procedures before the DPA's authority is defined, produces documents that reference roles and structures that do not exist yet. Sequence matters more than most first-time builders expect.
For the full breakdown of what each of the eight SMS document categories must contain — policy, roles, resources, operations, emergency preparedness, reporting, maintenance, document control — the ISM Code compliance guide covers the content requirements in detail. This guide focuses on the order and process of building them for the first time.
Step 3: Understand How Interim and Full Certification Actually Sequence
This is the part of setting up an SMS from scratch that trips up first-time DPAs the most: certification is not one event, and it does not happen ship-first.
A newly established company — one with no prior DOC — can be issued an Interim Document of Compliance, valid for up to 12 months, provided it can demonstrate a safety management system that meets the ISM Code's objectives and a credible plan to reach full compliance within that window. This is the bridge that lets a new management company or first-time owner operate legally while the full SMS documentation is finished and tested.
Only once the relevant DOC is in place — interim or full — can the ship-level certificate follow. An Interim Safety Management Certificate can be issued to a new ship on delivery, when a company takes on a vessel new to its fleet, or when a ship changes flag. It is valid for up to 6 months, with a possible extension of a further 6 months, and issuing it requires more than paperwork: an assessed SMS, an internal audit planned within three months, and a crew already familiar with the system — not just handed a manual on embarkation day.
Once the interim period demonstrates the system is genuinely working — not just documented — the full DOC survey and full SMC survey follow, each valid for up to five years, with annual verification on the DOC and an intermediate verification on the SMC between the second and third anniversary.
Step 4: Budget a Realistic Timeline
A first-time SMS build is not a two-week project, and treating it as one is how companies end up rushing an Interim DOC application with documentation that will not survive the full survey.
A workable planning horizon:
- SMS drafting: 4–8 weeks for a focused effort with a competent DPA; longer if the company is also standing up its shore-side structure at the same time.
- Interim DOC application and issuance: several weeks, depending on Recognized Organization availability and how complete the submitted documentation is.
- Operating under Interim DOC / Interim SMC while building operational evidence: the bulk of the interim window — drills need to actually happen and get recorded, maintenance logs need real entries, near-miss reporting needs to start generating real reports, not zero.
- Internal audit before the full survey: required within three months of the Interim SMC being issued, and it should surface problems before the external surveyor does, not after.
- Full DOC and SMC surveys: booked once the company is confident the system will hold up, not at the last possible week of the interim validity period.
Recognized Organization surveyors are frequently booked weeks in advance, particularly during peak charter season when yacht management companies across a region are all trying to schedule at once. Build that lead time into the plan rather than discovering it when the interim certificate is six weeks from expiry.
Common Mistakes That Stall a First-Time SMS Build
Adapting a template instead of writing for the vessel. A generic SMS template is a starting structure, not a finished manual. Surveyors recognize template language immediately, and procedures that reference equipment or watch systems the vessel does not actually have are treated as evidence the SMS was never really built around this ship.
Treating the DPA appointment as administrative. The role needs real authority and a real line to top management, established before the vessel starts operating under it — not a title added to satisfy a checklist item.
Skipping the internal audit before the external survey. The ISM Code requires it, and companies that treat it as optional walk into their SMC survey blind to the gaps a surveyor will find in minutes. A properly run internal audit — independent, evidence-based, with findings actually closed out — is the single best predictor of a clean external survey. The internal audit walkthrough covers how to run one correctly, including who can conduct it and how to classify what you find.
Building forms and records as an afterthought. A drill that happens with no record, or a maintenance job completed with no log entry, is functionally invisible to a surveyor. The record templates need to exist and be in use before the first drill, not designed retroactively once the survey date is confirmed.
Underestimating the crew familiarisation requirement. An Interim SMC specifically requires the crew to already be familiar with the SMS — not simply that copies exist on board. Building familiarisation sessions into the setup timeline, not treating them as a survey-week cram, is what makes that requirement genuine rather than nominal.
Planning the build but not the years after it. Certification is not the finish line. The DOC needs annual verification, the SMC needs an intermediate verification between its second and third anniversary, and the company's own internal audit cycle starts running on a 12-month clock the moment the interim period ends. Companies that pour all their effort into passing the first survey and none into planning who owns the audit calendar afterward tend to relearn the same setup lessons a year later, once the initial adrenaline of certification has worn off and nobody has been tracking deadlines since.
HelmOps' ISM audit checklist tool covers all twelve ISM Code elements with DOC and SMC readiness flags — a reasonable way to sanity-check documentation coverage before submitting for Interim DOC, and again before the internal audit that precedes the full survey.
Where This Fits
Setting up an SMS from scratch is the beginning of a cycle, not a one-time project. Once certification is achieved — interim or full — the same system needs annual internal audits, ongoing maintenance records, and document control that survives crew turnover. The ISM Code compliance guide covers what the finished system needs to contain and how the certification cycle continues after the initial build. The internal audit walkthrough covers the process that keeps it honest going forward.
For the ISM Code's own text and the IMO's guidance on implementation, see the IMO's official ISM Code page.
