LPG Voyage Duration: Bridge Arrival and Sales Decisions

Overview

The sales team may need a planning date before the receiving arrangement is fully confirmed. The chartering desk may hold a voyage estimate whose conditions are still evolving. The coordinator's job is to connect those pieces honestly, showing which assumptions support each decision and when they need to be refreshed.

Key takeaways

• Identify the business decision supported by each time estimate.
• Keep forecast arrival, readiness and contractual milestones distinct.
• Obtain duration assumptions from responsible sources and retain their conditions.
• Test changes at the milestone they affect rather than adding a generic buffer everywhere.
• Update downstream decision owners when the basis changes.

Define the milestone before using the date

Ask what the reader means by arrival, availability or delivery. These words can describe different events in different parts of the business. A schedule that uses them loosely may be internally consistent while supporting incompatible expectations.

Record the event in plain language and identify the source of its time. If a commercial agreement uses a defined milestone, retain the agreed wording and seek appropriate review where its meaning is uncertain. The planning model should not silently interpret the contract.

Then identify the decision that depends on the milestone. A buyer may need to confirm a receiving arrangement before the forecast event. An internal finance or sales team may need an update for planning but lack authority to change the programme. These distinctions help determine who needs notification and what the notification should ask them to do.

A well-designed schedule therefore has both an event column and a decision column. It shows the physical or commercial event being described and the action that the business associates with it.

Build the estimate from sourced assumptions

Obtain the relevant programme estimates from the responsible vessel and shore contacts. Record whether they are preliminary, conditional or updated for the current proposal. Do not infer an LPG carrier's performance from a generic class description.

If an estimate is supplied as a range, preserve it. The desk can test the business decisions affected by the range without claiming that an arbitrary midpoint is the expected outcome.

IMO's work on just-in-time arrival links timing information with readiness of port services and facilities. An arrival forecast should therefore be read alongside its relevant readiness dependencies. IMO arrival coordination information.

For the commercial model, identify which readiness responses have actually been obtained. A blank field should remain visible as an unresolved input, rather than being filled with the most convenient assumption from an earlier voyage.

Also preserve the programme version. If the receiving arrangement changes, the estimate may need review even when the origin and broad destination description remain similar.

Trace decisions backward from the required event

A decision can become urgent before the event itself is near. If a customer needs to confirm a receiving arrangement, identify when that confirmation must be sought and who can supply it. The schedule should show that action point as well as the forecast arrival.

Avoid creating backward deadlines through unsupported rules. Ask the relevant party what notice or decision process applies to this proposed arrangement and record the response.

This view helps the desk identify the earliest meaningful decision dependency. It may be a missing customer response rather than a change in the voyage estimate itself.

Test timing changes without inventing probability

A scenario can ask what would happen if a forecast event moves later, if a receiving response remains outstanding or if the programme is amended. State the change and trace its effect on the associated decisions.

The scenario need not claim to be likely. Its purpose can be to reveal whether the business has a workable response. For example, the team may discover that it needs an earlier customer update or a confirmed alternative contact if the usual decision owner is unavailable.

Do not assume that every downstream event moves by the same amount. Ask responsible sources for revised estimates where the relationship is uncertain. A simple shifted schedule can be used as an internal test, but its provisional nature should remain clear.

Keep contingency tied to a stated uncertainty. If a buffer has already been included in the source estimate, adding another allowance for the same issue can distort the result. Ask what the supplied estimate contains before applying further planning adjustments.

Fictional case: an arrival date used for the wrong promise

A fictional LPG trader receives a preliminary arrival forecast and passes it to the sales team. A sales colleague uses the date in a customer planning note as though it describes completion of the customer's receiving commitment. The receiving arrangement itself has not yet been confirmed.

The coordinator reviews the note and separates the event definitions. It records the forecast supplied by the vessel contact, the outstanding receiving confirmation and the commercial milestone that the sales team needs to discuss with the customer.

The sales team issues a corrected planning update with the appropriate scope. The coordinator assigns the receiving confirmation to the nominated contact and records the next forecast refresh. Management now sees the unresolved dependency instead of assuming the original date answered every scheduling question.

The correction does not require a new technical estimate. It requires the business to stop using one event label as a substitute for another and to obtain the missing commercial information through the proper route.

Maintain a decision-focused revision log

When the estimate changes, record the source, reason stated and affected decisions. Avoid updating dates silently across several systems, since different teams may otherwise retain different versions without realising it.

A brief revision note should say what changed and what action is required. Some recipients may only need awareness; others may need to obtain a new confirmation or reconsider a commitment. Make that distinction explicit.

At handover, identify the next information event the team expects and who owns the follow-up. A schedule is useful only while someone remains responsible for keeping its important assumptions current.

Common mistakes

Using arrival, readiness and delivery as interchangeable labels can turn a reasonable forecast into an unsupported commercial promise.

Another mistake is to add a general buffer without understanding the allowances already present in the source estimate. Tie contingency to a specific uncertainty and avoid overlap.

Finally, avoid sending revised dates without identifying the decisions affected. Recipients need to know whether they should simply note the update or take a new action.

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

Visit the Zeaclub website