Build a current inspection pack
The company should identify the documents requested by the current official advisory and the vessel's applicable flag, coastal, customs, sanctions and security requirements. A generic folder from an earlier voyage may be incomplete or contain inconsistent data.
The pack can include ship identity and registry, ownership and management details, flag and class documents, crew list, last and next ports, voyage history, cargo manifest, bills of lading or cargo declarations, dangerous-goods information, bunker data, chartering parties, sanctions screening and relevant exemptions or authorisations. The exact contents depend on the voyage.
Every key fact should reconcile across documents. A destination mismatch between AIS, clearance, bill of lading and agent messages can look suspicious even when caused by a late commercial change. Corrections should be documented and versioned rather than hidden.
Both secure electronic and controlled paper access may be needed. The ship should plan for poor connectivity or a request that cannot be satisfied by opening an office cloud drive. Sensitive personal and commercial data should remain protected, with copies released only under the approved procedure.
The company should name a shore contact who can verify documents and answer ownership, cargo or sanctions questions. The master should not have to resolve a complex beneficial-ownership chain while managing an approach by armed personnel.
Document readiness can shorten an encounter, but it does not guarantee clearance. Nor does a request for documents prove that the requester is legitimate.
Authenticate before changing the ship's plan
A hail should be logged with time, position, channel, claimed identity, requested action and any visible or radar information. The bridge should use current official contact and authentication procedures to confirm the caller where circumstances permit.
MARAD advises U.S.-flagged ships to answer coalition naval calls, maintain specified standoff and coordinate with NAVCENT NCAGS. It separately warns that Iranian forces have historically used small boats and helicopters in boarding operations and tells U.S.-flagged vessels how to treat certain over-the-horizon Iranian calls or emails. Other flags may receive different instructions and must follow their competent authorities.
The bridge should not extrapolate U.S.-flag guidance to every vessel. The company should place flag-specific instructions in the passage pack and identify whom to call for real-time advice.
Changing course or speed to facilitate a visit can create collision, mine, grounding or misidentification risk. The master must consider traffic, depth, corridor limits and surrounding military activity. If an instruction cannot be executed safely, that constraint should be stated clearly and reported through the authorised liaison channel.
Closed-loop communication reduces error. The ship repeats the requested action, location, speed and time. Ambiguous phrases such as "follow us" need clarification. Crew should avoid argumentative radio exchanges while maintaining a precise record.
Control access without escalating the encounter
The ship security plan should define how access is controlled, who meets authorised visitors, which route they use, what spaces remain restricted, and how identity and purpose are checked. IMO guidance says ship security plan access controls should normally be respected by everyone, including public authorities seeking access during routine ship and port activities.
A conflict-zone visit at sea is not routine. The master and ship security officer may need to adapt under flag and authority guidance to protect life. The plan should define decision authority and escalation contacts rather than assume the crew can enforce ordinary visitor procedures against an armed boarding party.
Crew roles should be simple. One team manages navigation, one handles communications and records, one controls the designated access point if safe, and non-essential crew remain in assigned protected locations. The chief engineer maintains propulsion and power as instructed by the master. No one should crowd the boarding area or make unauthorised recordings that could be misinterpreted.
Weapons, drones, helicopters, fast boats or forced entry can rapidly change the classification from inspection to security incident. The ship security alert system is designed to send a covert alert ashore when ship security is threatened or compromised. Activation criteria and locations belong in the approved ship security plan and should be known to authorised crew.
The crew should not destroy documents, conceal people or cargo, or volunteer speculative explanations. They should provide authorised factual information, note what is taken or copied where possible, and preserve safety.
Plan for delay and loss of schedule
A query may take minutes; a visit may take hours; a diversion or detention can last much longer. The voyage model should include fuel, machinery, crew-rest, cargo-care and ETA consequences rather than treating the encounter as a fixed inspection time.
Waiting or slowing can move the ship outside its planned traffic sequence or security window. The operator should notify the coordination authority and recalculate the route before resuming. An earlier approval should not be assumed valid after a long interruption.
Cargoes with temperature, pressure, ventilation or time constraints need specific contingency limits. Dangerous goods and gas cargoes can affect where personnel may board and which areas can be entered safely. Technical restrictions should be explained factually.
Charterers and cargo interests should receive a controlled status: query received, identity under verification, visit in progress, ship held, diverted, cleared or incident response activated. Exact security details and personnel identities should be limited to those who need them.
Commercial allocation may involve hire, off-hire, deviation, detention, delay, war risk, sanctions and cargo claims. The contract and facts control. The bridge should preserve events rather than debate legal labels during the encounter.
Record the encounter and review the voyage
The ship should maintain a contemporaneous log of communications, position, course, speed, personnel, observed markings, instructions, documents provided, access areas, duration and outcome. VDR, radar, ECDIS, CCTV and communications data should be preserved under approved procedures if the event becomes suspicious or hostile.
Facts and allegations must remain separate. "Caller identified itself as X" is an observation. It is not proof of identity. "Four persons boarded wearing specified uniforms" is stronger than an unsupported conclusion about their organisation.
Required reports should go to the flag, company, UKMTO, coastal or naval authority, insurer and others under the current matrix. If safety or security was threatened, emergency procedures take precedence over administrative completeness.
A Zeaclub visit-and-search workflow can hold the verified document pack, flag guidance, contact matrix and role checklist. During an encounter it can provide a restricted event log and release role-specific updates to the company, insurer and charterer. It should never publish live location or boarding details broadly.
After clearance, the ship should reassess route validity, crew fitness, systems, fuel and cargo before resuming. Any security-plan weakness or document inconsistency becomes a corrective action for the next vessel.
The objective is calm preparedness. A neutral ship can cooperate with a verified inspection without surrendering navigational safety or abandoning access controls. It can also recognise when the facts no longer match an expected visit and activate the security response approved for its flag and voyage.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- Joint Maritime Information Center, "Update 114 to JMIC Advisory Note," 15 November 2026:Accessed 2026-11-19
- U.S. Maritime Administration, "2026-011 Persian Gulf, Strait of Hormuz and Gulf of Oman: Iranian Attacks on Commercial Vessels," current advisory accessed 18 November 2026:Accessed 2026-11-19
- International Maritime Organization, "SOLAS XI-2 and the ISPS Code," accessed 18 November 2026:Accessed 2026-11-19
- International Maritime Organization, MSC/Circ.1156, "Guidance on the Access of Public Authorities, Emergency Response Services and Pilots on Board Ships":Accessed 2026-11-19
- International Maritime Organization, Resolution MSC.147(77), "Revised Recommendation on Performance Standards for a Ship Security Alert System":Accessed 2026-11-19
- International Maritime Organization, "Frequently Asked Questions on Maritime Security," accessed 18 November 2026:Accessed 2026-11-19