Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Why Do Our Pre-Booked Taxi Jobs Run Late Every Time the On-Demand Work Gets Busy?
Problems We Solve

Why Do Our Pre-Booked Taxi Jobs Run Late Every Time the On-Demand Work Gets Busy?

Taxi pre-booked jobs slip when on-demand work floods in. We build dispatch rules and a lookahead that protect pre-books and show when to stop taking new work.

Updated 3 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Pre-booked jobs slip because on busy nights every free driver is swallowed by on-demand work, and the pre-book is only dispatched when its time arrives and no car is near. We build a lookahead that reserves capacity for pre-booked work in each area, releases jobs to drivers early enough to reach them, and tells call handlers when to quote longer waits or decline on-demand work for a while.

Twenty past ten and the pre-books are late

The pattern is familiar. The pubs and restaurants start emptying, the phone and app fill up with people wanting a car now, and every driver who comes clear is given the next on-demand job nearby. Meanwhile, the jobs booked days ago, the couple going to the station for the last train and the account customer's late meeting pickup, come round on the screen at their time and there is nobody free within miles.

The controller pulls a driver off the queue, or begs one to take the job after their current fare. The pre-booked customer, who did everything right by booking in advance, waits longest. Some ring to ask where their car is. Some ring another firm.

Why pre-books lose out

Dispatch systems are good at matching the nearest free car to the job in front of them. On a busy night that logic favours whatever is waiting now, and it does not plan ahead for jobs that are due in twenty minutes.

  • Pre-booked jobs are released to dispatch at a fixed time before pickup, often too late when drivers are all tied up.
  • No capacity is held back in the areas where pre-books are due.
  • Call handlers accepting on-demand work cannot see how many pre-books are due in the next hour.
  • Long journeys taken on demand, such as a fare to another town, remove a car for much longer than the controller expects.
  • Airport and account pre-books, the most valuable work, get the same treatment as a short local hop.

Most dispatch systems have settings that help, such as advance release times and priority for booked work. They are often left at their defaults because nobody has had time to tune them against your own busy-night patterns.

Two kinds of customer, both disappointed

Pre-booked customerOn-demand customer
What they expectThe car at the time they bookedA reasonable wait quoted honestly
What goes wrongCar arrives late or not at allQuoted a short wait, then waits much longer
What it costs youTrust, repeat bookings and account workCancellations and bad reviews
Who takes the callController, at the busiest timeCall handler, repeatedly

Account and airport customers are the ones you can least afford to let down, and they are the most likely to be pre-booked.

A lookahead that protects the booked work

What we build works alongside your dispatch system, using its data and, where it allows, its settings.

  1. We start with your own past busy nights: when pre-books fell late, how long on-demand jobs in each area took, and how many cars were really free.
  2. A rolling lookahead shows, for each area, the pre-booked jobs due in the coming period and the drivers likely to be clear in time to reach them.
  3. Where the lookahead shows a shortfall, pre-booked jobs are released to drivers earlier, and account and airport work is given priority according to rules you set.
  4. Call handlers and your booking app see a live indication of the realistic wait for on-demand work in each area, so quotes are honest.
  5. When capacity is fully committed, the tool advises the office to pause or limit on-demand acceptance in that area, and the decision stays with the controller.
  6. After each busy night, a short report shows which pre-books ran late and why, so the rules can be adjusted.

Where your dispatch system allows changes to release times and priorities through its settings or API, we adjust them there rather than building a second dispatch.

Busy nights, pre-books on time

Controllers see trouble coming. If a cluster of station runs is due at quarter to eleven and every car in that area will be on a job, it shows up earlier in the evening, while there is still time to bring a driver across from a quieter area.

Call handlers stop promising five minutes when it will be thirty. On-demand customers get an honest wait, and fewer of them cancel after booking.

Your best work, the airport runs and the account customers, becomes the most reliable part of the night rather than the part that suffers most.

Is this your Friday night?

  • Pre-booked customers ring asking where their car is.
  • Controllers pull drivers off the queue to cover booked jobs.
  • Call handlers quote waits that turn out far too short.
  • Your dispatch settings have never been reviewed against your busy nights.
  • Account and airport jobs run late on the same nights every week.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Do we have to replace our dispatch system?

No. We work with your existing system, using its data and any settings it lets us adjust, and only add what it cannot do.

Will it turn down customers automatically?

No. It advises the controller when capacity is committed. Whether to decline or quote a longer wait is your decision.

How does it know how long jobs take?

From your own completed jobs, by area and time of day, which reflects local traffic better than a general estimate.

What drives the cost?

How much data your dispatch system exposes, whether settings can be adjusted through its API, and how many areas and rules you want.

Keep reading

More on Problems We Solve

Start here

Tell us where your taxi office loses time

Describe the bookings, the drivers and the paperwork that are causing trouble, the dispatch system you run and the accounts you invoice. We will tell you what we would build around your existing setup and what we would leave alone, and if your dispatch system already does the job with a setting you have not switched on, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →