Governance Begins With the ISM Risk Duty
IMO describes the International Safety Management Code as requiring assessment of identified risks to the company's ships, personnel, and environment and establishment of appropriate safeguards.
The Code is principles-based because ships and companies differ. That flexibility is not permission for vague judgment. The company should show which hazards were identified, what evidence was used, what controls were selected, who owns them, and what residual risk remains.
A generic Gulf risk assessment copied across fixtures will not capture route, ship, cargo, crew, affiliation, port, timing, or changing advisories. Board approval should be voyage-specific or clearly define the narrow class of voyages it covers.
The Master Is Not the Board's Final Control
SOLAS regulation XI-2/8 protects the master's professional judgment over decisions needed to maintain ship security and says the master should not be constrained by the company, charterer, or another person in that respect.
This means the board cannot approve a voyage and then treat departure as mandatory regardless of later evidence. The master's authority is a separate and continuing safeguard.
The approval record should state that the master may delay, alter, or refuse movement when safety or security requires it. It should also provide practical support: immediate shore contacts, authority to incur reasonable protective cost, and freedom from retaliation for a good-faith stop decision.
Define the Decision Being Approved
"Approve Gulf voyage" is too broad. The record should identify ship, cargo, ports, route, time window, reporting framework, insurance, assumptions, and conditions.
A decision might authorize proceeding to a holding area but not entering the Strait. It might approve transit only through a recognized corridor, during a specified window, after current mine information and insurer confirmation. It might authorize loading but require a separate departure decision.
Conditional approvals reduce pressure to stretch an old decision after facts change. They also show counterparties precisely which gate remains open.
Require an Evidence Pack, Not a Slide of Headlines
The core pack should contain current official advisories, verified incident data, route and navigation information, flag-state guidance, master and security-officer assessments, insurer terms, port status, crew considerations, cargo and affiliation screening, and contingency routes.
Every source needs a timestamp. Facts, allegations, forecasts, and hypothetical scenarios should be separated. Unknowns should appear as unknowns rather than disappear from the presentation.
JMIC warned in March that public claims of attacks remained unverified and advised reliance on official channels. Senior governance should enforce the same information discipline.
Ask What Has Changed Since the Last Approval
A board or delegated crisis committee should not reread the entire conflict history for each transit. It should focus on material change:
- new verified attacks or casualties; - a different threat level or weapon; - mining or route warning; - change in blockade or inspection rules; - electronic interference affecting navigation; - port or infrastructure disruption; - insurer or flag-state condition; - crew fatigue or objection; - cargo, ownership, transfer, or destination change.
The approval should automatically expire when a listed trigger occurs. A new event then reopens the relevant part of the assessment.
Test the Controls Against Failure
A list of controls is not enough. Directors should ask what happens if each fails.
If satellite communications fail, how does the ship report? If GNSS is unreliable, can it navigate with adequate redundancy? If a VHF caller gives conflicting instructions, how is identity authenticated? If the route closes after departure, is there fuel and sea room to hold or divert? If an attack disables propulsion, what rescue, tow, and medical support exists?
The answers reveal whether controls are operational or aspirational. "Maintain contact with authorities" is weak if the company has not tested numbers, call signs, backups, and responsibility.
Residual Risk Must Be Stated Plainly
Risk matrices can create false comfort when high-consequence events are converted into colors. The approval paper should describe the remaining harm in words: death or injury, fire, sinking, detention, pollution, loss of navigation, collision, abandonment, or prolonged stranding.
It should explain why the residual risk is considered tolerable, by whom, and for how long. If no mitigation can reduce a known threat below the company's limit, the correct governance outcome is not a darker shade of amber. It is no approval.
IMO's 9 June statement said seafarers must not be exposed where risks were known, significant, and clearly beyond mitigation. That is a substantive boundary, not a disclosure exercise.
Commercial Benefit Belongs in a Separate Section
Boards are entitled to understand revenue, customer impact, market position, and strategic importance. Those considerations should not be embedded in the safety score.
A separate commercial section prevents attractive freight from quietly changing the assessed likelihood or consequence of harm. It also makes the tradeoff visible: this is the benefit sought, these are the costs and controls, and this is the residual exposure imposed on people and assets.
The safety conclusion should stand even if the expected margin is removed from the paper.
Crew Readiness Is a Governance Metric
Crew composition, experience, fatigue, health, welfare, training, and ability to execute emergency procedures affect residual risk. A technically capable ship can be unready if key personnel have not rested after a prior high-alert passage.
The board does not interview every seafarer. It should require a credible process confirming briefing, competence, rest, welfare support, and escalation of concerns. It should know whether collective agreements, flag requirements, or company policies create additional obligations.
Crew concern should not be filtered out because it complicates the fixture. It is operational evidence.
Insurance Approval Is Necessary but Not Sufficient
War-risk underwriters may quote an additional premium, impose warranties, require notification, or decline the voyage. P&I and other covers may have separate positions.
An insurer's acceptance proves only that cover has been addressed under stated terms. It does not establish that the voyage is safe, lawful, contractually required, or acceptable to the master.
The board pack should identify covers, limits, exclusions, deductibles, conditions, aggregation, and confirmation status. It should also show who verifies compliance during the voyage.
Decision Rights Must Work at 0300
A beautiful governance chart is useless if the ship reports a new threat outside office hours and no one can decide.
The company needs a 24-hour escalation chain with named roles, deputies, contact methods, authority limits, and a default safe action if contact fails. The master should not wait for a commercial director to wake before taking necessary protective action.
The shore team should run tabletop exercises involving conflicting naval hails, new attack reports, loss of GNSS, casualty assistance, insurer conditions, and charterer pressure. Exercises expose gaps without exposing a crew.
Record Dissent and Uncertainty
If the master, designated person ashore, security adviser, insurer, or operations team disagrees, the dissent should appear in the decision record with the response. Consensus achieved by removing contrary views is not governance.
The paper should also identify evidence gaps and sensitivity. If approval depends on a route remaining open, say so. If traffic data exclude AIS-dark vessels, say so. If the attacker's targeting logic is uncertain, do not replace it with a convenient assumption.
A transparent record protects decision quality more than a unanimous-looking one.
A Hypothetical Approval Meeting
Assume a tanker is offered a high-rate Gulf cargo. The route is operating at reduced traffic, JMIC assesses the Strait as severe, insurers will cover the voyage subject to conditions, and the master has requested updated mine and naval guidance.
The committee does not approve immediate sailing. It approves preparation and a time-limited transit window conditional on current route information, insurer confirmation, crew briefing, fuel for diversion, authenticated reporting, and the master's acceptance after reviewing the final plan.
A new attack occurs before the window. The approval expires automatically. The company does not ask whether the attack was severe enough to matter after the fact; the trigger already answered that governance question.
Minimum Board Questions
Before approval, senior decision-makers should be able to answer:
- What verified change creates the opportunity to sail now? - What can kill or strand the crew despite our controls? - Which assumptions are unverified? - What would cause us to stop? - Does the ship have a safe alternative after departure? - Are insurance and legal reviews current for this exact voyage? - Is the crew rested, briefed, and supported? - Can the master say no without commercial penalty? - Who decides during an overnight change? - When does this approval expire?
If the answers are incomplete, the decision is incomplete.
The ZeaClub View
Board governance adds value by setting risk appetite, demanding evidence, funding controls, and defining decision rights. It destroys value when it turns a volatile voyage into a one-time commercial authorization.
The company and master share serious responsibilities, but their roles are not identical. Shore leadership must provide a realistic system and must not constrain the master's judgment when conditions aboard or ahead make movement unsafe.
A defensible Gulf approval is narrow, conditional, time-stamped, independently challengeable, and easy to stop. That is not indecision. It is what responsible command looks like from shore.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- IMO, International Safety Management CodeAccessed 2026-11-19
- IMO, SOLAS Convention overview and master's professional judgmentAccessed 2026-11-19
- IMO, Frequently asked questions on maritime securityAccessed 2026-11-19
- IMO, No safe passage: Strait of Hormuz remains highly volatile, 9 June 2026Accessed 2026-11-19
- JMIC Advisory 017-26, 18 November 2026Accessed 2026-11-19
- JMIC Advisory Update 007, 7 March 2026Accessed 2026-11-19