Parcel Tanker Duration: Model Shared Dependencies

Overview

The commercial schedule is a model of the proposed programme, not an operating instruction or a promise of performance. It should make clear which event times came from responsible parties, which remain assumptions and which customer commitments depend on them. That visibility matters more than producing a single precise-looking completion date.

Key takeaways

• Model the shared itinerary once and connect each parcel's commitments to it.
• Label estimated, requested and actual event times accurately.
• Identify which delays propagate and which affect only a local decision.
• Keep scenario changes separate from contingency already included in the base estimate.
• Update affected commitments when the programme changes, not only the final arrival line.

Start with a common event map

List the commercial events needed to describe the proposed movement. The relevant detail may include departure, arrival at successive destinations and the confirmations on which the next stage depends. Obtain the appropriate estimates from the responsible vessel and shore parties rather than deriving them from generic vessel-class assumptions.

Attach each parcel to the events that matter to its commercial commitment. One customer may care about a destination arrival forecast; another may need a decision earlier so it can prepare its receiving arrangement. These milestones should remain visible even when they share the same voyage.

IMO's Compendium dataset distinguishes event information using defined data elements, including time status. Consistent labels help prevent a request being mistaken for an actual event. IMO Compendium dataset.

Use those distinctions in plain language. A requested time expresses a desired arrangement. An estimate describes an expectation. An actual time records what occurred. Moving between those statuses should be based on new evidence, not on a spreadsheet cell becoming old enough to look settled.

Separate sequence from duration

A programme can change because an event takes longer or because the order of events changes. Those are different revisions. An analyst who updates only the total duration may miss the consequences for particular customers.

Represent the sequence explicitly. If a destination is moved later in the programme, identify every commitment affected by that position. Do not assume that a similar overall voyage duration means the commercial effect is unchanged.

Then record the duration assumptions between events with their source and status. Where a responsible party supplies a range or a conditional estimate, retain that limitation instead of converting it to an unexplained point value.

The commercial model should remain proportionate. It need not simulate detailed vessel operations. Its purpose is to show the relationship between the supplied estimates and the decisions the business must make.

Test propagation without assuming every delay spreads

When an event changes, ask the responsible parties which later estimates need revision. Some consequences may be direct; others may depend on arrangements that have not yet been confirmed. Record those distinctions rather than moving every subsequent line automatically by the same amount.

A uniform shift can be useful as an initial planning scenario, but label it as such. It is not a substitute for revised information from the people responsible for the programme.

Also look for shared causes. If several parcel rows rely on the same preceding event, their timing uncertainty is connected. Treating each row as an independent risk and adding all allowances together can exaggerate the total programme exposure.

Conversely, a stable final completion estimate does not prove that every intermediate commitment remains achievable. A programme may recover time later while an earlier customer's decision point has already been affected. Review the individual commercial milestones as well as the overall voyage finish.

The output should help the desk decide whom to notify, which assumptions to refresh and whether a commercial commitment needs reconsideration. It should not instruct the vessel or shore facility how to recover time.

Keep contingency visible and purposeful

A planning allowance should answer a specific uncertainty. Identify its purpose and where it sits in the model. A general buffer applied to every parcel can conceal both double counting and gaps.

When actual information replaces an assumption, reconsider the related allowance. Leaving it untouched may make the model progressively more conservative without anyone choosing that result. Removing it automatically may be equally inappropriate if the original uncertainty remains elsewhere in the programme.

Explain scenario results in terms of the decision. A case may show that an early customer notification is prudent, that a receiver needs to confirm flexibility or that the desk requires a revised estimate before making a sale commitment. The model should lead to an action whose owner is clear.

Avoid reporting a scenario as the most likely outcome unless there is a basis for that judgment. It can be useful simply as a test of how the programme responds to a stated change.

Fictional case: one shared delay, several parcel rows

A fictional analyst maintains a schedule with a separate row for every parcel. After a change at an early call, the analyst adds a delay allowance to each affected parcel and totals the allowances in a programme summary. The resulting exposure looks much larger than the change described by the responsible parties.

A review shows that the rows all depend on the same preceding event. The analyst rebuilds the schedule around a shared event map and links the parcel commitments to it. The common change appears once, while customer-specific consequences remain visible in their own rows.

The revised view reveals a more useful distinction. Some later commitments require updated forecasts, while one customer's earlier decision deadline needs immediate attention. The desk contacts that customer through the agreed route and requests refreshed programme information from the responsible parties.

The model now supports targeted coordination instead of an inflated total. It also retains the original assumptions, so the team can explain why the earlier summary was misleading without suggesting that all uncertainty has disappeared.

Update the record as evidence improves

Preserve the base version when issuing a revision. Show which event changed, the source of the new information and the affected parcel commitments. A brief change log is usually more useful than silently replacing dates throughout a large workbook.

At handover, identify the next expected update and the person responsible for obtaining it. A schedule with no update owner can remain internally consistent while becoming commercially stale.

Common mistakes

Summing parcel-level buffers that reflect one shared event can double count uncertainty. Map the dependency before aggregating allowances.

Another mistake is to focus only on final voyage completion. Intermediate customer decisions may be affected even if the overall estimate later recovers.

Finally, avoid turning a uniform planning shift into a confirmed revised schedule. Obtain scoped updates from the responsible sources and preserve their stated limitations.

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