Authenticate the source and version

The company should establish which authorities and internal roles can issue or forward route information. The bridge should verify the sender through an approved contact, especially when the message changes a previously authorised track.

Email display names and messaging accounts can be spoofed or compromised. A second channel, digital signature where used, known reference number or confirmation through the official liaison desk can establish provenance.

The message should identify issue time, validity, affected direction, vessel conditions, coordinate datum, issuing authority and whether it supersedes an earlier route. "Use attached route" is incomplete.

Every version needs a unique label. The bridge, company security officer and authority must be discussing the same coordinates. Old screenshots and files should be removed from operational selection or clearly marked superseded while retained for audit.

If the route came through a broker, agent or charterer, the ship should obtain the authoritative source before loading it. Commercial parties can relay information but do not automatically have authority to direct navigation.

A route forwarded from another vessel may show what that ship used. It does not prove current approval or suitability for a different draft and manoeuvring profile.

Inspect the file before connecting it to navigation

Route files should pass through the company's approved cyber-security process. The bridge should not connect an unknown USB drive, open an executable attachment or import an unscanned file into an operational ECDIS.

IMO's maritime cyber-risk guidance addresses risks that can cause operational, safety or security failure when systems or information are corrupted, lost or compromised. Navigation systems belong within that risk-management process.

Where possible, the route should move through a segregated, controlled transfer method. File type, hash or signature, source and scan result can be recorded. A read-only or staging workstation can inspect the contents before operational import.

The officer should check for unexpected waypoints, route legs, turn radii, speed instructions, notes and embedded objects. Hidden or distant points can distort route-check results and scale.

A screenshot is not a machine route. Coordinates should be obtained in text from the authoritative source and independently entered and checked. Optical extraction from an image can introduce errors.

If the file cannot be safely inspected, the bridge can build the route manually from authenticated coordinates using double-entry verification. Urgency does not justify bypassing cyber controls.

Check every coordinate and chart relationship

Two qualified officers should independently compare each waypoint against the authoritative message. They should verify latitude and longitude, degrees and minutes, decimal precision, hemisphere and datum.

The route must be displayed at appropriate chart scales with current official ENCs or authorised charts and updates. The team should check depth, safety contour, under-keel clearance, charted hazards, traffic separation, prohibited areas, cables, anchorages and current navigational warnings.

Automated route checking is useful but not conclusive. ECDIS settings, safety values, display scale and data quality affect what it finds. IMO has previously issued guidance on ECDIS operating anomalies, reinforcing the need for competent human review.

Turn radius, wheel-over position, cross-track limit and corridor width should fit the ship's speed, draft and manoeuvring data. A series of safe waypoints can still produce an unsafe turn between them.

The route should include approach, exit, abort and holding logic rather than only the constrained middle sector. If the authority supplied only a corridor, the bridge remains responsible for connecting it safely to the voyage plan.

Any uncertainty should be sent back as a precise question. "Confirm waypoint 6 longitude and whether cross-track limit extends west of line" is more useful than "route looks wrong."

Separate route geometry from position integrity

A correctly loaded route does not establish the ship's position. GNSS spoofing can show the vessel neatly following a safe track while its true position is elsewhere.

The Hormuz industry guidance says electronic position feeds to ECDIS cannot be relied upon during transit. It recommends shortened fix intervals, radar, visual observations, dead reckoning, echo sounder and independent sources. When interference is confirmed, it calls for continuous independent fixing and radar-based plotting.

The passage plan should identify landmarks, radar ranges, parallel indexes, expected depths and fix intervals for each leg. The team should know how to select a trusted sensor or use dead reckoning without allowing a corrupted GNSS input to reset the picture.

Paper charts may form part of the approved backup arrangement or additional resilience, depending on the ship. Carrying them is not enough; officers need current charts, plotting tools and proficiency.

Route alarms and cross-track limits should reflect the validated corridor and position uncertainty. A narrow alarm boundary may be meaningless if the fix error is larger.

The bridge should test that both primary and backup ECDIS units contain the approved route where applicable, while avoiding simultaneous import of a corrupted file.

Obtain master approval and brief the team

The officer preparing the revised route should present the changes, hazards and unresolved points to the master. Approval should be explicit and time-stamped. Shore endorsement does not replace the master's passage-plan approval.

The bridge team should compare the new route with the superseded one and understand where the first divergence occurs. It should review expected traffic, speed, turn points, reporting, authority calls, abort criteria and action after loss of position integrity.

If the route arrives during transit, the team needs a safe workload window for review and entry. One officer should retain conning and collision avoidance while another validates the change. The ship should not accept a last-second file import that leaves no time for appraisal.

The company should tell charterers and brokers that the route is under navigational validation rather than announcing a new ETA immediately. The bridge may find that the supplied geometry is unusable for the ship.

If critical data cannot be confirmed before the decision gate, the correct state is hold pending clarification.

Preserve evidence and manage commercial effects

The ship should retain the source message, file, scan result, coordinate check, route-check output, master approval, changes and authority confirmations under the safety-management and cyber-retention procedures.

After transit, the company can compare planned and actual track using trusted position evidence. It should avoid treating commercial AIS history as definitive when interference was present.

A route change can affect distance, fuel, speed, arrival, insurance and charter-party performance. Owners should disclose material changes through agreed channels. No party should describe a shore-issued route as guaranteed safe.

A Zeaclub route-control board can store the authoritative coordinate set, checksum, issuer, validity, ship conditions and approval chain. It can compare versions and flag changed points. It should not push a route directly to ECDIS or mark it approved without bridge review.

Future standardised ship-shore route exchange may reduce transcription and interoperability problems, but it does not remove cyber, hydrographic or master-approval requirements. IMO's evolving ECDIS standards recognise digital route exchange while maintaining navigation as a safety-critical human process.

The safest response to a new Hormuz route is deliberate verification under time pressure. Authenticate it, inspect it, plot it, test it against the ship, separate track from true position and obtain the master's approval. A route file can accelerate planning. It cannot perform it.

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

Sources