Measuring Chauffeur and Fleet Performance: The Dispatch Numbers That Matter

Most black car operations have more data than they use. Every job leaves a trail: when it was booked, when it was assigned, when the chauffeur accepted, when they arrived, when the trip ended. The problem is rarely a lack of numbers. It is knowing which few are worth looking at every week.

This is the short list we would start with, and how to read each one without fooling yourself.

Start with on-time performance, and define it

On-time pickup rate is the number clients feel most. But it only means something if you define it. We would suggest measuring whether the chauffeur was at the pickup location before the scheduled time, not whether they were within a few minutes of it.

Split it by service type. Airport transfers, hourly bookings and point-to-point city jobs fail for different reasons. A single blended figure hides where the problem is.

When a job is late, record the cause: traffic, late assignment, vehicle issue, chauffeur error, wrong address on the booking. If every late job is filed under "traffic", the number tells you nothing.

Measure dispatch, not just chauffeurs

Chauffeur numbers are often really dispatch numbers. A chauffeur who is late on jobs assigned 40 minutes before pickup is not necessarily a slow chauffeur.

Track these on the dispatch side:

• Time from booking to assignment. How long does a confirmed job sit unassigned?
• Time from assignment to acceptance. Where is the delay between your office and the chauffeur app?
• Reassignment rate. How often is a job moved after it was first allocated, and why?
• Jobs assigned late. Anything allocated close to pickup time should be visible as its own group.

If reassignments cluster around certain times or certain chauffeurs, that points to a scheduling or availability problem rather than a performance one.

Chauffeur numbers worth keeping

Keep the chauffeur scorecard small. A few figures, reviewed consistently, beat a dashboard nobody reads.

• Acceptance rate and response time in the app.
• On-time arrival, using the definition above.
• Completed-job data quality. Are wait times, extras and notes recorded properly at the end of the trip? Missing data becomes missing revenue at invoicing.
• Complaints and compliments per trips completed. Use it as a ratio, not a raw count, so busy chauffeurs are not penalised for volume.

Use these for conversations, not just ranking. A chauffeur with a low acceptance rate may be declining jobs for a good reason, such as repeated long deadheads to a pickup zone.

Fleet: utilisation and idle time

For the fleet, the central question is how much of the time a vehicle is available is it actually earning.

Look at revenue hours against available hours for each vehicle, and revenue per vehicle per day or week. Compare like with like: a sedan and a people carrier serve different demand and should not share one benchmark.

Then look at deadhead, the distance or time driven without a passenger. Some is unavoidable. But if one vehicle or one chauffeur consistently carries more empty running than the rest, check whether the cause is how jobs are being allocated.

Do not forget downtime. Days out of service for maintenance or repair, tracked per vehicle, tell you which vehicles are costing you more than they earn and when replacement conversations should start.

Commercial numbers that connect it all

Operational performance only matters if it shows up in the business. A few commercial figures complete the picture:

• Cancellation and no-show rates, with late cancellations separated out, since those cost you a vehicle slot.
• Margin per job after chauffeur pay or subcontractor cost. Revenue alone can flatter jobs that lose money.
• Revenue by client or account, to see who depends on your best service and who takes the most effort.
• Time from trip completion to invoice sent, and to payment. Slow invoicing is often a data-capture problem from the chauffeur app.

How to read the numbers honestly

A few habits keep reporting useful rather than misleading.

Watch the trend, not the single week. One bad Friday in a busy event period is not a pattern. Four weeks of the same issue is.

Look at the distribution. An average on-time figure can look fine while a handful of jobs are very late. Review the worst cases individually.

Separate cause from owner. Before a number goes into a chauffeur review, check whether the job was assigned late, had a wrong address or hit a known disruption.

Keep the definitions fixed. If you change what counts as on time, note the date. Otherwise your trend line compares two different things.

A simple review rhythm

Daily, the dispatcher checks late jobs, unassigned jobs and any no-shows, and records the cause.

Weekly, the owner or operations manager reviews on-time rate by service type, assignment timing, acceptance rates and vehicle utilisation.

Monthly, look at margin per job, client mix, downtime by vehicle and invoice-to-payment time, and decide on one or two changes. Not ten.

The aim is not a bigger report. It is to find the two or three things that cost you the most, fix them, and check that the numbers moved. Run your reservations, dispatch, driver app and invoicing on one system and most of this data is already being captured as the work happens. The discipline is deciding what to look at, and looking at it on schedule.