Most fleets record litres, cost and perhaps an odometer reading. That is useful for accounting, but it is not enough to establish what happened when fuel quality, theft, consumption or supplier performance is questioned.
A defensible fuel-event record links the person, vehicle, supplier, place, transaction, test and decision in one traceable workflow.
The control point is the refuelling event
Once the vehicle leaves, evidence becomes harder to reconstruct. The driver may not remember the pump, the receipt may be lost, photographs may not exist and the fuel may already be mixed with the vehicle’s existing tank contents. The strongest record is therefore created before the vehicle continues.
What the event should identify
- driver and supervisor where applicable;
- vehicle, trailer, equipment and trip reference;
- supplier, depot or service station;
- GPS location, date and timestamp;
- odometer or hour-meter reading;
- litres, unit price and total transaction value;
- receipt, invoice or pump-display photograph;
- DensiTest result and test photograph; and
- exception, escalation or approval status.
Why compulsory testing matters
If drivers test only when fuel looks suspicious, the control is inconsistent and vulnerable to hindsight. The FuelGuard Fleet model treats rapid DensiTest verification as a required step at every participating diesel refuel. The event is not complete until the required evidence is submitted.
Supplier accountability
Comparable records allow management to review patterns by supplier, location, route and vehicle. A single anomaly may require investigation; repeated anomalies associated with one source create a stronger basis for supplier engagement or escalation.
Fuel theft and consumption anomalies
The evidence trail also supports non-quality controls. Location, route, odometer, litres and receipt evidence can highlight unauthorised stops, duplicate transactions, improbable volumes or consumption that falls outside expected performance.
Maintenance and insurance investigations
When pumps, injectors or engines fail, maintenance teams need more than a driver statement. A chronological fuel-event history can help identify recent suppliers, affected vehicles, shared routes and available samples. It does not prove causation, but it materially improves the investigation.
Escalation should be defined in advance
Drivers and supervisors need a clear rule for what happens when the test or evidence is abnormal:
- stop the event or prevent departure where safe and permitted;
- notify the designated supervisor;
- retain the fuel sample and transaction evidence;
- record observations and any repeat test;
- quarantine or isolate the risk where possible; and
- obtain confirmatory laboratory analysis when required.
Core proposition: every refuel is tested, photographed, geolocated and recorded before the vehicle continues.
Start with a pilot
Select a controlled group of vehicles, routes and suppliers. Define the evidence checklist, train drivers, measure compliance and refine the exception process before scaling across the fleet.
Explore the FuelGuard Fleet Fuel Integrity model or request a fleet pilot discussion.
By FuelGuard
