Knowledge / Navigation and collision

Voyage planning and ECDIS: from route checking to execution assurance

An evidence-based passage-planning guide covering chart quality, ECDIS settings, route-check limits, changing assumptions and execution monitoring.

On this page

A route line is only one part of a voyage plan. Safe execution depends on the relationship between chart information, ship condition, environmental assumptions, equipment configuration and decisions made as the voyage develops. Electronic Chart Display and Information Systems, or ECDIS, can assist that work, but an automated route check does not prove that every relevant danger has been assessed. This article follows the evidence needed to connect planning with execution. Its calculations are deliberately simplified teaching examples, not settings for a particular bridge system or permission to navigate a real passage.

1. Treat planning as a continuing process

IMO Resolution A.893(21) organizes voyage planning around appraisal, planning, execution and monitoring. Its berth-to-berth scope includes pilotage. The 1999 date identifies the source; applicability is considered with the current statutory and flag-state framework, rather than assuming that age alone makes the guidance obsolete.

For an educational assessment, connect each important assumption to a later check. If passage timing assumes a tide window, identify how the prediction will be compared with available observations. If a turn assumes a particular propulsion condition, record what would invalidate it. A plan becomes useful when it tells the team what must remain true and what needs reassessment when circumstances change, rather than merely recording where the ship was expected to go.

2. Establish the ship and information baseline

Begin with the actual draught, trim, dimensions, relevant equipment condition and available manoeuvring information. A route reviewed for one loading condition is not automatically suitable after cargo or ballast changes. The question is not whether a route filename is familiar, but whether the assumptions behind its latest review still describe the vessel.

Create a compact evidence list for the passage: official chart coverage and updates, navigational warnings, weather and water-level information, applicable routeing measures, port restrictions and communications arrangements. Record the source and time associated with each changing item. Two copies of yesterday’s information do not constitute a current independent check. Missing information should have an owner and a decision consequence; a blank field is not evidence that no restriction exists.

3. Separate chart currency from survey quality

A recently updated electronic navigational chart can contain older survey information. Update status and underlying measurement quality answer different questions. IHO S-66, edition 2.0.0, explains chart-data quality and its interpretation. The IHO catalogue confirms that the English S-67 depth-accuracy guide has been incorporated into this edition.

Consider an invented route segment whose chart is fully updated but whose seabed has limited survey coverage. A precise vessel position cannot supply missing seabed measurements. Conversely, excellent bathymetry cannot correct an erroneous ship position. Record both issues separately. Quality categories are not guarantees that every obstruction is known or that depths remain unchanged on a mobile seabed. A visually detailed display should not be confused with equally detailed knowledge of the water beneath it.

4. Understand safety depth and safety contour

In the established MSC.232(82) performance-standard framework, safety depth and safety contour perform different display functions. A selected safety depth emphasizes relevant soundings; the safety contour distinguishes areas and supports associated warnings. If the requested contour is unavailable, the system uses the next deeper available contour. Confirm the behaviour of the installed, approved equipment.

For example, an illustrative calculated requirement of 11.4 metres does not create a new 11.4-metre contour in an ENC containing only 10- and 15-metre contours. The selected boundary may therefore be 15 metres. That does not mean every place outside it has been independently assessed for the passage. Nor does moving the setting to reduce inconvenient shading resolve the underlying depth requirement. Settings must follow the assessment, not be adjusted to make an attractive picture.

5. Show the vertical budget without double counting

Suppose a generic passage assessment uses 9.2 metres of static draught, 0.5 metres for an assumed dynamic increment, 1.0 metre of required residual clearance and 0.7 metres of explicitly allocated uncertainty allowance. The illustrative minimum total water depth is 11.4 metres. If a reliable water level of 0.8 metres above the chart datum is available, the corresponding arithmetic requirement for charted depth is 10.6 metres.

Those numbers are invented; the uncertainty allowance is not a CATZOC formula or universal company policy. The terms must share a consistent datum and physical meaning. Do not count the same squat or uncertainty twice under different names. If the usable water level becomes only 0.3 metres, the charted-depth requirement rises to 11.1 metres. The change is 0.5 metres even though neither the route line nor the vessel’s static draught changed.

6. Check the corridor, turns and escape space

An automated scan examines a configured area using available chart data and system functions. The MCA’s ECDIS guidance warns that route checking is constrained by the selected cross-track corridor. A clean scan cannot establish that water outside the checked corridor is suitable.

As a simple coverage example, a corridor extending 0.10 nautical miles either side of a centreline reaches 185.2 metres each way. A charted hazard 0.12 nautical miles away is 222.24 metres from that centreline, outside the corridor by 37.04 metres. No clearance conclusion follows without hull dimensions, positioning allowances and the actual turn geometry. The example shows only why scan boundaries must be visible. A route amendment or avoiding action may enter water that the original scan never examined.

7. Review geometry and displayed detail deliberately

A waypoint joins legs mathematically; a real vessel turns over time and occupies an area. The review should therefore examine the anticipated turn and swept path, not just the intersection of two straight lines. Verify that any turn model and associated settings are supported by suitable manoeuvring information for the expected condition.

Display scale also affects what the reviewer notices. Zooming can enlarge symbols without creating new survey accuracy, and a broad overview can hide a critical local relationship. Use both overview and appropriate detailed inspection, including relevant object information. Maintain a record of unresolved warnings and why accepted warnings were judged acceptable. Repeatedly acknowledging an alert is an interface action; it is not the same as demonstrating that the associated hazard has been assessed.

8. Make timing assumptions testable

Consider a hypothetical 18-nautical-mile approach segment. At a constant speed over ground of 9 knots, transit time is two hours. At 7.5 knots, it is 2.4 hours, a delay of 24 minutes. This simple difference may affect a time-limited assumption elsewhere in the plan, even though the geometry is identical.

Real timing also involves speed changes, waiting, traffic and manoeuvring; the example assumes none of those. Its purpose is to reveal a dependency. Identify which decisions depend on arrival time and when the uncertainty becomes material. A useful plan includes a reassessment point before a commitment becomes difficult to reverse. The responsible bridge team determines the real decision criteria using approved procedures, current information and local requirements; this article provides no universal latest-turn or abort threshold.

9. Treat transfer and revision as controlled changes

A route sent between workstations can lose context even when every waypoint transfers correctly. Parameter values, available chart cells, software behaviour, permitted corridor widths and warning acknowledgments may differ. Verify the received route and its relevant settings on the equipment that will be used; do not equate successful file import with completed review.

Give revisions a clear identity and record the reason for change. When a waypoint, draught assumption or tide estimate changes, identify which earlier checks must be repeated. The bridge team should be able to establish which version is active and what changed since the last briefing. Retaining an approved-looking screenshot from an earlier version creates ambiguity rather than useful evidence. Change control is especially important when urgency encourages small edits that appear harmless in isolation.

10. Connect monitoring to the plan’s assumptions

Monitoring needs to detect more than a departure from the centreline. The ship can remain on the planned track while its timing, equipment state, visibility or assumed water level no longer matches the plan. A useful monitoring brief therefore includes the variables that could invalidate the passage assessment and the response authority for each.

Avoid treating correlated displays as independent position confirmation. Record which sensor supplies each system and how alternative observations are used under the ship’s procedures. If information conflicts, the issue is to establish a trustworthy situational picture, not to select the most convenient screen. Similarly, backup arrangements must support the intended navigation function when needed. The mere presence of a second display does not demonstrate that data, power or source failures are independent.

11. Account for the ECDIS transition accurately

The IMO’s 2026 update states that MSC.530(106)/Rev.1 can apply voluntarily to new ECDIS installations from 1 January 2026 and applies to all new installations from 1 January 2029. This is not a statement that every existing installation must be replaced in 2026. The applicable equipment standard depends on the actual installation and governing requirements.

For practical assurance, identify the installed system, software, supported data products and applicable documentation. A new data format does not remove the need to examine assumptions, quality and route-check coverage. Do not claim a capability because another system with the same brand supports it. Training, approval and operational familiarity should relate to the actual configuration. Transition dates belong in an equipment assessment, not in an unsupported promise that all chart-related uncertainty has disappeared.

12. Produce an evidence trail rather than a green tick

A concise review record can identify the route revision, ship condition, chart and warning status, depth-budget basis, corridor and turn review, unresolved issues, timing dependencies and monitoring arrangements. Include who reviewed which part and what must trigger reassessment. This is more informative than the statement that the ECDIS reported no dangers.

Common errors are reusing a route without rechecking its assumptions, confusing safety depth with safety contour, subtracting tide against the wrong datum, and assuming a scan examined every potential deviation. Other errors include treating chart updates as new surveys and accepting an imported route without checking its received settings. The analytical output should state both what was checked and what remains unsupported. Completeness of documentation does not by itself prove the underlying assessment correct.

13. Scope and application

The core question is whether the passage remains supported by current evidence from berth to berth. ECDIS helps expose and monitor that evidence when its data, configuration and limitations are understood. It cannot assume responsibility for an unexamined plan or make uncertain water safe by drawing a line through it.

All worked numbers are original hypothetical examples. They are not an under-keel-clearance policy, an ECDIS setup procedure, a voyage approval or a substitute for competent navigation. Public international material and UK guidance are identified at their proper scope. Actual flag, coastal-state, port and shipboard requirements must be established for the voyage.

Sources