Port Agent Shift Handover: SOP and Template

Most vessel agents have handled more shift handovers than they can count.

Some are simple. Others happen while the berth plan is changing, the pilot window is still loose, vendors are waiting on confirmation, and the principal wants a clean update.

That is when handover gets risky.

The incoming agent needs the current truth fast: what changed, what is open, who has been updated, what still needs approval, and what proof is missing for the FDA.

If that context lives across email, chat, verbal notes, and spreadsheets, the next shift starts with gaps.

A port operations handover template gives the team a better structure. The stronger fix is making sure that handover lives with the port-call record itself.

This guide gives you a practical port agent shift handover SOP, a printable template, and a clearer way to think about handover: the document helps, but the live system prevents the gap.

How Port Agent Shift Handovers Are Usually Handled

Most port agency teams have a handover process, even if nobody calls it an SOP.

The outgoing agent sends a shift email, gives a quick verbal rundown, updates the spreadsheet, drops a few notes in chat, and trusts the next person to piece the rest together.

That can work on a quiet call.

It gets shaky when the vessel is nearing berth, the pilot time is still loose, the terminal wants a revised file, and the principal expects the next update before business hours start on their side of the world.

One active call can already stretch the handover. Several active calls across different ports, terminals, vendors, principals, and time zones leave more room for a missed update to turn into a real problem.

Here is where the usual handover methods start to break down.

Email Threads Hide the Current Truth

Email carries much of the work: nominations, principal instructions, vendor quotes, terminal requirements, documents, invoices, and approvals.

It also buries the latest answer.

The current ETA may be in one thread. The pilot request may be in another. The terminal’s document comments may sit under a separate subject line. The principal’s approval for an extra cost may be buried six replies deep.

The incoming agent has to search, compare, and decide what is still current.

That is a bad place to start a shift.

Verbal Handovers Leave Too Much Open

A verbal handover helps when both agents are at the desk and the outgoing agent can talk through the call.

It should not carry the record.

“Pilot is requested” does not tell the next agent whether the time is confirmed, tentative, waiting on berth confirmation, or still sitting with port control.

“Documents are handled” does not say which file was submitted, which one is waiting on the master, and which one the terminal rejected.

Verbal handovers usually pass the story. The next shift needs the status.

Chat Messages Split the Record

Chat is useful because it is fast.

A launch provider confirms timing in WhatsApp. A teammate flags a document issue in Teams. Someone notes a berth change without starting a new email thread.

That works in the moment.

The problem comes later, when that message becomes the only place the update exists. The next agent may not see it. Finance may not know it exists. The person preparing the FDA may not find the approval, receipt, or explanation when they need it.

Chat can help the port call coordination. It should not become the handover file.

Spreadsheets Can Look Current While Missing Context

Spreadsheets are easy to use, which is why so many teams rely on them. In fact, some industry estimates place spreadsheet reliance among independent port agencies as high as 70% to 90%, though there is no exact public census.

They can show vessel status, vendor status, documents, tasks, and notes. They do not always show the source behind the update.

A cell may show the latest ETA without showing who provided it, when it changed, which vendors were notified, or whether the principal received the update.

A field may say “pilot requested” without showing whether that means confirmed, pending, or waiting on another event.

The sheet may look updated. The next agent may still be missing the context needed to act.

Shift Notes Become One More Place to Check

A dedicated handover note is better than memory.

The issue is what happens when the note sits apart from the actual job record.

It may say “extra launch approved,” while the approval sits in email. It may say “cargo plan rejected,” while the rejected file sits in a folder. It may say “vendor invoice pending,” while the quote and PO live somewhere else.

Now the incoming agent has a handover note and still has to rebuild the call.

That is the handover gap.

Port Agent Shift Handover SOP

There is a better way to handle shift handover.

Treat it as an operating checkpoint. The job is not to recap the last shift. The job is to transfer control of the vessel call with enough context for the next agent to act.

The incoming agent should not have to rebuild the call from email, chat, verbal updates, and spreadsheets.

Use this SOP during:

• Pre-arrival
• Alongside operations
• Cargo work
• Crew changes
• Husbandry services
• Departure
• PDA or FDA closeout

Step 1: Start From the Active Job Record

Start with the active job, port call, project, or vessel record. This gives both agents the same starting point before reviewing details.

Confirm:

• Vessel name
• IMO number
• Voyage or internal reference
• Port
• Terminal
• Berth or anchorage
• Principal, owner, charterer, or operator
• Current job owner
• Incoming shift owner
• Current job status
• Local port time and time zone

The incoming agent should never start a shift unsure which vessel, berth, principal, or record owns the handover.

Step 2: Confirm the Current Operating Picture

Give the incoming agent the current call status before going into open tasks.

Record:

• ETA
• ETB
• ETC
• ETD
• NOR status
• Pilot status
• Tug status
• Lines status
• Cargo status
• Berth status
• Departure clearance status

Use clear status labels:

