Sit next to a chartering broker in London or Piraeus in 2015 and you'd see a Bloomberg, three phones, a stack of position lists faxed from correspondent offices, and a whiteboard. Sit next to one in 2026 and you see a laptop, a phone, a browser tab with a live tonnage feed, and a Slack channel with the ops team.
What changed on the desk
The workflow itself hasn't changed much — cargo comes in, tonnage gets matched, an indication is worked, a fixture is concluded, laytime and demurrage get calculated after the voyage. What has changed is the tooling under each of those steps.
Position lists are now aggregated live. A broker in Kigali or Karachi can see, within a few minutes' latency, roughly the same open-tonnage picture as one in London. That structurally lowers the return on being physically located in a traditional broking centre. The desk of the next decade is smaller, more distributed, and much younger — because the barrier to running a credible desk from anywhere with good internet has fallen dramatically.
Where the human still owns the trade
Everything upstream of the fixture — reading the counterparty, judging whether an owner will actually perform at the indicated rate, sensing when a market is about to turn — is still a human trade and always will be. The tools compress the mechanical work so the human can spend more time on the parts that can't be compressed.
The concierge model
One structural change worth naming: cargo owners increasingly want a broker who acts as a concierge across the fixture, not just an intermediary who introduces tonnage. That means the desk owns the process from cargo posting through fixture documentation, laytime confirmation and post-voyage settlement — not just the initial match. Our own Charter Concierge Desk was built around exactly that expectation, because the counterparties on our platform kept asking for it.
The younger, more digital desk is not less serious than the one it replaces. It's more accountable, because more of the workflow is visible. And it's more scalable, because a small team with good tools can now cover a book that used to require twice the headcount.
Open a UbuntuLogistics workspace or talk to our team about the corridors you actually run.