This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Overview
IMO describes CII as an annual operational carbon-intensity measure whose attained result is documented and verified against the required value to determine a rating. The commercial desk should therefore identify exactly which result it has received before using it to assess a proposed fixture or operational option.
Key takeaways
- Label historical, provisional and forecast results distinctly.
- Preserve the reporting period and calculation basis beside the value.
- Ask the technical team which inputs and adjustments support the result.
- Keep regulatory reporting separate from any contract-specific measure.
- Describe the proposed employment before requesting a forecast.
Begin with the decision the data should support
A chartering team might need background for vessel selection, an outlook for proposed employment or information relevant to an agreed contractual measure. Those are different questions. State the decision first so the supplier of the data can identify the appropriate result and supporting explanation.
For vessel selection, historical information may provide context about past operations. For a future employment decision, the principal needs assumptions about the proposed activity and a suitably qualified forecast. For a contractual question, the relevant agreement and its defined measure require their own review.
Do not combine those purposes under a single CII approved label. A historical result can be accurately reported while offering no direct answer about a future plan. A forecast can help compare options while remaining different from a verified result or a contractual conclusion.
Identify the period and status of every result
Record the period covered and whether the figure is final, provisional or forecast. Identify the person or function supplying it and the basis for any claim about verification. The desk should not infer status from the professional appearance of a dashboard or attachment.
Where the figure is cumulative to a reporting point, label that point and the included activity. Where it is a scenario, identify the future period and assumptions. This prevents a partial-period result from being compared casually with a full historical result as though they represented the same exposure.
Also preserve the metric's name and units exactly as provided, with any clarification from the technical team. Similar-looking values may have different definitions or boundaries. If the desk cannot establish comparability, it should ask rather than normalize the figures informally.
Request the calculation explanation at the right level
The commercial team does not need to reproduce the technical calculation to ask useful questions about it. Request a description of the relevant data sources, period coverage, calculation method and any adjustments or unresolved inputs that materially affect the result.
The technical owner should identify the current requirements and applicable methodology. Check the current text and refer interpretation to the appropriate specialists. Do not substitute a simplified spreadsheet for the required assessment or assume that a method suitable for one purpose applies to every ship and reporting context.
At the commercial level, focus on whether the evidence supports the decision. If a result depends on estimated input data, show that limitation. If a correction remains under review, the principal should know that the result may change before relying on it in negotiations.
Use a data-purpose matrix
The following table is an original collection framework. It helps the desk ask for the right explanation without prescribing a regulatory calculation or contractual obligation.
| Information received | Attributes to collect | Commercial use to qualify |
|---|---|---|
| Historical rating or result | Period, vessel identity and verification status | Background rather than a promise about future employment |
| Current provisional result | Included activity, reporting point and unresolved inputs | Monitoring with stated limitations |
| Future scenario | Employment assumptions and calculation owner | Comparison of proposed options |
| Contract-specific measure | Exact definition and relevant agreement | Assessment under that agreement |
| Operational data extract | Source, coverage and quality concerns | Input support rather than a final conclusion |
| Technical explanation | Method reference and material qualifications | Understanding the result's scope |
Use the matrix to prevent category errors. The same data may contribute to several analyses, but each conclusion should retain its own purpose and boundary.
Describe employment assumptions before asking for a forecast
Give the technical team a coherent proposed employment profile. Include the relevant activity, timing and operational dependencies that the team requests for its analysis. Mark uncertainties rather than presenting an optimistic schedule as a confirmed plan.
Where alternatives are being compared, keep their assumptions consistent enough to support a meaningful comparison. If an option assumes different waiting, activity or availability, show the difference. The principal should understand whether a changed forecast follows from the option itself or from an unbalanced set of assumptions.
Ask how sensitive the conclusion is to the unresolved factors. A forecast that changes materially when an uncertain operational assumption moves may need more context before it informs a commercial commitment. The desk can explain that dependency without offering its own engineering prescription.
Fictional case: a historical rating is used as a forecast
In a fictional vessel selection exercise, a broker receives a historical CII rating alongside a proposed employment programme. A colleague places the rating in a comparison table under a heading that implies expected performance during the proposed charter. No forecast has actually been supplied.
The coordinator corrects the heading and preserves the rating as historical context. It then asks the technical team for an assessment of the proposed employment, providing the assumptions and uncertainties relevant to that request. The resulting forecast is kept separate from the historical evidence.
During discussion, the parties also refer to a contractual performance measure. The desk obtains the relevant definition rather than assuming it is identical to either the historical rating or the scenario output. The principal can then see the different questions: past reported performance, expected outcome under a proposed plan and obligations under the agreement.
The case shows why more data alone is not the answer. The essential work is attaching the correct period, status and purpose to each result so the comparison does not make an unsupported promise.
Turn the evidence into a clear commercial note
Summarize what the data supports, what it does not yet establish and which assumptions matter to the proposed decision. Identify any outstanding technical clarification or contractual assessment. Avoid presenting a letter grade or single number without the context necessary to interpret it.
If the principal decides to proceed subject to a further review or agreed term, preserve that condition separately from the underlying technical result. A commercial decision does not change the status of provisional data or transform a forecast into a verified outcome.
Give the operating team the relevant information-sharing and review expectations actually agreed, without inventing obligations from a general description of CII. The current contract and applicable requirements should be checked where duties or rights are in question.
Common mistakes
One mistake is comparing historical, provisional and forecast results in the same column without labels. The figures may be useful individually while answering different questions.
Another is treating a data extract as a final CII assessment. Inputs need the appropriate calculation, context and review before the desk can describe a result accurately.
A third is assuming that a contract-specific measure and the regulatory result are interchangeable. Obtain the actual definition and assess its relevance under the agreement rather than relying on similar terminology.
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
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 a historical rating enough for a new charter decision?
It provides context about the period it covers. A proposed employment programme may require a separate forecast and commercial assessment. Label each item so the principal can distinguish past evidence from assumptions about future activity.
What should accompany a provisional value?
Identify its reporting period, included activity, calculation owner, method reference and material unresolved inputs or adjustments. The principal should know what could change before relying on the result in a negotiation or operational comparison.
Should the broker calculate regulatory CII independently?
The desk should obtain the appropriate technical calculation and explanation from the responsible function. It can check completeness and comparability of the information without presenting an informal model as the required assessment.
What if the parties use different CII figures?
Compare period, purpose, units, data coverage and definitions before assuming one is wrong. The figures may answer different questions. Refer genuine methodological or contractual disagreement to the relevant reviewers with both bases clearly described.