Where the margin is made, and where it quietly goes
Four capabilities carry the commercial weight of the system: the charter chain, the cost stack inside an estimate, the hours gained at sea, and the claims book. Each one is a place a trader-operator either keeps money or loses it on paperwork.
Where a trader-operator’s margin quietly goes
A position is not a list of voyages. It is a set of chains, tonnage taken in on one set of terms and employed out on another.
The margin lives in the spread. The risk lives in the places where the two sets of terms are not the same. Capacity is set before the chain is drawn: a vessel carries one flag, principal or agent, from the moment it enters the system.
As principal
The desk owns the spread and the chain holds, whether the top link is an outside owner or the owning entity.
As agent
The desk sits beside the chain rather than in it. The owning entity contracts and carries the voyage, and the estimate returns a commission instead of a spread.
Time charter in
Eleven to thirteen months, speed and consumption warranted, redelivery worldwide within trading limits. On internal tonnage the same link is an internal charter on the same fields, with a wider envelope and a related counterparty.
Employs the vessel
Carries the gap between what the tonnage costs and what the employment earns, plus every term that does not pass through cleanly.
Voyage charter out
Laytime and demurrage terms, a separate claim time bar, its own emissions allocation clause. The spread lives between this link and the one above it.
Hours gained at sea, value kept on the desk
Contract speed and speed over ground are not the same thing. The gain disappears into anchorage time unless somebody is watching for it.
Six steps, all running on data the system already carries
- 1
Baseline
Contract speed, estimate, reported arrival, laycan and berth context
- 2
Observe
Speed over ground, track, distance remaining, current and weather
- 3
Predict
Arrival against the commercial baseline, with a confidence range
- 4
Accrue
Predicted and realised hours posted to the voyage and vessel ledger
- 5
Watch
Stationary and anchorage periods after an early arrival
- 6
Act
Alert the trader, assemble the evidence, propose the follow up
Hours gained against the commercial passage baseline, by voyage
Who owns the hours is a chain question
On tonnage taken in on time charter the desk pays for every day, and the gained time belongs to the desk. On a voyage charter out the time belongs to the owner. In a three link chain the answer differs by link, so the ledger records the hours against the link that actually carries them.
Early is not automatically valuable
If the berth was never going to be free, arriving twelve hours early converts sea time into anchorage time and burns fuel for nothing. The useful output is a decision rather than a number. Where the gained time has no commercial use, the recommendation is to slow down and bank the fuel.
A ledger that counts every early arrival as a win will be dismissed by the first owner who reads it.
The ledger, so the desk holds a history rather than anecdotes
Predicted hours
Continuously updated from progress, remaining distance and the weather and current context that explains it.
Realised gain
Actual arrival against the agreed commercial baseline, stored per voyage with the baseline version used.
Stationary time
Anchorage and non-movement after an early arrival, logged separately from passage time.
Fuel value
Avoidable consumption during unnecessary waiting, priced at the grade actually burned.
Time value
Hours translated into hire-equivalent or freight-equivalent value, per the link that owns them.
Rolling accrual
Voyage, month, quarter and lifetime totals by vessel, owner, manager and route.
Navigation stays with the Master. Maintenance is context, not workflow.
The platform recommends a commercial review, such as discussing speed and arrival alignment or the use of gained time. Speed, routing and safety decisions remain with the Master and inside the charter party. If a vessel is stationary and the reason given is onboard work, the platform records the reason as context and stops there.
Entitlement, quantum, admissibility
Three separate fights. Most systems help with the second, which is the one that was never really the problem.
Where calculated entitlement goes on the way to the bank
- 1
Entitlement
Was the notice valid, and did laytime commence.
- 2
Quantum
Allowed against used, with the exceptions applied.
- 3
Admissibility
Served in time, with every required document.
The claimant is a field. Who contracts, who prosecutes and who is paid are three separate things. On an agency voyage the owning entity is claimant, the desk serves in that name, and the recovery posts to the owner’s account.
The clause is the rule
The calculation executes the wording in this charter, and states which clause it applied and which events it relied on.
The pack is the claim
The document set is derived from what the clause requires rather than from a generic checklist, and gaps are chased while they can still be closed.
The clock is absolute
Every bar date is derived from its own clause and escalated as it approaches. A bar missed on a claim held for someone else is a liability, so that fuse is shorter.
The argument is predictable
Sensitivity analysis shows which entries the counterparty will attack and what each is worth, before the claim is served rather than after.
Three positions, one set of facts
On a relet the desk is claimant on one link and respondent on the other, frequently on the same port call. On an agency voyage it is neither, it is the handler, and the same events produce a claim in the owning entity’s name. CapeSize holds one set of events and produces every position from it, which is also the only honest way to see the net.
The intelligence layer sits behind a gate
Twenty five years of fixture history is the one asset no vendor can sell and no competitor can copy. It is also the part of the programme with the largest gap between what it could be worth and what can be promised before anyone has looked at the data.