Cape Voyage Duration: Convert Distance into a Timeline

Overview

Use route and performance inputs supplied by the appropriate qualified parties for the actual movement. The commercial worksheet should make the arithmetic transparent without selecting a navigational route, prescribing speed or presenting a hypothetical itinerary as a forecast.

Key takeaways

• Keep distance, passage time and total employment as separate quantities.
• Use consistent units and a clearly stated starting event.
• Add only the service and waiting components relevant to the model's scope.
• Explain which assumptions differ between the original and Cape propositions.
• Test the receiving consequence of the revised completion time.

Define the start and finish before calculating

An estimate beginning at departure answers a different question from one beginning before loading. State the initial event and the final milestone, then apply that boundary consistently to both alternatives.

The final milestone might be arrival, commencement of receiving service or completed delivery. Do not use one meaning in the base case and another in the Cape case. Such a mismatch can create an apparent duration difference that is partly a reporting error.

For a movement already underway, identify the current decision point. The relevant forward comparison uses the remaining achievable alternatives, not the full original itinerary from a starting point that has already passed.

Historical elapsed time still matters to the complete transaction result. Keep that broader view available, but do not make past days change the ranking between forward options when those days are common to both.

Use the supplied passage inputs consistently

A commercial estimate needs a distance and an applicable average passage-speed assumption on compatible units. Preserve the source and scope of those inputs. A route label such as Cape does not provide a universal distance or voyage duration.

Where different candidates supply different assumptions, ask whether the difference reflects the proposed route, performance basis or another qualification. Do not rank their duration figures until the scope is understood.

The speed assumption used in the worksheet is an analytical input. It is not an instruction to the ship. Any actual operating or navigational decision remains with the responsible qualified parties.

Keep passage time distinct from other elapsed time. Loading, waiting, an additional commercial call and receiving service may belong in the total model, but they should not be hidden inside an unexplained sea-time figure.

Work through the arithmetic

The following distances and speed are invented for a comparison exercise. They do not describe any actual origin-destination pair, current route or vessel performance.

ILLUSTRATIVE: Assume Route A has a supplied distance of 9,000 nautical miles and the fictional Cape alternative has 12,000 nautical miles. Both are modelled at an assumed 12 nautical miles per hour. Passage time is distance divided by the assumed hourly rate.

A therefore takes 750 passage hours, or 31 days and six hours. The Cape alternative takes 1,000 passage hours, or 41 days and 16 hours. The passage difference is 250 hours, equivalent to ten days and ten hours.

Now add 72 hours of identical loading and receiving components to both models. A totals 822 hours, or 34 days and six hours. The Cape alternative totals 1,072 hours, or 44 days and 16 hours. If a further 24-hour commercial service component is included only in the Cape scenario, its total becomes 1,096 hours, or 45 days and 16 hours. The complete difference from A is then 274 hours, or 11 days and ten hours.

The example shows why the extra passage time and extra total employment are not always identical. A commercial service difference can change the itinerary even when the passage arithmetic remains unchanged.

It also shows the importance of preserving fractions of a day until the relevant presentation step. Rounding each component prematurely can accumulate a discrepancy in the final delivery estimate.

Show allowances without counting them twice

An input may already include a stated allowance. Identify that before adding another general contingency to the total. The desk should be able to explain whether an allowance covers a specific uncertainty or duplicates a component already present.

Do not remove every allowance merely to make the model more competitive. Instead, separate the central supplied estimate from a defined adverse scenario. That allows management to assess the transaction under both without confusing resilience testing with a forecast.

Where waiting is unresolved, describe the assumption explicitly. A base case of prompt service is an assumption, not confirmation that no waiting will occur. An adverse waiting scenario needs a stated purpose and should not be portrayed as an expected delay without evidence.

The same discipline applies to additional calls. Include them only when they belong to the proposed commercial scope, and show any unresolved timing rather than inventing a standard duration.

Connect the timeline to receiving value

Ask the buyer which receiving opportunity the revised estimate can support. A later arrival may still fit the same commercial objective, or it may require a different service arrangement or sales proposition. That is the economic consequence the desk needs to understand.

Avoid assigning a universal cost to each additional day. The actual value depends on the decision-maker's commitments and the relevant commercial terms. An internal time allowance can be useful if its basis and perspective are clear.

A missed receiving opportunity can create a different outcome from a simple proportional delay. Obtain the next achievable proposition from the appropriate party rather than assuming the cargo can be received immediately after the original window.

If the revised timeline no longer supports the original buyer, compare realistic alternatives. Do not keep the old sales value in the model merely because the cargo and vessel remain unchanged.

A duration review checklist

The checklist supports a reproducible estimate. It should not be presented as a technical voyage plan or a substitute for qualified route assessment.

Fictional case: extra distance was not the whole delay

A fictional cargo desk calculates the additional passage time for a Cape proposal and adds it to the old delivery estimate. The result appears to preserve the buyer's receiving opportunity.

A scope review shows that the revised proposition also includes an additional service call. Its timing was absent from the first model. Once included, the completed receiving milestone falls outside the original opportunity under the stated assumptions.

The desk obtains a revised receiving proposition and compares its commercial consequence with another feasible option. The corrected estimate does not claim that the service will take a universal amount of time. It simply includes the actual supplied component that the first calculation omitted.

Common mistakes

Using one additional-days figure for every Cape movement ignores origin, destination and scope. Mixing departure-to-arrival with pre-loading-to-delivery totals creates another distortion. A third mistake is adding a contingency already included in the supplied input. Finally, do not treat a hypothetical speed as an operating instruction or a calculated duration as a confirmed receiving opportunity.

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