Start with the comparison the rule makes
An event labelled speeding is a starting point for review. Before interpreting it, ask what value was compared with what reference. A fixed fleet threshold and a rule relative to a road-speed reference answer different questions. Record the selected basis and units beside the event; the label alone does not explain them.
Geotab’s official rule documentation distinguishes a defined speed threshold from conditions that compare speed with a road-speed reference. It also documents duration conditions. These are examples of that vendor’s configuration choices, not evidence that the same options exist in SafarTrak. Use them to prepare questions for the provider rather than assume matching controls.
Keep a review setting separate from road context
A threshold chosen for a demonstration is a software review setting. Ask whether any road-speed value is supplied, where it comes from and whether it is a recorded value, an estimate or a manual setting. If no road reference is available, keep it unknown. Do not fill the gap from the alert’s colour or name.
Geotab’s speeding-report documentation describes several possible road-speed data sources and says the applied source depends on availability and rule configuration. That vendor-specific distinction is useful when evaluating a proposal: ask the presenter to identify the reference used for the selected event and to state what is not covered. Do not assume any map-data supplier, update cycle or coverage for SafarTrak.
Reconstruct one event on the journey timeline
Choose an approved demonstration vehicle and a short recorded period. Write down the event timestamp and time zone, then inspect the corresponding position and available speed history. Keep the event reference with the journey reference so another reviewer can open the same evidence. A single selected value should not replace inspection of the surrounding records.
Ask what the system means by event start, event end and displayed duration. Does the rule use a sustained interval or a single observation? How are missing observations handled? Ask for the actual supported definition and mark an unanswered item unresolved. Do not infer continuous speed between sparse records or treat an unexplained gap as zero.
Separate detection from notification
For a proposed alert workflow, ask the provider to distinguish the underlying event time from any delivery or receipt time. Record who is expected to receive a notification, through which confirmed route and what evidence demonstrates receipt. A speed event visible in a journey review does not by itself demonstrate that a message was delivered to a person.
Use a provider-approved sample or existing demonstration event. Do not create a road test that requires exceeding a speed threshold, change an operational fleet rule during a sales demonstration or send test messages to real recipients without agreement. Keep any notification feature and delivery expectation unconfirmed until it has been demonstrated for the proposed setup.
Use a small acceptance record before a score
Capture the event reference, vehicle, reporting period, units, comparison basis, threshold, available duration definition, source record and unresolved questions. Mark each requirement demonstrated, unsupported or unresolved. The blank speed-rule review sheet provides fields for that conversation without including driver names, contact details or customer locations.
Review similar records under the same definitions before comparing event counts. A changed threshold, data source or available coverage can change what a count represents. The existing driver-behaviour Guide covers the wider coaching process, including context, exposure and the driver’s account; this checklist focuses on accepting the rule and evidence before that process begins.
Ask SafarTrak to demonstrate the supported scope
SafarTrak’s public platform walkthrough shows a selected speed event alongside recorded position, timestamp and speed history. Its description treats the selected threshold as a review setting. Bring the same one-event question to the platform demo and confirm the supported device, available signal, reporting intervals and workflow for your vehicles.
Keep a configurable rule editor, road-speed reference feed, notification channel, automatic corrective action and any safety outcome outside the accepted scope unless separately verified. Use the buyer evaluation kit for the wider procurement review. The useful result is a clear record of what was shown, what the proposed setup supports and what still needs an answer.
Sources and further reading
This is a buyer review checklist, not a road-speed rule or a claim that SafarTrak supports every alert configuration. Geotab documentation describes that vendor’s conditions and data sources only. Confirm supported events, timing and configuration for your own setup.
BRING IT TO YOUR FLEET
Start with your vehicles.
Ask the right questions.
Share your vehicle mix, existing devices and required signals with the SafarTrak team.
Review supported driving events in a demoDiscuss your deployment
