Fleet KPIs for Transport Managers in India

Start with ten: vehicle utilisation, empty running, trip turnaround time, detention at loading and unloading points, fuel use per kilometre, idle time, on-time delivery, breakdown downtime, risky-driving events per 1,000 km and cost per kilometre. Together they answer the questions a transport manager is asked every week: are the vehicles earning, where is time lost, where is fuel going and is the service reliable.

Add a data-health check before any of them. List the vehicles whose last location or reading is older than your agreed limit. A KPI built on a vehicle that stopped reporting on Tuesday will look like good performance when it is really missing data.

Most KPI arguments are really definition arguments. Decide what counts as a working day, a trip, a delay and a breakdown, and write it down. For example, a trip could start at gate-out from the depot and end at gate-in at the delivery point, or it could start when the vehicle is loaded. Either works if everyone uses the same one.

Record the data source for each KPI. Distance can come from the GPS trip record or the vehicle odometer. Fuel can come from fuel cards, tank sensors or the vehicle's own data where a compatible device supports it. Delivery times can come from geofence arrival or from the proof-of-delivery time. Note which source you used so this week's number can be compared with last week's.

Vehicle utilisation is the share of available days or hours a vehicle spends on paid trips. Count a day as utilised only if it carried a load you billed or a planned internal movement. Low utilisation on a few vehicles usually points to a driver shortage, a maintenance backlog or poor load matching rather than a fleet that is too large.

Trip turnaround time is the time from leaving the depot to being ready for the next load. Split it into driving time, stops on the way and waiting at the loading and unloading points. The waiting part is detention. Detention is often the largest avoidable loss, and the GPS record of when a vehicle entered and left a site gives you evidence when you discuss it with a customer.

Fuel use per kilometre, or kilometres per litre, should be compared by vehicle, route and load, not as a fleet average. Look for a vehicle whose figure has moved from its own normal range, then check the reasons in order: route and load change, idling, tyre pressure and maintenance, fuel data quality, and only then possible fuel loss.

Idle time is engine-on time while the vehicle is not moving. Separate it into idling that is needed, such as running a reefer unit, and idling that can be avoided, such as waiting with the engine on. A percentage of engine-on time is fairer than total idle hours when vehicles work different shifts.

On-time delivery is the share of deliveries that arrived inside the time window agreed with the customer. Record the agreed window, the actual arrival time and the reason for each late delivery. Reasons such as late loading, traffic, breakdown or a wrong address need different fixes.

Breakdown downtime is the number of days a vehicle could not work because of an unplanned repair. Track it next to planned maintenance done on time. A rising downtime figure with planned service falling behind is an early warning.

Use the same order every week. First, the data-health check: which vehicles are not reporting. Second, the ten KPIs against last week and the last four-week average. Third, the five vehicles or lanes that moved the most. Fourth, an owner and a date for each action.

Keep a short written record of each week's review. When a customer disputes a delivery time or a driver questions an event, the record shows what was known, what was decided and why.