The cheapest hour of hire is the one you don't need. The trick is knowing when that hour is. Projects move through rhythms - start-up, peak and run-down - and your fleet should move with them. This guide shows how to right-size across the life of a programme so machines are either busy or gone, never parked "just in case."
Phase 1: start-up - set the tempo without overloading the yard
- Pick multipurpose heroes. Early days favour versatile machines that can switch tasks quickly - materials in, access, light lifts - while you learn the site's quirks.
- Stage the right attachments. A rotating fork carriage, a hook and a platform close most early gaps without a second hire.
- Plan a short review window. After the first week or month, check what really got used, where you were short, and what never moved.
Phase 2: rise to peak - focus on throughput and sequencing
- Protect the workhorses. If one machine runs hot all day, keep it close to the workface and remove distractions - fuel, checks and minor fixes scheduled around it.
- Balance the load. If two areas are peaking out, rotate machines on a timetable. It beats having one overworked and one idling.
- Kill the queues. If a daily jam at laydown is driving idle, move the delivery slot or pre-stage loads. Cheaper than adding another machine "just to be safe."
- Use data with discipline. A simple weekly snapshot - productive hours, idle, near-misses, fuel per productive hour - tells you whether to add, hold or off-hire.
Phase 3: run-down - exit as deliberately as you entered
- Off-hire early, off-hire cleanly. As trades peel away, identify the next machine to go and book collection before it spends a week gathering dust.
- Consolidate attachments. Return what you won't use again this phase and stage only what the finishing crew needs.
- Tidy the compound. Fewer movements reduce risk; clear space makes the final weeks calmer.
Signals you're carrying too much iron
- Productive utilisation below a healthy threshold for two weeks running.
- Persistent idle in the same time window - often a sequencing problem in disguise.
- Machines parked far from any active workface "just in case."
Signals you're starved
- One machine with sustained high utilisation and a growing queue behind it.
- Rework and damage from rushed approaches or long shunts across site.
- Teams borrowing attachments because the right tool is always somewhere else.
The end-of-project audit (60 minutes)
- What did we over-hire? Under-hire? Which attachments saved a second machine?
- Where did idle hide? In queues, in layout, in habit?
- What would we change in week one if we ran this project again tomorrow?
The payoff
Right-sizing by phase keeps money in your pocket and pressure out of the day. You move faster and run safer because movements are deliberate. And your team sees a plan that adapts as the project does - calm, predictable and effective.
