Do not confuse an approved plan with a current plan

Approval records that a plan was acceptable when reviewed. It does not guarantee that the evidence remains current.

A delay can make several inputs stale:

- UKMTO, JMIC, flag-state or naval threat advice; - temporary routes, waypoints, reporting instructions or transit windows; - NAVAREA and coastal-state navigational warnings; - weather, visibility, current and traffic forecasts; - port, pilot and terminal arrangements; - GNSS interference observations and available terrestrial references; - machinery, steering, communications and emergency-system status; - bridge-team composition and hours of rest; - war-risk quotations, warranties and notice periods; and - charter, laycan, cargo-document and sale-contract assumptions.

The master and company should identify each time-sensitive input when the original plan is approved. A source should have an issue time, version and planned review time. “Latest guidance checked” without identifying the document is not adequate control.

The active MARAD advisory illustrates the point. It asks US-flagged vessels to coordinate voyage planning with NAVCENT NCAGS, consider current recommendations, avoid identified hazard areas and report anticipated Hormuz traffic-separation-scheme entry and exit times. If the sailing changes materially, the coordination data may also need correction.

Set event-based triggers, not one arbitrary expiry time

There is no universal number of hours after which every Hormuz plan becomes invalid. A quiet six-hour berth delay may change little. A one-hour delay during a reported attack or corridor closure may change everything.

The operator should use event-based triggers alongside a scheduled review. Reappraisal should occur when there is:

1. a new attack, suspicious approach, mine report or military warning near the route; 2. a revised route, waypoint, transit sequence or coastal-state instruction; 3. a missed allocated window or a significant ETA change; 4. an equipment defect, alarm, repair or change in redundancy; 5. a change of master, key bridge personnel or security team; 6. degraded crew rest or a medical concern; 7. a material change in draft, trim, cargo status or manoeuvring capability; 8. new weather, visibility or current conditions outside the plan; 9. changed insurance approval, warranty or additional-premium validity; 10. a changed destination, pilot station, port status or commercial order; or 11. evidence that the expected traffic picture has materially altered.

A daily review may be useful for a ship waiting several days, but it cannot replace an immediate event-driven review. The decision log should state which trigger occurred and what was rechecked.

Reappraise the threat before rebuilding the route

JMIC’s November 15 update assessed the regional threat level as severe and reported a tanker attack eastbound in the Arabian Gulf before the Strait. It also said traffic continued with high anchorage congestion and described persistent harassment activity, surveillance and VHF hailing. Those are dated observations, not permanent facts, but they show why yesterday’s threat picture cannot simply be carried forward.

The security review should distinguish confirmed reports from unverified messages and predictions. A confirmed UKMTO warning can alter the route assessment. A social-media claim may justify investigation, but it should not be recorded as a verified incident unless an authoritative source confirms it.

The vessel-specific profile also needs review. A new port call, ownership link, cargo disclosure or public tracking pattern may change perceived exposure. Conversely, the absence of an incident during the delay does not prove that risk declined.

A reappraisal should end with a clear threat statement, the evidence time, remaining uncertainties and the controls required. If a competent authority has not confirmed the applicable route or window, the document should say so rather than infer permission from other ships moving.

Rebuild the navigational and technical case

The May 2026 industry guidance asks operators to confirm the latest threat assessment and advisories, review whether transit is necessary at that time, check technical resilience, assume GNSS may be unavailable or unreliable throughout the passage and conduct a bridge-team GNSS-loss drill before transit.

After a long delay, the bridge should rerun route checks against current charts, corrections and warnings. Waypoints, cross-track limits, wheel-over positions, no-go areas, abort points and safe holding options must still match the authorised route and actual ship condition.

Radar ranges, visual bearings and parallel indexes selected for position verification should be checked again. Changes in visibility, traffic, draft or tide can affect which references and margins are useful. An old ECDIS validation result does not cover a subsequently amended route.

The technical review should confirm propulsion, steering, generators, emergency power, radars, gyro, speed log, communications, watertight integrity and firefighting readiness. Machinery that has been idling or repeatedly started while waiting may need more attention, not less.

Any defect should be assessed for its effect on the whole contingency concept. A failed secondary radar or degraded steering pump may remove the redundancy on which the original approval depended.

Revalidate the people, not only the equipment

Waiting can consume the rest margin built into the first plan. Repeated standby orders, uncertain sailing times, inspections and company calls may leave the master, officers and engineers less ready than the paperwork suggests.

The revised plan should identify who will be on the bridge and in the engine room, their actual rest status and relief arrangements through the constrained sector. If personnel changed, the incoming team needs the full route, threat, communications and emergency briefing.

Drills should be repeated when the relevant team did not participate, the procedure changed or the earlier exercise exposed a weakness that has not been closed. The objective is demonstrated readiness, not a second signature on the same checklist.

Shore teams also need continuity. The duty manager, designated person ashore, security officer and commercial contact should know the current plan version and authority chain. A plan approved by one shift can be undermined if the next shift acts from an older attachment.

Reopen insurance and contract checks

A delayed transit can outlive a war-risk quotation, approval window or underwriter warranty. The assured should confirm cover in writing where required and disclose material changes under the policy terms. A previous premium indication is not evidence that cover remains bound.

Charterers and owners should review whether the delay affected notices, laycan, cancellation rights, off-hire arguments, war clauses, safe-port analysis or voyage orders. This is a contract-specific legal question. An operational decision to wait does not by itself determine which party pays.

Cargo interests should test documentary-credit dates, sale deadlines, storage exposure, inventory cover and downstream delivery obligations. Brokers should refresh arrival ranges only after the sailing window and passage assumptions are credible.

The commercial comparison should use updated scenarios: proceed in the next verified window, continue waiting, change employment where lawful, or cancel under an available right. Each scenario should separate observed costs from estimates and include fuel, port charges, security, insurance, crew, cargo delay and potential knock-on commitments.

Use a controlled release-to-sail gate

The final release should join the operational and commercial reviews without allowing commercial approval to override the master’s safety authority.

A concise release gate can require confirmation that:

- current advisories and warnings were checked at recorded times; - the route version and reporting procedure were authenticated; - bridge and engine teams are rested, briefed and drilled as necessary; - navigation and machinery redundancies are available; - insurer, flag, company and authority conditions are satisfied; - cargo and charter implications were escalated; - abort criteria and decision authority are understood; and - the departure and TSS timing reports were updated.

If one required condition is missing, the record should show whether sailing is prohibited, deferred for clarification or permitted with an approved compensating control. Silence should never be treated as acceptance.

ZeaClub can support this process by linking every route assumption to its source, expiry and owner, then flagging a plan when a delay or new event invalidates a dependency. It can prepare the evidence pack and prevent an obsolete attachment from circulating. It cannot authenticate a military instruction, bind insurance or replace the master’s judgment.

Commercial conclusion

A delayed Hormuz passage does not always need to be redrawn from a blank chart. It does need to be reappraised from first principles whenever a material input changes or expires.

Owners gain a defensible release record. Masters gain a route matched to the ship and team they actually have. Charterers, brokers, insurers and traders gain a clearer basis for timing and cost decisions.

The correct question is not “Was this plan approved?” It is “Does every assumption required for this ship to sail still hold now?” If the answer is uncertain, the passage is not ready for execution.

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

Sources