Safety Leadership Onboard: Why It's Different From Just Enforcing Rules

Two Officers, Two Different Ships

Every seafarer has worked under both kinds of officer: the one who enforces the SMS — checks the boxes, holds the drills, signs off the permits — and the one who, on top of all that, makes the crew genuinely want to flag a problem before it becomes one. Both officers might be fully compliant on paper. Only one of them is providing safety leadership, and the difference matters enormously for what actually happens on that vessel when something starts to go wrong.

What Safety Leadership Actually Looks Like

1. Treating Procedures as a Floor, Not a Ceiling

The SMS defines minimum requirements. Safety leaders treat it as the baseline and actively look for gaps the procedures don't cover — the situation that's technically compliant but still feels wrong, the equipment that passes its check but is clearly degrading faster than the schedule accounts for. Officers who only ever ask “does this meet the requirement?” miss the things that the requirement was never written to catch.

2. Making It Easy to Say “I'm Not Sure”

One of the most consistent findings across incident investigations is that someone, somewhere, had a moment of doubt before things went wrong — and didn't raise it, often because raising uncertainty felt like admitting weakness, or because previous experience suggested it would be brushed off or met with irritation. Safety leaders actively create space for “I'm not sure about this” to be a normal, valued contribution — not a confession.

3. Modelling the Behaviour They Expect

An officer who insists on PPE compliance but doesn't follow it themselves, or who emphasises hours-of-rest compliance for the crew while routinely working through their own rest hours, undermines the message regardless of what they say. Crew calibrate based on behaviour, not policy documents.

4. Treating Fatigue as an Operational Input, Not Just a Compliance Record

Safety leadership means actively factoring fatigue into decisions — not just recording hours of rest after the fact, but considering whether a particular evolution should wait, or whether an extra person should be brought in, because the team doing it is tired. This requires a willingness to push back on schedule pressure from ashore when safety genuinely warrants it — which is itself a leadership act, not just a technical one.