
Overview
This distinction matters when a desk evaluates several cargo commitments together. A fuel price change may affect a common voyage budget, while an additional call or revised cargo programme may create a separate exposure. The analyst should show those effects independently before discussing how they are distributed internally or recovered under an agreement.
Key takeaways
- Calculate the change in the voyage fuel estimate before splitting it between cargo accounts.
- State the allocation rule and explain what the rule measures.
- Keep a cargo's share of common cost separate from an incremental cost attributed to its request.
- Use scenario prices and quantities without presenting them as a vessel forecast.
- Check recovery provisions separately from the internal costing model.
Define the question the model will answer
A voyage sensitivity model can show how a selected fuel assumption changes the estimated budget. It cannot, by itself, determine which customer must pay. That second question depends on the relevant commercial arrangements and the authorised interpretation of them.
Begin by naming the decision. A trader may need to compare contribution estimates across cargo accounts. A chartering manager may need to assess the voyage as a whole. A finance team may need to explain why a monthly allocation changed. These users require related but different outputs.
For the voyage decision, preserve the total fuel cost and its change. For the cargo account view, show the chosen allocation basis alongside each assigned amount. For a recovery discussion, link to the applicable agreed mechanism without implying that an internal spreadsheet creates an entitlement.
Do not introduce a detailed allocation merely because the spreadsheet can support one. If the business makes its decision on total voyage contribution, an elaborate cargo split may distract from the more important question of whether the combined programme still works.
Keep three layers of evidence separate
The first layer contains inputs: assumed fuel quantity, scenario price and currency. Record where the quantity assumption came from and who can revise it. Commercial staff should obtain the relevant estimate from an authorised source rather than deriving vessel performance from a broad class label.
The second layer contains arithmetic. This should be reproducible without interpretation. A reviewer ought to be able to reconstruct the total using the stated inputs and formulas.
The third layer contains allocation judgment. If the business uses cargo quantity, revenue, occupied capacity or another basis to divide common costs, say so. Each basis describes a management choice; none should be disguised as an observed physical cause merely because it produces precise numbers.
| Layer | Question answered | Evidence to retain |
|---|---|---|
| Voyage inputs | What assumptions were tested? | Quantity source, scenario price and currency |
| Voyage calculation | How much does the estimate change? | Formula and checked results |
| Cargo allocation | How is the common estimate divided? | Approved allocation basis and denominator |
| Incremental request | What changes because of a specific request? | Separately reviewed scenario and attribution |
| Contract recovery | What amount may be claimed or passed through? | Relevant agreement and authorised review |
Keeping these layers visible allows a reviewer to challenge an allocation without rejecting correct arithmetic, or to revise an input without silently changing the costing policy.
Test an additional cargo request separately
Suppose a cargo account asks for an itinerary change. Do not apply its allocation share to an assumed extra fuel amount and call the result the cost of the request. First obtain a separately reviewed scenario showing the effect of the proposed change on the voyage estimate.
The commercial team can then decide how to treat that effect within its costing policy. It may keep the incremental amount visible against the requesting account while continuing to allocate the original common cost on the existing basis. Alternatively, an agreed policy may require a different treatment. The key is to document the decision instead of letting the spreadsheet's default formula decide it.
Be alert to costs that have already been included in a revised voyage estimate. Adding a separate incremental line without removing the overlap can count the same exposure twice. Reconcile the scenario total before discussing account-level consequences.
A request can also affect timing, service commitments or other cost categories. Present the fuel sensitivity as one component of that wider decision. Avoid implying that an acceptable fuel increment proves the whole request is commercially workable.
Fictional case: the apparent improvement
A fictional chemical trader reviews a shared voyage after its internal allocation policy changes. One cargo account appears to have improved even though the voyage fuel estimate has risen. Its manager proposes accepting a tighter sales margin on the next shipment because the account now looks less costly to serve.
The analyst separates the voyage change from the allocation movement. The revised policy transferred part of the common cost to another account; it did not reduce the voyage's exposure. The manager therefore reviews the next sales decision against both the account report and the combined voyage result.
The business may still prefer the new allocation policy. The model does not decide that question. It ensures that a reporting change is not mistaken for a physical or commercial saving, and that the next commitment rests on a clearly described basis.
Common mistakes
Using allocated cost as proof of causation is a recurring error. An account's share can reflect a management convention rather than the marginal effect of carrying that cargo.
Changing both the price scenario and the allocation rule without showing separate effects makes the result difficult to audit. Freeze one while explaining the other.
Another mistake is to describe an internal charge as recoverable from a customer. Recovery requires its own contractual basis and review; the allocation model does not supply it.
Where Zeaclub fits
Zeaclub supports agentic, AI-assisted operations with a human in control.
Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.
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
Is cargo quantity always the right allocation basis?
No universal basis follows from this model. Choose a policy that suits the business purpose, document its limitations and apply it consistently enough for comparisons to remain meaningful.
Should the allocated increases sum to the voyage increase?
Yes, when the allocation is intended to distribute the full common change. A difference indicates an omitted share, rounding issue or other model feature that should be explained explicitly.
Can an allocation change improve total voyage contribution?
Redistributing the same cost does not change the total. It changes account reporting. Any improvement in the combined result needs a separate explanation involving actual revenue or cost assumptions.
Where should contractual recovery appear?
Use a separate view linked to the relevant agreement and reviewed by the responsible commercial or legal team. Do not merge a disputed recovery assumption into the physical cost calculation.