What a double-booked car really costs
A double-booked car is not a paperwork problem. It is a chauffeur who finds out at 6:45 a.m. that the car he is driving to Hudson Yards was also promised to a second customer at JFK ten minutes earlier. Someone has to be told no, usually after they are already waiting. The office then spends the next twenty minutes finding a second car, apologising, and hoping the second pickup is still close enough to save.
This is the second of the three problems that show up on almost every fleet still running dispatch from memory: double-booked cars, a driver sent across town, and nobody sure who is actually free at 6 a.m.
Why a whiteboard or group chat cannot catch it
A whiteboard only shows what was written on it last, by whoever had the pen. A group chat only shows what was typed, in the order it was typed, which is not the same as the order jobs actually start and end. Neither one calculates anything. Nobody is checking, in real time, whether car A 12345 is still out on a 06:40 job when a second booking tries to claim it for 06:45. The clash is only discovered when a chauffeur is already driving toward the wrong pickup, or standing next to a car that is not actually free.
Hard clashes blocked, soft clashes logged
The SK Fleet dispatch board treats a double-booking the way a system should: a car cannot hold two overlapping duties, full stop. That is a hard clash, and it is refused outright — the booking cannot be assigned to a car that is still out on another job.
Not every tight schedule is a mistake, though, so the board does not block everything equally. A turnaround tighter than your threshold is a soft clash: it is allowed, but only when a dispatcher explicitly overrides it, and that override is logged with their name. Nothing gets double-booked silently, and nothing gets blocked so rigidly that a genuinely workable tight turnaround becomes impossible.
Dispatchers keep full control throughout. Ranking is a recommendation, not an instruction — any card can be dragged to any lane. The board's only job is to refuse what cannot physically happen and flag what is risky enough to need a named decision.
Ranked candidates, not guesswork
Refusing clashes is only half the problem. The other half is picking the right car from everyone who actually is free. Every available car and chauffeur is scored on distance to pickup, vehicle class fit, today's load, and document validity, and the dispatcher sees the ranking, not just a list of names. A chauffeur 2.1 km away with a clean fit and two jobs today outranks one 9.3 km away who would need an upgrade and already has a soft clash — and the dispatcher can see exactly why.
Expiring papers are handled the same way as clashes: they warn, they do not silently block. A dispatcher can still assign a chauffeur whose permit is close to expiring in a genuine emergency — the system just makes sure nobody does it by accident.
When a car breaks down anyway
None of this prevents a car from actually breaking down mid-trip. What changes is what happens next. The dispatcher splits the booking at the car's live position — tracked every 4 seconds by the chauffeur's phone, with no GPS hardware to install — and sends the nearest free car as a rescue leg. The customer's tracking link keeps working through the handoff, and the booking stays one invoice with two legs in the record, not two separate jobs to reconcile later.
Whiteboard vs dispatch board
| Situation | Whiteboard or group chat | SK Fleet dispatch board |
|---|---|---|
| Two bookings claim the same car | Discovered when the chauffeur is already en route | Hard clash refused outright before it is assigned |
| A tight but workable turnaround | Allowed or blocked with no record of the call | Soft clash needs a named dispatcher override, logged |
| Choosing which free car to assign | Whoever the dispatcher remembers is nearby | Ranked by distance, class fit and today's load |
| Expiring chauffeur documents | Easy to miss until it is checked | Flagged on the candidate list, warns rather than silently blocks |
| A car breaks down mid-trip | A second booking is started from scratch | Rescue leg split at the live position, same invoice |
FAQ
Can a dispatcher still override the board?
What counts as a hard clash versus a soft clash?
Do we need to install GPS hardware for this to work?
What happens if a car breaks down mid-trip?
See your own cars on the dispatch board.
30 minutes, no slides. We load a week of your bookings first.