Start with the event, not the presumed attacker

An initial ship report should describe observable facts before assigning motive or responsibility. Examples include:

- a small craft closed to a stated range and matched course; - an unmanned aerial object was sighted on a stated bearing; - an explosion was heard and damage was found; - an unknown projectile passed the vessel without impact; - a VHF caller ordered the ship to alter course; - GNSS positions diverged from radar and visual fixes; or - crew found a hull breach, fire or injured person.

“Hostile Iranian drone attack” combines event type, intent, weapon and attribution. Each may require different evidence. If the bridge saw only an unidentified object followed by an explosion, the first verified record should say that. Security authorities can add an assessment later.

The master’s immediate safety response need not wait for final classification. MARAD Advisory 2026-011 tells US-flagged vessels to report attacks, incidents and suspicious activity promptly through designated channels. Reporting a suspicious event is not the same as declaring who caused it.

Separate four classification layers

A company incident record should hold at least four layers rather than one free-text label.

The first layer is occurrence status. Was the event reported, corroborated by another source, or confirmed through a defined validation process? “Reported” means a claim exists. It does not mean the claim is false, and it does not make it verified.

The second is event type. Useful working labels include suspicious activity, threatening communication, attempted boarding, attempted or targeted attack, weapon impact, detention, seizure, hijacking, collision, fire, navigational interference and unknown event.

The third is consequence. Record no known damage, minor damage, serious damage, fire, pollution, loss of propulsion, abandonment, injury, fatality or missing person. “No reported injuries” is different from “all crew medically assessed and uninjured.”

The fourth is attribution. This can be unknown, alleged by a named party, assessed with a confidence level, or officially attributed by a competent authority. Attribution should include the source and time. A weapon’s apparent origin does not by itself establish who launched it.

These layers prevent a common data error. A projectile that misses can be an attempted attack with no damage. A vessel damaged by an explosion may be a confirmed casualty while the weapon and perpetrator remain unknown. A suspicious approach may merit evasive action but never develop into an attack.

Use JMIC categories as definitions, not shortcuts

A JMIC weekly dashboard published in 2026 explained its general categories. It described a serious attack as a deliberate weapon launch or ramming producing serious damage, a total loss or a significant threat to life. It described a minor attack as a deliberate weapon launch or ramming resulting in a miss or minor damage. It distinguished an attempted attack or targeted event involving force that misses without damage, and suspicious activity near a vessel that warrants suspicion.

Companies can use those definitions to improve consistency, but they should preserve the exact document version and explanatory note. A category designed for a regional dashboard may not have the same meaning as an insurance-policy term, a flag-state casualty classification or a criminal-law allegation.

If JMIC or UKMTO later reclassifies an incident, the company should record the new category and the time of change. The original label should remain in the audit trail because voyage decisions made earlier were based on the information then available.

Understand what IMO confirmation proves

IMO’s Middle East information page says its regional attack data are compiled through a rigorous validation process involving flag States, coastal States and credible verified third-party sources. Its highlighted list provides a strong public baseline for confirmed ship incidents.

Inclusion supports the proposition that an incident affecting the identified ship was validated to IMO’s standard. It does not necessarily prove the identity or motive of an attacker, the exact weapon, every casualty detail or the legal character of the act.

Absence from the list is also not proof that nothing happened. Validation takes time, reports may be incomplete, and some events may fall outside the list’s scope. An owner can therefore have a credible urgent ship report before the event appears on a confirmed public register.

Counts must carry a date and scope. A running total can change after a new incident or retrospective validation. Combining UKMTO warnings, JMIC categories, media reports and IMO confirmed entries without deduplication can count the same vessel several times.

Build a time-stamped evidence ladder

A practical evidence ladder helps the duty team update its confidence without delaying emergency action.

Level one is the originating report: master, crew member, nearby vessel, port, military unit or other named source. Preserve the wording, UTC time and communication method.

Level two is internal corroboration: radar recording, voyage data recorder material, CCTV, photographs, alarm history, damage inspection, medical report or independent witness. Preserve originals and chain of custody.

Level three is operational authority reporting: UKMTO warning or advisory, flag-state message, coastal-state notice, naval coordination report or search-and-rescue communication. Note whether the authority confirms the event or merely relays a report.

Level four is validated public or investigative evidence, such as an IMO confirmed entry, flag-state casualty finding or other competent investigation.

The incident log should never overwrite timestamps. A dashboard must show “known at decision time” separately from “confirmed later.” That protects learning and helps determine whether a master, operator or charterer acted reasonably on the available information.

Match language to operational decisions

The fleet alert should use controlled phrases. “Unverified report of an explosion 20 nautical miles ahead; authority confirmation requested” tells masters both the potential urgency and the evidence gap. “Confirmed vessel damage; cause under investigation” prevents a casualty from being misrepresented as proven attribution.

Route decisions should use triggers broader than final attack confirmation. A credible suspicious approach, navigation anomaly or authority warning may justify increased lookouts, revised timing or an abort under the vessel’s risk plan. The action should be proportionate and documented.

Masters must retain authority to respond to the conditions around their ship. Shore staff should avoid demanding photographic proof before accepting an urgent security report. Equally, masters should distinguish observation from interpretation when time permits.

Protect insurance, chartering and market integrity

Incident language can have immediate financial consequences. War-risk notice, sue-and-labour steps, P&I notification, hull inspection and evidence-preservation duties depend on policy wording and facts. The first notice should report promptly without conceding uncovered causation or speculating about liability.

Charter parties may contain war-risk, safe-port, employment, deviation and cancellation provisions. Calling an event an “attack” does not automatically activate a clause, while calling it “suspicious” does not prevent a legally relevant danger from existing. Parties need the actual wording and verified circumstances.

Brokers and traders should not forward a screenshot as confirmed market intelligence. Before circulating an alert, they should identify the vessel where disclosure is lawful, source, location, time, event status and whether another report may describe the same occurrence.

A corrected report should be distributed as visibly as the original. Quietly editing a dashboard leaves recipients acting on stale information.

Design the Zeaclub workflow around uncertainty

ZeaClub can structure each report into event, consequence, verification and attribution fields. It can link later updates to the original record, detect possible duplicates by ship, time and location, and warn when a source is superseded.

The workflow can require a confidence statement, preserve links and checked times, and prevent an allegation from being displayed as fact. It must not invent missing details or collapse conflicting accounts. Human security professionals, masters, flag States and investigators remain responsible for consequential judgments.

Commercial conclusion

A maritime-security report is not a single yes-or-no fact. It is a developing record of observation, consequence, validation and attribution.

Owners should adopt controlled categories, a time-stamped evidence ladder and a correction process. Masters should report observable facts quickly while taking protective action under the ship’s plan. Charterers, insurers, brokers and traders should use the classification appropriate to their decision without stretching it beyond the evidence.

The best answer to “Was it an attack?” may initially be: “A threatening event was reported, damage is being checked, and attribution is unknown.” That is not indecision. It is the precise foundation from which safer and more defensible decisions can follow.

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

Sources