How auto-allocation of drivers and vehicles works in dispatch software

Auto-allocation is the feature every dispatch demo shows and few operators trust. A button is pressed, twenty unassigned duties get a driver and a vehicle, and the screen says done. The question an operator should ask is not whether the software can allot automatically. It is what rules it follows, what it refuses to do, and what it says when it cannot do the job. This article explains how automatic allocation of drivers and vehicles works in general, where it goes wrong, and exactly how MobilityDrive's version behaves.

What auto-allocation is, and what it is not

Auto-allocation, also called auto-assignment or automatic dispatch, is a set of rules that picks a vehicle and a driver for a booked duty without a dispatcher choosing them. In software for booked duties, which is what chauffeur, cab and corporate transport operators run, it works ahead of time on duties that have a known pickup time. That is different from the on-demand matching in a ride-hailing app, which looks for the nearest available driver this minute. It is also different from route optimisation, which decides the order of stops. Auto-allocation answers one question: who takes this duty?

The four checks every allocation has to pass

• Clash. Is this vehicle or this driver already on a duty that overlaps the new one? A duty has a start and an end, and two of them on one driver is the most common manual mistake.
• Documents. Has the vehicle's permit, fitness, insurance or pollution certificate expired? Has the driver's licence or permit? An allocation that ignores this puts an illegal car on the road.
• Availability. Is the driver on leave on the day of the duty, or marked off duty?
• Fit. Is the vehicle of the type the customer booked? A sedan allotted to a booking for a seven-seater is not an allocation, it is a complaint.

A dispatcher runs these checks in their head. Software has to run them from data, which is why auto-allocation is only as good as your duty times, your leave records and your document expiry dates.

The failure mode: half an allocation

Here is a failure worth knowing about, because we had it ourselves. An early version of our rules took the first free driver and the first free vehicle and allotted either or both. On a day when every car's insurance had lapsed in the test data, it handed seven duties to one driver with no vehicle and reported seven duties allocated. The board showed nothing unassigned, and the driver could not start any of them. The count was right and the outcome was useless.

The lesson is general. An allocation is a pair. A duty with a driver and no car, or a car and no driver, is still unallotted, and software that counts it as done hides the problem from the one person who could fix it.

How MobilityDrive's auto-allocation decides

• It allots a duty from your own fleet only when it can find both a vehicle and a driver. Half an allotment is not made.
• It passes over any vehicle that has a clashing duty or an expired document, and any driver who has a clashing duty, an expired document, leave on a day of the duty or off-duty status.
• If you switch on vehicle type matching, the vehicle must be of the booked type.
• It spreads the work: the driver with the fewest duties on the day of the pickup goes first, then the vehicle with the fewest, so one driver is not given the whole day while others sit free.
• It keeps a driver with their own car, the one your fleet master assigns to them, when that car is free.
• If your own fleet cannot cover the duty and you have allowed it, the duty falls back to a vendor.
• When nothing can be picked, the result says what was missing, a vehicle, a driver or both, and counts why each candidate was passed over.

Auto-allocation is optional and switched off by default. It is a setting per company, with your own choices for matching vehicle type, preferring your own fleet, falling back to a vendor and whether an expired document may ever be overridden. The module page for booking and dispatch software lists the settings.

What it does not do

It does not choose the nearest car by live distance. It does not plan a route or the order of pickups, and it does not build a shift roster for employee transport: you set the duties, and recurring bookings repeat them. It does not learn customer preferences. A VIP client's preferred chauffeur is still a dispatcher's decision, which is why a dispatcher can always allot by hand or change what the rules picked.

When to use it and when to allot by hand

Automatic allocation suits volume work where one compliant car of the right type is as good as another: staff transport, airport transfers in a standard class, contract duties that repeat. It suits executive chauffeur work less, where the pairing of client and chauffeur is part of the service. A sensible pattern is to let the rules allot the routine duties the evening before and leave the named-chauffeur jobs for the dispatcher, who then spends time on the twenty duties that need thought instead of the two hundred that do not.

How to test auto-allocation in any product

• Expire one vehicle's insurance and run it. The vehicle should be passed over, and the result should say why.
• Put a driver on leave for the day and run it. The driver should not be picked.
• Book two overlapping duties and leave only one driver free. The second duty should stay unallotted, visibly.
• Remove every free vehicle and run it. The product should report that it could not allot, not that it allotted drivers.
• Check the spread. Ten duties and five free drivers should not produce one driver with ten duties.

Run the same five tests on any product you are considering. For the rest of what a dispatch desk needs, including SLA rules for duties that are still unassigned close to pickup, see the fleet dispatch software page, and for a wider buying checklist read how to choose fleet dispatch software.