Published 2025-11-27
Decide what will change before you fit anything
A rollout with no named decision attached to it produces a system everyone can see and nobody uses. Before installation, agree two or three specific things that will be done differently once the data exists — a weekly exception review, a monthly fuel reconciliation, an arrival notification process.
Those commitments determine which reports matter, which alerts are configured, and who needs an account. Without them, configuration defaults to everything, which is indistinguishable from nothing.
Tell drivers first, and tell them plainly
Drivers learn about vehicle tracking whether or not they are told. Finding out by accident reliably produces the worst version of the conversation.
State what is recorded, what it is used for, who can see it, and how long it is kept. Where private use is permitted, state how it is treated. Clear answers given in advance cost nothing and remove most of the resistance.
Stage the rollout
Fit one depot or one vehicle type first. Run it for a few weeks. The configuration you end up with will differ from the one you designed, and it is much cheaper to discover that across twenty vehicles than across two hundred.
- Pilot a single group and let the configuration settle
- Review the first month's alerts and switch off the noisy rules
- Give each role only the reports it will actually read
- Set a review date three months out, and keep it
Review the configuration, permanently
Fleets change: depots open, contracts end, vehicle classes shift. A configuration that was right at go-live drifts. A short quarterly review of zones, rules, users and scheduled reports keeps the system matched to the operation it is supposed to describe.