Preserve the exception before interpreting it
A falling line on a fuel chart is a reason to review the evidence. It does not establish theft, a leak or driver misconduct. Save the original readings and their timestamps, the review time, units and vehicle reference. Keep the incident open until the responsible team has checked the available evidence.
Start a review note with what is observed and what remains unknown. Write “reported fuel level changed” rather than naming a cause that has not been established. Restrict access to operational records through your normal business process.
Identify what the value measures
Ask whether the value is a sensor reading, a vehicle-reported percentage or an estimate. Confirm the units and conversion method for this installation. Teltonika documents calibration for analog fuel inputs; Samsara distinguishes fuel percentages from other vehicle statistics. These are provider examples, not proof of the signals available in a SafarTrak deployment.
A percentage change cannot be converted into a reliable litre loss by assuming a generic tank capacity. Ask the installer or provider to explain the actual measurement and conversion before calculating a quantity.
Check the sequence and the surrounding records
Compare several readings before and after the exception. Check position time, fuel time and receipt time where available, using a consistent time zone. A gap in records leaves a period without evidence; it does not mean consumption was zero.
Use the normal dispatch log to establish whether the vehicle was parked, travelling, refuelling or undergoing service. Confirm whether readings settle afterwards and whether other signals also show gaps. Preserve contradictory evidence and avoid editing data to fit the first explanation.
Review calibration and installation history
Ask whether there was a recent sensor replacement, wiring change, tank change or recalibration. Request the calibration record and the configuration version from the authorised installer. Compare the affected vehicle with vehicles using the same setup only when their measurement methods are comparable.
Have the qualified installer assess suspected measurement faults using the vehicle and sensor instructions. An operations review should not improvise fuel handling or wiring tests.
Separate evidence from the decision
Record each possible explanation, the evidence supporting it and the information still needed. An illustrative case might show a drop across a connectivity gap followed by a stable series. That observation warrants checking the missing period; it does not establish when or why a physical change occurred.
Agree who owns the review, the next check and a follow-up time. Follow established emergency procedures if a physical fuel leak or other immediate hazard is suspected. Otherwise retain an unresolved status until the available evidence supports a conclusion.
Make future exceptions easier to review
Build a short review sheet containing signal source, units, timestamps, surrounding records, calibration reference, operational context and owner. Use an agreed exception rule demonstrated on representative vehicles, rather than copying a threshold from a different fleet.
Bring this sheet to a SafarTrak deployment review and ask which readings and history are supported for your vehicle, device and configuration. Use the fleet data quality acceptance guide to test the evidence before relying on it in daily decisions.
Sources and further reading
Manufacturer documentation illustrates vehicle-specific coverage. It does not establish compatibility for a SafarTrak deployment.
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.
Explore fuel review workflowsDiscuss your deployment