How to set excessive idling rules for each vehicle group

A heavy truck parked with its engine running can burn roughly three litres of diesel an hour while covering no distance. What counts as excessive idling depends on the vehicle: an excavator powering hydraulics is working, while a delivery van outside one address for twenty minutes is not. Idle rules work when they are set per vehicle group.

What excessive idling really costs a fleet

Fuel is where idle waste shows up first, and it is nowhere near the whole cost.

A parked engine burns fuel and produces nothing in return, and fuel is usually one of the largest running costs in a commercial fleet. In RAAD, Power keeps fuel and energy on a single ledger, checking every fill against what the tank actually took, so the diesel an idle habit wastes sits on the same record as the diesel that moves loads.

Engine wear follows. Combustion byproducts build up faster at low engine speeds, and cylinder walls, bearings and turbochargers all degrade while the wheels stand still. An hour of idling ages an engine much like an hour of driving, but with no revenue kilometres to show for it, so distance-based service schedules underestimate the wear. RAAD's Maintenance module keeps inspection reminders on schedule, though the cheapest maintenance is always the wear you avoid.

Compliance adds another layer. Several jurisdictions, particularly in North America, fine prolonged idling at the kerb, and repeat offences cost more than the first. In some US states, cab comfort during a rest period is expected to come from an auxiliary power unit, a small engine that heats or cools the cab without the main one. Diesel burned at a standstill counts in carbon terms too, and RAAD's ESG module reflects it in indicative carbon reporting.

The timing problem compounds all of it. By the time an idle event reaches a weekly report, the fuel is burned, the wear is done, and the driver has no memory of why the engine ran for twenty minutes at a loading dock last Tuesday.

Why one idle threshold fails a mixed fleet

A single idle threshold treats every stationary engine the same. Stationary engines are rarely doing the same thing.

Ten minutes of ignition-on at a distribution centre may be worth investigating. Ten minutes on a site where a concrete mixer is turning its drum is completely normal. Generic idling reports fail here because they lump every stationary-with-ignition-on event together, regardless of what the vehicle is for.

The exact number of categories is not the point. Any operation that treats idling as one fleet-wide metric is missing what its vehicles actually do, and the harder job is applying group-specific rules consistently across dispatch teams, sites and regions. Once idle policy becomes a matter of local judgement, it stops being enforceable at scale.

Why after-the-fact idle reports arrive too late

Traditional idling management measures the problem well enough. Its weakness is timing.

A summary reviewed on Friday about an event from Tuesday changes very little about next week. The fuel is gone, the wear is done, and the driver has long forgotten the reason. Drivers respond far better to feedback that arrives while the engine is still running than to a coaching session weeks after a habit has repeated itself dozens of times.

Driver behaviour is rarely malicious. Engines stay running because the cab is cold or a phone is charging, or because waiting for a gate feels like just a minute. Habits form quickly where there is no in-the-moment feedback, and coaching effects decay within weeks without reinforcement. A system that only observes and reports cannot intervene, so idling stays a silent cost until the fuel invoice arrives.

How RAAD catches idling while the engine is still running

RAAD turns idle policy into live rules rather than monthly summaries, and it runs on the tracking hardware your fleet already has.

Start by finding what kind of idling you actually have: how much idle time the fleet carries, where it happens, and what should count as too much in your operation. Only then automate the response.

1. Group vehicles by role in Track: haulage, last-mile, plant, refrigerated, field service.
2. Set a threshold for each group, with explicit exceptions where engine-on is legitimate, such as sleeper-cab rest or passenger comfort.
3. RAAD watches each vehicle for ignition on and speed at zero, and tracks how long that condition persists.
4. If the vehicle moves before the threshold is crossed, the timer resets and nothing is raised. If the idle persists, the event escalates in real time: dispatch is notified and the driver gets feedback while the engine is still running.
5. Every alert passes through AI Insights, which reads it, holds back what does not need a person, and brings the rest with a reason and a proposed fix. Nothing touches a vehicle until someone approves it.
6. Trip and stop history and scheduled reports keep the after-the-fact record for compliance and coaching.

Idle behaviour also feeds the eco-driving picture in Track, so standing-engine habits count in a driver's record alongside driving style between trips instead of surfacing once a quarter.

The same pattern of a condition, a duration and a threshold sits behind other RAAD rules. A cold-storage door left open too long, or a temperature drifting out of range on the site's Sense sensors, escalates on the same logic that catches a van idling outside one address.

Keeping idle rules consistent as you scale

What makes an idle policy stick is consistency.

Once thresholds and escalation paths are set, the same rules apply across every vehicle in a group, every site and every dispatch team, without depending on someone remembering to open a report. Drivers see the same standard everywhere, and managers review exceptions rather than raw events, which keeps the policy enforceable as the fleet grows.

The structure holds for partners reselling RAAD, too. Each customer account runs its own idle rules inside its own walled-off tenant, so a delivery operator, a utilities contractor and a refrigerated transporter can each hold different thresholds on the same setup, branded and billed by the partner.

Common questions

What is a good idle threshold for a delivery fleet?

About three minutes is a common starting point, because last-mile work means constant movement between addresses, so any extended stop at a single address stands out. Long-haul is different: around five minutes is the usual starting point, with exemptions for rest in the sleeper cab.

Should a running refrigeration unit count as idling?

No. A refrigeration unit holding temperature is doing its job, and flagging it as waste trains everyone to ignore alerts. Monitor it as working equipment and apply idle rules to the cab engine, so what gets flagged is the driver waiting for a dock assignment.

How do I prove that idle rules saved money?

Compare idle minutes per vehicle and fuel used per kilometre before and after the rules go live. Trip and stop history holds the per-vehicle record, scheduled reports put the numbers in front of the right people on a cycle, and the fuel ledger shows what each fill actually bought, so the saving is measured rather than asserted.