Every van, every skill tag, every minute — on one board.

Position is captured while a technician is clocked into a shift, and it exists to answer one question: who can reach this site soonest. It is not retained as a movement history, it is not visible outside dispatch, and it stops when the shift ends. Ontario employers have obligations under the ESA's electronic monitoring disclosure rules; Novel Systems ships a written monitoring policy template you can adapt rather than leaving you to draft one.

Yes, on every axis except certification. Distance, capacity, and priority are advisory — a dispatcher who knows the site can overrule all three. The certification gate is the one that does not bend, because that is the one that shows up in an insurance claim.

Subcontracted crews are modelled as technicians with their own certification set and their own rate. They see only the work orders assigned to them, and their close-out artefacts land in the same billing queue. Their utilisation is tracked separately so it never distorts your own capacity picture.

The mobile client holds the full work order locally. Photos, notes, part consumption, and the signature are written to a local queue and pushed on reconnect, in order, with conflict resolution favouring the field record. A technician never has to remember what they did in a basement.

The figures shown here come from a deterministic model — road factor, blended speed, per-stop overhead — so the same inputs always produce the same estimate. Live traffic is available through the Google Maps Platform integration, which replaces the model's travel term with observed conditions while leaving the stop overhead intact.

Booked windows are a constraint on the schedule, not a promise the system makes on your behalf. If a van will miss its window, dispatch surfaces the conflict before the technician leaves the previous site, and the customer notification carries the revised arrival rather than the original booking.