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 Alternate / Deputy 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 during the European night. A well-run primary DPA will answer, and the Code expects them to. But a call answered at night is not the same as a working day: decisions and documents can wait for morning. That same 0200 UTC call lands in the early-to-mid afternoon in New Zealand and Australia, where a DPA in this region has the working day ahead of them.

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.

We hold that training and certification directly through Lloyd's Maritime Institute as an ISM/ISPS/MLC Internal Auditor and Designated Person Ashore, backed by two decades of worldwide command on commercially operated superyachts as an MCA Master 3000T. A competent DPA needs to 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, and the flag state's requirements and those of the relevant Recognised Organisation. It's the command background as much as the compliance qualifications that makes the difference: knowing what a captain is actually dealing with at 0200, not just what the paperwork says should happen.

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 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 vessel's own working day, which for primary DPAs based in Europe or the US falls at night. 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 night.

This isn't about replacing your existing management company. We work alongside your current structure, as Alternate / Deputy DPA cover adding qualified capacity in a different part of the working day, 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.

Consider a captain calling at 0200 UTC about a crew welfare issue that needs shore-side escalation. In the south of France it is 0300. In New Zealand it is early afternoon.

In a case like that, the Alternate / Deputy DPA, acting with the company's authority, takes immediate ownership of the situation shore-side: mobilising support, coordinating the response, and communicating with the company as the agreement sets out. That's the practical value: qualified shore-side capacity in a different part of the working day.

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, not a loose understanding. It sets out the vessels covered and the SMS applicable to each, the contact arrangements and expected response times, and the escalation paths to the company's senior management. It also defines the scope of involvement in audits, drills, and SMS reviews, and, where a primary DPA is already in place, how the two roles work together and communicate.

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, provided it's explicitly documented in both the SMS and the Ship Security Plan and the flag Administration accepts it. Who may hold the CSO appointment is more restricted: in most flag state cases the CSO must be an employee of the Company. If your vessel is also subject to the ISPS Code, it's worth reading our companion article on what a Company Security Officer does, and why location matters.

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, whether as your primary DPA, or as an Alternate / Deputy DPA adding qualified shore-side capacity in a different part of the working day.

Frequently asked questions

Does every superyacht need a Designated Person Ashore?

In practice, once a superyacht is operating commercially, trading internationally, and crosses 500GT, the same line that triggers full ISPS compliance. It's a threshold the industry takes seriously enough that an entire generation of yachts is deliberately designed to sit just under it, at 499GT. Vessels outside that threshold aren't legally required to carry a DPA, though the underlying safety risk doesn't disappear along with the paperwork requirement.

Can the DPA and CSO be the same person?

Often, yes. Nothing in the ISM or ISPS Codes prevents one person holding both roles, and in smaller operations it is common, provided the dual role is documented in both the Safety Management System and the Ship Security Plan, subject to the requirements and acceptance or notification arrangements of the applicable Flag Administration. Where the flag requires the CSO to be a Company employee, an external DPA can still provide regional security support alongside the Company's appointed CSO.

Does a DPA really need to be reachable at all times?

Yes. This is a specific requirement under Section 4 of the ISM Code, which requires the DPA to have direct access to the highest level of management and be reachable at any time to provide a link between the company and those on board.

Why would a vessel use a DPA based in New Zealand or Australia instead of near its management company?

Because a vessel operating in this region does much of its business while it is night-time in Europe and the US. A regionally based DPA adds qualified shore-side capacity in a different part of the working day, strengthening the resilience and reach of the existing management structure, combined with regional knowledge and on-the-ground capability.

Does hiring a regional DPA mean replacing our existing management company?

No. Most vessels using our DPA services keep their existing management company in place, and we integrate as Alternate / Deputy DPA cover within that structure. For vessels without an existing shore-side arrangement, we can also act as primary DPA. Either way, the appointment is subject to the requirements and acceptance or notification arrangements of the applicable Flag Administration.