How diesel leaks from construction fleets — fuel log gaps, litres-per-hour and ₹/km benchmarks by machine type, and a driver accountability system that works.

Diesel is the second or third largest cost head on most Indian construction sites, and the least supervised. Cement is counted in bags and locked in a store; steel is weighed on arrival; diesel is pumped from a barrel into a machine by the same operator whose consumption nobody checks. Industry estimates put fuel leakage — theft, siphoning, inflated logs, and idle burning — at 10 to 20 percent of fleet fuel cost on unmonitored sites. At ₹90-plus a litre, a site spending ₹8 lakh a month on diesel may be donating ₹1–1.5 lakh of it. This article covers how the leakage actually happens, the consumption benchmarks that expose it, why fuel logs alone fail, and the accountability system that closes the gap.

Where Diesel Actually Goes

Knowing the mechanisms matters, because each one defeats a different control:

Direct siphoning. Fuel drawn from machine tanks overnight or during refuelling — a few litres per machine per day, sold to the roadside market that exists near every major site.
Short delivery. The bowser or barrel that arrives with 180 litres billed as 200. Without dip measurement or flow-meter readings at receipt, the loss is invisible at the gate.
Inflated issue logs. The register shows 60 litres issued to the excavator; the tank got 45. The operator and the storekeeper reconcile perfectly, because they wrote both numbers.
Idle burning. Engines idling through lunch, machines kept running to power nothing, air conditioners on in parked tippers. Not theft — but 2 to 4 litres an hour of pure waste per machine.
Private use. Tippers making unlogged trips, the site pickup running personal errands — diesel plus wear, off the record.

No single control stops all five. Reconciliation does — litres in versus work out, machine by machine, week by week.

Benchmarks: What Your Machines Should Burn

Leakage hides in the absence of expectations. Publish expected consumption for every machine class, and deviations become conversations. Reasonable working benchmarks for machines in average Indian site conditions:

Backhoe loader (JCB 3DX class): 4 to 6 litres per hour in normal excavation duty
20-tonne tracked excavator: 12 to 16 litres per hour; heavy rock or long-swing duty runs higher
Tipper (16–25 tonne GVW): 2.5 to 4 km per litre loaded on haul roads — roughly ₹25–38 per km in fuel at current prices
Transit mixer: 1.8 to 2.5 km per litre plus drum consumption on site
Motor grader: 10 to 15 litres per hour working
Vibratory soil compactor: 8 to 12 litres per hour
Diesel generator: roughly 0.25 to 0.3 litres per kVA per hour at realistic load — a 125 kVA set near 25–30 litres an hour at load, and watch sets that "consume" at full-load rates while running lights

Treat these as starting points, not gospel — terrain, machine age, and duty cycle move them. The benchmark that really matters is each machine against its own history: an excavator that burned 13.2 litres an hour for three months and now burns 16 has a story to tell, and it is rarely a mechanical one.

Why Fuel Logs Alone Fail

Every site already has a fuel register, and the leakage happens anyway, because a log without reconciliation is theatre:

Issues are recorded against machines, not against output. Sixty litres to the excavator — but nobody writes down the hour-meter reading at issue, so litres per hour can never be computed.
Receipts are taken on trust. Bowser quantities accepted from the delivery challan, no dip, no meter.
The log and the work never meet. Fuel data lives in the store; hour meters and trip counts live with the plant department; the DPR lives with the site engineer. The three are reconciled never.
Month-end totals hide daily patterns. A monthly diesel number 8 percent high triggers a shrug; the same 8 percent shown as one machine, every Tuesday, triggers an inspection.

The fix costs one column: record the hour-meter or odometer reading at every fuel issue. That single discipline turns a custody log into a consumption record — litres per hour and per km, by machine, by operator, computable daily.

The Accountability System

Fuel discipline is 20 percent measurement and 80 percent consequence. The system that works on Indian sites:

One issue point, one custodian. All fuel through a metered pump or measured barrel issue, logged at issue time with machine, operator, hour-meter reading, and litres — into a system, not a notebook, the way fleet & mobility captures it against each vehicle's file.
Receipts measured, not assumed. Dip the bowser before and after, or meter the transfer, and reconcile against the supplier invoice. Short deliveries stop when suppliers know you measure.
Operator-wise consumption published weekly. A board — physical or dashboard — showing litres per hour by machine and operator against benchmark. Nothing changes operator behaviour faster than their number, with their name, next to their peers' numbers.
Exception review, not blanket suspicion. The weekly fuel meeting looks only at deviations beyond a tolerance band — say 10 percent off the machine's own baseline — and every deviation gets one of three explanations: duty change, mechanical issue, or unexplained. Two unexplained weeks means the machine gets locked to supervised fuelling.
Close the loop with GPS and telematics where the fleet justifies it: geofenced movement, trip counts against tipper logs, engine-hour capture, and fuel-level sensors on high-burn machines. Telematics does not replace the human system — it makes lying to it uneconomical. The full picture of vehicle tracking is covered under fleet management.

What the Numbers Look Like When It Works

Run the arithmetic for a typical mid-size site fleet — two excavators, two backhoe loaders, six tippers, a grader, a compactor, and two DG sets, burning around 9,000 litres a month, call it ₹8.3 lakh:

Cutting a 12 percent leakage to 4 percent recovers roughly ₹66,000 a month.
Idle-hour discipline — switching off at breaks, no phantom DG loads — typically saves another 3 to 5 percent of burn.
Short-delivery control on 20,000 litres a quarter at even 2 percent recovers ₹35,000 a year by itself.

Across a company running five such sites, that is ₹40–50 lakh a year — recovered not by buying anything, but by measuring what is already being bought. Put your own fleet numbers through the ROI calculator and see where you land.

Start This Week

You do not need sensors to begin. Three moves, effective immediately: add the hour-meter column to the fuel issue log and make it non-negotiable; dip-measure every fuel receipt; and publish last week's litres-per-hour by machine on one sheet at the Monday meeting. The first anomaly usually surfaces within ten days — and the deterrent effect starts the day the operators see the sheet. Once the manual loop holds for a month, decide where telematics earns its cost: start with the highest-burn machines and the tippers with the longest unsupervised hauls, because that is where the residual leakage concentrates.

Diesel leakage survives on one belief: that nobody is looking. Stop deserving that belief.

Book a ProjectSathi demo at /contact to see machine-wise fuel reconciliation and exception alerts running on live fleet data.