Overview
The estimate should therefore connect named milestones with current information sources. A single transit duration is insufficient when the buyer's real concern is whether the parcel arrives in time for a receiving or resale commitment.
Key takeaways
- Define the start and finish of the duration being discussed.
- Track loading readiness independently from vessel readiness.
- Show how receiving changes affect the delivery sequence.
- Use qualitative scenarios when numerical evidence is unavailable.
Ask which clock the business is using
A chartering desk may discuss time from departure to arrival, while a cargo planner thinks in terms of nomination to usable inventory. Both measures can be legitimate, but they are not interchangeable. Identify the clock before supplying an estimate.
For a regional Aframax delivery, define whether the endpoint is arrival near the destination, berthing, discharge completion, or availability under the receiver's arrangements. The receiver should confirm which event supports its planning decision. Do not infer that event from a familiar port name.
The starting point also matters. If the parcel is not yet ready, a duration from expected departure leaves out the uncertainty most relevant to the buyer. Show the loading assumption explicitly and connect it to the seller's current confirmation.
Once the voyage progresses, substitute actual events for forecasts where appropriate. Keep the earlier versions that supported decisions so the team can see whether changes came from cargo supply, passage information, or the receiving programme.
Build a short chain of dependencies
A useful regional schedule can be simple: cargo readiness, vessel readiness, expected departure, destination arrival, receiving readiness, and cargo completion. The important feature is the relationship between events and their information owners.
Ask the owner for the relevant passage outlook and the terminal or agent channel for current port information. Keep those inputs distinct. A confident passage estimate should not make an unconfirmed berth programme appear equally reliable.
The IMO's Just In Time work connects ship arrival planning with the availability of port services. The commercial lesson is to coordinate milestone information rather than assume arrival alone determines the rest of the call. See the IMO ship-port interface portal.
Where a cargo has alternative receivers, add a branch to the schedule rather than blending both into one date. Each receiver may have a different confirmation process. The cargo desk should see which branch is being used in the current forecast and what decision would switch it.
Use an itinerary sensitivity table
An illustrative qualitative sensitivity table shows how changes propagate without inventing port waiting statistics or vessel performance. Tailor the entries to the actual programme and retain the responsible source for each assumption.
| Programme event | Current planning basis | Alternative condition | Commercial effect |
|---|---|---|---|
| Seller readiness | Parcel allocated for intended window | Allocation remains provisional | Departure cannot be treated as firm |
| Vessel readiness | Owner indicates suitable timing | Previous employment changes | Loading coordination needs review |
| Regional passage | Owner supplies current outlook | Updated passage information arrives | Receiver notification may change |
| Primary receipt | Terminal programme appears workable | Receiver requests another slot | Arrival may precede useful delivery |
| Alternate receipt | Option under evaluation | Alternative buyer confirms | Destination branch must be revised |
| Cargo completion | Receiver identifies relevant milestone | Planning team uses another event | Internal schedule needs reconciliation |
The table is a decision aid rather than a prediction. Its purpose is to show which new information could change an action, such as confirming a resale, arranging storage, or seeking another supply source.
Avoid giving every uncertainty the same generic buffer. A supply delay and a receiving delay may interact differently depending on the programme. Describe the dependency first; only quantify it when reliable voyage-specific inputs and an appropriate calculation basis are available.
Link updates to the receiver's next decision
Ask the cargo desk what it will do differently if the delivery range changes. A schedule that informs no decision may be reporting for its own sake. The answer might involve a sales nomination, an intake programme, or a contingency purchase.
Set a review point before that decision becomes urgent. Identify the information expected by then and the person who will obtain it. If the evidence is still incomplete, the team can make an explicit conditional decision rather than discovering the gap at the last moment.
An update should identify the changed assumption and the affected milestone. For example, a later receiving slot changes the cargo completion outlook even if the ship's expected arrival is unchanged. Sending only a new completion date obscures the cause and can lead colleagues to question the wrong party.
Where internal teams use different systems, agree a short set of milestone definitions. The value comes from consistency across chartering, cargo planning, and the receiver, not from creating an elaborate schedule that nobody maintains.
Fictional case: a short passage with a longer commercial timeline
A fictional regional trader buys a crude parcel for an Aframax delivery to a nearby refinery. Its sales team assumes that the short geographical movement means the cargo can support an immediate resale commitment.
The chartering coordinator separates the itinerary into loading readiness, passage, and receiving stages. The seller's allocation is still conditional, and the refinery has requested confirmation of its intake programme. Neither uncertainty is reflected in the passage estimate the sales team has been using.
The trader delays making an unconditional resale promise until the relevant confirmations arrive. It also evaluates an alternative receiver using a separate schedule branch rather than simply adding a destination name to the existing forecast.
When the seller confirms supply, the departure assumption improves, but the receiving uncertainty remains visible. The team can now explain the delivery range accurately and avoid confusing geographical proximity with certainty about cargo availability.
Review the schedule without prescribing operations
Commercial staff should communicate the required outcome and ask qualified parties for current information. They should not create vessel speed instructions, cargo-handling assumptions, or technical shortcuts to make the spreadsheet meet a sales deadline.
If the forecast no longer fits the commercial commitment, escalate the mismatch. Possible commercial responses include revisiting the sales timing, seeking receiving flexibility, or evaluating an alternative programme. Each requires its own authority and confirmation.
At voyage close, compare the forecast chain with the actual sequence. Identify whether the team misunderstood a milestone, received information late, or faced a genuine change. Improving the process depends on distinguishing these causes.
Preserve the lessons in the next enquiry template. For example, if supply allocation controlled the timeline, ask for clearer readiness status earlier. If receiver terminology caused confusion, make the required endpoint explicit in future schedule requests.
Common mistakes
Treating regional sailing time as total delivery time omits cargo and port dependencies. Another mistake is updating the arrival field while leaving the receiving assumption unchanged and undated.
Avoid presenting a broad range without explaining what would narrow it. Decision makers need to know which confirmation matters and when it is expected.
Do not assume that an alternative receiver uses the same schedule. A different destination can require a new branch of the commercial plan, even when it appears geographically close.
Where Zeaclub fits
Zeaclub supports agentic, AI-assisted operations with a human in control.
Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.
Explore Zeaclub
Educational information only; not legal, financial or trading advice. Contract wording and applicable rules control. Verify current requirements and obtain qualified advice before acting.
Frequently asked questions
Why can a regional Aframax voyage remain difficult to schedule?
The passage is only part of the commercial timeline. Cargo allocation, vessel readiness, terminal programmes, and receiver decisions can remain unresolved and affect when the parcel becomes available.
Should the estimate include loading time?
Include it when the decision requires a timeline beginning before departure. If the estimate covers passage only, label that boundary clearly so the cargo desk does not interpret it as total delivery duration.
Who should confirm cargo availability at destination?
The receiver should identify the milestone relevant to its own arrangements. The owner and terminal provide their respective information, while the commercial coordinator aligns those inputs with the buyer's planning requirement.
How often should the itinerary change?
Update it when reliable new information changes a relevant assumption or milestone. Keep a routine review rhythm, but do not delay communicating a material change that affects an imminent commercial decision.