Bridge Resource Management (BRM)
It is not a course to complete once and forget: it is the discipline that explains why most navigational incidents originate from a team that fails to communicate, not from an unknown rule.
Operational Explanation
Bridge Resource Management (BRM) is the set of practices that optimise the use of the human and technical resources available on the bridge: effective communication, clear allocation of tasks, the ability to "challenge and respond" among team members regardless of rank, and the building of a shared mental model of the navigational situation.
Investigations into navigational incidents, with striking consistency over time, do not identify ignorance of a navigation rule as the primary cause, but weaknesses in how the team functions: unclear task allocation, ineffective communication, absence of challenge when something does not add up, and lack of a shared picture of the situation among bridge team members.
Regulatory Reference
BRM is not codified in a single specific rule, but is promoted through STCW Code Section A-II/1 (bridge resource management/bridge teamwork in training programmes) and extensively developed by industry bodies such as the Nautical Institute, which places the human element at its core.
Scope of Application
Every navigational situation involving more than one person on the bridge (practically always, except in exceptional operating conditions), with particular relevance during critical phases (port manoeuvres, heavy traffic, restricted visibility).
Procedure / How to Complete It
- Assign clear tasks to every bridge team member at the start of each critical phase of navigation (manoeuvre, port entry, heavy-traffic area).
- Communicate every relevant piece of information (position, traffic, intentions) explicitly and verifiably, never assuming it has been understood.
- Explicitly encourage challenge by every team member, regardless of rank, whenever something does not match expectations.
- Periodically verify that all team members share the same mental model of the situation (position, traffic, plan under way).
- Conduct a debrief after every critical phase, to identify any communication or coordination gaps that need correcting.
Diagram: the 4 most frequent BRM weaknesses found in investigations
Practical Example
Example of good practice: during a port-entry manoeuvre, the helmsman verbally reports every course alteration carried out, the officer of the watch confirms receipt, and a third team member independently monitors the position via ECDIS, openly challenging any deviation perceived from the plan.
Real Cases
Common Mistakes Mistake Library
| Mistake | Consequence | How to avoid it |
|---|---|---|
| Tasks not explicitly assigned during critical phases, with overlaps or gaps in responsibility | No one monitors a critical aspect, assuming someone else is handling it | Always assign explicit, verifiable tasks at the start of every critical phase |
| Hierarchical culture that discourages challenge from more junior or lower-ranking team members | Errors evident to a team member go unreported out of deference | Explicitly promote a culture that encourages challenge regardless of rank |
| No verification that the whole team shares the same mental model of the situation | Decisions made on the basis of different information among team members | Periodically verify, out loud, that the shared understanding of the situation is genuinely aligned |
PSC Observations
Operational Tips
- Treat BRM as a daily practice, not as a one-off course to complete and forget.
- Explicitly promote a culture of challenge and response, especially towards more junior team members.
- Use the debrief after every critical manoeuvre to identify communication gaps, not just to confirm the success of the operation.
Checklist
- Tasks explicitly assigned for every critical phase
- Communication verified, not assumed
- Culture of challenge and response actively promoted
- Shared mental model periodically verified
- Debrief conducted after every critical phase of navigation