1. Capture the request wherever it arrives.
Most chauffeur work starts as an email, a phone call or a web form, and the first test of any booking system is what happens to that message. A good one turns it into a structured record with the pickup, the dropoff, the date and time, the passenger count and the contact, without someone retyping it.
Ask what happens when information is missing or the message describes several journeys. A flight number buried in a paragraph, a return trip mentioned in the last line and a second pickup for a colleague are all normal. The system should keep each of them as its own part of the request and show what is still unknown.
- Send it a messy real email and see what it extracts.
- Check that missing details are visible, not blank or guessed.
- Confirm repeat enquiries from one person land on one client record.
2. Quote, get acceptance and confirm.
Between the enquiry and the booking sits the quote, and this is where many tools fall apart. The price should come from rates you have set, not from memory, and the customer should be able to accept without a phone call. Check what the customer actually sees, how long the offer stays valid and what happens when it expires.
Then look at the handover. Acceptance, booking confirmation and payment are three separate events, and the software should show each one on its own. Converting an accepted quote into a booking should carry over every detail, and it should stop you if the vehicle or driver is already committed elsewhere. In 4fleet the customer gets an emailed link to an accept page, and an accepted quote converts into a booking.
- Price a job from your own rates, then change one detail.
- Open the customer's side of the quote as the customer would.
- Find out what happens to an accepted quote that nobody has booked.
3. Assign a driver and vehicle you can trust.
Assignment is where the booking meets your real fleet. The software should let you see drivers and vehicles by day, assign by dragging or selecting, and warn you when a vehicle cannot carry the group or the same person is already on another job. It cannot know about a driver stuck in traffic, so treat its checks as a safety net and not as a replacement for the dispatcher.
If you sometimes pass jobs to another operator, test that path too. You need a clear record of who was asked, who said yes, the price agreed and who is actually driving. A job that went to a partner and has no named driver is the one most likely to fail on the day.
- Assign a job to a vehicle with too few seats and see the response.
- Reassign a job and check what the old and new driver are told.
- Follow a partner job to the point a driver is named.
4. Check the driver's view on a phone.
The driver does not need your whole system. They need today's jobs, the pickup details, the passenger's contact and a quick way to report progress. Open the driver view on an ordinary phone and judge it at arm's length, in the way a driver will use it between pickups.
Look at how status updates flow back. When a driver marks that they have arrived or the passenger is on board, the office should see it without a call. Ask what the driver sees if you change the pickup time after assigning, and how the app behaves when the signal is poor.
- Read a job on a phone without zooming or scrolling sideways.
- Change a job after assignment and see what reaches the driver.
- Ask how a driver proves the job was done.
5. Turn the finished job into an invoice and a payment.
A booking is not finished when the passenger is dropped off. The system should produce an invoice from the booking without re-entering the price, number it consistently, send it, and show whether it has been paid, part paid or is overdue. Extras such as waiting time or parking should be able to follow the original price instead of being invented later.
Test the awkward cases. Raise a credit note for a price correction, take a part payment, bill a company that wants one invoice a month, and look for the link the client can use to pay. The invoice list should tell you at a glance what is owed and what is late. 4fleet covers these cases with numbered invoices, payment links, recorded payments and credit notes.
- Create an invoice from a finished booking and compare the figures.
- Record a part payment and check the remaining balance.
- Issue a credit note and see how the balance changes.
6. Give clients access and read the results.
Corporate clients and regular customers want to see their own trips, quotes and invoices without emailing you each time. Check whether the software offers a client area, what it shows, and whether a client can ask for a change or a new journey there. Make sure one client can never see another's records. 4fleet's client portal lists a client's trips, quotes and invoices.
Finally, look at what the system tells you about the business. You should be able to see the enquiries won and lost, revenue by period, unpaid invoices and what each job earned after costs. Reporting is only useful if the numbers come from the same records your team works in every day.
- Log in as a client and see only that client's records.
- Ask for the margin on one job and see where each figure comes from.
- Find the unpaid invoices report and check it against one client.