Safety management (ISM & DSM)
ISM Code Element 9: a practical guide to incident and near-miss reporting for small operators
Element 9 of the ISM Code requires every shipping company to have procedures for reporting, investigating and analysing non-conformities, accidents and hazardous occurrences, and for taking corrective action that stops them happening again. The aim is to prevent the next incident, not to find someone to blame for the last one. For small operators, meeting this requirement is less about paperwork and more about whether crew actually report things, and whether anything changes when they do.
What the Code actually says
Element 9 has two parts:
- 9.1: The safety management system must include procedures to make sure non-conformities, accidents and hazardous situations are reported to the Company, then investigated and analysed with the aim of improving safety and pollution prevention.
- 9.2: The Company must have procedures for putting corrective action in place, including measures to prevent recurrence.
In practice, most companies route reports through the Designated Person Ashore (DPA), but what the Code requires is a reliable route to the Company.
Does this apply to you? ISM vs the DSM Code
The ISM Code applies to SOLAS vessels. Many UK domestic passenger operators come under the Domestic Safety Management (DSM) Code instead, which applies the same principles in a form scaled to smaller operations. Reporting and learning from incidents sits at the centre of both.
What an audit actually looks like
The first time I was audited, it was a DSM Code audit for a small charter company. The owners were badly disorganised, and I didn’t really know what was going on. I turned up at a small home office with five bags of paperwork.
The auditor started with simple questions. First he asked for the induction logs for the fleet, so he could see who had been trained on which boat. I dug through the bags until I found them. Then he asked for the masters’ logs and spent twenty minutes reading through them.
Then the real questions started. This skipper worked on this boat on this date, so where is his induction for that boat? That cross-checking went on all day, one record against another, for hours.
The lesson is that an auditor doesn’t judge each record on its own. They check whether your records agree with each other, and incident reporting gets the same treatment. If a log mentions an engine failure, expect to be asked for the report, the investigation and what was done about it.
That day is what led me to build Helmsman.
Where small operators go wrong
- Near-misses go unreported. In a small company, nobody has told the crew that near-misses should be reported, so most of them are simply missed.
- Reports are phone calls, not records. A mechanical failure or a close call becomes a quick call to the boss: “This nearly happened.” Nothing gets written down.
- The cause is decided, not investigated. The boss decides what the problem was during that phone call, without looking into it, and the real cause is missed.
- The same accident keeps happening. If the root cause is never found, it is never fixed.
- The person who reported it is blamed and left in the dark. Staff can spend an hour being told off for something happening, then never hear whether anything was done about it. After that, they stop calling.
The six stages of a good incident process
- Capture. Log the event as soon as possible, with what happened, where, who was involved, and any photos. If reporting takes longer than a couple of minutes, near-misses stop being reported.
- Triage. Classify it as an accident, near-miss, non-conformity or equipment failure. Decide whether it has to go to an external authority (in the UK, the MAIB, and RIDDOR for some injuries ashore) and how deep the investigation needs to be.
- Investigation. Look for the root cause, not just the immediate error. Ask what failed in the system, not who got it wrong. Include the crew member closest to the task, because they usually know the real answer.
- Severity. Rate both the actual outcome and the potential outcome. A near-miss that could have killed someone deserves the same attention as an injury.
- Outcome and corrective action. Give each action a named owner, a deadline and the evidence needed to close it. “Crew reminded to be more careful” is not a corrective action. Changing the checklist, the layout or the equipment is.
- Learning. Tell the reporter what changed, share the lesson with the rest of the fleet, and review trends at management review.
What auditors look for
Auditors look at patterns and culture, not just individual forms. When records don’t join up, they dig deeper into why.
- Records that agree with each other. The fuel added in the master’s log should match the fuel drawn from the bunkers for the same period. A skipper on duty should have an induction for that boat.
- Checks done when they were due. Not caught up in a batch the week before the audit.
- Everything signed and filled in correctly. Blank fields and missing signatures invite questions.
- Incidents that close the loop. Every event that shows up in a log should have a report, and every report should have a corrective action that has been closed with evidence.
A real example
I was the skipper of a small charter boat. The company’s maintenance regime was simple: if something breaks, we’ll fix it.
On my way to a charter, the engine refused to go ahead. I only had reverse. I ended up going astern for about 4 NM back to the pier, an incredibly dangerous passage, and tied up. I told the owner, changed boats, ran the charter and didn’t think any more about it.
The next day the boat was towed to dry dock and the broken part was replaced. The owner then drove it out of dry dock, and the engine overheated.
The company never gave me a proper explanation. The only account I got came from the owner, while he spent over an hour telling me off. His explanation was that while the engine was stuck in reverse, not enough cooling water was flowing, and that burnt out the impeller. Nobody investigated whether that was actually the cause.
So I looked into it myself, because I wanted to know what I could have done better. This is what I found:
- The engine overheat alarm was broken, and fixing it was on the owner’s to-do list.
- I had reported the overheating, informally, in that phone call. I said the engine smelt and felt very hot, but the gauge was broken.
- The owner never passed that on to the engineer. The yard fixed the obvious fault and missed the one that caused the second failure.
How the six stages would have changed this:
- Capture. A written report would have recorded the smell, the heat and the broken gauge, not just “the engine won’t go ahead.”
- Triage. Going 4 NM astern with a failed drive is a hazardous occurrence in its own right, not only a repair job.
- Investigation. The engineer would have had my report and could have checked the cooling system before the boat left dry dock.
- Outcome. The broken alarm would have been a defect with a named owner and a deadline, not an item on a to-do list.
- Learning. I would have been told what was found, instead of hearing one person’s version of it while being blamed.
Quick checklist
- Can any crew member submit a report in under two minutes?
- Do your crew know that near-misses should be reported, not just accidents?
- Does every report get a response back to the person who raised it?
- Does every corrective action have an owner, a deadline and evidence of closure?
- Do you rate near-misses on their potential outcome, not just what actually happened?
- Would your records survive an auditor checking them against each other?
- Would your crew say reporting is safe? Have you asked them?
Helmsman runs this six-stage process for you — capture to close-out, with the records joined up so they survive an audit.
Join the waitlistAbout this guide. Written by John Wilmans, a working skipper who has been through a domestic safety management audit from the side of the operator being audited.Reviewed by John Wilmans on 23 September 2026.
This guide is general information, not legal advice, and it describes United Kingdom (MCA) — ISM Code and DSM Code. Requirements differ between flag states and administrations — always confirm with your own flag state or administration. Spotted something wrong?Tell me and I'll correct it.