Hired and Leased Vehicles

Most fleets are mixed: owned, leased and hired. The telematics questions differ for each.

Leased vehicles

The lessor owns the asset and cares about its condition at return.

Wiring a device requires their permission, and the lease frequently requires removal and making good.

Which is a cost at return that nobody budgets for unless it is agreed at the start.

Ask before fitting, in writing, and keep the response.

Maintenance under lease

Frequently included, performed by the lessor's network, with records in their system.

So your whole-life cost data has a gap exactly where the maintenance is.

Request the records as a contractual term, which lessors will generally provide and rarely volunteer.

Without them you cannot compare a leased vehicle against an owned one, which makes the lease-or-buy analysis guesswork.

Excess mileage and condition charges

The two costs that appear at return and surprise people.

Telematics answers the first exactly: actual distance against contracted, visible months before the end.

Which turns a charge into a decision — extend, swap, or redistribute work — taken while there is still time.

Track projected end-of-lease mileage per vehicle, quarterly. It is a simple calculation and it is rarely done.

Short-term hire

Usually no device, so no data.

Which means hire vehicles are a hole in every fleet figure and should be stated as such rather than averaged in.

Track hire days and cost separately, because a rising hire spend is usually a signal about owned fleet availability or utilisation.

And check whether the hire company's own telematics data is available, which is increasingly the case and is worth asking.

The comparison worth running

Cost per mile for owned, leased and hired, on comparable work.

With the gaps stated: leased maintenance costs may be embedded, hire has no condition data.

Most fleets have never compared the three and hold the mix they inherited rather than the one that suits the work.

The measure

Projected against contracted mileage, per leased vehicle.

Hire days and spend, trended.

And end-of-lease charges, recorded by cause, because they are predictable in aggregate and nobody predicts them.

Project the lease mileage quarterly

A simple calculation almost nobody runs.

Actual distance against contracted, extrapolated to the end date.

Which turns an excess mileage charge into a decision — extend, swap, or redistribute work — taken while there is still time.

The charge is predictable months ahead and is routinely discovered at return.

Reproduce the workflow

For another way to make this requirement testable, consult time tracking for temporary fleet staff. Reproduce the case with real roles, codes, failures and recovery steps.