When your vessel loses access to an important service, you need to know what is affected, what can still be used and when to expect the next update.
Your crew may be contacting support, your shore team investigating and your supplier working on a solution. Without clear communication, it becomes difficult to make informed decisions onboard and ashore.
On 2 September, cyber authorities from five countries published joint guidance on communication during IT and OT outages. It calls for clear communication plans, transparent updates and practical information that helps customers respond. These are recommendations, not new maritime regulations. Read the joint guidance summary.
For shipping, the relevance is clear. Restoring a system takes technical expertise. Keeping the operation informed requires communication to be part of the response from the beginning.
“We are investigating” may be accurate, but it gives a master or technical manager little to work with. They need to understand which services are affected, whether a workaround exists and what action they should take.
Not every answer will be available immediately. What matters is clearly separating confirmed information from what remains uncertain, and setting an expectation for the next update.
An estimated recovery time should never become a promise simply because someone needs an answer.
For Sea IT, this is an important part of maritime support. The technical investigation and the customer dialogue must work together, so vessel and shore teams can make informed decisions while recovery continues.
An incident can also affect the tools normally used to coordinate the response. Email, the support portal or a shared platform may depend on the same unavailable infrastructure.
Shipowners and service providers therefore need agreed alternative channels, accessible contact details and clear responsibility for keeping people informed. These arrangements should be tested alongside technical recovery procedures.
The same clarity matters after service is restored. Customers need to understand what happened, what was corrected and what will be done to reduce the risk of it happening again.
Prepare
Agree on communication responsibilities, contact routes and fallback channels before an outage.
Inform
Explain what is affected, what users should do and when the next update will follow.
Review
Share the confirmed cause, corrective actions and lessons after recovery.
A customer may accept that a system takes time to restore. They should not have to guess what is happening while they wait.
