Collision risk data gaps
Moving a device or changing your database can cause temporary gaps in your safety reports. See why your data may be missing and what steps you can take to resolve it.
MyGeotab is designed to keep your safety ranks fair. When you make a change, MyGeotab may pause new data for a short time on the Collision Risk page. This keeps old driving data from mixing with your new data. It also ensures your reports stay accurate after you move a device or switch databases.
Why are certain assets or databases missing from my reports?
Some assets or databases may not appear in Collision Risk if they do not have enough data or use restricted settings.
An asset is active in MyGeotab but does not appear in Collision Risk reports or benchmarks.
MyGeotab excludes certain devices to keep your fleet data accurate. An asset or database may be missing if it meets any of these conditions:
Low activity: The asset has not driven at least 50 km in the last 7 days.
No communication: The device has not sent data to MyGeotab in the last month.
New database: The database is less than one month old.
Privacy: The device is set to Restricted Data Mode.
Device type: The asset uses an OEM, third-party, or FedRAMP device.
Small fleet: The database has fewer than two active devices.
- Check your device settings to make sure they are not in Restricted Data Mode.
- If your database is new, wait until the one-month mark for data to appear.
- Make sure your assets drive at least 50 km each week to stay active in reports.
Why did my collision risk data disappear after a device swap or move?
Safety ranks may show as N/A immediately after moving a device between assets or databases. See when MyGeotab finishes processing your new data and calculates your collision risk ranking.
Collision risk data shows as N/A immediately after moving a device to a new asset or a different database.
Moving a device pauses data for a set time. This prevents data from the old asset from mixing with the new one. If you move a device to a different database, MyGeotab resets the data for that day to keep the new data separate.
- Wait 7 days for asset swaps. You will see no data for either asset during the week of the move. Data returns once MyGeotab has a full week of new driving data.
- Wait 24 hours for database transfers. Data will start recording in the new database the day after the move.
- Make sure the asset drives at least 50 km during the first week to help MyGeotab build a new profile.
Why are my driver ranks different across multiple databases?
Driver safety ranks can look different in separate databases if the setup details do not match. Align your asset assignments to see the same data everywhere.
A driver has a high safety rank in one database but shows a different rank, or no rank at all, in another database.
Driver data stays inside each database and does not move between databases automatically. To see the same ranks everywhere, your setup must be the same in every database.
- Assign the driver to the same assets in every database (through the Assets page).
- Allow 24 hours: It may take a full day for driver ranks to align across all your databases.
Why are fleet benchmarks missing when I use multiple databases?
Fleet-wide benchmarks will not appear if a database owns fewer than two assets. Check if your assets are owned or shared to fix missing benchmark data.
You can see collision risk data for drivers or assets, but the fleet benchmark shows as N/A or does not appear.
MyGeotab handles data differently depending on whether a database is the primary database that owns the asset or a shared database that only sees the data.
Asset ownership: MyGeotab only uses assets owned by a specific database to create fleet benchmarks. It does not include assets shared from another database.
Minimum asset count: A database must own at least two assets to create a fleet benchmark. MyGeotab needs this minimum to accurately analyze fleet traits like asset types and the work the fleet does.
- Check ownership: Review the settings for each asset to see if it’s owned or shared.
- Add owned assets: You must own at least two assets in that specific database to see fleet data. If you own fewer than two, the benchmark will be unavailable.