← All articles

By Morgan P. · 8 November 2026 · 5 min read

Planned vs reactive fleet maintenance: why mileage matters

Planned maintenance is work you schedule before anything goes wrong: a service, an inspection, a part changed on a set interval. Reactive maintenance is work you do after something has already broken. Every fleet does some of both, but the calmer, cheaper ones lean on the first to avoid the second. A planned service is a known cost booked at a quiet time. A breakdown is an unknown one that lands halfway through a job.

You will also hear planned maintenance called preventative. Same thing. You spend a small, predictable amount now to dodge a large, unpredictable one later, and the skill lies in picking the moment, which is where the calendar falls short.

Mileage over dates

Vehicles wear by use, not by time. A service is a check that an engine has done enough work to need attention, and work is measured in miles.

Take two vans bought on the same day. One does 8,000 miles a year between local sites, the other 40,000 on motorways. Service both every twelve months and the first is serviced too often while the second is left far too long, hitting its wear in three or four months. That is how a vehicle fails an inspection with plenty of life left on its paperwork.

Your own car works the same way. Its service light counts distance, because the date has no idea how hard you drove.

Dates keep a place. An annual safety inspection or MOT is fixed by rule. So book on whichever comes first, the date or the mileage.

Getting the mileage right

Mileage servicing only works with accurate mileage, and this is where it usually collapses. If someone walks the yard reading odometers or chases drivers for a figure, the number is stale and the service goes out late or off a guess.

Tracked vehicles do not need that. The distance arrives from the tracker as the van drives, so the interval counts itself and nobody writes anything down. It is the main reason to keep maintenance next to your fleet management software: the data that triggers a service is already there.

AutoM8 tracking is live. The maintenance scheduling built on top of it is still being finished, so ask to see its current state in a demo.

Where reactive work fits

Not everything can be planned. A tyre picks up a screw, a bulb fails, a driver spots a fault on the morning walkaround check. Reactive work is half the job, and doing it well is not a failure.

The danger is a defect that vanishes into a phone call. A reported fault should become a repair you can follow from raised to fixed, with parts and cost against the vehicle. Without that, the same fault is reported three times or forgotten until it becomes a breakdown. Defect, repair and proof of the fix kept together is also what an inspector wants to see, and it is where maintenance meets fleet compliance.

What skipping a service really costs

Servicing is not the expensive bit. Downtime is. A van off the road mid-job means a missed appointment, an idle driver, sometimes a recovery truck and a hire vehicle, plus a customer who remembers.

Because every service and repair is logged against the vehicle, you also build its full history and whole-life cost, so replacement is decided on figures. For plant hire, where an idle machine earns nothing, that history matters more than most. The planned side is described under maintenance and servicing.

Ending the surprise

Plan what you can, respond well to the rest, and trigger services on the earlier of mileage or date. Stop reading odometers by hand and let the tracker supply the number. To see how that works on your own vans, book a demo.

Related features

Maintenance →Compliance →

For your field: Plant & Tool Hire →

Next article

Field service software for electrical contractors: what to look for →

Book a demo →