Every tanker fleet has layers of navigational oversight. At the base of that structure sits the ship navigational audit — conducted by the Master and Chief Officer, on their own vessel, monthly. Around that sits the marine superintendent’s annual navigational visit. Further out, the independent or VDR-based audit. On the outer edge: SIRE and PSC, where findings become records that follow the vessel commercially.
The logic is sound: each layer catches what the inner layer missed. In practice, most companies have quietly inverted this relationship. The layer closest to the ship — where intervention is cheapest, fastest, and most frequent — is treated as a formality. The layers furthest from the ship, where findings are expensive and consequences are public, end up doing the work that should have been done at the first barrier.
This article is about restoring that first barrier to what it is supposed to be.
“If the ship’s navigational audit finds nothing, it didn’t find nothing. It found something — a problem with the audit.”
What the ship navigational audit hierarchy is supposed to do
Think of navigational oversight as concentric rings. At the centre is the ship itself — the Master and Chief Officer conducting their own monthly internal navigational audit. Around that sits the marine superintendent, whose navigational visit is, for most vessels, an annual event. The ISM Code requires internal audits at intervals not exceeding twelve months; that is the outer limit, not a target. In practice, a vessel may see a marine superintendent on the bridge once a year, if that.
Further out is the independent or VDR-based audit, also typically annual. On the outer edge: SIRE and PSC, which operate on their own schedules, outside the company’s control.
This means that if the inner ring is not functioning, there is an eleven-month gap between each external navigational oversight event in which nothing is caught. Deficiencies accumulate. Habits form. By the time an external auditor steps aboard, what they find is not a snapshot of that week — it is the residue of months of uninterrupted practice.
The ship navigational audit exists to prevent exactly this. Whether it does so depends entirely on how it is conducted, by whom, and how seriously the results are taken ashore.
Why the first barrier quietly fails
The reason ship navigational audits produce thin findings is not usually incompetence. It is a specific, understandable psychological pressure that operates on both parties — the Master conducting the audit and the company receiving it.
The Master’s calculation runs like this: if I find ten observations on my own vessel, I am documenting that standards on my ship are not what they should be. The superintendent will ask questions. It may affect how I am perceived. If I find two minor items, I look like a competent Master who has his ship in order.
The superintendent’s parallel calculation: if I visit and find significant observations, it raises an uncomfortable question — why didn’t the Master find them? Pressing too hard creates friction with a Master he needs to work with for the duration of the contract. And so observations are softened, or not written at all.
The external auditor runs the opposite calculation entirely. An external auditor who finds nothing is questioned. The value of the engagement is measured, implicitly, by what is found. This creates pressure to find — and to frame findings in the strongest defensible terms.
The result of these three pressures acting simultaneously is predictable: findings migrate outward through the audit chain. The ship audit finds little. The superintendent finds a bit more. The external auditor finds the most. And SIRE finds whatever was left.
This is precisely backwards. The most frequent, ship-familiar, lowest-consequence audit — the one where findings can be corrected before they become habits — should be producing the most observations. The external audit, which has no corrective function and carries reputational consequences, should ideally be confirming that the inner layers have already done their work.
What a healthy observation count actually tells you
There is a common instinct among fleet managers to read a low observation count as a good sign. I read it as a warning.
In fleets where the Master’s navigational audit routinely surfaces a meaningful number of observations, what you tend to find downstream is better SIRE performance, fewer PSC deficiencies, and a lower rate of navigational near-misses. The audit is functioning as a corrective mechanism. Standards are being set, measured, and maintained at the ship level.
In fleets where the ship navigational audit produces one or two minor items consistently — regardless of fleet size, trading pattern, or crew composition — the external auditors and SIRE inspectors are finding the observations that should have been caught internally. The findings did not disappear. They just travelled further than they should have before anyone noticed them.
A high internal observation count is not evidence of a poorly run ship. It is evidence of an honest audit.
The new-joiner pattern as a diagnostic
There is a specific trend that appears in fleets where the ship navigational audit is conducted properly, and it is worth understanding because it runs counter to instinct.
When a new Master or Chief Officer joins, the observation count in the first audit of their contract tends to be the highest of the entire tenure. It then tapers as the contract progresses. When the next changeover happens, it spikes again before settling.
This pattern is not a symptom of poor performance. It is the system doing exactly what it should.
A new joiner brings fresh eyes to a ship they have not seen before. They notice discrepancies between what the SMS requires and what the vessel actually does. They find equipment issues that have been normalised by the outgoing crew. They identify procedural gaps that were invisible to people who had lived with them for months.
As the contract progresses and the officer becomes familiar with the vessel, findings naturally reduce — not because standards have slipped, but because the known gaps have been closed and the officer now knows the ship well enough to manage it without generating new ones.
A fleet where every new-joiner audit looks identical to every other audit — flat, low, consistent — is a fleet where nobody is actually looking. The absence of a new-joiner spike is itself a finding.
Monthly cadence. Alternating conductor.
The ship navigational audit should be conducted monthly. This reflects the minimum frequency at which the first barrier can function as a barrier rather than a record-keeping exercise.
Alternating the conductor between Master and Chief Officer serves two purposes. First, it prevents the audit from becoming a single officer’s habit — a checklist completed to a predictable standard with predictable results. Different eyes find different things. Second, it gives the Chief Officer structured, repeated exposure to navigational audit methodology. A Chief Officer who has conducted twelve navigational audits as part of an alternating cycle is meaningfully better prepared for command than one who has observed the Master conduct twelve audits and countersigned them.
The conducting officer should complete the audit independently before any discussion with the other. The findings should then be reviewed jointly. Disagreements about whether something constitutes an observation are worth having — that is where standards are actually set.
Benchmarking is the corrective for suppressed findings
The single most effective intervention for the psychological pressures described above is to make observation counts visible across the fleet.
When a fleet manager can see that Vessel A consistently produces ten navigational audit observations per month and Vessel B consistently produces two, that divergence becomes a question rather than a statistic. It might reflect genuine differences in navigational practice and equipment condition. It might reflect differences in audit rigour. Both are worth understanding.
What benchmarking does is remove the incentive to under-report. When observation count is tracked and compared fleet-wide, producing a consistently low number is no longer a safe position. A Master whose ship navigational audit routinely produces two findings, when the fleet average is eight, is not demonstrating competence — he is inviting scrutiny of a different kind.
Benchmarking also allows near-miss reporting to be read alongside audit findings. A vessel with a healthy near-miss report rate and a high internal audit observation count is a vessel where the safety culture is functioning. Near-misses are being identified and reported because the audit culture has established that finding problems is the right answer, not a liability.
What effective looks like over time
The trajectory of a fleet where the ship navigational audit is genuinely working follows a recognisable pattern.
In the early period, internal audit observations increase. Masters and Chief Officers who were previously producing thin reports begin finding more. This looks worse before it looks better — and it is important that companies read this correctly. The findings were always there. The audit is now surfacing them.
Over the following months, the observation count begins to stabilise and gradually decline. Recurring issues are closed out. Procedural gaps are addressed. Bridge team habits shift under regular oversight. Not immediately, and not linearly — but consistently.
The test of whether this decline represents genuine improvement is what happens to downstream findings during the same period. If SIRE and PSC observations also reduce, or hold stable, Layer 1 has done its job. If internal audit findings decline while external findings stay flat or rise, the audit has not improved navigational standards — it has simply stopped recording them.
The marine superintendent visits once a year. The external auditor visits once a year. SIRE and PSC operate on their own schedules. The ship navigational audit runs every month. The arithmetic of oversight is straightforwardly in favour of the first barrier doing the work. The question is whether the people conducting and receiving it believe that is their job.
If you want to understand what your fleet’s internal audit data is actually telling you — or whether your first barrier is functioning — that is work we do. Get in touch.
More from the HSEQ Series
→ Explore our HSEQ Outsourcing Service — View Service Page
- The Audit Is Closed. The Problem Isn’t.
- The TMSA Safety Audit: What Element 9 Stage 4 Actually Requires
- The TMSA Engine Room Audit: What Element 4 Stage 4 Actually Requires
- The TMSA Mooring Audit: What Stage 4 Requires for Element 6A
- The TMSA Cargo Audit: What Stage 4 Requires for Element 6
- TMSA Navigational Audit: What Each Stage Actually Requires





