Your Near-Miss Reporting Looks Healthy. But What Is It Actually Telling You?

Near miss reporting in shipping sits at the heart of any serious safety management system. ISM Section 9 requires it. TMSA KPI 5A scores it. SIRE 2.0 & RightShip RISQ inspectors ask about it. Every SMS I have reviewed — regardless of fleet size or trade — contains a near-miss reporting procedure that is thorough, well-structured, and largely compliant on paper.

The question I ask during a gap analysis is a different one: not whether the system exists, but whether the data it produces is telling you something real.

What Good Near Miss Reporting in Shipping Actually Looks Like

A healthy near-miss reporting culture produces data with texture. Reports vary by department, by trade, by season, by port. The types of observations shift as operational patterns change. High-frequency, low-severity events appear regularly — not because anything dramatic is happening, but because crew on board are noticing, naming, and logging what they see around them.

When I look across a fleet’s reporting records over twelve months, I expect to see that variation reflected. Different vessels, different voyages, different risk profiles — the data should carry some of that operational reality within it.

What it should not look like is a flat line.

The Question a Gap Analysis Asks

During an SMS gap analysis, near-miss reporting is one of the areas I look at closely — not just whether reports are being submitted, but what the reports contain, how they are distributed across the fleet, and whether the findings are connecting back into the system in any meaningful way.

The procedure itself is rarely the problem. Most near-miss procedures I review are well-written. They define hazardous observations, unsafe acts, and near-misses clearly. They describe investigation workflows, root cause methodologies, and fleet dissemination requirements. Some include risk matrices to guide escalation decisions.

What a gap analysis is really examining is whether the procedure and the practice are describing the same organisation.

When reporting volume is consistent across vessels with very different operational profiles, that is worth understanding. When the categories of reports remain unchanged year on year despite changes in trade or cargo, that is worth exploring. When corrective actions are closed on paper but the same observation types continue to appear in subsequent reports, the system is telling you something — though perhaps not what it was designed to tell you.

None of this is a failure of intent. The crews on these vessels are experienced professionals. The shore teams reviewing reports are doing so under considerable workload. The system accumulates data because the procedure requires it to. The gap is between data accumulation and safety intelligence.

Why This Matters for TMSA and SIRE

TMSA KPI 5A at Stage 2 requires that a near-miss and hazardous occurrence reporting system is in place and that trends are analysed. At Stage 3, it requires that the system demonstrably influences safety performance — that there is evidence of learning and of change.

RightShip’s RISQ assessment draws on the same TMSA framework — a fleet’s near-miss reporting maturity is visible in the evidence it can produce at assessment, not just in the procedure it can point to.

The distinction between Stage 2 and Stage 3 is not procedural. It is analytical. A company operating at Stage 2 can show that reports are submitted and reviewed. A company operating at Stage 3 can show what the reports revealed, what changed as a result, and how that change was verified.

SIRE 2.0 inspectors are increasingly looking beyond volume. The CVIQ questions around safety culture are designed to probe whether reporting generates action — whether crew understand what happens to a report after it is submitted, whether they have seen evidence that their observations made a difference. That is a much harder question to answer from a procedure document alone.

What a Mature Reporting Culture Produces

The fleets where near miss reporting in shipping is genuinely working share some observable characteristics. Reporting rates are not the primary measure — what matters is what the reports contain and what the organisation does with them.

Observations tend to be specific and operational: a particular piece of equipment, a recurring condition during a specific type of operation, a communication gap that surfaces during crew changes. The types of hazards reported shift as the fleet’s trading patterns change. Deck department observations differ meaningfully from engine room observations. Reports from vessels on coastal trades look different from those on deep-sea voyages. That variation is what operational reality produces — and it is what genuine engagement with the reporting system looks like.

The shore-side response is equally important. When a report is submitted, the crew who submitted it should be able to see — within a reasonable timeframe — that it was received, reviewed, and acted upon. Not necessarily with a formal investigation every time, but with some visible acknowledgement that the observation entered the system and was taken seriously. That visibility is what sustains participation. Without it, the reporting culture gradually hollows out — not through any single decision, but through the quiet accumulation of reports that disappeared without trace.

When a gap analysis examines near miss reporting, this is the loop it is looking for: observation, submission, shore-side review, response, and feedback back to the vessel. Where that loop is intact, reporting tends to be active and varied. Where it is broken at any point — most commonly at the feedback stage — reporting continues for a while on the momentum of compliance, and then quietly stabilises at whatever level the system expects.

That is a management question, not a compliance question. And it is one that an SMS audit can surface — but cannot answer on its own.