Move it: planning, dispatch, and the tracked haul

A booked load is a promise. This group keeps it: the load is built, a second wallet approves the dispatch, the movement runs by mode, and every milestone and exception lands on the shipment record where the shipper can see it.

Load Planning — the accepted bid becomes a load

The plan takes the order reference and the winning bid and builds the physical load: load number, equipment type, weight and volume, consolidation (a full truckload for one shipper, or freight consolidated across orders), planner and plan date. Plans move Draft → Optimising → Planned → Tendered → Confirmed, with Replan required as the exception when the freight changes under the plan. Load LD-2601 was a single-shipper full truckload — no consolidation — confirmed the day before pickup.

Dispatch Board — no truck rolls on one signature

Dispatch assigns the load: carrier, driver, vehicle, dispatch time and ETA, moving Planned → Assigned → Dispatched → Completed, with Reassigned and Stood down for the days that don’t go to plan. In the canonical workflow, dispatch is also the control point: the workflow holds for a second wallet’s approval before the haul proceeds — the dispatcher who planned the load is not the only signature on it rolling. On ORD-2601 the approval was held and decided on the record, and the dispatch completed with the delivery.

Transportation Management — the movement, by mode

The movement record is mode-neutral on purpose: the same fields carry a truck on the QEII, an air waybill’s flight, or a vessel’s sailing — carrier, lane, vehicle / flight / vessel, driver / master, departure and arrival. Movements run Booked → Tendered → Assigned → Departed → Arrived → Completed, with Delayed and Cancelled as exceptions. Land, air and sea are one discipline with three vehicle vocabularies, which is why this module — not three separate ones — anchors the suite.

Shipment Tracking — milestones and the exception

Tracking carries the shipment’s story: milestone, location, event time, temperature where it matters, and the exception note. Its states run Booked → Picked up → In transit → At hub → Out for delivery → Delivered, with Exception, Delayed and Held as the states that make tracking honest. The exception is a state, not a comment: on ORD-2601, at 11:15 the tracking record moved to Exception — “winter storm slowdown, QEII near Red Deer” with the corridor note and a revised ETA — and back to In transit at 12:30 when the cell passed, before Delivered at 14:20. The shipper’s own view showed the same exception from the same record at the same time. A driver who slows for a storm is doing the job properly; the record says so, and nobody downstream has to guess.

Route Optimization — lanes and corridors

Routes are records, not habits: lane, origin, destination, mode, distance, transit days, and the corridor notes — the GIS layer of the suite, where what is known about a corridor lives. Routes move Draft → Optimised → Approved → Active. The Edmonton–Calgary record carries 299 km via Highway 2 and the note that mattered on the day: the Highway 2A alternate held in reserve when the storm cell crossed. When the exception came, the decision — proceed at reduced speed rather than divert — was made against this record and written onto the tracking record.