This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Overview
The commercial file need not duplicate every technical record. It should identify the responsible source and preserve the links needed to understand what the principal relied upon, while the designated technical and regulatory functions maintain the records required for their roles.
Key takeaways
- Keep the metric's definition, period and status beside the result.
- Preserve the input and method references supporting each material version.
- Distinguish corrected actual data from revised future assumptions.
- Link commercial decisions to the result actually available at that point.
- Follow reviewed retention and access requirements without inventing a universal period.
Preserve the identity of the result
A value labelled CII is incomplete without its context. Record the vessel, metric name, units, period and whether the result is historical, provisional or forecast. Identify the calculation owner and the basis for any description of verification status.
If the result serves a contractual purpose, preserve the definition and agreement reference used for that purpose. If it serves an operational planning exercise, preserve the scenario description. These records may share inputs while answering different questions, so their labels should remain distinct.
Avoid allowing a later result to inherit an earlier status automatically. A revised provisional calculation is not made final by being saved in the same folder as a historical verified record. Each version needs its own status and relationship to the earlier information.
Link the result to the input set
The record should identify which input dataset was used and who controlled it. Keep relevant coverage, source and quality notes with the dataset reference. If the commercial team does not hold the detailed technical records, preserve an appropriate controlled route to the responsible owner.
Record material exclusions, adjustments or unresolved inputs as described by the technical reviewer. Do not invent the technical rationale or simplify it into a conclusion the reviewer did not make. The commercial purpose is to preserve the basis of reliance accurately.
Where an input is corrected, identify the affected period and reason, then link the recalculated result to the correction. This helps distinguish an improved understanding of earlier activity from a change in current operations. Both can move a reported value, but they have different explanatory histories.
Keep method changes distinguishable from data changes
A result can change because the underlying facts changed or because the calculation basis changed. The file should let a reviewer identify which occurred. Preserve the relevant method reference and any explanation from the calculation owner about comparability with the previous version.
Check the current text and obtain appropriate technical advice where methodology or regulatory requirements are material. The coordinator should not decide that two methods are equivalent simply because they produce similar values in a particular case.
The same principle applies to commercial models. If the desk changes a forecast assumption, retain the old assumption and the reason for the update. Do not describe the resulting movement as measured improvement unless the evidence actually supports that statement.
Use a result-to-reliance index
The following table is an original record design. It focuses on traceability rather than prescribing a statutory record list.
| Record element | Relationship to retain | Later question it answers |
|---|---|---|
| Result identity | Vessel, metric, period, units and status | What exactly was the displayed value? |
| Input dataset | Source version and coverage | Which observations supported it? |
| Method reference | Calculation owner and relevant basis | How was the result produced? |
| Quality note | Missing data, estimates or corrections | What limitations were known? |
| Forecast scenario | Assumptions and proposed employment | What future activity was modelled? |
| Review response | Question and scoped conclusion | What did the specialist assess? |
| Commercial decision | Result version and principal's direction | What did the principal rely upon? |
The index can point to controlled systems rather than copy all data into a voyage folder. What matters is that the references remain specific and retrievable after a file update, staff change or system migration.
Fictional case: the corrected file replaces the decision basis
In a fictional chartering exercise, the principal compares employment options using a provisional result supplied by the technical team. Later, a historical input is corrected and the team issues an updated calculation. The file link in the commercial note opens the new version, while the old version is no longer visible.
A colleague reviewing the decision assumes the principal had the corrected figure from the start. That creates an inaccurate account of the decision even though the current technical result is correct. The problem is the missing version relationship, not the correction itself.
The team restores the historical reference and links it to the correction and recalculation. The commercial note explains whether the principal reconsidered the option after receiving the update. The current operational record uses the new result, while the historical decision record preserves the information available at the earlier point.
The case shows why retaining only the most accurate current file is insufficient for explaining past reliance. Both the correction and the earlier evidence have a distinct role in the record.
Retain forecasts as scenarios rather than outcomes
A forecast should remain attached to its employment assumptions, timing and unresolved dependencies. If the proposed activity never occurs, preserve that fact when the scenario is used later for comparison. A forecast should not quietly become part of an actual-performance history merely because it was the last available model.
Where a decision relied on a forecast, record the relevant uncertainty and any sensitivity explanation supplied by the technical team. The principal's acceptance of a proposal does not convert those assumptions into verified facts.
If actual performance is later compared with the forecast, identify the differences in activity and data basis. The comparison may be useful, but it should not attribute every gap to technical performance when the employment itself differed from the scenario.
Govern access and disposal deliberately
CII-related files can combine technical data, commercial assumptions and contractual advice. Apply access according to the purpose and sensitivity of the material. Operations may need the current agreed reporting expectations, while a reviewer investigating a discrepancy needs the calculation history.
Retention periods and any preservation restrictions should follow the applicable requirements and reviewed policy. Check the current text where regulatory reporting, contractual disputes or other legal considerations matter. This article does not provide a universal storage period or substitute for the technical record obligations applicable to the vessel.
Before archiving, test a real decision. An authorized reader should be able to identify the result, supporting dataset, method, limitations and principal's reliance without guessing which file version was intended.
Common mistakes
One mistake is retaining only the latest dashboard. It may show the best current information while concealing the basis of an earlier decision.
Another is separating a forecast from its assumptions. The number can then look like a promise or measured outcome rather than a scenario under stated conditions.
A third is describing every change as a performance trend. Preserve whether the movement followed new activity, corrected data, revised assumptions or a different calculation basis.
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
Must the broker store all technical input data?
Not necessarily. The commercial file should preserve a specific, controlled route to the relevant evidence and identify its owner, version and scope. The designated technical and regulatory functions should maintain the records required for their responsibilities.
Should a superseded result be deleted immediately?
Follow the applicable retention policy and requirements. A superseded value may still explain a material decision. Preserve its status so it cannot be mistaken for the current result while retaining the relationship needed for historical reconstruction.
How should a corrected dataset be recorded?
Identify the affected period, correction reason, source and resulting calculation version. Link it to the superseded record and note any commercial review prompted by the change. Do not overwrite the historical decision basis without explanation.
What makes the archive useful in a disagreement?
It should reveal the exact metric, period, inputs, method, limitations and agreement or decision context. That allows technical and contractual reviewers to address the real discrepancy rather than debate values whose origins are unclear.