This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Overview
BIMCO's CII Operations Clause for Time Charter Parties distinguishes its charter-party attained measure from the vessel's annual rating and stresses the need to understand the applicable regulations. Check the current text and the actual agreement; a shared acronym does not establish that the parties are discussing the same result or obligation.
Key takeaways
- Classify the disagreement before requesting a decision.
- Align period, metric, units, status and included data.
- Separate technical correction from contractual interpretation.
- State the proposed act affected by the unresolved issue.
- Preserve each conclusion within the reviewer's actual scope.
Name the competing propositions
A useful escalation begins with the statements that appear inconsistent. One party may quote an annual result while the other refers to a charter-period measure. One may use a provisional value and the other a forecast. Describe each with its period, purpose and status before deciding that they conflict.
If the figures are intended to represent the same thing, identify the numerical or methodological difference and the supporting records. Avoid a generic statement that the CII data is wrong. The reviewer needs to know which element requires explanation and how it affects the commercial question.
State what the principal is being asked to do. The issue may affect an employment proposal, a request for information, a negotiation about a target or another act under the agreement. An escalation without that connection can become an open-ended technical debate with no decision point.
Separate data, method and interpretation
An input discrepancy concerns the underlying record. A methodological disagreement concerns how the relevant data should be treated in the calculation. A forecast disagreement concerns assumptions about future activity. A contractual disagreement concerns the meaning or consequences of the actual agreement.
Those categories may overlap, but they should not be collapsed. A corrected input can resolve a technical difference while leaving the parties' interpretation of the agreement unsettled. Conversely, an agreed definition can clarify which calculation is needed without establishing that the available data is complete.
Assign the questions to the appropriate reviewers. The technical owner should explain the data and method. Legal or contractual advisers should address the agreement where necessary. The principal should receive the resulting commercial implications without a coordinator presenting a technical explanation as a legal determination.
Build a reconciliation sheet
The following table is an original tool for preparing the escalation. It is not a substitute for the applicable calculation or the contract.
| Comparison item | Party or report A | Party or report B | Resolution question |
|---|---|---|---|
| Purpose | State the decision or reporting use | State the corresponding use | Are these results intended to answer the same question? |
| Period | Identify the included interval | Identify the included interval | Is a period mismatch driving the difference? |
| Status | Final, provisional or forecast | Final, provisional or forecast | Is measured information being compared with assumptions? |
| Inputs | Identify source and material exclusions | Identify source and material exclusions | Which underlying records differ? |
| Method | Identify calculation reference | Identify calculation reference | What technical interpretation needs review? |
| Contractual meaning | Cite the actual definition relied upon | Cite the actual definition relied upon | What legal or commercial question remains? |
The table should reveal the smallest unresolved question capable of changing the decision. Do not ask every reviewer to approve every cell if the main issue is a specific period or data mismatch.
Request a technical answer that can be used commercially
Ask the technical reviewer to explain the reason for the difference and its significance to the stated comparison. A corrected number alone may not tell the principal whether an employment assumption, an input error or a methodological choice caused the change.
Preserve qualifications. If the available records do not support a definitive reconciliation, show which data remains missing and what range of conclusions is still possible in qualitative terms. Do not manufacture precision or silently select the value most convenient to the commercial sponsor.
Where a forecast is involved, ask for the assumptions to be made comparable before discussing the apparent advantage of an option. The principal should understand whether the difference reflects the proposed employment itself or inconsistent assumptions used to model it.
Fictional case: calendar-year data meets a charter-period claim
In a fictional time-charter discussion, the owner supplies a calendar-year CII result. The charterer supplies a calculation relating to the period during which it employed the vessel. The parties initially describe the figures as contradictory and begin debating who caused the difference.
The coordinator records the purpose and period of each result and retrieves the actual agreement. The technical team establishes which underlying activity each calculation includes. The contractual reviewer considers which defined measure is relevant to the specific claim or request being made.
The annual result is retained for its proper reporting context. The charter-period information is assessed for the purpose it was prepared to serve. If a genuine data or interpretation issue remains after alignment, it is escalated explicitly rather than hidden behind the initial mismatch.
The principal receives a clearer decision: which figure addresses the relevant question, what remains uncertain and what authority is requested. The case does not determine responsibility under any particular charter; it illustrates why comparability should precede argument about consequences.
Present options without creating an unintended obligation
The escalation can identify practical next steps, such as correcting a data record, obtaining a revised forecast, clarifying an agreed definition or discussing an alternative employment proposal. State what each step resolves and what it leaves open.
Do not infer authority to change orders or accept a commercial consequence from an unfavorable figure alone. The actual agreement, relevant facts and appropriate advice need to be considered. A technical result can inform that process without determining every right or remedy.
If the principal authorizes negotiation, retain the scope of that authority. A request to explore a solution is different from permission to agree a target, accept responsibility or vary an obligation. External communications should reflect the mandate actually given.
Close the exception with a traceable answer
Record the original disagreement, comparable basis established, reviewer conclusions and principal's direction. If only part of the issue is resolved, identify the remaining question and the act it affects. Avoid an all-purpose completed status when the technical and contractual work have different outcomes.
Link any corrected result to the superseded version and explain why it changed. The next monitoring cycle should start from a clear baseline, while the historical file should still show what information the earlier decision used.
Common mistakes
One mistake is arguing about responsibility before confirming that the figures cover the same period and purpose. The apparent disagreement may be a comparison error rather than a performance finding.
Another is treating a technical correction as a settlement of contractual consequences. Keep the method explanation and the agreement assessment separately identifiable.
A third is choosing the more favorable figure without reconciling the difference. The principal needs a supported basis for reliance, not a convenient number that leaves the underlying question unresolved.
Where Zeaclub fits
Zeaclub offers digitalised procedures across the voyage workflow.
Zeaclub provides 24/7 operating systems and worldwide coverage.
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
What should happen when two CII reports disagree?
Compare purpose, period, units, status, data coverage and method first. If they are intended to represent the same result, send the specific remaining discrepancy to the responsible technical reviewer with both bases attached.
Does a regulatory result determine a charter-party claim?
The actual agreement and relevant facts require assessment. A regulatory result may be relevant evidence, but its relationship to the defined contractual measure or alleged consequence should not be assumed from similar terminology.
Can a broker propose alternative employment?
The desk can prepare and discuss options within its authority, with the relevant technical and commercial assumptions visible. Any instruction, agreement or variation should follow the principal's mandate and the applicable review process.
What makes the exception ready to close?
The specific question should have an identifiable answer or an explicit principal's direction addressing the remaining uncertainty. Preserve the scope of each conclusion and keep unresolved technical or contractual questions open where they still affect reliance.