The situation
The operator's business ran on three disconnected rhythms. Cargo and terminal schedules were negotiated in email threads and re-typed into calendars. Trades were captured in spreadsheets that only reconciled at month-end. Field data — volumes, movements, measurements — arrived days after the fact, on paper or in photographed forms. Management's picture of the business was always days old and assembled by hand.
The problem underneath the problem
Each delay looked operational, but the cost was commercial. A deal changes exposure the moment it is struck; a delivery changes position the moment it lands. When those events take days to reach the people managing risk, every decision in between is made against stale numbers. The diagnosis priced that lag — and the platform was scoped against it.
What we built
One operations platform, delivered in milestones that each replaced a specific manual flow. Terminal scheduling came first: shared schedules with change tracking instead of email archaeology. Trade capture followed — deals entered once, at the desk, with positions computed continuously. Field reporting closed the loop: structured daily entries from site, on mobile, synced the moment connectivity allows.
The hard part
Field adoption. An operations platform is worthless if site crews keep faxing forms, and site crews have seen software fail before. The field module was designed with the people filling it in: fewer fields than the paper form it replaced, working offline by default, and visibly saving crews time from the first week. The paper form was retired by the crews themselves, not by a memo.
Results that held
The field-to-report cycle fell from days to hours, and position and exposure are now visible the moment a deal or delivery changes them. Month-end stopped being a reconstruction project, because the numbers were never days apart to begin with. The platform now carries scheduling, trade capture and field reporting for the whole operation — one system, one source of truth.