
Key takeaways
- Define which days are payable under the actual or explicitly assumed arrangement.
- Show hire rate and duration as separate inputs.
- Recalculate the full product when both change.
- Compare the value of rate negotiation with supported changes in committed time.
- Keep hire-only sensitivity separate from a complete employment-cost forecast.
Define the payment model before testing it
The simplest illustrative hire model is daily rate multiplied by payable days. That model is useful only where its assumptions match the question being asked.
Real proposals may contain conditions affecting the relevant duration or payment. Use the actual agreed basis and obtain qualified interpretation where it is uncertain. Do not assume that every operational day is payable in the same way, or that an estimated early finish necessarily reduces the commitment.
The examples here deliberately assume that all modelled days are payable at one stated rate. They do not address off-hire, redelivery disputes, minimum periods or other contractual mechanisms. Those matters require their own current-text and evidence review when relevant.
Also identify the cost scope. A hire-only calculation isolates the effect of rate and days. It does not include every expense the charterer may retain during employment. Label it accordingly.
Start with a two-dimensional table
A single rate sensitivity asks what happens if the daily amount changes while duration remains fixed. A single duration sensitivity asks what happens if days change while the rate remains fixed. A table containing both shows whether the recommendation depends on a particular combination.
Use supported ranges for an actual decision. Do not choose a narrow range merely to make the preferred offer appear stable. Equally, do not invent extreme inputs that have no connection to a plausible programme and present them as forecasts.
The table should contain a small number of interpretable cases. Each row and column needs a clear unit, and the reader should know which combination represents the current comparison basis.
Illustrative hire sensitivity matrix
ILLUSTRATIVE fictional model. Assume all stated days are payable at the stated daily rate, with no other hire adjustment. The base case is USD 18,000 per day for 40 days, producing hire of USD 720,000. All figures are invented.
| Daily hire | 40 payable days | 45 payable days | 50 payable days |
|---|---|---|---|
| USD 18,000 | USD 720,000 | USD 810,000 | USD 900,000 |
| USD 19,000 | USD 760,000 | USD 855,000 | USD 950,000 |
| USD 20,000 | USD 800,000 | USD 900,000 | USD 1,000,000 |
At the base duration, increasing the rate from USD 18,000 to USD 20,000 adds USD 80,000. At the base rate, increasing duration from 40 to 45 days adds USD 90,000.
If both changes occur, hire becomes USD 900,000, an increase of USD 180,000 from the base. Adding the two separate base-case effects would give only USD 170,000. The missing USD 10,000 is the rate increase of USD 2,000 applied to the five additional days.
The interaction is ordinary multiplication, but it has a practical reporting consequence. A summary of separate sensitivities should not be used as the exact combined scenario unless the interaction is included.
Use the interaction to explain the complete movement
The cost change can be decomposed into a rate effect on the original days, a duration effect at the original rate and the interaction between the two changes.
That decomposition helps explain why the full recalculation differs from the sum of isolated tests. It is an analytical bridge, not an allocation of blame or contractual responsibility.
If a report uses another valid bridge order, label the method and apply it consistently. For example, applying the revised rate first and then adding days at that revised rate incorporates the interaction into the second step. The final total should still reconcile.
The safest practice is to calculate each complete scenario directly from its own inputs, then use the bridge to explain the result. Do not build the final total from rounded intermediate sensitivities if that would create a reconciliation difference.
Compare rate savings with duration assumptions
A rate concession has value only across the days to which it actually applies. A duration reduction has value only if it reduces the relevant payment commitment under the actual arrangement.
ILLUSTRATIVE negotiation comparison. Under the base fictional model, a USD 1,000 daily rate reduction over 40 days saves USD 40,000. At the unchanged USD 18,000 rate, reducing payable time by two days saves USD 36,000. Reducing it by three days saves USD 54,000.
These comparisons assume the shorter paid period is actually achievable and that other relevant costs do not change. They do not establish an operational right or a way to reduce real hire automatically.
The desk can use such comparisons to prioritise negotiation and evidence. A modest supported change in the commitment may matter as much as a visible rate reduction. But an optimistic schedule improvement is not equivalent to a firm commercial concession.
Keep time savings commercially coherent
Ask what produces the shorter period. Does a different delivery position remove part of the relevant commitment? Does a revised programme genuinely finish earlier? Does the actual agreement allow the payment basis to change as assumed?
Then assess any offsetting expense or lost benefit. An earlier finish achieved through a more expensive service may reduce hire while increasing total employment cost. A shorter programme may also carry less cargo or serve a different commercial requirement.
The hire sensitivity should therefore feed into a complete comparison rather than become the final recommendation on its own. Keep the reduced hire, additional costs and changed service output visible.
Do not use a duration estimate borrowed from another vessel or programme without checking its applicability. The arithmetic may be exact while the commercial basis remains unsupported.
Identify the input worth resolving next
A sensitivity matrix can show where uncertainty matters. If the preferred proposal changes across plausible rate-and-duration combinations, the desk should identify which unresolved input can be clarified before commitment.
A firm rate offer may narrow one dimension while leaving duration uncertain. A supported programme may narrow duration while the commercial terms remain open. The next action should address the uncertainty that could alter the decision.
Avoid treating every cell as equally likely. The matrix is a set of conditional calculations. Some combinations may not be feasible or available together. Exclude unsupported combinations from the actual recommendation or label them clearly as stress tests.
The resulting decision note should state which combination is supported, which alternatives remain plausible and what evidence would change the conclusion.
Common mistakes
One mistake is adding isolated rate and duration effects without their interaction. Another is assuming operational time saved automatically means payable time saved.
A third error is treating hire-only savings as a complete cost improvement when additional services or reduced cargo output have been ignored. Finally, do not present the matrix as a forecast of actual rates or duration: it contains conditional calculations under stated assumptions.
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
Why do simultaneous changes create an extra effect?
The higher rate also applies to the additional days in this fictional model. That product is absent when both separate sensitivities are measured only from the original base.
Is the simple rate-times-days formula always sufficient?
No. Use the actual payment terms and relevant conditions. The simple formula is an explicit assumption for this example, not a universal contract interpretation.
Should the desk negotiate rate or duration?
Compare the supported value of each change and the practical ability to obtain it. A hypothetical shorter period should not be treated as equivalent to an agreed rate concession.
Does lower hire mean a better programme?
Not necessarily. Assess other retained costs, the cargo service delivered and the feasibility of the revised arrangement.
What should the sensitivity table lead to?
A clearer view of which inputs can change the choice and which confirmation is worth obtaining next. It should support a specific decision rather than remain an isolated mathematical exercise.