What Is a Designated Person Ashore (DPA) — and Do You Need One?

If your vessel falls under the ISM Code, you need a Designated Person Ashore — that part most operators already know. What fewer have thought through is what the role actually requires day to day, what "reachable at all times" means in practice, and why the timezone your DPA sits in can matter as much as their qualifications. For superyachts operating in or heading toward New Zealand, Australia, and the South Pacific, a timezone-appropriate DPA or backup DPA is the difference between cover on paper and cover that actually works.

What the ISM Code actually requires

Section 4 of the ISM Code, "Designated Person(s)," requires every company to designate a person or persons ashore with direct access to the highest level of management, who can be reached at any time to provide a link between the company and those on board.

In plain terms: the DPA monitors the safety and pollution-prevention performance of each vessel, makes sure adequate resources and shore-based support actually reach the ship, and stands ready as the point of contact between the vessel and senior management. That last part — availability at any time — is the requirement most frequently underestimated, and the one Port State Control tests most directly.

What "available at all times" actually means

It means exactly what it says. A vessel does not stop operating at 0200, and emergencies do not wait for office hours. A vessel in difficulty in the South Pacific at 0200 UTC is calling in the middle of the European night — a DPA asleep in the UK, Continental Europe, or the US East Coast is, for practical purposes, unreachable. That same 0200 UTC call lands in the early-to-mid afternoon in New Zealand and Australia. A DPA on the ground in this region is at their desk, not asleep.

This isn't a theoretical compliance gap. PSC officers under the Tokyo MOU — which covers New Zealand, Australia, and the wider Asia-Pacific — and the Paris MOU in Europe both routinely ask to see evidence of DPA contact arrangements, and will test whether the number provided is actually answered. A DPA who can't be reached is a documented deficiency, not an administrative technicality.

Who can be a DPA?

The Code sets out functional requirements: direct access to senior management, a working understanding of the company's SMS, and the training and experience needed to be genuinely competent in the role. In practice, flag states, Recognised Organisations, and PSC increasingly expect documentary evidence of formal DPA competence — structured training covering ISM requirements, emergency response, and the legal responsibilities the role carries. A competent DPA should be conversant with:

• The ISM Code and the company's Safety Management System
• The vessel types and operations involved
• Emergency response procedures and escalation paths
• The flag state's requirements and those of the relevant Recognised Organisation

For larger fleets, the DPA is usually a senior shore-side employee. For smaller operators and individual vessel owners, an externally contracted DPA is a well-established and entirely legitimate alternative.

Not fully ISM-compliant? You may still need this

Not every vessel this applies to carries full ISM certification. Charter yachts under 500GT, vessels running a voluntary or "mini-ISM" safety management system, and private vessels with no statutory SMS obligation at all sit outside the mandatory Code — but the risks the Code was written to manage don't disappear just because the paperwork isn't compulsory.

We see this distinction get missed constantly: a lack of legal obligation is not the same as a lack of need. Captains often say they don't need ISM or a planned maintenance system, when what they usually mean is they aren't legally required to have one — a different thing entirely. Fire and sinking incidents on yachts in the 25–40m range make the point well: risk doesn't respect the ISM threshold, and a vessel running reactive, break-then-fix maintenance carries avoidable risk regardless of certification status — a view SuperyachtNews has also put on record ("You don't require ISM, fine, but that doesn't mean you don't need it").

A DPA is one of the most practical pieces of that risk management to put in place voluntarily: an independent line to shore management for handling emergencies without commercial pressure, a structural push toward planned maintenance instead of run-to-failure repair, and an advocate ashore who ensures the crew actually gets the equipment and budget approvals they need. For an owner planning to move toward commercial charter or full ISM certification, it also builds the habit and paper trail early, so the transition is a formalisation of what's already working, not a standing start.

It's worth a brief mention that domestic commercial vessels in Australia and New Zealand running overnight expedition or high-end cruise itineraries face their own, quite different, shore-support requirements under AMSA and Maritime NZ rules — a topic detailed enough that we'll cover it properly in a future article. Get in touch if you'd like to know how these requirements apply to your operation in the meantime.

The case for a timezone-matched DPA

An external contracted DPA performs the same function as an in-house one: formal designation in the SMS, round-the-clock reachability, direct access to management, and ongoing oversight of compliance — without the vessel owner or management company carrying a dedicated shore-side role on payroll.

We operate exclusively across the South Pacific, New Zealand, and Australian time zones — the window most primary DPAs, based in Europe or the US, structurally cannot cover. New Zealand sits roughly 11 to 13 hours ahead of the UK and 10 to 12 hours ahead of Continental Europe depending on daylight saving; Australia's eastern states run 8 to 11 hours ahead — putting our business day squarely across the European overnight, precisely when a primary DPA is least reachable.

This isn't about replacing your existing management company. We work alongside your current structure — as backup DPA cover during your primary's off-hours, or as regionally based DPA for vessels operating semi-permanently in the South Pacific — integrating into your existing SMS and reporting lines rather than duplicating them. For a vessel whose management sits outside this time zone, that's real, usable cover added to what's already in place.

"The captain called at 0200 UTC — a crew welfare issue that needed shore-side escalation. In the south of France it was 0300 in the morning and the primary DPA was unreachable. In New Zealand it was early afternoon."

In a case like that, the backup DPA — acting with the company's authority — takes immediate ownership of the situation shore-side: mobilising support, coordinating the response, and formally briefing senior management as soon as they're reachable. That's the practical value of timezone-matched cover: not a replacement for the primary DPA, but genuine capability during the hours the primary structurally can't provide it.

What a contracted DPA arrangement looks like

A properly structured contracted DPA arrangement is a formal agreement between the DPA and the vessel's company, specifying:

• The vessels covered and the SMS applicable to each
• Contact arrangements and expected response times
• Escalation paths to the company's senior management
• Scope of involvement in audits, drills, and SMS reviews
• Handover procedures with the primary DPA, where applicable

The DPA is named in the SMS, with contact details on board — active participation in the company's safety management, not a name on a document. PSC scrutiny is increasingly geared toward checking that the involvement is real.

The DPA and the CSO — not the same role

A common point of confusion: the DPA (ISM Code) and the Company Security Officer, or CSO (ISPS Code), are different roles — safety versus security. In smaller operations the same person often holds both, which is acceptable provided it's explicitly documented in both the SMS and the Ship Security Plan.

Summary

If your vessel needs a DPA under the ISM Code, the requirement is real, and so are the consequences of a non-functioning arrangement: PSC deficiency citations, potential detention, and a captain without proper shore-side support when something goes wrong. If your vessel doesn't legally require a DPA at all, the case for genuine shore-based support is a risk-management case, not a compliance one — waiting for an incident to prove the point is the expensive way to learn it.

Contact us if you'd like to know more about how we can help your company operate safely, securely, and within requirements — as your primary DPA, or as timezone-matched backup cover alongside your existing management structure.