Monitoring Speeding in Geotab

Geotab combines NAVTEQ and OpenStreetMap posted speed data, then uses driving context, such as where the vehicle was before and where it went next, to match the vehicle to the correct road. This helps it tell a highway apart from the service road beside it.

Geotab reports that posted road speed can be relied on for about 99% of trips. A small share of roads have missing or inaccurate limits, so it is smart to double-check important exceptions before acting on them.

An exception is the record MyGeotab creates when a vehicle breaks a rule, such as speeding. An alert is the notification sent about that event. You can review every exception in reports at any time, and choose which ones also notify your team.

Yes. Rule events can be sent immediately by email or within the system to the recipients you choose. The Geotab device can also beep inside the vehicle so the driver knows right away.

No. The in-cab speed threshold is a fixed speed set on the device. Rules that compare speed to the posted limit are configured in MyGeotab.

Using both gives you the most complete coverage. The in-cab beep sets a fixed ceiling, such as a company-wide maximum, and corrects the driver in the moment. Posted-speed rules in MyGeotab show who is going over the actual limit and by how much.

Three main tools cover most needs. Trips History marks speeding events on the trip log and map. Speed Profile graphs a vehicle’s speed against the road limit. The Exceptions Detail Report lists violations for any time period and exports to Excel or PDF.

Yes. In Trips History, exclamation-triangle markers appear in the colour of the rule, and the vehicle’s path on the map changes colour wherever the rule was broken. The Speed Profile report then shows how long the vehicle was over the limit.

Yes. The Exceptions Detail Report can be pulled for any time period and exported to Excel or PDF, which is handy for managers, insurers and driver reviews.

Yes. You can build rules around how far over the posted limit a vehicle is, set a minimum speed so low-speed zones are ignored, and add time or distance conditions so only sustained speeding is flagged. For example, you might trigger only when a vehicle is more than 15 km/h over the posted limit.

No. You can switch on a built-in stock rule for a quick start, or clone it into a custom rule that matches your policy. Custom rules can be written in the plain-English rule editor or in the advanced conditions editor.

The usual cause is a threshold that is too low or a rule that flags very brief spikes. Raising the margin over the posted limit and adding a time or distance condition, such as travelling above a set speed for longer than one minute, keeps the report focused on obvious or dangerous violations.

Editing an existing rule removes its historic events, because they may no longer be valid under the new settings. You can reprocess a reasonable date range to rebuild them. Large requests are generally processed after hours, so plan ahead and ask us before changing a rule you rely on for reporting.

Yes. Rule events can be pulled into your own tools through the MyGeotab Data Feed API, in addition to being sent as email or in-system notifications.

Yes, exception reports and Speed Profile give you specific events to review with a driver, and in-cab alerts give feedback with no manager involved. Because a small share of posted speed data can be missing or inaccurate, validate any exception that could lead to discipline before you act on it.

Speeding is one of several behaviours that drive collision risk, along with harsh braking, hard acceleration and sharp cornering. The Safety Center rolls these into risk analytics and lets you benchmark your fleet against similar fleets. Start with the speeding tools, then use the Safety Center to see the bigger picture and prioritize coaching.

Yes. Our team can help you choose a sensible starting rule, fine-tune it after the first few weeks of data, and walk you through rule changes so you don’t lose reporting history by accident. Contact us to get started.