How to set a redeployment radius for an idle machine

An idle excavator sitting on a closed-out site isn't just lost revenue. Move it too far and the haul bill eats the margin on the next job. Leave it parked too close to a site that's already stocked with the same iron, and it sits another two weeks earning nothing. Fleet managers end up guessing at the radius because nobody's tracking which nearby sites need another machine class until a PM calls asking where their excavator is.

What "redeployment radius" actually means for a fleet

A redeployment radius is the distance a branch is willing to pay to move a machine between job sites, weighed against what that machine earns sitting idle versus what it costs to haul to the next one. That number changes with every job and every machine class, so treating it as a fixed rule is where most of the waste comes from. For a compact track loader, that radius might run 40 to 60 miles before the lowboy and fuel surcharge eat the margin on a short assignment. For a crawler crane, the math flips. A crane that costs several thousand dollars to mobilize only makes sense moving to a site with months of work left on it, even at 150 miles out.

The radius also depends on what's happening at the destination site right now, not what the project schedule says. A site that's supposedly in the excavation phase for another six weeks might already be down to grading and compaction work, which means the excavator you're about to haul over has nothing to do when it shows up. Schedules slip both directions. A phase that was supposed to run through October sometimes wraps in September because the crew got ahead of it, and nobody updates the spreadsheet.

How far to move an excavator between job sites

There's no single mileage number that holds across a territory, but the inputs that should drive the call stay the same:

• Haul cost per mile for that machine class. A skid steer on a trailer costs a fraction of what a 50-ton excavator costs to move with a permit and escort.
• Remaining idle cost at the origin site. If the machine's already sat three weeks, the radius can stretch further, because the alternative is zero revenue, not reduced revenue.
• Confirmed phase at the destination, not the schedule date. A site still in mass excavation needs excavators and haulers. A site that's moved into finish grading needs compactors and smaller gear. Hauling the right class the wrong distance wastes a trip. Hauling the wrong class any distance wastes it worse.
• Return-trip odds. If the destination site is likely to need the same class again for a second phase, a longer radius pencils out better than a one-way move does.

Branch managers running this by instinct tend to default to "whatever's within an hour of the yard," because that's the radius they can picture without checking anything. That works fine in a slow territory. It leaves money on the table when three sites inside that hour already have the same machine class sitting idle, and a site forty miles out has a crew waiting on an excavator that hasn't shown up.

Why site phase changes the radius math

The real constraint is knowing, before you book the haul, what's parked on the destination site today. A schedule says a job entered dirt-moving in August. That doesn't mean the site still needs an excavator in October. If a smaller sub already brought their own machine, or the job moved faster than planned into forms and pours, the radius you'd have paid for in August isn't worth paying for now.

That's the gap Site Machine Mix is built to close: a monthly read of which rental and OEM machine classes are sitting on a site at its current build phase, so a redeployment call gets made against what's on the ground instead of a static project calendar. Once you can see which nearby sites are genuinely short a machine class, the radius stops being a guess tied to drive time and starts being a number tied to actual demand.

Running a handful of sites in your territory through that kind of monthly read is a reasonable way to find out whether your current radius assumptions still hold.