Designated Person Ashore (DPA)
The Designated Person Ashore (DPA) is the shore-based manager required by the ISM Code who acts as the link between the vessel and company management. The DPA has direct access to the highest level of management and is responsible for the safety management system and emergency response.
Definition
Semantic definition
- Subject
- Designated Person Ashore (DPA)
- Predicate
- is the ISM-required shore-based manager who
- Object
- links the vessel to company management and oversees the Safety Management System.
Designated Person Ashore (DPA) is the ISM-required shore-based manager who links the vessel to company management and oversees the Safety Management System.
What is a Designated Person Ashore?
The Designated Person Ashore (DPA) is the shore-based safety manager required by the ISM Code for every commercially operated vessel. The DPA acts as the essential link between the vessel and the highest level of company management. They must have direct access to the CEO or equivalent authority at all times. The DPA is responsible for monitoring the safety and pollution prevention aspects of the operation and ensuring that adequate resources and shore-based support are applied. The role is not administrative — it is a functional safety management responsibility with personal liability implications.
DPA Responsibilities
Under ISM Code section 4, the DPA's specific responsibilities include: monitoring the safety and pollution prevention aspects of the operation of each ship; ensuring that adequate resources and shore-based support are applied; direct access to the highest level of management; responsibility for ensuring that the SMS is functioning and being updated; coordinating shore support for vessels in emergency situations; conducting and verifying internal ISM audits; reviewing nonconformity, accident, and hazardous occurrence reports; and liaising with flag state, class society, and Port State Control authorities.
DPA Qualifications and Competency
The ISM Code does not prescribe specific DPA qualifications. However, flag states and recognised organisations expect DPAs to have: substantial seagoing experience (OOW or higher); familiarity with the SMS and ISM Code requirements; understanding of SOLAS, MARPOL, and MLC; experience with internal and external audits; and sufficient seniority to influence the highest level of management. In practice, most DPAs hold or have held senior officer certificates. Some flag states publish guidance on DPA competency. The DPA is identified by name in the Document of Compliance and the vessel's SMS.
DPA and Emergency Response
In any vessel emergency — grounding, fire, flooding, man overboard, medical emergency — the DPA is the shore-side emergency coordinator. The master contacts the DPA, who activates the company emergency response plan, coordinates shore-based support (salvage, medical, legal, PR), liaises with authorities (flag state, coast guard, classification society), and ensures the vessel has the resources needed. PSCOs verify that the DPA is named in the SMS and that the crew know how to contact them at any hour.
Common DPA Deficiencies Found by PSC
Port State Control most commonly cites DPA deficiencies when: no DPA is named in the SMS documentation on board; the DPA's contact details are not posted where crew can access them 24/7; the crew cannot identify the DPA by name; the DPA is unreachable during the inspection; or the DPA position is held by someone without the authority to access senior management. Each of these is an ISM nonconformity that can result in a PSC deficiency notice.
DPA Qualifications: What Flag States and Class Societies Require
There is no single universal IMO certificate that automatically qualifies a person to act as a Designated Person Ashore. The ISM Code defines the function and authority of the DPA, but it does not prescribe one global training syllabus, sea-time threshold, or licence title. In practice, the qualification standard is set through a combination of flag state guidance, recognised organisation audit practice, company SMS procedures, and the complexity of the vessels being managed. A DPA for a small commercial yacht fleet is assessed against the same functional requirement as a DPA for larger ships: they must understand the safety management system, have direct access to the highest level of management, and be able to secure resources and shore support when the vessel needs them. Common expectations are consistent across serious flag administrations and class society audits. The DPA should normally have a maritime supervisory background, often as a former master, senior deck officer, chief engineer, technical superintendent, yacht manager, fleet manager, or shore-side safety manager. They should be able to read a vessel's SMS, understand how the procedures connect to SOLAS, MARPOL, MLC, STCW, flag state requirements, and class survey obligations, and recognise when a nonconformity is operationally serious rather than just a paperwork defect. A purely administrative employee can support document control, but they should not be the named DPA unless they have the maritime competence and organisational authority to challenge unsafe operations. Many DPAs complete flag state or recognised training provider courses. Lloyd's Register, Bureau Veritas, MCA-aligned training providers, and other maritime organisations offer DPA, ISM, internal auditor, and emergency response programmes. These courses do not replace the company's duty to appoint a competent person, but they provide structured evidence that the DPA understands ISM responsibilities, audit practice, corrective action, emergency escalation, and company verification. During an audit, the question is not only whether the DPA attended a course. The auditor will test whether the DPA can explain the company SMS, identify the vessels under their responsibility, describe recent incidents and corrective actions, and show how they monitor each vessel. Availability is part of competence. A DPA who is qualified on paper but cannot be reached during an emergency is not fulfilling the role. Commercial yacht operations require 24/7 contact arrangements, deputy coverage during leave, and a tested escalation chain. The SMS should state the named DPA, deputy DPA or emergency contact, phone numbers, email addresses, and escalation steps if the first contact fails. The crew should know where those details are posted and how to activate them without searching through old binders. Emergency response training is therefore not optional in practice: the DPA must know how to coordinate medical evacuation, pollution response, casualty reporting, salvage support, class notification, flag state notification, owner communication, and legal or insurance contact without delaying the master's immediate safety decisions.
DPA in Practical Yacht Operations: Common Failures
The DPA role often fails in yacht operations because the appointment exists in the SMS but does not function under operational pressure. Port State Control, flag state auditors, and class auditors do not assess the DPA only by reading the name printed in the manual. They look for evidence that the master, crew, shore manager, and senior company management all understand the same escalation route and have used it in real situations. A yacht can have a neatly formatted SMS and still receive an ISM nonconformity if the crew cannot explain who the DPA is, how to contact them, or what the DPA does during an emergency. A common failure is the emergency drill that exposes an unreachable DPA. The crew runs a fire, flooding, grounding, or pollution drill and the scenario requires shore support, but the listed DPA phone number is not answered, goes to a former employee, or reaches an office switchboard that is closed outside business hours. The drill record may still be signed off as complete, but an auditor will treat the communication failure as a real defect. The purpose of the drill is to test the system, and a system that cannot reach the DPA at night, on weekends, or across time zones is not a functional ISM emergency response arrangement. Another frequent problem is a DPA change that is handled informally. The management company appoints a new safety manager, but the vessel SMS, emergency contact card, bridge posting, crew induction pack, Document of Compliance records, or internal contact list still show the previous DPA. On board, this creates exactly the ambiguity the ISM Code is designed to prevent. If the master has one DPA in the yacht manager's email signature, the engineer has another number in the SMS, and the crew mess noticeboard shows a third contact, the vessel does not have a clear shore-side safety link. The corrective action is not just updating one document. The company must update controlled documents, remove obsolete versions, brief the crew, and retain evidence that the new contact chain was communicated. A more subtle failure is a DPA who is named for compliance but has no direct knowledge of the yacht's procedures. This is common where a management company uses a central DPA across a diverse fleet but does not give that person enough vessel-specific context. During an inspection, the DPA may be able to describe ISM theory but cannot answer basic questions about the yacht's high-risk operations, recent nonconformities, overdue maintenance, pollution prevention arrangements, or emergency equipment status. That gap matters because the DPA is supposed to monitor safety and pollution prevention aspects of the operation. Monitoring cannot be performed from a generic manual alone. The DPA must have access to current drill records, maintenance status, defect reports, audit findings, crew familiarisation records, and incident logs for each vessel.
How the DPA Communicates with the Master and Crew
A strong DPA arrangement has a predictable communication rhythm. In day-to-day yacht operations, this usually means a weekly or fortnightly safety and operations check-in between the master and the DPA, with additional contact whenever the vessel changes operating mode, enters a higher-risk passage, prepares for charter, completes a drill, reports a defect, or closes a corrective action. The rhythm does not need to be bureaucratic, but it must be visible. A short weekly safety report that captures drills completed, defects raised, near-misses, crew changes, overdue PMS items, and upcoming inspections is much stronger evidence than a general statement that the DPA is available if needed. Incident reporting should follow a clear flow: crew member to head of department or officer, officer to master, master to DPA, and DPA to the company, flag state, class society, insurer, or other authority where required. The SMS should define which events require immediate DPA notification, which can be included in routine reporting, and which require formal investigation. Examples of immediate DPA events include injury, fire, flooding, grounding, collision, pollution, loss of propulsion, significant machinery failure, security threat, serious guest or crew complaint, and any Port State Control intervention. Near-misses and hazardous occurrences should also reach the DPA, even when no damage occurred, because they are the raw material for SMS improvement. The master-DPA relationship must preserve the master's authority while still giving the company an active safety role. The DPA is not a remote captain and should not second-guess urgent bridge or engine-room decisions during a casualty. The master makes immediate decisions for the safety of the vessel, people on board, and environment. The DPA supports those decisions by arranging resources, notifying the right parties, obtaining technical advice, coordinating the emergency response team, and making sure senior management understands the risk and cost of delayed support. This distinction is important during charter pressure, owner pressure, or schedule disruption. A DPA who simply passes messages from the owner to the master is not performing the ISM safety function. Routine communication should include both operational status and system health. Operational status covers itinerary, crew changes, charter schedule, weather exposure, open defects, and upcoming port or survey events. System health covers whether drills are being completed, whether near-misses are being reported, whether overdue PMS tasks are controlled, whether certificates are approaching expiry, and whether corrective actions are closing on time. When those two views are combined, the DPA can see risk developing before it becomes an incident. For example, a tight charter turnaround, tired crew, overdue fire pump maintenance, and a planned night departure are individually manageable items. Together they may justify additional controls or a change in plan. The DPA also needs a direct route to crew concerns. Crew should normally report through the master and department heads, but the SMS should not make the master the only possible path for safety issues. If a crew member believes a safety concern is being ignored, there should be a confidential or escalation route to the DPA. This protects the company and the master as well as the crew. It allows fatigue, bullying, unsafe contractor work, falsified records, defective equipment, or repeated procedural shortcuts to reach shore management before they become a casualty or MLC complaint. The DPA should treat such reports carefully, preserving confidentiality where appropriate while still investigating facts and respecting the master's command role. Drill reporting is one of the simplest ways to prove that the DPA is actively involved. A completed drill record should identify the scenario, participants, equipment tested, deficiencies found, and corrective actions. The master or safety officer sends the record to the DPA, the DPA reviews it, asks questions where the drill was weak, and tracks any corrective action to close-out. If a fire drill finds that one crew member did not know the location of breathing apparatus, the DPA should not merely archive the form. They should verify that familiarisation was repeated, the training record was updated, and the next drill tested the same weakness. This creates a traceable loop from observation to action to verification. Corrective action tracking is where many DPA systems become weak. A defect, near-miss, or audit finding is not closed because someone wrote "done" in a spreadsheet. Closure should record what was changed, who verified it, when it was communicated to crew, and whether any SMS procedure, risk assessment, PMS task, or training record also needed updating. The DPA should challenge vague closure notes such as "crew reminded" or "monitor going forward" when the underlying issue requires a physical repair, procedural change, or evidence of competence. The goal is not paperwork volume. The goal is to prevent the same finding from reappearing at the next audit or, worse, during a casualty investigation. Flag states and recognised organisations increasingly expect evidence of DPA intervention rather than just DPA appointment. Evidence can include email trails, audit reports, signed drill reviews, nonconformity registers, corrective action close-out notes, emergency call test logs, management review minutes, and vessel visit reports. The important point is that DPA communication should be documented enough to prove that the shore-side safety link works, but not so heavy that crew stop reporting problems. The best yacht DPAs make reporting easy, respond quickly, close the feedback loop, and give the master practical support without undermining the master's authority on board. For multi-vessel yacht managers, communication also needs fleet-level learning. If one yacht reports a failed emergency fire pump test, obsolete DPA contact card, weak tender recovery procedure, or repeated rest-hour pressure during charter turnaround, the DPA should ask whether sister vessels have the same exposure. This is one of the advantages of a functioning DPA role: lessons learned on one yacht can become preventive action across the fleet. Fleet bulletins, targeted safety alerts, and short management review notes are useful evidence that the company learns from events rather than treating every incident as isolated.
Frequently Asked Questions
Manage Designated Person Ashore (DPA) with HelmOps
Purpose-built for yacht operations — offline-first, compliance-ready.
Track certificates, crew documents, and deadlines in one place
30-day free trial. No credit card required.
Start Free TrialVerified reference
https://www.imo.org/en/OurWork/HumanElement/Pages/ISMCode.aspx(opens in new tab)
Related terms
Last updated: