Knowledge / Navigation and collision

Bridge–pilot information exchange: a shared plan and continuous monitoring

Build a shared pilotage understanding through current vessel information, explicit roles, plan changes, communication and continuous monitoring.

On this page

Pilotage brings local knowledge together with the shipboard team’s knowledge of its vessel. The benefit depends on shared understanding of the intended passage, the vessel’s actual capabilities, the conditions and the responsibilities for monitoring. A signed information card can support this exchange, but cannot demonstrate that the team understood or maintained the same plan. This article explains the information process through a fictional change-of-plan example. It is educational material, not a pilotage procedure, a local legal opinion or instructions for maneuvering a particular vessel.

Understand the partnership and its limits

The IMO pilotage overview describes the contribution of specialized local knowledge and the framework of recommendations for maritime pilots. Pilotage arrangements and legal responsibilities also depend on local law and the competent authority. A general article cannot determine who may perform pilotage or which vessels require it in a particular port.

IMO resolution A.960(23), Annex 2, emphasizes communication, understood roles and continued duties of the master and watchkeeping officer despite the pilot’s presence. The useful learning point is that expertise is combined through teamwork. The arrival of an expert does not turn the rest of the bridge into passive observers, and the shipboard team’s unfamiliarity with local details does not make its vessel knowledge irrelevant.

Exchange the actual condition, not only design particulars

Length, beam, draft and maneuvering information establish part of the vessel description. Current limitations, equipment status, loading condition and relevant deviations can be equally important. A standard card copied from an earlier call may be tidy while omitting a changed response or unavailable function. Distinguish design capability, demonstrated performance in a stated condition and the capability available now.

For an educational review, ask where each value came from and whether it still matches the vessel. Is the stopping information from trials, an approved booklet or recent observed performance? What condition did it represent? Which limitation has been reported by the engineering team? The aim is not to improvise new limits but to prevent old or decontextualized numbers from becoming unexamined assumptions in the shared plan.

Convert a route into a shared description of phases

A line on a chart does not explain the sequence of tasks. The team also needs a common understanding of the passage’s phases, expected changes, external assistance and the observations used to monitor progress. The relevant detail depends on the operation. A long written plan can still leave uncertainty about who watches a particular condition or how a change will be communicated.

In a fictional arrival, distinguish the approach, pilotage transit, tug connection, turning area and final berthing phase without assigning real positions or speeds. For each phase, ask what information must be current and what resources are assumed. This is a method of reading the plan, not a prescribed maneuvering sequence. It reveals where one person’s mental picture contains a step that another person has not anticipated.

Make roles observable rather than implicit

Role allocation should make it clear who is conning, who is communicating, who is monitoring navigation and how concerns are raised under the applicable bridge procedures. One person may perform several roles, but the workload and overlaps should be understood. Two people assuming the other is checking a critical parameter creates a gap that an organizational chart may not reveal.

A useful briefing describes the function of each role and the information that must flow between roles. It also accounts for handovers, interruptions and personnel leaving the bridge. The question is not merely whether enough people are present; it is whether the necessary observations, decisions and communications remain covered. A role that exists only on paper offers limited protection when the actual task sequence changes.

A written card supports a conversation

A.960(23) treats master–pilot exchange as a continuing process and states that a card or form supplements the verbal exchange. In an educational audit, therefore distinguish a completed form from evidence of understanding. The conversation should reveal inconsistent assumptions and unresolved questions, rather than simply read out fields until signatures can be added. Local practice and the specific navigational demands determine the required content.

For a fictional example, a form says “two tugs,” while one participant assumes both are available before entering the turning phase and another assumes the second arrives later. The words match but the plans do not. Asking when each resource is required exposes the difference. This is an information problem even before considering the technical adequacy of either arrangement, which requires a separate ship-specific assessment.

Communicate in a language the team can use

The IMO Standard Marine Communication Phrases overview explains the purpose of standardized safety language in reducing misunderstanding. Familiar words can still be ambiguous when they refer to different objects, times or actions. Clear communication requires more than fluent speech: the recipient must understand the intended meaning and relevant context.

When a pilot communicates with external parties in a language not understood by the bridge team, the essential meaning needs to be made available so the team can monitor the consequences, as addressed in A.960(23). For learning, separate the message, acknowledgement and observed execution. Acknowledgement shows receipt or understanding to the extent established; it is not physical proof that a tug, engine or rudder has done what was expected.

An original change-of-plan example

Assume a classroom passage has a fictional 0.8-nautical-mile remaining leg and an illustrative constant ground speed of 6 knots. The reference-point travel time is eight minutes. A newly reported assistance delay of five minutes is therefore material to the earlier timing assumption. The calculation does not determine whether the passage should continue or stop; it merely makes the size of the information change visible.

The team’s analytical task is to identify which assumptions depend on that assistance: phase timing, monitoring, communications and the available authorized alternatives. The revised understanding should be explicit to everyone who relies on it. Do not infer that waiting, accelerating or changing route is safe from this example. Those decisions require the actual vessel, waterway, traffic, conditions and competent authority arrangements.

Monitor the plan as conditions evolve

The shared plan is an initial statement of intended action under stated assumptions. Traffic, visibility, current, equipment status or assistance can change. Monitoring should therefore compare the observed situation with the assumptions supporting the next phase. Discovering a deviation matters only if the information reaches the people who can evaluate and respond to it in time.

An educational observation log can distinguish position, motion, environmental change, equipment condition and external-resource status. It should retain the time and source of each update. Avoid presenting a single green “on plan” indicator as though it proves every category remains acceptable. A vessel can follow the charted line while an important timing or machinery assumption has ceased to hold.

Challenge should focus on the discrepancy

A constructive challenge names the observed difference or uncertainty and seeks clarification through the established bridge procedures. It should not require a junior team member to prove the final consequence before speaking. Equally, it should not turn an uncertain reading into an unsupported accusation. Specific observations make it easier to resolve the issue: what was expected, what is seen and which assumption may have changed.

The MAIB investigation of Ali Ka’s contact with Oikos Jetty 2 includes lessons and recommendations concerning bridge resource management, roles, pilot support, exchange and challenge procedures. That is evidence from one investigated casualty, not a frequency estimate for pilotage failures. The general analytical lesson is to examine the working relationship and information flow, rather than attributing the entire problem to a vague label such as “human error.”

External teams are part of the information boundary

Tugs, mooring teams, VTS and terminal personnel can hold information the bridge needs. Each also needs the relevant part of the vessel’s intended operation. Their involvement does not make them interchangeable authorities or guarantee they share the same plan. The IMO VTS explanation provides the general service framework; local roles and powers require their own verification.

In a debrief, trace a material update from its origin to all affected parties. Was a change in tug availability received only by one person? Did the bridge understand an external exchange that altered the next phase? Was a reported equipment limitation reflected in the shared plan? The aim is an intelligible information chain, not indiscriminate broadcasting of every detail to every participant.

Treat handover and completion as separate states

A pilot change, watch change or shift in the conning position can interrupt a previously shared understanding. The incoming person needs the current state, relevant limitations, pending actions and changes from the original plan. Repeating the original briefing without the intervening changes can restore an obsolete picture. The handover should preserve what is still unresolved as well as what has been completed.

Likewise, completion of one phase does not prove readiness for the next. Tug release, equipment restoration and transition to another watch arrangement have their own conditions. This article does not define those operational gates. It explains why a review should record the state actually reached and the evidence for it, rather than assuming the plan’s next box has become true automatically.

Debrief for learning rather than hindsight

Reconstruct what each participant knew before showing the complete event record. Identify where assumptions diverged and whether the divergence was discoverable with the information available at the time. Separate a missing observation from a misunderstood message and from an understood concern that did not receive an effective response. These distinctions produce more specific improvement actions than simply recommending “better communication.”

A useful learning record names the context, sources, agreed roles, changes, monitoring evidence and unresolved limitations. Common errors include treating a signed card as a complete exchange, hiding current machinery limitations behind design data, assuming external communication is understood and letting pilot expertise suppress independent monitoring. Effective exchange is demonstrated by a maintained shared understanding, with local requirements and qualified bridge judgment still necessary.

Sources