Project cargo, run from one control tower.
Assigned consignments, leg-by-leg progress, inspection and customs status, exception handling and landed cost — in a workspace the buyer and supplier see at the same time, with every update logged and attributable.
Eight views, one shared version of events.
Project freight goes wrong in the gaps between parties. The control tower removes the gap: the same record, the same status and the same evidence for the forwarder, the supplier and the buyer.
Delays, held consignments, failed inspections and documentation gaps surfaced as a ranked queue with the affected package and its consequence attached.
Every consignment by state, with the responsible party named, so nothing sits without an owner.
Leg-by-leg timeline from collection through port, sailing, discharge and inland move. No map to interpret — a sequence with dates.
Pre-shipment and on-arrival inspection status, with the report held as the evidence for the milestone it supports.
Declaration and clearance status per consignment, with the documents that clearance depends on visible in one place.
Freight, duty, handling and insurance built up per consignment, reported separately in sterling and euro. Currencies are never summed together.
Confirmed and provisional bookings against port windows and vessel availability, so a slipped window is visible before it becomes a delay.
The delivery schedule against site readiness, sequenced so heavy-lift arrivals match the installation programme.
Break-bulk, heavy lift and IMO-class cargo.
The workflow reflects how project freight actually moves — not a parcel model stretched to fit a transformer or a battery container.
Exception handling
An exception is raised against the consignment, routed to a named owner and closed with a recorded resolution. Nothing is resolved by conversation alone.
Sailing & port windows
Vessel, port window and discharge sequence tracked per leg, with slippage visible against the original plan rather than replacing it.
Inspection as evidence
Inspection reports attach to the milestone they support, so an acceptance decision points at the document that justified it.
Customs documentation
Bills of lading, certificates of origin and packing lists exchanged under version control, so clearance never waits on the current revision.
Landed cost build-up
Cost components captured per consignment and reported in sterling and euro separately, with the basis of each component recorded.
Delivery sequencing
Arrivals aligned to the installation programme and site readiness, with the consequence of a moved date made explicit.
Inland movement
The final leg tracked with the same rigour as the sailing, including escorts, route constraints and access windows.
Damage & claims
Damage, shortfall and deviation raised on a shared timeline across supplier, forwarder and buyer, with evidence held against the claim.
A logistics event is a payment event.
Delivery milestones are the evidence that releases money. A failed inspection or a missing certificate of origin does not simply delay a consignment — it holds a milestone, and the funds behind it, until the position is resolved.
Because the control tower and the contract workspace are the same system, that consequence is visible to everyone at the same moment, and closing it out is a recorded action rather than an email.
Open the control tower on a live lane.
We will configure one of your current project lanes and show the exception, inspection, customs and landed-cost views against it.