A tank can appear full on paper while quietly losing margin every day. This tank inventory accuracy improvement case study follows a representative fleet operation that moved from delayed paperwork and unexplained variances to accountable, transaction-level fuel records. The lesson is straightforward: a tank gauge can tell you what remains, but only controlled dispensing can explain where it went.<\/p>\n
The operation managed a mixed vehicle fleet from two depots, with a primary on-site diesel tank and a smaller petrol tank for light vehicles and equipment. Fuel was a major operating cost, yet month-end stock checks regularly produced discrepancies that nobody could confidently explain. The finance team saw a variance. The workshop saw vehicles that needed fuel. Operations saw busy shifts and no time for another administrative process.<\/p>\n
That gap between physical inventory and recorded consumption was not simply a reporting problem. It was a control problem.<\/p>\n
Before the change, drivers and supervisors accessed pumps using keys and informal local arrangements. A paper log sat near the tank, but it was often incomplete, difficult to read or filled in after the fact. Delivery dockets were retained, although they did not reliably feed into a current inventory position.<\/p>\n
The depot performed manual dip readings, usually at irregular intervals. These readings were useful as a physical check, but they could not identify whether a variance came from a missed transaction, an incorrect entry, a delivery quantity issue, unauthorised dispensing, meter calibration or a simple calculation error.<\/p>\n
The impact showed up in three places. First, fuel reconciliation consumed hours at the end of each month. Second, managers had no practical way to challenge exceptions while the details were still fresh. Third, the organisation could not confidently allocate fuel use to a vehicle, driver, cost centre or job.<\/p>\n
A common response is to install a more sophisticated tank monitor. Better level data can help, particularly where frequent deliveries, multiple products or remote sites are involved. But level monitoring alone does not establish who dispensed fuel, into which asset, at what time, or under whose authorisation. For this fleet, the priority was to secure the point of dispense and create a record automatically.<\/p>\n
The fleet introduced smartphone-authorised pump access<\/a> and cloud-based transaction logging through FluidSecure\u2122 supplied by Manage Every Drop. The equipment was configured so that the pump remained unavailable until an approved user authenticated through the app. Each dispensing event created a digital transaction record as it happened.<\/p>\n The implementation was deliberately practical. The fleet began by cleaning its asset and user lists. Vehicles that had been sold, parked or duplicated in records were removed. Drivers, supervisors and approved contractors were assigned only the access they required. Product type, site and dispensing permissions were considered separately, rather than granting broad access by default.<\/p>\n This matters because inaccurate inventory often starts with inaccurate master data. If a lorry is listed twice, a vehicle is wrongly assigned, or former staff retain access, even the best reporting will produce unreliable conclusions.<\/p>\n The team then set a simple reconciliation routine. Tank opening stock was confirmed with a physical reading. Fuel deliveries were recorded against supplier documentation and checked against the expected tank increase. Authorised dispenses were totalled from the cloud records. A closing physical reading was taken on a defined schedule, with the same measurement method and correction factors applied consistently.<\/p>\n The operating calculation was clear:<\/p>\n `Opening stock + confirmed deliveries – recorded dispenses = expected closing stock`<\/p>\n The difference between expected and measured closing stock became the variance requiring attention. Rather than waiting for a month-end surprise, managers reviewed this figure regularly. At a high-throughput depot, that may mean daily. At a lower-volume site, a weekly check may be proportionate. The right frequency depends on tank size, turnover, delivery patterns and the financial exposure of a variance.<\/p>\n The first notable result was not a dramatic claim about fuel savings. It was visibility. The fleet could see every authorised dispense in one place, including the user, asset, time, site and volume. Staff no longer needed to interpret handwriting or chase missing log sheets.<\/p>\n Early reconciliation also exposed issues that had previously been buried in a single monthly variance. One vehicle was consistently receiving more fuel than its expected operating profile suggested. Investigation found that its identifier had been selected incorrectly during several earlier manual entries. A second issue involved an after-hours refuelling practice that management had not formally approved. Once identified, permissions and procedures<\/a> were adjusted immediately.<\/p>\n Neither finding required an accusation. That is a valuable feature of a well-designed fuel control process. It replaces assumptions with evidence. Some variances point to theft or misuse; many come from weak processes, poor data discipline, delivery discrepancies or measurement error. Secure transaction data helps an operator distinguish between them.<\/p>\n The administrative burden also fell. Supervisors stopped collecting and interpreting paper slips. Finance received a far cleaner audit trail for fuel allocation and stock reconciliation. Maintenance could compare fuel use against hours, mileage and known repair events, making abnormal consumption easier to investigate.<\/p>\n Inventory accuracy improved because the operation connected four records that had previously lived apart: tank measurement, fuel deliveries, dispensing activity and asset identity. The system did not remove the need for physical tank checks. It made those checks more meaningful.<\/p>\nWhat changed in the first operating cycle<\/h2>\n
Why the process improved accuracy<\/h2>\n