19 October 2026

Idle vs. down: how to split them apart in a rental fleet utilization report

A single excavator sits parked and idle at dusk beside a calm lake, in silhouette.

Pull a utilization report from most rental fleet software and you'll see a single number for "non-revenue hours" or "not on rent." That number hides two completely different problems, and if you don't split them, you'll end up making the wrong call on which units to move, sell, or pull back from a branch.

Idle time is a unit sitting with nothing wrong with it. No work order, no parts on backorder, no mechanic assigned. It's just parked, fully capable of earning, waiting for a rental agreement or a dispatch that hasn't come.

Scheduled downtime is a unit that can't earn right now on purpose. It's in for a 250-hour service, waiting on a hydraulic hose, or sitting with a yellow tag because something failed an inspection. One is a utilization problem, the other a maintenance problem, and they need different people acting on them.

Idle time definition vs. scheduled downtime definition

If you're writing this into a policy or training a new branch manager, the line is simpler than it sounds:

  • Idle time: the unit is rent-ready. It could go out today if a customer called. Nothing is blocking it except demand.
  • Scheduled downtime: the unit is not rent-ready. There's a work order attached, parts on order, or a PM interval that came due. It's blocked by the shop, not by the market.

The confusion happens because both show up as "hours not generating revenue" in most billing or ERP systems, and a lot of yard software doesn't force a mechanic to log a work order the moment a skid steer gets pulled off rent for service. So the unit sits in the same status bucket as one that's just been sitting there for three weeks because nobody's called for it.

Why your current reports blur the two together

A few things cause this in practice. Telematics coverage is uneven across a mixed fleet, so engine-hour data exists for the newer compactors but not the older gradalls, and whatever's missing just gets backfilled with a guess or left blank. Work order timestamps lag behind reality, because a tech might pull a unit aside on Tuesday and not open the ticket until Thursday. And branch managers, under pressure to keep utilization numbers looking decent, sometimes let "down for repair" sit in the system longer than it should because it reads better than "idle, no demand." None of that is malicious. It's just how the data gets soft at the edges, and it means the regional roll-up you're looking at before a fleet review meeting is probably off by more units than you'd like.

The fix most ops teams reach for is a windshield survey: send someone to walk the yard, cross-reference what's parked against the work order list, and flag the mismatches by hand. It works, but it's a half-day per yard and it's stale the moment the person drives away.

A cleaner way to separate the two

What separates idle from down shows up on the ground, not in a status field. One that's been moved, loaded, or worked near will show disturbance around its footprint: tire tracks, shifted stabilizers, a different parking spot than last week. Units down for repair usually sit in the exact same spot for days or weeks, often near the shop bay or wherever they died. Idle units with no demand also sit still, but nothing's blocking them: no shop activity, no ticket, no mechanic assigned.

That's the gap Asset Utilisation Monitor is built to close for fleets that don't have telematics on every unit, or don't trust the data from the units that do. It compares a machine's position and the disturbance around it between two passes over the same yard, so you get a weekly read on which units moved and which didn't, independent of whatever the work order system says. You still need the maintenance log to tell you why a unit's down. Knowing which parked units are idle, no ticket, no excuse, is the part that's been hard to get without walking the yard yourself.

If sorting idle from down across every branch sounds like a weekly chore you'd rather not own, see how the weekly idle vs. active read works across your yards.

Join the pilot list

← Back to the blog