Iran's Hormuz Coordination Protocol: Six Workflow Changes That Determine Whether Your Coverage Holds
Iran's March 23, 2026 IMO note dropped into an active casualty environment. According to Marine Link reporting, the note conditions transit rights for "non-hostile" vessels on active coordination with Iranian maritime authorities—a requirement issued against a backdrop of significant disruption to global oil and LNG shipments through the strait. Among the incidents reported in that environment: the Thai cargo vessel Mayuree Naree was struck and set ablaze on March 11, 2026, according to India Today. Operators reviewing these facts should verify current incident counts and endorsement terms against Lloyd's List and BIMCO advisories at time of voyage order issuance—the situation is fluid and individual casualty details should be confirmed from primary shipping intelligence sources before being cited in claims correspondence.
What the note is not is a geopolitical circuit-breaker. Operationally, it is a compliance trigger. Most P&I clubs and ops teams are not yet structured to handle what it requires. Operators who treat it as a headline rather than an auditable coordination obligation will find themselves reconstructing records retroactively under claims pressure—a posture no P&I defense counsel wants to defend before a London arbitration panel.
What the March 23 IMO Note Actually Requires
The note conditions non-hostile vessel transit on active coordination with Iranian maritime authorities before and during passage—not passive notification, and not a routine AIS broadcast. The word "coordination" is doing significant legal work. It means initiating contact, documenting that contact, obtaining acknowledgement, and confirming routing before the vessel enters the corridor. Silence or non-response from Iranian authorities cannot be treated as implicit clearance.
There is a second complication many operators are not yet factoring in: the coordination act itself may constitute a reportable interaction under OFAC sanctions regulations or EU Regulation 833/2014, depending on the nature of the communication and the identity of the Iranian authority involved. Standard P&I club rules also exclude losses arising from compliance with orders of any government or authority not recognised by the flag state. For vessels on Western flag registries, Iranian coordination instructions occupy an unresolved legal zone that has not been tested at claims arbitration under these specific circumstances.
The Coverage Void Risk: P&I and War-Risk Mechanics
War-risk underwriters have been repricing Hormuz endorsements in real time since early March 2026. The specific clause operators need to watch for is any language that shifts coverage voidance risk onto the operator when coordination failure is a contributing factor in a casualty.
The mechanics: if a vessel is struck during a Hormuz transit and the operator cannot produce a timestamped, sequenced coordination log demonstrating pre-transit contact with MRCC Iran, the underwriter's claims team will argue that the operator failed to satisfy its due-diligence warranty. The coverage dispute then runs in parallel with the casualty response—precisely when the operator needs unimpeded access to war-risk and P&I indemnity.
Salvage liability deepens the exposure. If a coordinated vessel requires SCOPIC engagement, the coordination record—or its absence—becomes central evidence in determining whether the operator acted with reasonable care. The sequencing of records matters as much as their completeness; a log clearly assembled after the incident rather than generated contemporaneously will be challenged.
Six Workflow Changes: Minimum Operational Standards
The following six steps represent best-practice minimums before any Hormuz voyage order is issued under the new protocol. They are not universally binding across all clubs or endorsements—operators must verify specific requirements with their own underwriters—but failure to implement them creates unhedged exposure at every stage of the claims chain.
1. Establish a dedicated MRCC Iran contact protocol with redundant channels. VHF Channel 16 alone is insufficient. Identify the MRCC Iran email address, establish a primary and backup VHF frequency, and test both before the voyage order is issued. Coordination attempts made via a single channel with no auditable backup will face scrutiny.
2. Log every coordination attempt with UTC timestamps and officer signature. A generic voyage log entry reading "contacted Iranian authorities" will not meet arbitration evidentiary standards. Entries must record: channel used, time and date in UTC, content of communication, identity of the officer making the entry, and the response received—or documented absence of one.
3. Request written confirmation from the P&I club and war-risk underwriter that the coordination act does not constitute a sanctions-reportable interaction. This step must precede the voyage order. However, operators should note that underwriters themselves may not have definitive OFAC or EU Regulation 833/2014 guidance on coordination acts with Iranian MRCC, and may be unable to provide written clearance. If confirmation is not obtainable, document the written request and the underwriter's response (or non-response), and obtain an operator-specific sanctions counsel opinion as the fallback. Both the request and the counsel review must be retained in the voyage claims-defence file. There is no universal clearance; the answer varies by flag state, ownership structure, cargo type, and the specific Iranian counterparty involved.
4. Update the Vessel Safety Management System with a Hormuz-specific pre-transit checklist. The SMS checklist must include evidence fields for each coordination act—not a generic high-risk area entry that predates the March 23 note. SMS administrators should audit existing OOW log templates to confirm they capture channel, UTC timestamp, content summary, response received, and officer signature. For operators reviewing route deviation scenarios and MRCC contact geography, the Rynda ports map provides route comparison and deviation-impact context useful during pre-voyage SMS review.
5. Align charterer indemnity language in current voyage orders to reflect the coordination requirement. Charterparty indemnity clauses written before March 23 will not allocate liability for coordination-act delays, rerouting costs triggered by MRCC non-response, or coverage disputes arising from coordination failures. This is not a routine clause update; it requires specific drafting addressing the new protocol's operational consequences.
6. Brief masters and chief officers on the evidentiary standard required to preserve coverage—and on the MRCC non-response escalation decision tree. Bridge team briefings must communicate not just what to record but that the record is a claims-defence instrument. Masters should understand: what constitutes an adequate MRCC response for coverage purposes (routing confirmation with timestamp, not merely voice acknowledgement); at what point repeated non-response—typically after two documented attempts across separate channels within the established contact window—triggers escalation to the operator's DPA; and whether voyage departure should be delayed pending underwriter notification of MRCC non-response before proceeding. HSEQ managers reviewing crewing competencies for high-risk documentation environments may find digital crewing workflows such as Rynda Crewing useful for targeted crew assignment against Hormuz-specific voyage requirements.
Each of these steps has a hard dependency on the previous one. Sequencing, not just completion, is the compliance risk.
Master and Crew: Evidentiary Standards and Non-Response Escalation
The bridge team is the last line of documentation defence. Post-incident reconstruction of coordination logs—even where the underlying coordination genuinely occurred—is highly vulnerable to challenge. An arbitration panel will scrutinise whether entries were made at the time claimed, whether metadata is consistent with contemporaneous entry, and whether content is specific enough to have been recorded in real time.
Masters must understand that when MRCC Iran does not respond, the absence of response must itself be logged as fully as a positive acknowledgement: channel attempted, UTC time, duration of attempt, officer identity, and the decision taken as a result. If non-response persists across both primary and backup channels, the escalation chain is: notify the DPA; document DPA guidance received; notify the war-risk underwriter before departure if time permits; and retain all communications. A voyage that proceeds after documented good-faith MRCC contact attempts with no response is in a materially stronger coverage position than one where no contact was attempted at all—but only if the log supports that narrative contemporaneously.
OOW log templates not designed to capture coordination-act specifics will produce generic entries that create exactly the documentation vacuum coverage disputes are built on. SMS administrators must revise templates before the next Hormuz voyage order to include dedicated fields for each element described above.
Sanctions Interaction and Counsel Review Triggers
The sanctions layer is the most operator-specific compliance variable in the entire protocol. No operator should issue a Hormuz voyage order under the new coordination protocol without first requesting a written opinion from sanctions counsel on whether the contemplated coordination acts are exempt from OFAC reporting requirements and fall within any applicable EU Regulation 833/2014 derogation.
The answer will differ by flag state, vessel ownership structure, cargo type, counterparty identity within the Iranian coordination chain, and the specific nature of the communication. There is no industry-wide guidance covering all these variables. If sanctions counsel cannot provide a clean opinion—or if the analysis remains unresolved at the time of voyage order issuance—that unresolved status must be documented and retained. Operators who rely on informal market consensus rather than a documented operator-specific legal review will have no privileged legal opinion to protect if the interaction is later scrutinised.
All counsel consultations and underwriter confirmations or correspondence must be retained as part of the claims-defence file—not filed only in the voyage folder. If a casualty occurs and the operator's defence turns on whether reasonable care was exercised before transit, the documented sequence of legal review, underwriter engagement, and operational workflow implementation is the evidence that supports that argument.
The window to structure these workflows is narrowing. With war-risk endorsements actively repricing and underwriters inserting coordination-failure clauses into renewals, every Hormuz voyage order issued without the six-step framework represents an unhedged coverage gap at maximum loss exposure.
Sources & References
- Marine Link, 24 March 2026 — Iran Tells UN and IMO: 'Non-Hostile' Ships Can Transit Strait of Hormuz with Coordination
- India Today, 25 March 2026 — Thai Cargo Ship Mayuree Naree Struck and Set Ablaze in Strait of Hormuz
Operators are advised to verify current incident counts and endorsement terms against Lloyd's List, BIMCO incident advisories, and IMB reports at time of voyage order issuance.