The Designated Person Ashore (DPA)

Every ISM Code requirement in Lessons 1 and 2 depends on one specific person being able to do their job without being blocked, ignored, or overruled by budget politics. That person is the Designated Person Ashore — and the ISM Code goes out of its way to guarantee them a kind of organisational independence almost no other shore-side role has.

The Legal Basis: ISM Code Section 4

Section 4 of the ISM Code — titled simply "Designated Person(s)" — requires every company to designate a person or persons ashore with direct access to the highest level of management. That phrase is doing more legal work than it first appears: it's not describing a normal reporting line. It means the DPA can raise a safety concern straight to the CEO or equivalent, without needing to go through operational management first — specifically so that a safety issue can never be quietly buried by whoever's budget it might affect.

The Code assigns the DPA responsibility for monitoring the safety and pollution-prevention aspects of every vessel's operation, and for making sure adequate resources and shore-based support are actually applied when the ship needs them — not just promised on paper.

Authority vs Responsibility: Why the Code Separates Them

The DPA's job is best understood as two related but distinct things:

The separation matters because responsibility without authority is powerless — a DPA who could see every safety gap but had to ask permission from the department causing it before raising the alarm would be structurally unable to do the job. The ISM Code's insistence on direct access exists specifically to prevent that.

Communication Flow: Ship, DPA, Top Management

This is a deliberately two-way arrow in both directions, not a one-way reporting chain. The Master raises operational safety concerns to the DPA; the DPA verifies, escalates, and coordinates shore-based support back to the ship; and the DPA reports fleet-wide safety and pollution-prevention performance directly to top management, who in turn are expected to act on what they're told — including funding a fix, not just acknowledging the report.

Real Audit Evidence: What Auditors Actually Check

An auditor verifying the DPA role isn't satisfied by an org chart with a name on it. What they typically look for:

• Evidence the DPA has actually visited vessels, not just reviewed paperwork from shore.
• Records showing the DPA raised — and top management acted on — a real resourcing or safety gap, not just routine reports.
• The DPA's own account, cross-checked against the Master's, of how a recent non-conformity or accident was escalated.
• Master's Reviews that reference genuine two-way communication with the DPA, not template language repeated every cycle.
• Confirmation that the DPA has direct access to top management in practice, not just on paper — sometimes tested by asking the DPA to describe the last time they used it.

Case Study: Escalating a Real Incident

The point of the case study isn't the technical failure — it's the escalation path. A vessel that had this scenario land on an operations manager's desk first, with the DPA informed later "for the record," would already be showing the exact structural gap ISM Section 4 exists to prevent.

Common Mistakes Companies Make With the DPA Role

• Appointing a DPA who also holds a conflicting operational role, undermining the independence the position requires.
• Treating "direct access to top management" as theoretical rather than something the DPA is expected to actually use.
• Under-resourcing the DPA function — one person covering a large fleet with no real capacity to visit vessels or investigate properly.
• Writing Master's Reviews that don't reference any real DPA interaction, suggesting the relationship is a formality rather than active.

Frequently Asked Questions