Crude Voyage Timing Before the Cargo Is Nominated

Overview

The commercial team may need an early planning view for a refinery or receiving customer. It can provide one without pretending that the cargo allocation is complete. The key is to show which part of the schedule comes from responsible sources, which part depends on nomination and what event will trigger the next update.

Key takeaways

• Keep cargo availability assumptions separate from voyage-duration estimates.
• Use a clearly identified base nomination and realistic alternatives.
• Show the decision impact of each scenario rather than only a final arrival date.
• Avoid adding the same nomination uncertainty in several schedule lines.
• Assign ownership of the update when the cargo source confirms its position.

Identify what is not yet known

List the unsettled elements of the cargo proposition. The buyer may lack a final loading arrangement, a confirmed quantity or a supplier response on timing. Each uncertainty can affect a different part of the planning model.

Do not treat them as one generic delay allowance. A location uncertainty may require a different movement estimate, while a timing uncertainty may affect the starting point of an otherwise unchanged programme. The responsible sources should explain those effects.

Record the current information from the cargo source in its actual terms. A suggested window, a requested date and a confirmed nomination are different statuses. The commercial schedule should preserve that distinction.

The planning note should also explain why an estimate is needed now. A customer may be deciding whether to retain a receiving option, while an internal team may only need a preliminary budget. The appropriate level of detail follows the decision.

Build a conditional base case

Choose a base nomination scenario that reflects the best defined current proposition, and label it as conditional where necessary. Obtain the associated movement estimate from the responsible vessel and shore sources.

The base case should identify its starting event and the assumptions connecting it to later milestones. Avoid presenting a duration without explaining what starts the clock.

If the supplier's timing statement is preliminary, keep that qualification in the arrival planning view. The uncertainty does not disappear when a formula adds a voyage estimate to it.

This structure lets the reader understand the conditional chain without requiring the coordinator to forecast technical performance.

Test alternatives by changing the right input

Select alternatives that the cargo team is genuinely considering. If the loading proposition changes, obtain the relevant revised estimate rather than adjusting the total by an arbitrary allowance. If only the availability timing changes, state that the other assumptions are held constant for the scenario.

A scenario can be useful without assigning it a probability. Its purpose may be to identify whether the receiving customer needs an early discussion or whether the buyer should preserve another commercial option.

Do not let a broad range become a promise that every point within it is equally feasible. The range is a planning tool based on stated assumptions, and the relevant parties still need to confirm the actual programme.

Compare the consequences at the decision level. Which customer notification would change? Which option would need to be retained? Which commitment should wait for nomination? These questions make the schedule commercially useful.

Avoid duplicate uncertainty allowances

A common model problem arises when the analyst adds a nomination buffer before loading, includes the same uncertainty in a general voyage allowance and adds another contingency to the final arrival. The result can look prudent while counting the same issue repeatedly.

Identify the purpose of every allowance and ask what is already included in estimates supplied by others. Do not remove contingency simply to make the schedule attractive; remove overlap only when the basis is understood.

As information improves, update the relevant allowance. A confirmed nomination may resolve one uncertainty while leaving a separate receiving question open. The model should reflect that change rather than keep every early buffer indefinitely.

Explain revisions in terms of evidence. The schedule may narrow because the supplier confirmed the loading proposition, not because the vessel estimate became more certain. That distinction matters when the receiving team asks what confidence to place in the new view.

Fictional case: an arrival date with an invisible starting point

A fictional crude buyer asks chartering for an expected arrival date while its supplier is still allocating the cargo. The analyst uses a tentative loading date from an earlier conversation and adds the current movement estimate. The result is circulated without the tentative status.

The receiving customer begins planning around the date. Later, the supplier nominates a different loading proposition and timing basis. The buyer now has to explain why the earlier forecast changed substantially.

The team rebuilds its planning format. It shows cargo availability, nomination scenario and movement estimate as separate inputs, with a clear update trigger when the supplier confirms the parcel. Customer-facing notes identify the conditional basis rather than displaying one unqualified arrival date.

The new process does not eliminate uncertainty. It makes the uncertainty visible at the point where the customer is deciding how much reliance to place on the forecast.

Update downstream decisions deliberately

When nomination is confirmed, reconcile the actual cargo proposition against the base case. Identify which estimates and customer commitments need review.

Send a scoped update explaining what changed, what remains uncertain and what action is requested. Some recipients may only need the revised planning basis; others may need to confirm whether an existing arrangement still works.

Avoid treating the confirmed nomination as proof that every later milestone is settled. It resolves its own part of the chain. The responsible sources should provide updated programme information where needed.

At handover, name the person monitoring the next cargo-source response and the teams that need the resulting update. A conditional schedule without an update owner can become stale while continuing to look internally consistent.

Review the assumptions after the movement

A later review can compare the original uncertainties with the information that eventually arrived. Focus on whether the desk identified the right update triggers and communicated the conditional basis clearly.

Do not judge the planning method solely by whether the base case happened to match the outcome. A lucky unqualified date is less useful than a transparent scenario process that helps the business act responsibly when the nomination changes.

Common mistakes

Adding a voyage estimate to a tentative loading date does not turn the result into a confirmed arrival. Preserve the starting assumption's status.

Another mistake is to count nomination uncertainty repeatedly through several buffers. State the purpose of each allowance and reconcile overlap.

Finally, avoid leaving a conditional schedule without an owner for the nomination update. The model needs a clear trigger and a responsible person to keep it current.

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