From Fixture to Final Settlement: The Commercial Voyage Workflow Explained

The six stages, and where each one leaks

A voyage is not a transaction. It is a chain of commercial promises, operational events, documents, calculations and approvals, handed between five or six teams that rarely share a system. The final result is set less by the quality of any single stage than by the quality of the hand-offs between them.

Mapped end to end, the chain looks like this:

Each row is a place where information changes hands and loses fidelity. The rest of this article works through them in order.

1. Opportunity and voyage estimation

Before a fixture, the commercial team evaluates cargo, vessel suitability, route, port costs, bunkers, duration, freight, commissions, weather and risk. The estimate is a decision model, not a guarantee.

The discipline that matters is versioning the assumptions, not refining the arithmetic. A voyage that returns less than the estimate is only useful information if you can still see what the estimate assumed. Six weeks later, the question is never "what did we estimate?" — it is "which assumption was wrong?"

• Bunker price and consumption at the assumed speed and load, with the source and date of the price used.
• Port costs by port, distinguishing tariff-derived figures from an agent's estimate.
• Laytime allowance and expected turnaround, which is where most estimate-to-actual variance originates.
• Weather and seasonal margin applied to the passage, stated as a number rather than absorbed silently into speed.

Keep the estimate as a record, not a spreadsheet that gets overwritten by the next opportunity.

2. Negotiation, subjects and fixture

The brokered negotiation produces offers, counteroffers and subjects. Once the essential terms are agreed, a fixture recap records the commercial understanding pending the full charter party.

Clean transfer from recap to the operational record is the single highest-leverage control in the whole chain. A recap is written for speed, in commercial shorthand, often at the end of a long day. The operations team then re-keys it. Small transcription errors at this point can affect notices, laytime, freight or claims months later, and they are extremely difficult to detect once downstream documents have been built on top of them.

The fields worth double-checking on every recap, because they carry the most downstream consequence:

1. Laytime allowance, whether it is reversible, and the demurrage rate.
2. Whether the charter is berth or port, which determines when a Notice of Readiness can validly be tendered.
3. The exceptions to laytime — weekends, holidays, weather, shifting — in the exact wording agreed.
4. Freight terms, payment timing and commission percentages.
5. Laycan, and the cancelling provisions attached to it.

Subjects deserve their own status. An opportunity that is "fixed on subjects" is not fixed, and treating it as fixed in the operational record produces a class of error that is expensive and entirely avoidable.

3. Handover to operations

Operations turns a commercial promise into an executable voyage. The team confirms instructions, contacts, certificates, cargo details, port requirements, agents, bunker plans and reporting expectations.

A structured handover distinguishes three categories that are usually collapsed into one document:

Where a handover fails, it almost always fails because an assumption was passed downstream wearing the clothes of a confirmed fact.

4. Voyage and port-call execution

The vessel and shore team exchange ETAs, noon reports, notices, instructions and port documents. Agents coordinate clearances and services. Changes in weather, congestion, berth availability, cargo readiness or vessel performance can alter the plan quickly.

Every material event needs three attributes, and an event missing any of them is weak evidence: time, source and context. "Vessel arrived" is not a record. "NOR tendered 06:12 LT 14 March, by master via agent, vessel at anchorage awaiting berth" is.

The events that later carry the most commercial weight are the least glamorous: arrival at the pilot station, anchoring, NOR tender and acceptance, berthing, hoses connected, commencement and completion of cargo, and every stoppage with its stated reason. Capture them as they happen. Reconstructing a timeline from an email thread three weeks later is how claims are lost.

5. Laytime, demurrage and claims

The Statement of Facts, Notice of Readiness, charter-party clauses and supporting documents form the evidence base. Laytime is calculated according to the contract, not intuition.

Exceptions, stoppages and time bars must be handled carefully. Most charter parties impose a time bar on demurrage claims, and the clock generally runs from completion of discharge — not from the moment somebody notices there is a claim. A well-founded claim submitted without its supporting documents, after the bar, is worth nothing.

• Assemble the supporting file during the call, not when the claim is raised.
• Reconcile the agent's Statement of Facts against the master's own record before signing anything.
• Record letters of protest with the event they protest, not as loose attachments.
• Diary the time bar the day the voyage completes.

A transparent calculation reduces avoidable disagreement. Where the facts or the legal meaning are genuinely disputed, human review is not optional — see our guide to demurrage and laytime for the mechanics.

6. Freight, disbursements and final settlement

Finance reconciles freight, hire where relevant, commissions, bunker adjustments, port disbursements, claims and other voyage costs. The quality of settlement depends entirely on the quality of the operational record that preceded it.

Two habits separate a closed voyage from an abandoned one. The first is reconciling the final disbursement account against the pro forma line by line, with variances explained rather than absorbed. The second is preserving the reasoning alongside the numbers: why a claim was settled at that figure, why a cost was accepted, which assumption in the original estimate proved wrong.

Closing a voyage should produce something the estimation team can learn from. In most companies it produces a number in a ledger and nothing else, which is why the same estimating errors recur for years.