How to choose fleet dispatch software: a checklist for operators

Most fleet dispatch software looks convincing in a demo, because a demo shows the happy path: a booking arrives, a driver is assigned, a map lights up. Your real operation lives in the exceptions: the booking that changes at 11 pm, the driver whose insurance expired last week, the client who disputes a toll. This checklist is for judging a tool on those.

Start with your own operation, not the feature list

Before you look at any product, write down how a booking travels through your business today, from the first message to the money in the bank. Note who touches it, which tool or spreadsheet it sits in at each step, and where it gets retyped. Every retyping step is a place where software can help, and a place where a weak tool will quietly fail. Take that written flow to every demo and ask the vendor to show it, step by step, with your own examples.

The ten questions worth asking

• Where do bookings come from, and do they all land in one list? Phone, email, a client portal, an app and your website should create the same kind of record.
• What stops a bad allotment? Ask what happens if you assign a vehicle with an expired permit or a driver whose licence has lapsed. A good system refuses or warns, and you can see who overrode it.
• Can it handle sub-contracting? Many operators buy capacity from partners. The vendor's cost, the vendor's compliance and the partner's invoice should all attach to the trip.
• Does it handle your booking patterns? Recurring daily pickups, outstation trips and monthly contracts price and schedule differently from one-off transfers.
• How does it know where a vehicle is? Find out whether it uses the driver's phone, installed GPS devices or both, and what setup each needs. Be wary of 'integrates with any tracker' without detail.
• Does the duty record come from the vehicle? Opening and closing odometer, tolls, parking and waiting captured on the driver's phone are the evidence behind a correct invoice.
• Does a completed trip become an invoice without retyping? Ask to see this live, with your tariff, including the tax your country requires.
• How does it fit your accounts? You probably already have an accountant and a tool. Ask exactly what it exports, in which format, and whether the link is live or a file.
• What do the reports read from? Reports built from the same records as your books agree with your accounts. Reports built from a separate copy drift.
• Can you take your data out? Ask for the export formats before you sign, not after.

Run the demo on your own data

A tailored demo is more useful than a polished one. Give the vendor three of your real tariffs, five of your real vehicles and one client contract, and ask them to run a week of your bookings through it. Pay attention to how much setup each step needs and who does it. The time from raw data to a first correct invoice tells you more than any feature list.

Ask for the awkward cases as well: a booking cancelled after a driver was assigned, a duty that runs past midnight, a trip with two extra stops, a credit note for a disputed charge. If the vendor says 'that is on the roadmap', write it down and weigh it honestly. Roadmaps are plans, not features.

Check the limits, not just the strengths

Every product has things it does not do. The honest ones will tell you early. Ask directly what the product does not cover for your business model, for example automatic rostering, route optimisation, self-drive rental features or a certification you need. A vendor who answers specifically is easier to trust than one who says everything is possible.

Check the paperwork side of limits too. If you invoice in India, ask about e-invoicing and e-way bills. If you operate in Saudi Arabia, ask about ZATCA and what stage the integration has reached. If you are somewhere else, ask what the product knows about your country and what you would configure yourself.

Red flags

• Only headline numbers, such as the percentage of cost saved, with no method behind them.
• No way to see a real invoice produced from a real duty.
• Tracking that depends on hardware nobody can name.
• Reports that cannot be reconciled to your accounts.
• Pricing that is not explained beyond 'it depends'. A vendor should be able to say what you pay for and what is extra.

Decide with a small trial

Where you can, run a small live trial before committing: one branch, one client contract or one month of one duty type. Choose something with real money attached, so you find the invoicing gaps early. Set the success measures beforehand, such as bookings entered without retyping, allotments checked for documents, and invoices raised without manual correction.

If you want to see how one product answers this checklist, MobilityDrive's fleet dispatch software page sets out what each module does and where its limits are, the pricing page lists plans, and the transport billing software guide covers the invoicing side in detail.