This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Overview
The check should help the principal understand the decision's dependencies. It does not replace the vessel's technical assessment, regulatory process or safe operational judgment. The commercial desk's contribution is a clear account of the proposed employment and the basis on which the parties intend to rely.
Key takeaways
- Compare the final plan with the forecast's actual assumptions.
- Keep historical evidence, current provisional data and future scenarios distinct.
- Identify changes in timing, activity or dependencies before relying on the outlook.
- Assess contractual questions under the actual agreement.
- Give operations a clear direction and defined reporting expectations.
Start with the employment that is actually proposed
Prepare the current commercial plan, including the activity and timing relevant to the technical review. Identify uncertain elements, such as a provisional schedule or an operational dependency awaiting confirmation. Do not present the most favorable possible sequence as the established plan.
Retrieve the scenario or assessment the principal is considering. Compare its assumptions with the current proposal, noting differences explicitly. A forecast can be internally correct yet answer the wrong question if negotiations or operational arrangements changed after it was prepared.
The comparison should be proportionate. If the plan remains within the assessed assumptions, preserve that basis. If a relevant fact differs, ask the technical owner to explain the effect rather than rerunning unrelated onboarding work or drawing an unsupported conclusion from the change alone.
Confirm the starting data and result status
Identify the current baseline used in the forecast and whether any input correction or calculation update remains pending. The principal should know if the scenario rests on provisional data that could change. A recently issued file is not necessarily a final result.
Keep the historical rating or result separate from the outlook for the proposed activity. Historical information may provide context, but it should not appear as a promise about the future plan. Similarly, a contract-specific measure should retain the definition and period relevant to the agreement.
Ask the calculation owner to confirm the appropriate method and scope. Check the current text where regulatory methodology matters. The coordinator should not substitute a simplified commercial calculation for the required technical assessment or label a forecast as verified merely because it has been reviewed internally.
Compare the assumptions that drive the decision
The following table is an original pre-voyage comparison tool. It identifies questions for the responsible reviewers without prescribing a technical solution.
| Assumption in the assessment | Final-plan comparison | Question if different |
|---|---|---|
| Activity described | Proposed service and employment now intended | Does the scenario still address the plan? |
| Timing and sequence | Current schedule and dependencies | Which changed assumptions affect the outlook? |
| Starting data | Latest appropriate baseline and corrections | Is the forecast using the right input version? |
| Operational option | Option the principal is actually considering | Has its feasibility been assessed appropriately? |
| Contractual measure | Definition and period in the actual agreement | Is the result relevant to the commercial question? |
| Information sharing | Process the parties actually agreed | Who supplies which update and when? |
| Decision authority | Principal's instruction and limits | Is the desk authorized to propose or commit? |
Do not mark a row complete merely because a document exists. The evidence should answer the comparison question and retain any material qualification.
Evaluate the trade-off without optimizing a single label
A commercial option may affect timing, cost, operational dependencies and the CII outlook differently. Present those dimensions together with the relevant technical input. A more favorable forecast does not automatically make an option operationally feasible or commercially preferable.
Where the principal is comparing options, keep the assumptions aligned and show what remains uncertain. If one scenario assumes an availability or timing advantage that has not been confirmed, label it. The decision maker should not confuse an optimistic scenario with a developed alternative.
Avoid making operational recommendations beyond the desk's role. The master and designated technical or operational teams must address the relevant feasibility and safety questions. The broker or coordinator can help ensure their assessments concern the same proposal that the commercial team is discussing.
Fictional case: an assumed short wait becomes uncertain
In a fictional fixture evaluation, the technical team prepares a CII outlook using a stated employment sequence. The commercial comparison assumes a short waiting period based on provisional information. Before commitment, the receiving arrangement becomes uncertain, but the favorable forecast remains in the proposal presentation.
The coordinator identifies the changed dependency and asks the calculation owner to assess the revised assumption. It does not assert that the changed wait produces a particular rating or contractual outcome. The principal receives an updated explanation of what the forecast depends on and which information is still missing.
The commercial team also checks whether the proposed arrangement includes any relevant agreed reporting or cooperation process. It does not assume that a general discussion about CII creates authority to vary instructions or impose costs on another party.
The eventual direction is linked to the final plan and its remaining conditions. The case illustrates why a pre-voyage review should test the assumptions behind an attractive result, rather than merely confirm that the result appears in the file.
Reconcile the agreement with the intended reliance
If the parties propose to use a CII-related measure or process commercially, obtain the actual wording and identify the decision it governs. Similar terminology does not prove that a regulatory result, forecast and contractual measure have the same purpose.
Refer questions about rights, duties, remedies or changes to orders for the appropriate assessment. A technical outlook can inform those discussions, but it should not be presented as an automatic authority to alter the arrangement. Check the current text and the final agreement rather than a model clause remembered from another fixture.
Record the principal's mandate for any negotiation. Permission to explore an alternative is different from authority to agree a new target or vary an obligation. The desk's communications should preserve that distinction.
Hand over the assumptions that remain active
Give operations the direction relevant to its work and the information-sharing expectations actually agreed. Identify which change should return to the technical or commercial review: a revised activity, timing dependency, input correction or altered contractual proposal.
Keep the supporting scenario and result version accessible to authorized users. A colleague receiving a late update should be able to understand which assumption it affects without reconstructing the whole fixture discussion.
If a condition remains pending, state the required evidence, responsible reviewer and affected act. Do not convert a forecast update expected later into an answer already received. The final review should make uncertainty usable for decision making rather than hide it behind a completed status.
Common mistakes
One mistake is using the most favorable scenario without checking whether its assumptions describe the final plan. The calculation may be sound while the intended reliance is not.
Another is treating a historical result as the expected outcome of a future charter. Keep period, status and purpose visible in the comparison and handover.
A third is letting a technical forecast create an implied contractual instruction. The principal's authority and the actual agreement need separate consideration before the desk communicates a commitment or variation.
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
Should the final review calculate CII again?
The responsible technical function should determine what calculation or update is needed. The commercial desk should identify changed facts and ensure the scenario used for the decision matches the final proposal, with method and data status appropriately explained.
Can a favorable forecast justify a voyage instruction?
It can inform the principal's assessment alongside operational feasibility, commercial considerations and the agreement. It does not independently establish authority or replace the relevant technical and safety judgments.
What if the final schedule remains uncertain?
State the uncertainty and ask the technical team how it affects the outlook. The principal should see the dependency before relying on the forecast. Define which later confirmation or change requires renewed review.
What should a broker record before handover?
Record the final proposal, result version, material assumptions, outstanding questions, principal's direction and agreed reporting expectations. Keep links to the technical and contractual assessments so their scope remains visible.