Weekly Cargo Demand Review: Separate Volume and Timing

Key takeaways

• Reconcile the cargo programme before describing growth or contraction.
• Keep quantity, sourcing and timing changes in separate parts of the explanation.
• Distinguish newly confirmed activity from genuinely additional cargo.
• Connect the weekly interpretation with the vessel enquiry or programme decision it affects.

This original review structure contains no current trade or shipment information. Populate its fields from verified sources and authorised programme records before making a live demand claim.

Begin with the relevant cargo population

Define the commodity, geography, transport scope and time horizon covered by the review. A report about a particular loading area should not be presented as a complete measure of global commodity demand.

State the measure used. Tonnes, monetary value, number of enquiries and quantity-distance work answer different questions. If the report uses several measures, keep them separately labelled and explain how they relate to the commercial decision.

The programme boundary should remain comparable with the previous review. If the desk adds a source, widens its coverage or changes the cargo definition, disclose that change before interpreting the new total.

Also identify the decision horizon. A broader trade observation may provide context while the immediate chartering question depends on a narrower set of loading windows and service requirements.

Build a quantity bridge before writing the headline

Reconcile what was previously expected with the current programme. Identify additional cargo, reductions, cancellations, deferrals and completed movements according to the actual evidence.

Do not treat a change in status as automatically a change in quantity. A forecast parcel becoming confirmed improves certainty but may already have been included in the earlier planning total. Adding it again would overstate the programme.

Similarly, a deferred shipment should move between relevant windows without appearing as new total cargo unless the evidence shows that the programme expanded. Retain the connection between its earlier and current timing.

The quantity bridge should distinguish a real programme change from a correction to the desk's record. Both affect the reported total, but only one represents a newly changed commercial requirement.

Explain timing and sourcing separately

The same total cargo can be spread across periods or concentrated in a narrower window. That distinction may matter to the enquiry even when the aggregate quantity is unchanged.

Keep the timing interpretation explicit. A concentration hypothesis should identify which programmes moved and whether the receiving or loading arrangements support the revised windows. Do not infer the current schedule from a broad seasonal expectation alone.

Sourcing can change another part of the demand picture. A revised origin or destination may alter the relevant corridor and model transport work without changing total tonnes. The review should preserve both the local implication and the wider quantity boundary.

These explanations help the desk understand why a market can feel busier without a simple increase in the headline total. They do not establish a price response by themselves; actual commercial evidence is still needed.

Use a weekly observation and hypothesis table

The table below is an original analytical template. It separates what changed from what the analyst thinks that change may mean.

A hypothesis should identify evidence that could weaken it. If the central view depends on cargo concentration, a confirmed spread of loading windows should change that interpretation. Avoid explanations that remain the same under every new observation.

The table should also make missing evidence visible. An unresolved programme update cannot support the same certainty as an authorised current instruction.

Refreshable weekly demand fields

For a current transaction, .

• Reconciled cargo quantities and movement stages for the defined population: not provided; obtain current verified information.
• Verified timing, sourcing and coverage changes with unresolved evidence retained: not provided; obtain current verified information.
• Conditional demand interpretation, contrary evidence and next enquiry action: not provided; obtain current verified information.

Use explicit unavailable states where necessary. Do not fill missing programme quantities from an unrelated headline or carry an old window forward as though it had been reconfirmed.

The action field should identify what the desk needs to learn next. If timing is decisive, seek the relevant window confirmation. If the issue is whether an announcement displaces existing supply, investigate the sourcing relationship rather than repeating the announcement as new demand.

Fictional case: more enquiries, unchanged programme

Imagine a fictional desk observing a busier flow of cargo messages for an approaching loading period. The first weekly draft describes this as an increase in total cargo demand and recommends treating the entire flow as additional business.

The programme review finds several different developments. Some earlier forecast cargoes have become confirmed, some existing shipments have moved into the later window and repeated messages concern the same underlying movements. The overall programme quantity has not increased on the reconciled basis.

The corrected review retains the commercially important timing conclusion: the relevant period may contain more concentrated activity. It removes the unsupported claim of additional aggregate quantity and identifies which windows and parcel requirements still need confirmation.

The resulting enquiry plan is more focused. The desk investigates capacity for the actual concentration rather than assuming that every message adds a new shipment. It also preserves the distinction between confirmed programme changes and remaining hypotheses.

Relate demand evidence to the actual commercial choice

A weekly demand review should help decide where to direct enquiry, whether a programme assumption needs revision or which alternative deserves further comparison. It should not merely repeat that the market is active.

Connect the observation to the vessel or cargo decision without skipping the missing steps. A larger relevant programme may justify seeking additional proposals, but it does not establish that suitable capacity is available or that a particular freight level will follow.

If the desk already has a commitment, identify which part remains exposed to the new information. A market update does not automatically change agreed terms. The review should focus on the actual open decision rather than inventing one from the headline.

Close the loop in the next review

Retain the prior hypothesis and its evidence test. The next update should explain whether the expected programme confirmations appeared, whether timing changed again or whether the sourcing interpretation proved incomplete.

Separate learning from correction. A revised hypothesis responds to new evidence; a duplicate removed from the record corrects the earlier description. Both deserve clear treatment so readers understand why the conclusion changed.

Over time, this creates a useful sequence of commercial observations. The review becomes a way to improve the desk's understanding of actual cargo activity rather than a collection of disconnected weekly adjectives.

Common mistakes

Calling more messages more cargo. Reconcile identity, stage and quantity before drawing the demand conclusion.

Adding a newly confirmed parcel twice. Check whether it was already included as forecast activity.

Confusing concentration with aggregate growth. Explain whether quantity changed or moved between windows.

Repeating the same hypothesis without testing it. Identify the evidence sought and report whether it appeared.

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