The trip, the dock window and the run — tied to the event they serve.
A trip books a dock at both ends, so the shop's yard board and the event's load-in board are two views of the same booking rather than two calendars to reconcile.
You move the gear. Two warehouses, six trucks, four events in the same fortnight, and a venue with eight dock doors and a fifteen-minute window. Every question you are asked is really the same question: where is that truck, and is it going to be there when it said.
- You work across events, not inside one
- Both ends of every run are somebody else's dock
- Your bad day is a run that is silently late
FleetOps Overview
/shows/[showId]/truckops
En route and planned runs, newest first, with the event each one serves, the driver, the ETA, the distance and the fuel. One en-route run and twenty planned is the shape of your week in a single row count.
What this module does
5 screens, and what each one is for.
Event dock board
/shows/[showId]/logistics
Trucks arriving for this event, soonest first, with ETA and dock. Trucks on the event's own board that have no trip yet are flagged 'needs trip' rather than being assumed. Drag across staging, dock and departed as the day runs.
Read the module page
Shop yard & docks
/shows/[showId]/shop
The other end of every run. Numbered doors drawn to scale, what is scheduled to arrive today, and which door each truck is on — the same booking the event board is showing from its side.
Read the module page
Truck packs
/shows/[showId]/shop
What is actually on each truck, to scale, by layer. Weight and fill are on the truck card, so 'will it fit' is answered before the run is booked rather than at the tailgate.
Read the module page
The driver's screen
/driver
What you are actually dispatching to: the trip, the destination with directions, the load list, the dock, and duty clocks. Read it before you assume a driver knows something.
Read the module page
Analytics — fleet
/shows/[showId]/analytics
On-time moves as a number with the overdue count beside it, and the recommendation that names which four runs are past their depart time and still not rolling.
Read the module page
The boundary, before you find it yourself
Half of these are somebody else's screen and half of them are things this software does not do at all. Both are worth knowing now rather than at 16:00 on a load-in day.
Live GPS
There is no vehicle tracking. Status is what a driver set and what a dock recorded.
A certified ELD
The duty clock is a helper for the hour rules. The product says so on the screen, and drivers must verify against their official log.
Booking a carrier
Outside vendors go on the board by name. Nothing here dispatches to a third-party network.
Load-in, show, load-out.
- PlanningBook the run, and with it a dock window at both ends.FleetOps · Trips & Routing
- MorningRead what is en route and what is planned but not rolling.FleetOps · Overview
- Before the runCheck weight and fill on the pack, so the truck is the right truck.ShopOps · Truck Pack Manager
- DepartureYard board shows the door emptying as the truck leaves.ShopOps · Dock / Yard
- ArrivalSet the dock on the event board; the driver's screen shows the space.Build Ops · Logistics
- Load-outThe return leg is a run in the other direction, booked the same way.FleetOps · Trips & Routing
- WeeklyOn-time moves, overdue runs, fuel and miles across the fleet.Analytics · Operations