JMIC and ISPS answer different questions

JMIC advisories synthesize incident reporting and regional military information for shipping. Their threat terminology helps a decision-maker understand the assessed likelihood of hostile events. It is an important operational input, but it is not itself a flag-State instruction or an amendment to a ship security plan.

The ISPS framework asks a different question: which approved protective measures must a ship or port facility maintain at the security level set by the responsible government authority?

IMO defines Security Level 1 as the normal level at which minimum appropriate measures are maintained. Level 2 requires additional measures for a period of heightened risk. Level 3 requires further specific measures for a limited period when a security incident is probable or imminent, even if the particular target cannot be identified.

Similar language about likelihood makes a one-to-one mapping tempting. It is still wrong. The systems have different issuers, purposes, geographical scope and legal effect.

Severe does not automatically set Level 3

Verified fact: IMO says Administrations set security levels for ships entitled to fly their flag. Contracting Governments set levels for port facilities and ships before entering or while in their ports. Ships must acknowledge and comply with instructions applicable at the declared level.

Operational interpretation: A JMIC “Severe” assessment should trigger immediate review by the company security officer, master and ship security officer. It does not, by publication alone, convert the ship’s official ISPS status to Level 3.

Not established: Neither a dramatic headline nor an insurer’s risk designation proves that a government has declared ISPS Level 3 for a particular ship, port or period. The company must confirm the direction through authenticated flag, coastal-State and port channels.

A forwarded screenshot saying “Level 3 now” is not adequate evidence of the issuing authority, affected area, effective time or required actions.

Who sets the level the ship must follow?

At sea, the ship should confirm instructions from its flag Administration or recognized security channel. Before arrival and in port, it must also identify the level set by the Contracting Government for that port facility.

IMO explains that a ship entering a port operating at a higher level must comply with that higher level. If the ship is already operating at a higher level than the port, it should inform the competent authority. The master, company security officer, ship security officer and port facility security officer therefore need one shared record of the official levels and additional instructions.

Conflicting messages require escalation, not improvisation. The company should establish:

1. which authority issued the instruction; 2. whether it applies to the flag, ship type, port, anchorage or defined waters; 3. when it begins and expires; 4. which approved measures or government directions must be implemented; 5. whether the port requires a declaration of security; and 6. who records compliance and authorizes stand-down.

The master’s overriding authority for safety remains essential. It does not permit commercial staff to relabel an official security level for convenience.

Companies can strengthen controls without inventing status

Remaining formally at Level 1 or 2 does not require a ship to ignore a severe threat. The ISPS Code is risk-based, and approved plans connect changing threats with protective measures. The company can implement additional measures allowed by its ship security plan, voyage risk assessment and flag guidance.

Depending on the vessel and approved procedures, measures may include tighter access control, additional deck and radar watches, protected lookout positions, restricted external lighting, enhanced communications, pre-rigged fire response, machinery readiness, revised muster arrangements and more frequent reporting. Measures must not create new navigation, fatigue, fire or evacuation hazards.

The May 2026 industry guidance for Hormuz tells operators to conduct a fresh voyage-specific assessment, use current official sources, incorporate appropriate protective measures into security plans and consider deferment when risk increases. It also says the guidance does not replace flag or coastal-State requirements, company procedures or the master’s judgment.

That hierarchy produces a practical rule: record “official ISPS Level 2 plus specified additional measures,” if that is true. Do not write “Level 3” as shorthand.

Level 3 is a package, not a mood

Level 3 is exceptional and normally time-limited. It should connect to identifiable directions and corresponding measures in the approved plan. Raising the label without the package can be worse than useless because departments may assume someone else completed an undefined task.

A usable escalation card assigns each action to a person and deadline. It covers bridge, deck, engine room, accommodation, communications and shore support. The master and ship security officer confirm completion; the company security officer resolves resource and authority questions.

Drills should test the transition without exhausting the crew before a demanding transit. A posture that depends on every seafarer remaining continuously alert is unsustainable. Additional lookouts and access watches need documented rest-hour and relief arrangements.

Threat level is only one transit input

Even an authoritative regional rating cannot decide whether one ship should sail. Exposure depends on location, timing, cargo, ownership signals, freeboard, speed, manoeuvrability, machinery reliability, crew capacity and emergency support.

MARAD’s November 2026 advisory says hazards and attack risks remain high in the Persian Gulf, Strait of Hormuz and Gulf of Oman. For U.S.-flagged vessels it calls for pre-voyage assessment, protective measures in vessel security plans, close coordination and immediate incident reporting. Those are concrete actions, not a substitute label.

Scenario, not a forecast: Two tankers can receive the same JMIC assessment and official ISPS instruction yet reach different voyage decisions. A fully ready ship with current reporting links may proceed under defined controls. A sister ship with defective fire equipment, an exhausted crew or unresolved insurance conditions may defer. The regional assessment is the same; residual risk is not.

Commercial parties need a common vocabulary

Owners should communicate the official security level, additional measures, source and timestamp separately. Charterers need to know what affects nomination, arrival, cargo windows, speed, route or port acceptance. Brokers should transmit the distinction without compressing it into “security raised.”

Insurers may require notification of changed exposure even where the formal ISPS level has not changed. Conversely, an official increase does not answer whether cover attaches, an additional premium is due or a charterparty permits refusal. Those questions depend on policy and contract wording.

Ports and terminals need notice to coordinate access, declarations of security and interfaces with the ship. Agents should verify government and facility instructions rather than become their unexamined source.

A concise status message should state:

- official ship security level and issuing authority; - port-facility level and authenticated source; - JMIC or other threat assessment with issue time; - additional company measures now active; and - next review time and decision owner.

This format helps claims handlers reconstruct what was known and prevents counterparties from treating an advisory assessment as a statutory order.

Document escalation and stand-down

The security log should preserve the advisory, verification calls, authority messages, risk assessment, master-CSO decision, measures implemented, crew briefing and notifications. Sensitive details require controlled distribution, but secrecy is not an excuse for an untraceable decision.

Stand-down deserves the same discipline. A reduced regional rating may lag a local incident, while an expired government direction may leave voyage-specific risks unresolved. Each measure should have a review trigger and a person authorized to relax it.

ZeaClub can keep source-stamped threat notices, official levels, ship-specific controls, commercial notices and deadlines in separate linked fields. It cannot declare an ISPS level, replace the approved plan or override the master, flag Administration or port authority.

Commercial conclusion

A Severe JMIC assessment is a powerful warning, not an automatic declaration of ISPS Security Level 3. Companies should verify the official level, comply with authority and port requirements, then add plan-compatible controls justified by the ship’s actual exposure.

Precision protects crews from vague orders, gives charterers and insurers a reliable record, and prevents an advisory judgment from being mistaken for legal status. Good security communication states who assessed the threat, who set the level, what the ship changed and when the decision will be reviewed.

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

Sources