Blog/Maritime & Shipping

Port Call Coordination: One Source of Truth for Every Party

Give owners, agents and terminals one shared, live view of each port call, so nobody works from an outdated email or ETA.

By Sagar Makker · 4 min read · October 2026
In short
Port calls go wrong when each party works from a different email, spreadsheet or ETA.
Keep one live record per call: ETA, berth status, services ordered, tasks and owners.
Push changes to everyone at once and log every update so nobody argues about who knew what.
The problem

The vessel's ETA moves by twelve hours. The master emails the owner, the owner forwards to the agent, the agent calls the terminal. Pilotage, towage and bunkers are still booked for the old time. The crew change flight does not move. By the time everyone catches up, the berth window has gone and the ship waits at anchor.

Every port call involves many parties: owner, operator, charterer, agent, terminal, pilots, chandlers and authorities. Each keeps its own version of the plan. Long email chains with changing subject lines become the record. When something goes wrong, nobody can easily show who was told what, and when.

Why it happens
01ETA and berth updates passed along by forwarded email instead of shared directly
02Each party tracks services, tasks and documents in its own spreadsheet
03No single owner for each task, so items fall between owner and agent
04No timestamped log of changes, so delays turn into blame instead of fixes
How to fix it
1
Create one record per call
Open a shared port call record as soon as the vessel is nominated: ETA, berth, cargo, agent, services needed and key contacts. Every party reads from this one place.
2
Assign every task an owner
List pilotage, towage, bunkers, provisions, crew change, waste and clearances with one named owner and due time each. Unowned tasks are where port calls usually slip.
3
Broadcast changes once
When the ETA or berth changes, update the record and notify all affected parties together. Show which services depend on the change so they get rebooked quickly.
4
Keep a timestamped event log
Record every update, confirmation and delay reason with time and source. Use it for SOFs, demurrage discussions and reviewing what to improve next call.
Where an AI agent helps
Input
Master's ETA updates, AIS positions, agent emails, terminal berth schedules
Agent does
Updates the shared call record, flags affected services, drafts notices to each party
Human gate
Operator or agent confirms ETA changes and service rebookings before they are sent
Outcome
One live port call view and a complete, timestamped event log
What to measure
Hours waiting at anchorage per callServices rebooked late after ETA changesOpen tasks without an ownerEmails per port call
Questions
Who should own the port call record?

Usually the operator or the port agent, depending on how your organisation splits roles. What matters is that one party maintains it, every other party can view it, and updates are not sent around it by private email.

Do we need terminals to adopt a new system?

Not necessarily. Terminals and service providers can receive updates by email or a shared link, while your team keeps the master record. Start with your own operators and agents, then widen access as others find it useful.

How does this help with demurrage and disputes?

A timestamped log of ETAs, NOR, berth instructions and delays gives you evidence to support or check statements of facts. It is much easier to agree times when everyone saw the same updates as they happened.

Keep reading
All posts →
Maritime & Shipping
Settle Laytime and Demurrage Claims Faster With Fewer Disputes
5 min readRead →
Maritime & Shipping
Never Miss a Crew Certificate Expiry Again: A Practical System
4 min readRead →
Maritime & Shipping
Extracting Key Clauses From Charter Parties in Minutes
5 min readRead →

Want this fixed in your business?

Send the workflow. We reply with a scope and a fixed price in two working days.
Send a brief →