Planning
The dispatch module plans the fleet's work for a given day: it collects customer jobs into a pool, sequences them into routes through an optimizer that is aware of the driver's remaining legal hours and the state of charge of electric vehicles, then assigns the route to a specific driver and vehicle. Every assignment passes through gates that keep an unroadworthy vehicle or a driver without valid credentials from being sent out.
Who uses it
The dispatcher plans and assigns routes day to day; the fleet manager and organization administrator share the same management rights. The compliance specialist and executive have read-only visibility into the dispatch board. The driver sees only their own route and its ETA (see Driver workflows).
Key concepts
- Job — a customer visit: a location, a service time window, a duration, a demand on vehicle capacity, and optionally the credential types the assigned driver must hold (e.g. ADR). A job sits in the pool until it lands on a route.
- Dispatch gate — a check run when a driver and vehicle are assigned to a route or job; depending on the organization's configuration it either blocks the assignment or lets it through with the violation recorded as a warning.
- State of charge (SoC) — the battery charge level of an electric or plug-in hybrid vehicle, factored into route planning.
The job pool and dispatch board
The dispatch board shows a chosen day: planned routes with their current status, assigned driver and vehicle, last known telematics position, and — separately — the pool of jobs that have not yet landed on a route and whose time window touches that day. You create and edit jobs from the jobs tab, giving a location, time window, service duration, capacity demand and any required credentials.
Route optimization
The optimizer sequences stops with a nearest-neighbour heuristic that respects vehicle capacity and each job's time window — waiting on site if it arrives early, skipping a job (and leaving it in the pool) if the window can't be met. Once a driver is assigned, the plan accounts for their remaining hours: it inserts a mandatory break before the driving limit would be exceeded, and flags the whole plan infeasible if it still overruns the driving, duty-window or cycle limit (see HOS clocks and duty status). For an electric or plug-in hybrid vehicle the plan also inserts a charging stop before a leg that would drop the charge below the configured floor — a long-enough charging stop doubles as the driving break too. A plan that still can't be closed out is saved anyway, with explicit warning codes (capacity exceeded, time window missed, HOS or charge infeasible), so you see exactly what needs attention.
Assignment gates
Assigning a driver and vehicle to a route or job runs through gates before it's saved. The system checks that the vehicle is roadworthy — a vehicle with an open safety defect is not (see Inspections and DVIR) — and that the driver holds a valid driving licence plus every credential the job requires. By default a violation of either gate blocks the assignment; an organization can configure a warn mode where the assignment goes through and the violation is recorded as a warning visible on the board. Reassigning a different driver or vehicle to the same route supersedes the previous assignment and runs through the same gates.
In the background
A successful assignment immediately fires a "route assigned" notification to the driver — in the app and as a push notification.