Skip to content
    Industry Insights

    How to coordinate outbound mining cargo across rail, port, and vessel

    May 29, 20266 min read

    Outbound bulk cargo loses margin to demurrage and missed laycans in the handoffs between rail, port, and vessel. Here's how to coordinate the chain that no single party owns.

    A unit train of copper concentrate leaves the mine on schedule, bound for the port two days out. What the mine doesn't know yet is that the vessel chartered to load it has slipped its berth window — congestion at the terminal pushed the laycan back 36 hours. The rail cars arrive faster than the port can stockpile them, the terminal runs short on laydown space, and the vessel, when it finally berths, runs into a slow load. Two clocks are now running against the cargo: detention on the rail cars that can't cycle back, and demurrage on a vessel that's waiting. The commercial team committed a laycan to the offtaker weeks ago. Nobody connected the rail dispatch to the live vessel ETA and the stockpile capacity — so the first time anyone sees the full picture is when the demurrage invoice lands.

    This is where outbound mining margin quietly leaks. The product is sold, the price is set, and the cost erosion happens entirely in the handoffs between the parties moving it to the customer.

    Why outbound is harder to coordinate than inbound

    Bulk carrier demurrage runs into the tens of thousands of dollars a day, and on a single missed berth window it can erase a meaningful slice of the margin on a cargo that was priced and sold months earlier. That's the exposure. The reason it keeps happening is structural: an outbound commodity flow passes through more independent organizations than almost any inbound one. The mine controls production and rail dispatch. A rail operator controls the line and the car cycle. A port or terminal controls berths, stockpile space, and load rate. Stevedores control the actual loading. A shipping line controls the vessel and the laytime clock. The offtaker holds a contract with a laycan window and quality specs. Each runs its own system, on its own clock, and no one of them can see the whole chain.

    When those parties coordinate by phone, email, and shared spreadsheets — which is still the norm — the chain only moves as fast as the slowest handoff, and the clocks that cost real money start running before anyone with the authority to act even knows there's a problem. The teams that protect outbound margin don't take over the rail line or the terminal. They build a single line of sight across parties who otherwise can't see each other. Here's how.

    1. Put the whole chain on one timeline

    Demurrage and detention are timing failures, and timing failures come from watching the pieces separately. The first move is to bring the rail ETA, the stockpile level, the berth window, the vessel ETA, and the contracted laycan onto one timeline keyed to the cargo. When the train dispatch, the terminal's available laydown, and the vessel's real arrival sit in the same view, a 36-hour berth slip becomes something you see while the train is still loading — not something you discover when the cars can't cycle. One timeline turns a string of independent schedules into a single plan you can manage.

    2. Synchronize rail dispatch to vessel reality, not the schedule

    Rail is usually dispatched to a plan set days earlier, against a vessel ETA that was already stale when it was written. The discipline that prevents the most expensive pile-ups is dispatching to the vessel's live position and the terminal's real capacity, not the original schedule. If the vessel has slipped, holding a train or metering the cars to match the berth keeps cargo from arriving into a terminal that can't take it. That single adjustment — moving product to where it can actually be received, when it can be received — is often the difference between a clean load and a yard full of detained cars.

    3. Watch the demurrage and detention clocks before they start

    Most operations learn what laytime cost them when the statement of facts is reconciled and the invoice arrives, weeks later. By then it's an accounting exercise, not a decision. The clocks are predictable: notice of readiness, berthing, load rate against the charter party's terms, rail car free time. Tracking them live — and flagging when a cargo is trending toward demurrage or a rail set toward detention — turns a back-office reconciliation into an operational alarm you can still act on. Knowing you're four hours from the demurrage clock starting is worth far more than knowing, a month later, that it ran for two days.

    4. Keep the cargo documents moving with the cargo

    Outbound bulk doesn't just move tonnes — it moves paper, and the paper can stop the tonnes. Weighbridge tickets, assay and quality certificates, bills of lading, certificates of origin, customs and export clearance: a missing or late document can hold a load at the terminal or a vessel at the berth just as effectively as a physical delay, and the clock keeps running while everyone waits on a PDF. Treat the document chain as part of the shipment, with the same visibility and ownership, so a cargo is never sitting loaded-but-uncleared because a certificate is stuck in someone's inbox.

    5. Give the exception an owner across company lines

    The hardest part of outbound coordination is that the exception almost always sits in the space between organizations. A slipped berth is the terminal's event, but the detained rail cars are the mine's cost and the offtaker's late cargo. When the problem belongs to everyone, it belongs to no one, and it drifts. Assign explicit ownership the moment a high-cost exception is raised — who is accountable for resolving it, with a deadline tied to the laycan or the car free-time — and make that ownership visible to every party in the chain. Coordination across company lines only works when one named person is driving the response and everyone can see who it is.

    6. Measure where the margin actually leaks

    Most mines track production tonnes and freight rate closely and the coordination cost barely at all. Put numbers on the leak: demurrage and detention paid per cargo, laycans missed, average rail car cycle time, hours of berth idle waiting on cargo or documents. Once that cost is visible by lane and by cargo, the pattern usually concentrates in a few predictable handoffs — and that's where a small coordination improvement returns more than another rate negotiation ever will.

    What to do Monday morning

    Take your last three cargoes and reconstruct the timeline of each: when the train dispatched, when the vessel actually berthed, when loading finished, what the statement of facts showed, and what demurrage or detention you paid. Mark the moment the cost became unavoidable — and then mark the moment someone could first have seen it coming. The gap between those two moments is your opportunity, and it almost always lives in the handoffs between rail, port, and vessel that no single party owns. You don't need to control those parties to close the gap. You need one line of sight across them.

    How Orkestra fits

    Building that single line of sight across modes and parties is exactly what Orkestra does. Rather than replacing the rail, terminal, and shipping systems each party already runs, Orkestra connects above them — normalizing rail, port, and vessel status into one timeline per cargo, tracking the laytime and detention clocks live, and routing an exception to a named owner before a slipped berth becomes a demurrage invoice. Seeing the whole chain is what keeps the margin you already sold.

    It's the pattern behind Matalco's work to unify its supply chain data and make smarter carrier selection decisions with measurable financial impact — a metals producer turning fragmented outbound logistics into one coordinated flow.

    Get full visibility — Book a demo.

    Continue reading

    Trusted by leading supply chain teams
    MatalcoOIA GlobalKingsdownDBWMatalcoOIA GlobalKingsdownDBW
    DLAIllyLevitt SafetySquareInstoreDLAIllyLevitt SafetySquareInstore
    TAKE THE NEXT STEP

    Action breaks down when operations are disconnected.

    Orkestra gives teams one place to see what matters, coordinate the response, and move operations forward.