• Confirmed
• Expected
• Pending
• At risk
• Rejected
• Waiting on vendor
• Waiting on port
• Waiting on principal

This keeps assumptions from being treated like confirmed facts.

Step 3: Show What Changed During the Last Shift

The incoming agent needs to know the current status and what moved since the last handover.

Capture changes to:

• ETA
• Berth
• Pilot window
• Tug timing
• Terminal instructions
• Cargo plan
• Crew change plan
• Vendor status
• Document status
• Principal instructions
• Cost approvals

For each change, include:

• Source of the update
• Time received
• Who was notified
• Who still needs to be notified
• Impact on timing, cost, documents, or client communication

This is one of the most important parts of the handover. Change history tells the next agent what has already been handled and what still needs action.

Step 4: List Open Actions in Priority Order

Open actions should be written as tasks the incoming agent can execute.

Each action should include:

• Task
• Owner
• Due time
• Dependency
• Current status
• Risk if missed
• Escalation point

Use priority labels:

• Due now
• Due this shift
• Watch item

The goal is to make the next move obvious.

Step 5: Review Vendor and Service Status

Vendor handover should cover every active service tied to the vessel call.

Review:

• Pilot
• Tugs
• Lines
• Launch
• Freshwater
• Sludge
• Bunkers
• Transport
• Hotel
• Medical
• Surveyor
• Security
• Terminal labor
• Immigration support
• Customs support

For each vendor or service, record whether it is:

• Requested
• Quoted
• Approved
• PO issued
• Confirmed
• On site
• Completed
• Invoice received
• Payment pending

If the vessel timeline changed, the handover should show whether each affected vendor has been updated.

Step 6: Review Documents by Name and Status

Avoid broad notes like “docs pending.” Name the document and the exact status.

For each active document, record:

• Document name
• Current version
• Status
• Submitted to
• Submission time
• Accepted, pending, or rejected
• Issue, if any
• Owner
• Deadline
• Next action

This can include:

• Pre-arrival forms
• Crew lists
• Cargo documents
• Certificates
• SOF drafts
• NOR
• Port clearance
• Customs paperwork
• Immigration documents
• Waste declarations
• Bunker notes
• Receipts
• Vendor invoices
• POs
• PDA backup
• FDA backup

The next agent should not have to guess which document is missing or which version was sent.

Step 7: Confirm Principal Communication

The incoming agent should know what the principal has already been told before sending another update.

Record:

• Last update sent
• Time sent
• Recipient
• Main points included
• Open questions from the principal
• Next update due
• Sensitive issues
• Escalation notes

This protects the team from stale updates, mixed messages, and duplicate questions.

Step 8: Capture Costs, Approvals, and Backup

Review all cost items created or changed during the shift.

Record:

• New quotes
• Approved extras
• Unapproved costs
• POs issued
• Vendor invoices received
• Receipts received
• Missing backup
• Currency notes
• Tax or surcharge notes
• Expected PDA variance
• Expected FDA variance
• Approval source
• Approval time

If an extra service was approved, the handover should show where that approval lives and what still needs to be attached.

Step 9: Record Risks and Escalation Triggers

Each shift should leave the next agent with a clear risk picture.

Common risk categories include:

• Pilot delay
• Berth congestion
• Weather hold
• Terminal document issue
• Cargo readiness issue
• Crew document issue
• Vendor availability issue
• Customs hold
• Immigration hold
• Missing receipt
• PDA variance
• Principal approval delay
• Vendor payment escalation

Each risk should include:

• Current status
• Impact
• Owner
• Next action
• Escalation trigger

A useful risk note tells the next agent when to act.

Step 10: Close With Readback

Before the outgoing agent leaves, the incoming agent should repeat the critical items back.

Readback should cover:

• Current vessel status
• Next three actions
• Top operational risk
• Top document risk
• Top cost or approval issue
• Next principal update

This is the final check. It catches gaps before the outgoing agent is unavailable.

Printable Port Operations Handover Template

Use this as a shift-change worksheet for active port calls, multi-port operations, husbandry services, crew changes, cargo operations, departure, and FDA closeout.

When a Handover Template Is Not Enough

A port operations handover template gives teams a better format. It tells agents what to capture and gives every shift the same structure.

That is useful.

It still does not solve the full problem if the template becomes another disconnected document.

A template does not automatically update the ETA. It does not attach the vendor quote. It does not preserve the approval. It does not tell finance which receipt is missing. It does not show the principal’s last update. It does not build the SOF from live events.

The template improves the handover conversation.

The system behind the template determines whether the record holds.

This is why the handover needs to live with the port-call timeline, vendor activity, documents, approvals, and cost trail.

The real takeaway is simple: a document can support the handover, but the live job record should carry it.

How Base Removes the Handover Gap

Base gives port agents one live record for every vessel call.

The timeline, vendor activity, documents, approvals, costs, and client communication stay tied to the same job. The incoming agent can open the call and see the current operating picture without rebuilding it from inbox threads, verbal notes, chat messages, and spreadsheets.

