Two jobs, one car: how double-booking happens

Double-booking is not carelessness. It is what happens when availability is a question someone has to ask rather than something the system knows.

The problem

Ask any dispatcher how a car ends up on two jobs and the answer is the same. Somebody needed an answer fast, the person who knew was on a call, and the booking was confirmed on the assumption that the afternoon was clear.

The second failure is scheduling a driver who should not be working. Shifts, rest requirements, and the hours already assigned live in different places, so the conflict is only visible to whoever holds all three in their head at the time.

How 8Move handles it

Availability is part of the record rather than a question. The board shows who is free, who is en route, and who is overdue, and conflicts are detected when the assignment is made instead of when the passenger calls. Driver availability is held as recurring shifts, and the scheduler refuses assignments that go past the driving limits you configure.

Assignment can also run automatically: the system ranks available drivers by proximity, rating, and schedule fit, sends the job out with an accept-or-decline window, and escalates when it is declined. Operations that move drivers between routes through the week, like alpine transfer management, get the most out of that.

Questions operators ask

At assignment time. The system checks the driver and vehicle against what they are already committed to before the job is confirmed.

Driver availability is set as recurring shifts, and the scheduler prevents assignments that would push a driver past the driving limits you configure.

Yes. In manual mode the system ranks the available drivers and the dispatcher confirms the one they want, so judgement stays with the person.

The job moves to the next driver automatically after the accept-or-decline window, rather than sitting unnoticed until the pickup time is tight.