All guides

Five configuration faults that ruin reporting

Most MyGeotab databases we look at have the same handful of faults. None of them stops the system running, which is why they go unnoticed. All of them quietly change what your reports say.

1. Groups that no longer match the business

How to spot it: run a report by depot or team and look for vehicles you know are in the wrong place, or a large "everything else" group at the top of the tree.

The fix: agree a group structure that matches how you actually run the fleet, by depot, team, region or cost centre, then move every vehicle and user into it. Write down who is allowed to change it.

2. Devices named by serial number

How to spot it: reports list vehicles as strings of letters and numbers, and people keep a spreadsheet to translate them.

The fix: give every vehicle a name your team uses, such as a fleet number or registration, and record it properly when a device moves to a new vehicle.

3. Missing zones

How to spot it: open one vehicle's stops for last week. If your own depot or regular job sites show as unknown locations, the zones are missing or drawn in the wrong place.

The fix: draw zones for depots, yards and the sites you visit often, and keep them current as sites open and close.

4. No driver identification

How to spot it: trip reports show a vehicle but no driver, or the same default driver on every trip.

The fix: choose a driver identification method that suits how your vehicles are shared, set it up, and make it part of how drivers start a shift. If it's awkward, drivers won't use it.

5. Rules with the wrong thresholds

How to spot it: exception reports run to hundreds of lines a week and nobody reads them, or one rule produces most of the alerts.

The fix: set thresholds that suit your vehicles and your work, switch off rules nobody acts on, and check the volume again after a month.

Why these faults keep coming back

A clean set-up drifts. New vehicles arrive, staff change, sites open and close, and each change made in a hurry adds a little more noise. Fixing the five faults once helps. Keeping them fixed needs someone to own the set-up from month to month.

Related service

Where this fits

Free data health check

Start with a free health check

The health check looks for these five faults, and others, in your own database. You get a two to three page written report on your top five problems, then a 30-minute call. It's free, and it's not a sales pitch.