Start with verified geography

Plot official incident coordinates and descriptions with event time, report time and confidence. Do not map a social-media location as confirmed merely because it looks precise.

IMO says its regional data use flag States, coastal States and credible verified third parties. UKMTO warnings may report information from a master, company security officer or military authority and can later be updated.

Keep layers for:

- IMO-confirmed incident; - UKMTO warning or advisory; - authority navigation or security warning; - company observation; - unverified open-source report; and - analytical zone or forecast.

A zone is an interpretation built from evidence. It is not itself a verified incident.

Use nautical context: traffic routes, port approaches, anchorages, terminals, offshore installations, ship-to-ship areas, depth, rescue access and state boundaries. A point without that context can distort the decision.

Update the map when an incident is reclassified, relocated or confirmed late.

Divide exposure by operation, not country

Country labels are too broad for shipboard decisions. One national coastline can include protected port waters, open approaches, high-density anchorages and distant offshore routes.

Create operating zones such as:

1. northern Gulf transit and Iraqi or Kuwaiti approaches; 2. Saudi northern and central offshore waters; 3. Qatar approaches, anchorages and offshore infrastructure; 4. UAE Gulf-side ports and approaches; 5. Strait of Hormuz traffic lanes and waiting areas; 6. Oman and UAE Gulf of Oman approaches; and 7. offshore rendezvous, bunkering and ship-to-ship areas.

The exact boundaries should follow current intelligence and the company's voyages, not this illustrative list.

For each zone, record threat types, recent incidents, time of last verification, navigation constraints, rescue time, port options, communications and no-go triggers.

A ship can move through several zones in one day. Voyage approval should follow the sequence, not assign one rating to the whole country call.

Time at anchor can exceed transit exposure

A fast Hormuz passage may last hours. Waiting for orders, berth, pilot, convoy or insurance approval can last days. A stationary ship is more predictable and may have reduced manoeuvring options.

JMIC specifically included anchorages and ship-to-ship areas in its warning about wider Gulf exposure. Companies should therefore calculate:

- planned and worst-case waiting time; - machinery readiness; - distance from recent incidents; - density of ships and infrastructure; - small-craft and access-control risk; - ability to move on short notice; - rescue, firefighting and medical support; and - mine or navigation-interference information.

The closest port is not automatically the safest waiting area. Proximity can improve response and protective coverage while increasing congestion and infrastructure exposure.

Charterers should disclose realistic berth and order delays during voyage review. Owners should price and approve the waiting window, not only the sea passage.

Port call risk has three phases

Treat arrival, alongside stay and departure separately.

Arrival includes approach channels, pilot boarding, tug rendezvous, traffic and reduced manoeuvrability.

Alongside includes predictable position, cargo hazard, shore personnel, loading connections and dependence on terminal protection.

Departure includes machinery readiness, pilot and tug availability, channel clearance and possible accumulation of ships after a pause.

A recent offshore event does not automatically make a named port unsafe under a contract. It does require a current, evidence-based assessment of the prospective port and approach.

Ports should share factual security and movement information with ships without disclosing protected defenses. Terminals need emergency departure, firefighting, casualty reception and personnel-accountability plans.

Owners should request the decision-relevant facts, not demand a guarantee that no attack can occur.

Fleet support must move with the risk map

A geographically wider threat stretches technical, medical and salvage resources. One response team near Fujairah may not support a casualty in the northern Gulf quickly.

Map:

- tugs and salvage capability; - firefighting and pollution response; - hospitals and medical evacuation; - class and survey attendance; - repair yards and spare parts; - crew-change options; - agents and launch services; - bunkers and provisions; and - secure communications.

Verify actual access during the conflict. A contractor on a list may lack insurance, security clearance or crew willingness to deploy.

Owners with several ships should avoid assuming the same tug or adviser can cover simultaneous incidents. Establish priority rules and alternates.

Insurers can help identify approved responders, but the master and authorities determine immediate life-safety action.

Supply chains need more than an alternate Strait plan

Cargo already inside the Gulf remains exposed even if a future shipment is rerouted. Importers and exporters should locate inventory by operational zone and stage.

Track:

- cargo afloat inside the Gulf; - cargo waiting at regional terminals; - empty equipment and containers; - critical imports by days of cover; - export storage constraints; - transshipment dependencies; and - payment or title triggers tied to shipment milestones.

