1. See the whole day on one board.
Dispatch starts with being able to see every job for a day next to the people and vehicles that could cover it. A list of bookings tells you what exists. A board with one lane per driver and a visible lane for unassigned work tells you what is missing. Ask for both views, and ask how quickly you can move between today, tomorrow and next week.
The board should answer three questions without opening a single booking: which jobs have nobody on them, which drivers have nothing, and which jobs are covered by a partner rather than your own crew. If you have to click into each record to find out, the busiest morning of the week will be slow.
Time off, servicing and compliance dates belong on the same calendar as the work. A driver who is on leave or a vehicle that is booked in for maintenance should be as visible as a job, otherwise someone finds out by phone. 4fleet has a dispatch board where you drag a trip onto a driver's lane to assign it, plus vehicle and driver calendars.
- Find unassigned jobs without opening any booking.
- Check that leave and servicing show beside the work.
- Switch between a day view and a week view in a few clicks.
2. Catch clashes before they become promises.
A double booking is usually created at the moment of assignment, and it is cheapest to stop it there. Good software compares the new job with the driver's and the vehicle's other work and warns you before you confirm. It should check the vehicle as well as the driver, because a car can be double-booked while both drivers look free.
Test the edges, not the obvious case. Two jobs at the same time is easy. Try a job that starts ten minutes after another finishes across town, a driver who is on leave, and a vehicle with a service booked. See whether the warning explains what clashes and with what.
Decide in advance who may override a warning and whether a reason is recorded. Some overlaps are deliberate, such as a driver finishing one job at the venue where the next starts. An override that leaves a note is far better than a warning everyone learns to ignore.
In 4fleet, converting an enquiry into a booking re-checks vehicle and driver conflicts, and moving a booking to a new time lets an owner or admin override a clash with a reason.
- Test a clash on the vehicle with the driver free.
- Ask what the warning says and who can override it.
- Confirm an override leaves a record of why.
3. Allow for travel between jobs.
A driver is not free the minute a job ends. They have to get from the dropoff to the next pickup, and that time is real even though no passenger is on board. Dispatchers call it deadhead. If software only compares job start and end times, it will happily assign a driver to a pickup they cannot reach.
Ask how the software treats the leg to the first pickup and the leg home from the last dropoff, and whether it uses real road distances or a flat buffer. Flat buffers are simple but wrong at both ends, too tight around airports and too generous across a small town. Whatever method it uses, you should be able to see the number it assumed.
Airport work needs an extra margin of its own. Parking, terminal access and passenger readiness all sit between a flight landing and a pickup. Keep that as a rule your team applies on purpose rather than something each dispatcher guesses. 4fleet plans routes and counts the empty running to and from base as part of a job's route.
- Ask how travel between jobs is calculated.
- See the assumed time on the booking itself.
- Set a standard margin for airport pickups.
4. Match the vehicle to the job: seats, luggage and class.
Passenger numbers are only the start. Six people with six large suitcases will not fit a vehicle that seats six. Luggage, child seats, wheelchair access and the class the client was quoted all decide which vehicle is suitable. Software should hold seats and luggage capacity on each vehicle and compare them with the job.
The warning needs to be firm and explained. A soft hint that is easy to miss produces a vehicle swap on the morning of the job. Look for a refusal that says why, with a controlled way for a senior person to override when they know better.
Fit also covers the quote. If a client was promised an executive saloon, sending a smaller car because it was free is a commercial decision, not a dispatch one. Make sure the class sold is visible when you assign. In 4fleet, assigning a vehicle with too few seats or too small a boot for the job is refused, and an owner or admin can keep it by giving a reason.
- Record seats and luggage space for every vehicle.
- Check that the sold vehicle class is visible at assignment.
- Limit overrides to a named role and keep the reason.
5. Plan for changes after the job is assigned.
Most dispatch pain comes after assignment. The client moves the pickup, the flight is late, the driver calls in sick. Software should treat a change as something that re-runs the checks, not as an edit to one field. Moving a pickup can create a clash that did not exist a minute ago, and the person making the change should see it straight away.
Decide who is told and how. The driver needs to know the job changed and needs a way to say they have seen it. Passengers may need a message. Do not rely on a dispatcher remembering to phone. A tracked change with an acknowledgement is safer than a call that was never logged.
Be careful with flight information. A delay is a reason to look at the plan, not an instruction to rewrite it. 4fleet's flight tracking, a per-company setting, checks flights with a flight number from about three hours before to six hours after pickup. It alerts the office in the app when a flight is delayed more than ten minutes and emails the passenger for delays over thirty minutes or a cancellation. It does not tell the driver and does not move the pickup, so dispatch still decides.
- Move a pickup and see whether clashes are re-checked.
- Confirm how a driver sees and acknowledges a change.
- Decide who moves the pickup when a flight is late.
6. Leave a clean handover and a record.
Dispatch rarely belongs to one person for a whole day. Someone starts early, someone covers lunch, someone closes. The handover should be visible in the system: which jobs are unassigned, which are waiting on a driver or partner reply, and which have an open question. A note in a shared chat is easy to lose.
Keep the conversation attached to the job. A message thread tied to a booking means the next dispatcher sees what the driver was told and when. Offers should work the same way, so a driver's decline is on the record rather than a missed phone call. In 4fleet, drivers accept or decline job offers in the driver portal, and each trip has a chat between dispatcher and driver.
Finally, keep the record after the job. Who was assigned, who was moved and why are the answers to a complaint a month later. A system that overwrites its history cannot answer them.
- List unassigned and unconfirmed jobs at each handover.
- Keep driver messages on the booking, not elsewhere.
- Check that reassignments leave a visible trail.