Define the disagreement before judging the number
A driver remembers a dashboard reading, while a fleet reviewer sees a different number in a report. Before deciding that either is wrong, write down what each number represents. Is the report showing a selected observation, an average or a maximum over a period? Does the dashboard observation refer to that same moment? A pair of unlabeled values is not yet a like-for-like comparison.
Use this checklist when evaluating fleet software or raising a data question with your provider. Keep the speed-reading question separate from the rule that labels an event. The existing speed-alert article covers thresholds, references and duration conditions; this review starts earlier, with the measurement behind the displayed value.
Ask where each reading came from
Record the vehicle, device and proposed source of the report value. Ask whether it is derived from positioning data, supplied through a supported vehicle interface or calculated in another documented way. A diagnostic connection does not by itself establish which signal the report uses. Keep an unverified source unresolved rather than infer it from a product name.
GPS Insight distinguishes its GPS-derived speed values from optional vehicle diagnostic speed and documents different report definitions. That is a vendor-specific example of why source and definition both matter; it does not establish SafarTrak calculations, sampling rates or diagnostic coverage. Ask the presenter to identify the source of the actual field being demonstrated.
Align the unit, moment and reporting period
Write the unit beside both values. Record the observation time, time zone and the interval covered by the report. A remembered dashboard observation and a report maximum for a whole journey are different evidence. Ask for an approved recorded example whose vehicle, period and displayed field can be identified by another reviewer.
Ask what the report means by instantaneous, average or maximum if those labels are offered. GPS Insight documents distinct meanings within its own reporting intervals. Do not transfer those definitions to another system, assume the last value is the maximum or reconstruct continuous speed from records that do not establish it. Where the timing or definition cannot be shown, mark the comparison incomplete.
Keep uncertainty separate from a fault finding
Geotab notes that sources of error in speed and other vehicle measurements depend on the device model. Use that caution to ask for the limitations that apply to the proposed setup; no accuracy figure from that vendor establishes the accuracy of another device. A difference alone does not identify its cause.
Preserve the original references and describe the discrepancy without assigning blame. If an instrument fault is suspected, refer it to the appropriate vehicle service or equipment provider. A fleet report, dashboard photograph or consumer navigation display is not a calibration certificate. This worksheet sets no permissible error or acceptance tolerance.
Use recorded evidence, not a distracted road test
Start with provider-approved demonstration records or evidence already obtained through the organisation’s approved process. Do not ask a driver to watch, photograph or operate a screen while driving, exceed a threshold or change operational device settings to manufacture a comparison. Agree any separate technical test with the responsible vehicle or equipment team.
The blank review sheet has fields for the reading reference, source, unit, timestamp, reporting interval, aggregation definition and open question. Keep driver names, contact details and customer locations out of public worksheets. Record demonstrated, unsupported or unresolved for each requirement; a blank field should not become a guessed value.
Bring a precise question to the SafarTrak demo
SafarTrak’s published platform walkthrough shows speed history with a selected event, position and timestamp. Ask the team to demonstrate the supported speed field for your vehicle and device configuration, explain its time basis and identify any comparison that remains outside the available evidence. The public walkthrough does not establish a universal dashboard match or an ECU-speed signal for every vehicle.
Use the wider driver-coaching Guide for contextual review and the data-quality Guide for broader acceptance. This checklist answers a narrower buying question: can the team explain what the proposed speed reading represents and reproduce the comparison before relying on it? Keep the answer open until the relevant evidence has been demonstrated.
Sources and further reading
This buyer checklist does not calibrate a speedometer or establish which reading is accurate. Vendor examples describe their own systems. Confirm the available speed source and report definition for your actual SafarTrak setup.
- Download the blank speed-reading comparison sheet (CSV)
- GPS Insight: speed sources and reporting definitions (vendor example)
- Geotab: device-specific data validation limitations (vendor example)
- Check the rule behind a speed alert
- Review the wider driver-coaching process
- Evaluate supported fleet workflows
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.
Discuss supported speed-reading evidenceDiscuss your deployment
