Why The Calendar Gets It Wrong
A van doing school runs and a van doing airport delivery runs do not wear out at the same speed, but a monthly service schedule treats them as if they do. One vehicle gets serviced too often, and the other one breaks down on a work day.
Engine hours and warning codes tell you the truth instead. The vehicle reports this information itself.
| Trigger | Calendar approach | Condition-based approach |
|---|---|---|
| Oil service | Every 3 months | At an engine-hour limit set per vehicle |
| Brakes | Wait for a complaint | Watch harsh-braking trend and wear warning code |
| Battery | Wait for it to fail | Watch the starting-power trend |
| Cooling system | Wait for overheating | Watch the temperature warning code |
Downtime Is The Real Cost
The repair bill itself is the small part. The big cost is the job that did not get done, the staff standing idle, the customer who called someone else instead, and the rental vehicle you needed for three weeks while a part was shipped in.
Every hour a vehicle sits waiting for a part is an hour of work you have already lost.
Building It
- Set service limits based on engine hours, by vehicle type, not one rule for the whole fleet.
- Send warning codes to one person who has the authority to book the vehicle in for repair.
- Keep a written list of the five parts that most often cause delays, and keep spares of them.
- Review overdue vehicles every week. A list nobody reads is not really a maintenance system.
Before Storm Season
Anywhere shipping can be paused, servicing based on actual condition becomes a way to prepare for emergencies. Go into the season already knowing which vehicles run hot, which batteries are weak, and which services are genuinely due — so during the season you are sending vehicles out, not troubleshooting them.
Sources
- · Society of Automotive Engineers, engine-hour based service intervals
- · Regional workshop lead-time practice notes, 2025-2026
- · MGFleet maintenance module documentation
