Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. How Do We Stop Our Regular Contract Taxi Journeys Falling Apart Every Time a Passenger, Driver or Timetable Changes?
Problems We Solve

How Do We Stop Our Regular Contract Taxi Journeys Falling Apart Every Time a Passenger, Driver or Timetable Changes?

Taxi firms running school, hospital and works contract journeys lose track of changes. We build a run planner that keeps passengers, drivers and times current.

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

Contract journeys break down because the details, passengers, pickup times, assigned drivers and approved escorts, change often and are updated in a spreadsheet, the dispatch system and phone messages separately. We build a contract run planner that holds each run's passengers, times and approved drivers in one place, applies changes from the contracting body and from your own team, updates the regular jobs in dispatch, and gives drivers the current run sheet every day.

A run that was right last week

Many taxi firms carry regular contract work alongside their public bookings: school runs for the local authority, patient journeys for a hospital or clinic, staff transport for a factory on shifts. Each contract has its own runs, each run its own passengers, times, pickup points and, often, rules about which drivers and escorts are approved for it.

The runs change all the time. A passenger moves house. A school changes its finish time on Wednesdays. A driver who is approved for a run goes on holiday and a replacement must be found from the approved list. The contracting body emails a change on Thursday afternoon for Monday morning. The office updates a spreadsheet, maybe the dispatch system, maybe a message to the driver, but not always all three.

On Monday, a driver arrives at the old address, or a passenger waits for a car that was never told about the new time.

Three copies of the truth

The run sheet, the dispatch system and the driver's own notes all hold a version of each run. Changes land in one and are copied, by hand, to the others.

Where the run livesWho updates itHow it drifts
Contract spreadsheetOffice contract managerUpdated when the email is read
Regular jobs in dispatchControllerNot updated for one-off changes, like an early finish
Driver's notes or phoneDriverUpdated when the office remembers to tell them
Contracting body's listLocal authority or clientChanges sent by email, sometimes late

Approved driver and escort lists add another layer. The approval rules come from the contract and are your contracting body's to set, but keeping track of who is approved for which run is your office's job, and it is usually kept in someone's head.

What goes wrong when runs drift

Contract work is valuable because it is regular, and it can be lost because of a few bad mornings. A missed pickup on a school run is taken very seriously by the contracting body. Repeated late arrivals can lead to penalties or the contract not being renewed, depending on the terms.

Internally, every change costs time: reading the email, working out which runs it affects, updating each copy, and telling the driver. Replacement drivers are found in a rush, sometimes without checking they are approved for that run.

One run planner for every contract

What we build holds each contract's runs in one place and makes every other copy follow it.

  1. Each run is set up once: its passengers, pickup points and times by day of week, the destination, vehicle needs, and the drivers and escorts approved for it according to the contract.
  2. Changes from the contracting body, whether sent by email, spreadsheet or their own portal, are read in, and an AI step picks out which runs, passengers and dates are affected. A person confirms each change before it applies.
  3. Your own changes, such as a driver's holiday, are entered in the planner, and replacements are suggested only from drivers approved for that run.
  4. Regular jobs in your dispatch system are created or updated from the planner through its API, including one-off changes for a single day.
  5. Drivers receive the current run sheet each day on their phone, with any change since yesterday highlighted.
  6. A record of changes, missed or late pickups and substitute drivers is kept for each run, ready if the contracting body asks.

A Monday morning without surprises

The contract manager sees every change in one list and confirms it once. Dispatch and drivers follow automatically. When a driver is off, the office picks a replacement from those approved for that run, and the replacement gets the full run sheet, including any notes about the passengers that the contract allows you to share.

When the contracting body asks about a particular morning, you can show the run as it was that day, who drove it and when each pickup happened.

New contracts are set up in the same structure, so taking on more contract work does not mean another spreadsheet.

Signs your contract runs need this

  • Contract runs live in a spreadsheet separate from dispatch.
  • Changes arrive by email and are copied by hand.
  • Drivers have missed a change to a passenger or time.
  • Approved drivers for each run are known by one person.
  • Answering a query about a past run takes a long search.

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 you advise on the contract requirements?

No. Approval rules, checks and reporting requirements come from your contract and your contracting body. We build the planner to follow them.

Does it work with local authority portals?

It depends on the portal. Many send changes by email or spreadsheet, which we read. Where there is a portal with an export, we can use that.

Is passenger information secure?

Passenger details are kept with access controls and only shared with drivers as far as the contract allows.

What drives the cost?

How many contracts and runs you have, how changes arrive, and how your dispatch system can be updated.

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 →