Aerial view of a tanker's bow underway

Overview

The best estimate explains those dependencies explicitly. It gives the trading desk a basis for deciding when it can commit to a sale, arrange receipt, or activate an alternative delivery plan.

Key takeaways

  • Define whether the forecast ends at arrival, discharge, or another receipt event.
  • Track product readiness and document readiness separately.
  • Show optional destinations as different itinerary branches.
  • Update the decision consequences when an assumption changes.

Identify the product commitment behind the forecast

Start with the transaction the schedule must support. A trader supplying a refinery, a distribution terminal, or another buyer may face different commercial deadlines. Ask the cargo desk which event satisfies its planning requirement rather than assuming that vessel arrival is sufficient.

Write the endpoint in ordinary language. If the internal planner needs product available for onward distribution, establish who confirms that event and whether it occurs after the maritime milestones. The chartering team should not create a receipt commitment on behalf of the terminal or buyer.

At the loading end, identify whether the product is allocated, whether the relevant specification is settled, and whether the planned loading arrangement is confirmed. These are separate inputs. A firm purchase does not necessarily mean every practical dependency for the intended departure has been resolved.

Keep the start point consistent. A duration beginning at departure excludes pre-departure uncertainty. If management needs a timeline from the decision to ship, include the earlier commercial dependencies or clearly state that they remain outside the estimate.

Separate passage from the product programme

Obtain the passage outlook from the owner or authorised operational channel. Record its date, geographical boundaries, and any conditions the owner identifies. Commercial staff should ask for clarification where needed rather than invent vessel performance assumptions.

The product programme should have its own source. The seller confirms cargo readiness, the terminal channel supplies relevant receiving or loading information, and the documentation team identifies outstanding records. Combining these inputs creates the schedule, but does not make one party responsible for every underlying assumption.

IMO's Just In Time Arrival work connects vessel arrival planning with service readiness. The useful commercial distinction is between reaching a place and having the receiving arrangements ready. See the IMO arrival guidance announcement.

For products intended for more than one receiver, preserve separate completion milestones. A single final voyage date may hide the earlier buyer's commitment and make the later buyer's exposure difficult to see. Each delivery should remain traceable to the relevant parcel and recipient.

Use a product-specific itinerary sensitivity

An illustrative qualitative itinerary is often more useful than unsupported numerical precision. List the assumptions capable of changing the delivery outcome and show the decision affected by each variation.

AssumptionCurrent planning positionAlternative conditionDecision affected
Product allocationSeller identifies nominated parcelAllocation remains conditionalWhether the desk can commit supply
Specification referenceAgreed document availableReceiver clarification outstandingReadiness of commercial review
DepartureOwner and loading information alignOne input changesDestination planning notice
PassageCurrent owner estimateRevised voyage outlookExpected arrival range
First receiverIntended programme acknowledgedReceipt moves to another windowInitial delivery commitment
Optional receiverDecision pendingOption exercised or withdrawnRemaining itinerary branch
Final availabilityBuyer defines relevant eventInternal teams use different endpointsOnward distribution planning

The matrix should not suggest that every uncertainty necessarily delays the voyage. Some items can be resolved in parallel, while others become critical only if a particular option is exercised. Explain the relationship rather than stacking a generic allowance against every row.

Name the person who can close each information gap. A forecast with several unresolved fields can still support a decision if the desk knows which gaps matter most and when they are likely to be resolved.

Connect the range to sales decisions

Ask the trader what decision the next schedule update will support. If the answer is a delivery promise to a buyer, the forecast should identify the evidence supporting that promise and the remaining conditions. If the answer is choosing a destination, compare the relevant itinerary branches.

Distinguish internal decision deadlines from external nomination limits. The desk may need time to obtain receiver confirmation and commercial authority before communicating a final choice. Planning only around the last external deadline can leave those internal steps unaccounted for.

When uncertainty is material, describe a base plan and a conditional alternative. Avoid assigning invented probabilities. A statement that a later receipt depends on a named unresolved confirmation can be more informative than a numerical confidence estimate with no evidence behind it.

Keep the impact of a change specific. An updated passage estimate might affect the receiving notice but leave the buyer's distribution plan intact. A documentation issue might affect the commercial release process without changing the ship's location. The schedule should help colleagues distinguish those consequences.

Fictional case: an arrival date becomes a distribution promise

A fictional products trader arranges an LR2 shipment for a distribution customer. The sales team uses the expected destination arrival as the date when the customer can begin its onward deliveries. The terminal programme and the customer's document review are still being finalised.

The chartering coordinator asks the customer to identify its actual availability milestone. The team then separates vessel arrival, intended receipt, cargo completion, and the customer's own release decision. It also records which party supplies each confirmation.

The passage estimate remains unchanged, but the sales promise is revised to reflect the correct endpoint. The trader now monitors the receiving and document decisions that could affect distribution rather than repeatedly asking the owner for a more precise arrival date.

The improvement is conceptual as much as procedural. A correct maritime estimate becomes useful only when it is connected to the commercial event the customer needs.

Maintain an assumption history through the voyage

Retain previous forecast versions when they support material decisions. Each revision should identify the changed input, its source, and the affected milestone. This creates a useful record without requiring an elaborate reporting system.

Replace estimates with actual events as reliable reports arrive. Do not let a confirmed departure make unrelated destination assumptions appear confirmed. The status of each milestone should remain visible independently.

At handover between colleagues, explain the forecast's main unresolved dependency. A replacement coordinator should know whether the key issue is seller readiness, an optional receiver, a terminal programme, or another specific decision. A list of dates without that context can be misleading.

After completion, review where the forecast became more or less reliable. The purpose is to improve the next enquiry and receiving dialogue. Distinguish a missing question from genuinely unavailable information so the team learns the right lesson.

Common mistakes

Using one date for arrival and product availability can create commitments that the maritime schedule never supported. Another mistake is treating document readiness as automatically complete because the product has loaded.

Avoid blending alternative destinations into one average itinerary. The buyer needs to understand the consequence of each actual choice, not a route that nobody intends to execute.

Do not prescribe speed or cargo-handling measures to make the schedule fit a sales promise. Escalate the commercial mismatch and seek current information from the responsible professionals.

Where Zeaclub fits

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Zeaclub offers digitalised procedures across the voyage workflow.

Explore Zeaclub

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

Which endpoint should an LR2 duration estimate use?

Use the endpoint required by the commercial decision and name it explicitly. Arrival, discharge completion, and availability for onward distribution can represent different events with different responsible sources.

Can documentation affect the commercial timeline?

It can affect decisions made by the cargo parties or receiver. Identify the actual process and owner of the decision rather than assuming that every missing document has the same consequence.

How should multiple receivers appear in the itinerary?

Give each delivery a distinct milestone and identify the dependencies between them. This lets the team see whether a change affects one buyer, the remaining programme, or both.

When is a qualitative range sufficient?

It is useful when it clearly states the underlying conditions and supports a decision. Add numerical detail only when reliable inputs and a consistent calculation basis make that detail meaningful.

Primary sources