14 October 2026

How to prioritize which yards to inspect first when fleet data is missing

A rusted, weathered motor grader sitting abandoned in a field of tall dry grass.

If you run fleet ops across a dozen or forty branches, you already know the uncomfortable math: telematics tells you what's moving at maybe 60-70% of your yards, and the rest is a shrug. Acquired fleets, older iron bought before anyone speced a box on it, third-party rental-return units sitting on your lot. The gap doesn't close on its own, and you can't send a regional manager to walk every yard every week just to find out which units haven't turned a wheel since spring.

Ranking yards by where the gaps and dollar value sit turns an impossible full sweep into a short list of five or six branches worth the drive this month.

Why a blanket inspection schedule doesn't work

A fixed rotation, every yard every quarter, treats a 400-unit mega-yard the same as a 15-unit satellite lot. It also assumes the problem is evenly spread, which it isn't. A branch that just absorbed an acquisition has a much bigger blind spot than one that's been running the same core fleet for five years. And the manager who calls every Friday asking why utilization numbers look off is telling you something a spreadsheet won't.

Treating inspections as a calendar task instead of a triage problem is how idle units sit for months before anyone notices.

A simple scoring method for triage

Rank yards on four things you likely already have, even if it's never been pulled together in one place:

  • Size of the data gap. What share of units at that yard report telematics at all? A yard at 40% coverage needs eyes a lot sooner than one at 90%.
  • Dollar value sitting there. A small yard with three idle excavators can outweigh a big yard with twenty idle compact loaders. Rank by the replacement value of the non-reporting units at each yard.
  • Time since last physical check. If nobody's walked that lot in six months, it moves up regardless of anything else.
  • Field noise. Complaints about availability, customer escalations, a branch manager who keeps asking for more units when the yard "should" have capacity. That's usually a sign something's parked that shouldn't be.

Score each yard 1-4 on those and add them up. You'll end up with a short list of five or six branches that need attention this month, not a forty-stop tour that takes a quarter to complete and tells you nothing about what's idle today versus what was idle when the survey started.

Where a first pass before the drive helps

The part that eats the most time in this process is the windshield survey itself: someone drives to the yard, walks the rows, and tries to remember what was parked where last visit. It's slow, it depends on who's doing the walking, and by the time the report's written up the picture's already a week old.

A faster way to run the first pass is to compare the yard from above between two dates and let ground disturbance around each unit tell you what's been moved and what hasn't. Asset Utilisation Monitor does exactly that: a weekly map layer showing idle versus active units per location, built from the same VHR imagery passes, no telematics box required. It doesn't replace the person who eventually walks the lot to confirm condition and decide what gets sold or redeployed, but it tells you which of your scored yards have idle iron worth the trip, and which ones can wait another cycle.

For a multi-yard fleet running partly blind, that's the difference between inspecting on a schedule and inspecting where the problem is.

Getting started

Start with the scoring exercise above using what you already track in your fleet management system. Once you've got your short list, see which of those yards show up with idle units on the next imagery pass before you book the drive.

Join the pilot list

← Back to the blog