Drayage dispatch board & loop builder
Stage 2 · Dispatch & Drayage Operations
P1Core Operations
Four-Lane View
Software Function
- ›Chained-leg assignment engine (dray → transload → outbound → empty repo) Chassis/TWIC/UIIA eligibility filtering at assignment time LFD/per-diem clocks on every container; exception surfacing Street-turn matcher (SIA) before empty return
Service Provider / Admin
- ›Dispatchers manage by exception — the board self-builds legal, eligible assignments Corridor balance dashboard: import vs outbound density (the loop lives or dies here) Named human owns every exception — support with authority (anti-Uber)
User — Driver / IOO
- ›Sees the whole week, not one load: 4 legs, all loaded, ending at the port Accept/decline with full pay math per leg and per week Per-diem clock visible — knows when dwell starts earning dispute evidence
Customer — Client / FF / NVOCC
- ›Container status from vessel to door without calling anyone Exceptions flagged by us before the client knows (appointment rebooked, chassis split resolved, $0 demurrage)
Software Function
- ›Chained-leg assignment engine (dray → transload → outbound → empty repo) Chassis/TWIC/UIIA eligibility filtering at assignment time LFD/per-diem clocks on every container; exception surfacing Street-turn matcher (SIA) before empty return
Competitors
PortPro (best-in-class single-leg dray dispatch), Trinium (enterprise depth), DrayNow (ramp marketplace)
Differentiation
They optimize a load. We optimize a tractor’s week — the loop is dispatched as one unit with balance engineered on both sides of the corridor.
Make It Better
First dispatch system where deadhead is a monitored KPI with a target (~10% vs ~30% industry) — because the loop, not the match, is the product.