26 October 2026
Rebalancing your rental fleet across branches before storm season

Storm season doesn't wait for a clean inventory count. By the time the first named storm is tracking toward the coast, branch managers in the affected region are already calling around asking who has spare generators, trash pumps, and light towers sitting in a yard somewhere doing nothing. The branches that handle this well know, a week or two ahead, exactly which units are idle and where, no matter how big or small their fleet is.
The problem most fleets run into is that this knowledge lives in people's heads, not in a system. Telematics covers the newer skid steers and the compact track loaders. It doesn't cover the pump trailers, the towable generators, the light towers that have been sitting behind the wash bay since March. Those are exactly the units that matter most when a storm is three days out and every branch in the path wants the same gear.
Start with what's actually idle, not what's supposed to be
Most branch transfer planning starts from the wrong document: the fleet roster, sorted by branch. That tells you what's assigned somewhere, not what's working. A unit can sit on a branch's books for two years while it's parked behind a dumpster the whole time, and nobody flags it because nobody's driving past that corner of the yard.
Before you build a pull list, you need an honest picture of idle versus active, branch by branch, across the whole footprint, not just the branches you already suspect are sandbagging equipment. Yard managers will tell you their inventory is tight right up until a regional ops call puts eyes on it from outside. Ground truth beats the spreadsheet every time, and increasingly that ground truth doesn't require someone walking every row with a clipboard. A weekly pass over each yard, matched against where units sat the week before, flags which ones haven't moved. That's the shortlist you start calling branches about.
Generators and pumps move first, and they move differently
Generators and pumps get prioritized ahead of earthmoving equipment for a simple reason: they're smaller, they're trailer-mounted or skid-mounted, and a single flatbed or tag-along can carry three or four units in one run instead of needing a lowboy per machine. That makes them the fastest category to rebalance once you know where the idle ones are sitting.
The sequence that works for most regional operations looks like this. First, pull the idle list for every branch within a day's drive of the forecast track, not just the ones in it, because demand spreads out as the storm moves inland. Second, sort by unit type and get a rough count of generators, pumps, and light towers per branch. Third, call the branch managers with specific unit numbers, not a general ask for "spare equipment," because a specific ask gets a faster yes. A branch manager who's told "your two idle 20kW towables" will release them faster than one who's asked to go find something.
Timing matters more than people plan for. Transfer requests that go out 48 hours before landfall compete with every other branch's requests and with fuel and logistics constraints that get worse as the storm gets closer. The branches that run this well start the rebalancing conversation five to seven days out, while roads are still clear and drivers aren't already committed to evacuation hauls.
Keeping the idle picture current after the first wave
A single rebalancing push before the storm isn't the end of it. Units come back from job sites mid-storm as projects pause, and some of that returning gear sits idle at the receiving branch for days before anyone notices it's available for a second wave of deployment. The same weekly idle-versus-active view that built the first pull list should keep running through the response, so a branch that ends up holding returned pumps nobody's logged shows up again instead of sitting on equipment nobody asked about.
If your fleet has gaps in telematics coverage, which most mixed fleets do, Asset Utilisation Monitor builds that idle-versus-active picture from imagery instead, flagging which units have sat untouched between weekly passes so branch transfers get built on what's actually parked, not what's assumed to be busy. Take a look at how the weekly idle map works for your branch network.