Pilot Boarding and Bridge Team Management Checklist
Use this pilot boarding and bridge team management checklist to confirm the pilot card exchange, agree the passage plan, verify UKC, and assign bridge roles before entering pilotage waters.
Trusted by frontline teams 15 years of frontline software
Built for: Maritime Shipping · Port Operations · Offshore Support · Tanker Operations
Overview
This Pilot Boarding and Bridge Team Management Checklist template is a pre-pilotage task checklist for confirming the essentials before a pilot takes control of navigation in pilotage waters. It is built around the handoff points that matter most: pilot card exchange, passage plan agreement, under-keel clearance confirmation, bridge team role assignment, communication channels, and any local restrictions that could affect the approach.
Use this template when the vessel is approaching a pilot station, harbor entrance, river transit, or any area where local knowledge and coordinated bridge execution are required. It helps the master, officer of the watch, and pilot verify the same plan and identify blocking issues before the vessel is committed to the maneuver. The checklist is also useful when the bridge team needs a clear record of who is monitoring, who is communicating, and who is handling helm or engine orders.
Do not use this as a generic arrival form or as a substitute for the vessel’s passage plan, pilotage instructions, or company SMS procedures. It is not meant for post-incident review or for routine open-sea navigation. If your operation requires tug coordination, berth-specific restrictions, or local reporting steps, those should be added as custom checklist items so the template matches the actual pilotage workflow.
Standards & compliance context
- This template supports bridge resource management expectations by making role assignment and communication checks explicit before a high-risk maneuver.
- It aligns with common pilotage and port entry procedures that require confirmation of passage plan, vessel particulars, and local navigation constraints.
- It can help demonstrate due diligence under company SMS and ISM-style operational controls by documenting pre-arrival verification steps.
- If your port, flag, or coastal authority requires additional pilotage checks, those items should be added to the template to reflect local compliance obligations.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Create the checklist before arrival and add any port-specific items such as tug coordination, local reporting, or berth approach requirements.
- Assign the DRI to the master, officer of the watch, or another designated bridge lead so one person owns completion and escalation.
- Run the checklist with the pilot present or immediately before boarding, and verify each checklist item with a clear yes, no, or N/A response.
- Pause the workflow if a blocking issue appears, such as an unresolved passage plan mismatch or insufficient UKC, and document the corrective action.
- Close the checklist only after bridge roles, communications, and navigation assumptions are confirmed and the team is ready to enter pilotage waters.
Best practices
- Keep each checklist item atomic so one answer confirms one condition, such as passage plan agreement or UKC verification.
- Mark any unresolved navigation discrepancy as blocking until the pilot and bridge team agree on the corrective action.
- Assign explicit bridge roles before pilotage begins so helm, engine, lookout, and communications responsibilities are not assumed.
- Verify the pilot card exchange against the vessel’s current particulars, draft, maneuvering limits, and local requirements.
- Use the checklist as a live verification step, not a paperwork exercise completed after the pilot has already taken control.
- Add port-specific items for tugs, VHF channels, tidal windows, or berth constraints instead of relying on memory.
- Record any N/A item with a short reason so the audit trail explains why a step did not apply.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this checklist cover?
This template covers the pre-pilotage handoff and bridge coordination steps that should be completed before the vessel enters pilotage waters. It focuses on pilot card exchange, passage plan agreement, under-keel clearance confirmation, bridge team role assignment, and communication readiness. It is meant to produce a clear yes/no record that the bridge team and pilot are aligned before maneuvering begins.
When should this checklist be used?
Use it during the pre-arrival or pre-boarding window, before the pilot starts directing navigation in confined or regulated waters. It is especially useful when the vessel is approaching a pilot station, harbor entrance, river transit, or other high-consequence area. It should be completed early enough that any disagreement can be resolved before the ship is committed to the passage.
Who should run this checklist?
The master or officer of the watch typically leads the checklist with the pilot and relevant bridge team members. The DRI should be the person responsible for ensuring the checklist is completed and any blocking issues are escalated. The exact assignment can vary by company procedure, but the key is that one person owns completion and follow-up.
Is this checklist suitable for all vessels and ports?
It is suitable as a starting point for most pilotage operations, but it should be customized to the vessel type, local port requirements, and company bridge procedures. Some ports require additional items such as tug coordination, VHF channel confirmation, berth approach notes, or local reporting steps. Treat this template as a reusable base, not a substitute for local pilotage instructions.
What are the most common mistakes this template helps prevent?
Common failures include assuming the pilot has the same passage plan as the bridge team, not confirming the minimum UKC, and leaving bridge roles ambiguous during a critical phase. Another frequent issue is treating the checklist as a formality instead of a verification step with real discussion. This template helps surface those gaps before they become blocking navigation problems.
How often should this checklist recur?
This is a recurring operational checklist that should be used for each pilotage event, not on a weekly or monthly schedule. The recurrence is event-based: every time a pilot boards or the vessel enters pilotage waters. If your workflow system supports recurrence_config, set it to the specific operational trigger rather than a calendar cadence.
Can this checklist be integrated with other bridge or port workflows?
Yes, it pairs well with arrival planning, passage planning, berth readiness, tug coordination, and pre-arrival communication workflows. It can also link to incident reporting if a blocking issue is found, such as an unresolved UKC concern or a mismatch in passage plan assumptions. Many teams use it alongside a broader bridge resource management or port call checklist set.
How is this different from an ad-hoc pilot briefing?
An ad-hoc briefing depends on memory and verbal coordination, which makes it easy to miss a critical item under time pressure. This template turns the briefing into a repeatable checklist item sequence with clear verification steps and ownership. The result is a more reliable handoff and a better record of what was confirmed before entering pilotage waters.
Related templates
Ready to use this template?
Get started with MangoApps and use Pilot Boarding and Bridge Team Management Checklist with your team — pricing built for small business.
