Key takeaways
- Identify the conditions that must be met before loading can begin.
- Show cargo readiness and vessel availability as separate timelines.
- Add only genuinely sequential durations after the controlling start condition.
- Reassess the receiving arrangement when the resulting arrival changes.
- Keep the model distinct from a forecast of actual operating performance.
Find the event that controls the start
A proposed loading start may depend on the vessel being available, the allocated cargo being ready and the relevant terminal arrangement being available. These conditions can develop at the same time. The last unresolved condition can therefore determine when the combined operation becomes possible.
For the actual shipment, ask the responsible parties which conditions apply. Do not assume that a berth, loading service or cargo review is automatically available once ship and cargo are present. The simplified example below deliberately fixes those other conditions to isolate one scheduling point.
The commercial desk should distinguish an input date from the resulting loading date. Cargo readiness is an input. Vessel availability is another input. Loading start is the result of the applicable conditions coming together.
This helps explain why an early improvement may have no immediate effect. If the vessel remains the later condition, bringing the cargo forward might create additional buffer without changing the planned start. That buffer can still have value, but it is not the same as an earlier delivery.
Keep parallel and sequential activities separate
Draw cargo preparation and vessel positioning on separate lines until the point where they must meet. After that meeting point, show the supported sequence of loading, sailing and receiving activities relevant to the commercial endpoint.
Some real activities may overlap or have additional dependencies. Use the actual parties' plan rather than forcing every operation into the simplified sequence. The aim is to make the scheduling logic visible, not to impose a universal voyage model.
A useful distinction is whether one activity must wait for another. If it does, their durations may belong in a sequence. If both proceed independently and only need to be finished by a common start, adding their delays can count the same elapsed period twice.
The distinction also changes the response. Accelerating an activity that is already ahead of the controlling condition may not advance the shipment. A proposal to pay for speed should identify which milestone it would actually move.
Illustrative case: two delays do not sum to six days
ILLUSTRATIVE fictional schedule. All dates are relative days, and all durations are invented. Assume the terminal and other required conditions are available whenever the later of cargo readiness and vessel availability occurs.
In the base case, cargo is ready on day 8 and the vessel is available on day 10. Loading starts on day 10, takes two days, and is followed by six days of sailing and one day of receiving activity. The commercial endpoint is reached on day 19.
Now delay cargo readiness by three days to day 11 and vessel availability by three days to day 13. Loading starts on day 13, not day 16. With the other durations unchanged, the commercial endpoint becomes day 22.
| Milestone | Base | Both inputs delayed |
|---|---|---|
| Cargo ready | Day 8 | Day 11 |
| Vessel available | Day 10 | Day 13 |
| Loading start: later input | Day 10 | Day 13 |
| Loading complete | Day 12 | Day 15 |
| Arrival after sailing | Day 18 | Day 21 |
| Commercial endpoint | Day 19 | Day 22 |
The endpoint moves by three days. Adding the two input delays would suggest six days and would double-count their overlap in this model.
For comparison, delaying only cargo readiness to day 11 while keeping the vessel available on day 10 moves the endpoint to day 20. The three-day change in cargo readiness creates a one-day endpoint change because the base plan had two days between cargo readiness and vessel availability.
None of these results predicts a real port call. They follow from the stated fictional dependencies. If the changed timing loses a terminal opportunity or alters receiving availability, build that consequence into a separate supported scenario.
Ask whether the later date changes another condition
A simple overlap model can understate the impact if a shifted start changes the rest of the plan. Ask the terminal and receiver whether their arrangements remain available at the revised dates. Ask the relevant service providers whether their scope and timing still apply.
Do not automatically add a missed-window consequence. Establish whether the specific alternative actually loses the opportunity and what replacement is available. A hypothetical disruption should remain labelled as a scenario, not become an asserted delay merely because the model has changed.
Keep the original cause and downstream consequence separate. For example, a later vessel availability date may change the loading start, which may in turn require a revised receiving appointment. Explaining the chain is more useful than placing a single unexplained delay allowance at the end.
Compare acceleration at the controlling point
Suppose a supplier offers to bring the cargo forward. Ask whether that would change the later condition governing loading. If it would not, the proposal may improve resilience without changing the expected endpoint.
Likewise, an earlier vessel does not necessarily produce an earlier shipment if the allocated woodchips cannot be presented sooner. The desk should compare the value of the actual milestone change with the full cost and conditions of the acceleration proposal.
Where the objective is resilience, state it explicitly. Paying for additional cargo buffer may be sensible for the business, but the recommendation should not claim a delivery improvement that the schedule does not show.
A supported alternative can change which condition controls the start. Recalculate the whole sequence when that happens. Do not continue using the previous controlling condition simply because it was the focus of the original discussion.
Present the model with its limits
Show the conditions held fixed, the inputs changed and the endpoint measured. This allows a reviewer to see what the model answers and which unresolved factors sit outside it.
Avoid combining independent worst cases without explaining whether they can occur together. Conversely, do not discard a combined scenario merely because each input has been analysed individually. The dependencies determine the result.
The best schedule comparison is small enough to inspect and specific enough to support a decision. It should identify what would make the conclusion change, such as a different terminal opportunity or a revised cargo-readiness basis, rather than hiding those factors inside a broad confidence label.
Common mistakes
The most common error is adding delays to parallel activities as though they happen consecutively. Another is assuming that every day saved upstream becomes a day saved at delivery.
A third mistake is keeping all downstream arrangements fixed after a material date change without checking whether they remain available. Finally, do not treat the fictional durations as operating benchmarks or use the model to allocate contractual responsibility for delay.
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
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
Should cargo and vessel delays always be combined using the later date?
Only where they are parallel conditions for the same start and the model's other conditions hold. Actual port and cargo arrangements may introduce additional dependencies.
Does earlier cargo readiness have no value if the ship is later?
It may create buffer or reduce exposure to a cargo delay. That value is different from an immediate improvement in the planned delivery date.
What if the revised start misses a terminal opportunity?
Obtain the next supported arrangement and model it explicitly. Do not assume either that the original opportunity remains available or that it has necessarily been lost.
Can this model establish delay liability?
No. It explains timing consequences under stated assumptions. Responsibility and claims require the actual terms, evidence and appropriate qualified review.
Which endpoint should the schedule use?
Use the endpoint relevant to the decision, such as material available to the receiver. State it clearly and include the actual required activities between loading and that point.