I manage a mixed fleet for an industrial service contractor in Ontario, where my days involve service vans, pickup trucks, crew buses, and a few heavier units that spend long hours around job sites. Over the years, I have learned that fleet management strategies are rarely about finding one clever system or buying the newest software. I get better results by watching how vehicles are actually used, fixing small problems before they become expensive, and making sure drivers understand what I expect from them. A fleet can look organized on paper and still lose money every week.
I Plan Around Actual Vehicle Use
I start with utilization because it tells me more than the vehicle count ever will. In one operation I helped manage, we had close to 60 units, yet several trucks were sitting idle for most of the month while other vehicles were running overtime. That imbalance created extra maintenance on the busy units and unnecessary insurance and registration costs on the underused ones. The spreadsheet said we had enough vehicles, but the yard told a different story.
I track mileage, engine hours, route type, load, and idle time rather than relying on odometer readings alone. A pickup that travels 20,000 kilometres on highways has a very different maintenance profile from a similar truck that spends its days crawling around a dusty industrial site. I also pay attention to repeated short trips because they can be harder on some components than longer steady drives. Context matters.
Every few months, I review which vehicles are essential and which ones are simply available because nobody has questioned them. Last winter, I noticed two older vans were barely moving except when a primary unit was in the shop. Keeping one backup made sense, but keeping both tied up money and parking space. We sold one and put the funds toward repairs on equipment that crews were using every day.
I Match Vehicles to the Work Instead of the Job Title
I have seen companies assign vehicles based on position rather than workload, and that usually creates waste. A supervisor may receive a large pickup even though most of the week involves paved-road travel, while a field crew gets a lighter vehicle that struggles with tools and rough access roads. I prefer to match payload, passenger capacity, terrain, and expected distance to the actual job. That keeps fuel use and wear closer to what the work really requires.
Passenger transport deserves the same attention, especially on remote industrial projects where one poor choice can affect an entire shift. If I am comparing bus configurations for a Canadian industrial route, I sometimes tell a colleague to click here for more background on choosing the right industrial bus in Canada before we narrow the shortlist. I still compare the information against our route, winter conditions, passenger count, and service support because a bus that works well for one site may be wrong for another. A 24-seat unit can be efficient on one contract and oversized on the next.
I also resist buying extra capability just because it sounds safer. Four-wheel drive, larger engines, heavy towing packages, and specialized tires all have their place, but they bring costs that continue long after the purchase. On one project, several vehicles carried equipment packages that crews had used only a few times all year. We moved those duties to fewer properly equipped units instead of paying to duplicate capability across the fleet.
Maintenance Works Better When I Use Patterns
I do not treat maintenance as a calendar exercise. Manufacturer intervals give me a base, but I adjust my internal checks around how the vehicle is operating and what our technicians are seeing. A unit running 10 hours a day in dust and stop-start conditions receives more attention than one covering easy highway kilometres. That difference has saved me from several avoidable breakdowns.
I keep a simple record of repeat failures by vehicle, component, mileage, and operating environment. After three similar battery complaints appeared in one group of service vans, we stopped treating each case as an isolated repair and looked at accessories, charging habits, and idle periods. The issue was not dramatic, but repeated service calls were wasting technician time. Patterns become useful when someone actually reviews them.
I also schedule work before the vehicle becomes urgent. If a truck needs brakes soon and I know it will have a quieter week coming up, I would rather take it out of service then than wait for a warning to turn into an emergency. Planned downtime is easier to manage. A crew losing a truck at 6:30 on a cold Monday morning creates far more disruption than a scheduled shop visit on a slower afternoon.
I Treat Drivers as Part of the Maintenance System
Drivers notice changes before any dashboard report does. They hear a new vibration, feel a brake pedal changing, or notice that a vehicle is taking longer to start in the morning. I ask them to report those things early, even if the problem seems minor. One short message can prevent a tow several weeks later.
I keep inspections practical because overly long forms tend to become paperwork exercises. Our daily check focuses on tires, lights, visible leaks, warning indicators, safety equipment, and anything that changed during the shift. It takes around 5 minutes when the driver knows the vehicle. If something looks wrong, I want a photo and a short description instead of a vague note that says "needs checking."
I also watch driving behaviour, but I avoid treating every harsh braking event as misconduct. A driver working downtown traffic will naturally produce different data from someone covering a quiet rural route. I look for repeated patterns across several days before discussing them. That approach gives me a better conversation and usually gets more cooperation from experienced drivers.
Fuel Control Starts With Behaviour and Routing
Fuel is one of the easiest costs to see and one of the hardest to control with a single rule. I have reduced waste by looking at idle time, unnecessary trips, vehicle assignment, and where crews refuel. Even a 15-minute daily habit can become noticeable when it is repeated across dozens of vehicles for an entire year. I care more about repeated behaviour than one unusual day.
Idling is a good example because there are legitimate reasons for it in extreme weather or when equipment depends on the vehicle. I do not set a blanket zero-idle target. Instead, I compare similar vehicles doing similar work and ask questions when one unit is consistently far above the rest. That gives me something practical to investigate instead of another policy nobody follows.
Routing also deserves regular attention because work patterns change. A route designed six months ago may no longer make sense after a customer moves, a supplier changes hours, or a crew starts from a different yard. Last spring, we removed a repeated cross-town supply run by changing where a small stock of common parts was stored. The distance saved each day was modest, but it removed a trip that had no productive value.
I Set Replacement Rules Before Emotions Get Involved
Older vehicles can be surprisingly useful, and I do not replace one just because it reaches a certain age. I look at repair frequency, downtime, operating cost, parts availability, reliability, and what the vehicle is worth to the operation. A paid-off 8-year-old truck that starts every morning may be more valuable than a newer unit with repeated electrical issues. Age is only one number.
I become concerned when repairs start affecting scheduling rather than just the maintenance budget. A truck that needs several thousand dollars in work may still be worth repairing if it remains dependable afterward. On the other hand, smaller repairs every month can make a unit difficult to trust even when the individual invoices look reasonable. Reliability has an operational cost that accounting reports do not always show clearly.
I maintain a replacement forecast covering about 3 years so purchases do not arrive as surprises. It is not fixed because mileage, contracts, resale values, and repair history can change the plan. Still, having likely replacement windows helps me avoid buying several units at once because nobody prepared earlier. It also gives me time to decide what the next vehicle truly needs instead of copying the specification of the old one.
I Use Fleet Data Only When It Changes a Decision
Modern systems can record far more information than I have time to review. I focus on a small group of measures that lead to action, including utilization, downtime, maintenance cost, fuel use, preventable damage, and recurring faults. If a dashboard has 40 charts but nobody changes a decision because of them, I consider most of that display noise. Useful data should answer a question.
I review exceptions rather than staring at every vehicle every day. If 45 units are behaving normally and 3 suddenly show unusual fuel use or repeated fault codes, those 3 get my attention first. This saves time and makes the discussion with technicians more focused. It also stops small anomalies from disappearing inside fleet-wide averages.
I am careful with comparisons too. A cargo van carrying tools through city traffic cannot be fairly judged against a light-duty pickup spending most of its time on open roads. I group similar vehicles and similar work before I decide that something is inefficient. Bad comparisons create bad decisions.
I Keep Vendors Accountable Without Constantly Switching Shops
A reliable maintenance vendor can be worth more than the cheapest labour rate in town. I care about diagnosis quality, turnaround, parts sourcing, communication, and whether promised completion times mean anything. If a shop saves me 10 percent on a repair but keeps a revenue-producing unit for four extra days, the cheaper invoice may cost the operation more. I measure the whole result.
I keep notes on repeat repairs and comeback work because memory becomes unreliable across a large fleet. If the same issue appears again within a few weeks, I want to know what was replaced, who diagnosed it, and whether the vehicle returned with the same symptoms. That record makes vendor conversations factual instead of emotional. It has also helped me identify situations where a different technician solved a problem that had already been "fixed" twice.
I do not switch providers after one bad repair. Shops have difficult jobs too, and unusual failures can fool good technicians. What matters to me is how they handle mistakes, whether they communicate clearly, and whether the same pattern keeps returning. A vendor who owns a problem and fixes it quickly can remain a valuable partner.
The fleet operations I trust most are usually the least dramatic because decisions happen before problems become emergencies. I would rather review 6 useful measures every month, listen closely to drivers, and retire the occasional wrong vehicle than chase a new fleet system every year. Good fleet management is built through hundreds of small choices made with the work itself in mind. That is what keeps vehicles available when the crews actually need them.