The Designated Person Ashore (DPA) is defined by the ISM Code as a shore-based role. Yet their presence is felt on board every day: they are the master’s direct link to the Company’s highest level of management, and the single escalation point for any safety incident or security threat. For that to mean anything, the DPA must be operationally live on board — which requires a rigorous setup, a tested communication channel, and a clear role in alert situations.
Setting up a DPA for a ship
Appointing a DPA goes well beyond writing a name on the Company’s Document of Compliance (DOC). Operational setup happens in three steps.
1. Registration with the flag. The flag administration (Marshall Islands, Cayman, RIF, Malta, etc.) receives the DPA’s name, 24/7 contact details and qualifications. It checks the actual authority granted to the DPA and direct access to the highest level of management. Without this registration, the SMS is non-compliant.
2. SMS integration. The ship’s SMS manual is updated to describe the escalation circuit to the DPA, contractual response times and cases requiring immediate contact (accident, serious near-miss, pollution, port refusal, security suspicion). The master signs an acknowledgment.
3. Onboard familiarisation. The DPA — or a firm representative — physically visits the ship when the mandate starts. This visit covers meeting the master and chief, reviewing critical procedures, checking the SMS notice board and live-testing the 24/7 contact circuit. That last step is what turns the DPA from an administrative mention into a genuinely live arrangement.
Utility and impact on board
From the crew’s standpoint, the DPA matters in three ways:
- Judgment backup. On a sensitive issue — an unlisted technical defect, doubt about a seafarer’s medical fitness, an owner instruction conflicting with safety — the master knows there is a shore-based referent, independent from commercial operations, who can arbitrate or cover a difficult decision.
- Psychological relief. The master is no longer alone. The DPA shares responsibility for ISM compliance and absorbs part of the stress of incidents and audits.
- Documentary discipline. Knowing that an active DPA tracks non-conformities and near-misses pushes the crew to document better. The SMS journal, near-miss log and drill reports get filled in for real — not out of fear of inspection, but because they serve someone.
Conversely, an inactive DPA — a name on the DOC, never reached, never seen — discredits the entire SMS. External ISM audits spot the gap immediately.
How the crew reaches the DPA from on board
The DPA contact must be reachable from the ship, at any hour, through several independent channels. Our mandate standard is:
- Visible SMS posting on the bridge, ECR and crew mess: DPA name, direct 24/7 phone number, backup number, email, Iridium link where relevant.
- Satellite phone (Iridium or VSAT) — directly dialable number, line tested monthly by the master as part of the ISM drill schedule.
- Dedicated operational email, separate from the Company’s commercial or accounting mailbox, monitored around the clock.
- Secure messaging (Signal or equivalent) for informal exchanges or sensitive attachments, with read receipts.
- Flag bypass voice number, to be used if the DPA is unreachable — every flag publishes this administrator emergency number.
Monthly testing of the circuit is mandatory under our methodology. It generates an SMS log entry and feeds into the annual Management Review.
The DPA in an SSAS alert
The Ship Security Alert System (SSAS), mandated by SOLAS chapter XI-2 and the ISPS Code, is a silent alarm triggered by the master or an authorised officer in case of serious security threat — piracy, hostage-taking, armed intrusion. An SSAS activation discreetly notifies the flag administration and the designated points of contact (Company Security Officer — CSO; and, depending on the flag, the DPA).
The DPA’s role in the SSAS chain:
- Cross-reception of the alert. The CSO is the primary operational recipient; in almost every configuration, the DPA also receives the alert. They confirm reception to the flag and activate the shore-side Ship Security Plan.
- Coordination with authorities. The DPA interfaces with the flag, the relevant MRCC and, where applicable, MSCHOA (Horn of Africa) or CRIMARIO (Indian Ocean). They transmit ship information — position, crew, cargo, route — in structured form.
- Operational stop authority. The DPA holds authority to impose a diversion, refuge anchorage or mission suspension. This authority is used in concert with the master and CSO, but it is real.
- Continuity of support. Throughout the incident, the DPA maintains a structured timeline of events, archived audit-ready: this is the document used for the flag report, P&I underwriters and, if proceedings follow, judicial authorities.
In many private configurations — yachts transiting the Red Sea, the Gulf of Guinea or the South China Sea — the DPA and the CSO are the same person or the same firm. Flags accept this dual hat provided there is no conflict of interest; it simplifies the chain and speeds up decision-making.
In summary
Setting up a DPA for a ship is not ticking an administrative box: it means placing ashore a permanent counterpart, able to arbitrate, cover and coordinate in the worst situations. On board, their existence is measured by SMS quality and the strength of the contact circuit. In an SSAS alert, they become the ship’s shore-side pivot — and that is where the robustness of the arrangement is truly tested.