An incident near a port can delay pilotage or traffic without damaging the terminal. A distant attack can still affect insurer approval or crew willingness across the region.

Alternative ports outside the Strait may require land transport, storage, customs and different vessel sizes. Capacity should be confirmed rather than assumed.

Traders should distinguish physical unavailability, delayed movement and increased risk premium. They have different commercial responses.

Insurance geography must match operations

War-risk areas and policy terms may use boundaries different from the company's internal zones. Read the actual coordinates and wording.

Confirm whether additional premium and prior agreement apply to:

- approach and departure; - anchorage and waiting; - ship-to-ship transfer; - deviation or refuge; - crew detention or injury; - multiple calls; and - extended stay.

A voyage can cross a policy boundary before it reaches the company's “high-risk” label. Conversely, a policy-rated area does not prove every point carries identical operational danger.

Track quote validity and the assumptions provided to underwriters. A change from direct transit to five days waiting can be material.

Brokers should identify whether a term is firm, indicative or subject to a security plan. Charter parties should allocate who provides information and bears defined costs, but cannot transfer the master's safety duty.

Crew information should be zone-specific

A generic briefing that “the Gulf is dangerous” does not help a lookout recognize the next phase.

Before each zone, brief:

- current verified incidents and threats; - expected traffic and operations; - watch and protected positions; - reporting and communications; - machinery readiness; - safe waiting or abort options; - medical and rescue support; and - triggers for the master-company review.

Avoid unsupported weapon attribution or promises of naval protection. State what is known and what remains uncertain.

Manage fatigue across the entire exposure window. A crew held at maximum security posture for a week can lose vigilance. Scale measures according to approved risk assessment without dropping critical readiness.

Record questions and concerns. Changes in destination or waiting should trigger a fresh briefing.

A wider map does not justify a blanket forecast

The geographic spread of confirmed incidents proves that relevant events occurred beyond the narrow Strait. It does not prove systematic targeting of every port, uniform weapon reach or an inevitable northward expansion.

Use three statements separately:

- Fact: a confirmed or officially reported incident occurred at a stated location. - Inference: the event broadens the area that should be considered in planning. - Scenario: future attacks might affect another zone or operation.

Attach evidence and date to each. Retire an analytical zone only through a documented review, not because several quiet days pass.

Avoid heat maps that imply quantitative probability unless the data and method support it. A coloured polygon can look more scientific than the underlying evidence.

Build a rolling zone matrix

The daily voyage gate should compare each ship's next 72 hours with the zone matrix.

Include:

| Field | Decision use | |---|---| | Verified incident recency | Current evidence | | Threat types | Readiness and vulnerability | | Expected hours | Aggregate exposure | | Static operations | Predictability | | Navigation constraints | Manoeuvring risk | | Response time | Consequence control | | Insurance status | Financial and contractual gate | | Authority information | Movement and support | | Trigger | Review, defer or abort |

One accountable security analyst maintains the evidence. Marine operations tests navigational feasibility. Technical, crewing, insurance and commercial teams add constraints. The master receives the result and retains onboard judgment.

Archive each version so later reviews can see what was known at decision time.

A controlled scenario

A gas carrier will load in Qatar, wait offshore, transit Hormuz and bunker near the Gulf of Oman. A single “Hormuz high risk” rating hides most of the voyage.

The company evaluates four operating zones, assigns different machinery and reporting postures, verifies rescue access and obtains insurance terms that include waiting. The charterer supplies a realistic berth range. A new confirmed event in the central Gulf triggers review before the ship enters its waiting phase, not only before the Strait.

This is a hypothetical commercial scenario, not a prediction about a named port or ship.

Commercial conclusion

The 2026 spillover is geographic and operational. Risk follows routes, waiting, terminals and service points, not a single chokepoint label.

Owners should manage time by zone and fleet concentration. Charterers should disclose the full port-call profile. Ports should connect security with casualty response. Insurers should state geographic triggers precisely. Supply-chain teams should locate cargo by stage and zone.

ZeaClub can maintain the evidence map, zone matrix, exposure hours and decision history. It cannot declare a port safe, predict an attack or replace the master and competent authorities.

This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.

Sources