For agencies evaluating port agency software, this is one of the clearest operational wins: every shift works from the same job truth.

The Live Timeline Replaces Stale Shift Notes

A static handover note can go stale as soon as the vessel status changes.

Base’s live timeline gives the team a place to capture updates as they happen. ETA changes, berth updates, event notes, document activity, comments, and follow-ups can stay connected to the job.

That helps the incoming agent answer the questions that matter:

• What changed?
• When did it change?
• Who updated it?
• Who was notified?
• What needs action next?

Instead of depending on a handover email written an hour ago, the next shift can work from the live call record.

Vendor Status Stays Connected to Requests, Quotes, POs, and Invoices

Vendor handover fails when service status and cost status are separated.

A tug request may be confirmed operationally, but the PO may still be pending. A launch trip may be completed, but the invoice may not be received. A surveyor may have been approved, but the principal approval may still need to be attached for FDA backup.

Base keeps vendor activity connected to the job. Requests, quotes, approvals, POs, invoices, and related files can stay in the same record.

That helps the incoming agent see both the service status and the money trail.

Documents Stay With the Vessel Call

Document status is one of the easiest handover areas to misread.

A file may be received, but not reviewed. Submitted, but not accepted. Rejected, but not corrected. Corrected, but not sent to the right contact.

Base keeps documents tied to the job, so the next shift can see what exists, what changed, and what still needs action.

This matters during the call and after departure. The same record can support SOF accuracy, PDA review, FDA backup, and principal questions.

Principal Updates Stay Consistent Across Shifts

Principals notice when agency updates drift between shifts.

If one agent says the vessel is waiting on pilot confirmation and another sends an outdated “awaiting ETA update” message, the principal starts questioning the process.

Base helps teams keep the last update and current activity tied to the same job record. The incoming agent can see what the principal has already been told before sending the next update.

That protects trust because the agency speaks from one record.

Cost Approvals Stay Ready for PDA and FDA Review

Port-call costs move fast.

Extra launch trips, standby charges, revised vendor quotes, surveyor changes, transport adjustments, and terminal charges can all appear during a shift.

If approval and backup do not stay connected to the job, finance has to chase the proof later.

Base helps keep cost notes, approvals, vendor invoices, receipts, POs, and backup tied to the call. That gives finance a stronger record for PDA-to-FDA review and invoice preparation.

The handover becomes part of the billing trail, not a separate ops note that finance has to interpret later.

The SOF Is Built From the Work, Not Rebuilt Afterward

A Statement of Facts is only as good as the event record behind it.

When each shift captures events, changes, exceptions, and timestamps in the live job timeline, the SOF becomes easier to prepare and defend.

The team does not have to reconstruct the call from memory after departure. The operating record already contains the sequence.

That is especially important when a delay, dispute, claim, or principal review depends on timing.

Base Turns Handover Into Operational Memory

Experienced agents carry valuable knowledge about ports, terminals, vendors, principals, and recurring issues.

The problem is that memory does not scale across shifts, offices, or turnover.

Base helps agencies preserve that knowledge inside the job record. Exceptions, vendor behavior, document issues, timing problems, and cost notes become visible across the operation.

Over time, the team is not only handing over the current shift. It is building a better record for the next call.

Conclusion on Port Agent Shift Handover

A port agent shift handover is supposed to make the next shift ready. Too often, it leaves the next agent piecing the call together from email threads, chat messages, verbal notes, spreadsheets, and document folders.

That is where the handover gap opens.

A missed ETA update, unclear vendor status, pending document, hidden approval, or missing receipt can follow the team through the rest of the call. It can slow the operation, frustrate the principal, weaken FDA backup, and make the final record harder to defend.

A template gives the team structure. It makes the right questions easier to ask at every shift change.

Base gives the handover a stronger home.

With one live timeline for updates, vendors, documents, approvals, costs, and client communication, every shift can take over from the same record. The next agent sees what changed, what is open, what is at risk, and what still needs proof.

If your team is still handing off port calls through scattered notes and inbox searches, contact us today to see how a live job record can make every shift handover cleaner, faster, and easier to trust.

Key Takeaways

• Port agent shift handovers often fail because the current call record is split across email, chat, verbal updates, spreadsheets, and shift notes.
• A missed handover detail can create operational delays, vendor confusion, stale principal updates, weak FDA backup, and a harder-to-defend final record.
• A strong handover should capture vessel status, recent changes, open actions, vendor status, document status, principal communication, cost approvals, risks, and readback.
• A port operations handover template helps teams ask the right questions at every shift change.
• A template alone is not enough if it becomes another disconnected document. The strongest handovers live inside the active port-call record, tied to the vessel timeline, vendors, documents, approvals, costs, and client communication.
• Base helps remove the handover gap by giving each vessel call one live job record that every shift can work from.

Frequently Asked Questions