How to Manage a Taxi Fleet: Dispatch, Drivers and Bookings

Managing a taxi fleet is four jobs at once: getting demand in the door, getting it assigned to a car, keeping enough vehicles and drivers available to answer it, and knowing afterwards what actually happened. Most local operators are good at the first three and blind on the fourth, which is why a busy month and a profitable month are not always the same month. This guide covers how the pieces fit together and what to fix first when the operation starts slipping.

What does managing a taxi fleet involve day to day?

Day to day, running a fleet comes down to four cycles that never stop: demand arrives, trips get assigned, vehicles and drivers stay available, and the results get recorded. Everything else, including the software, exists to make one of those four cheaper or less error-prone. When an operation feels chaotic, it is almost always because one cycle is being handled by memory instead of by a system, and the usual culprit is the second one. The trips that get lost are rarely the ones happening now; they are the ones somebody promised for Thursday.

How do you organize dispatch so rides stop getting lost?

Put every trip in one place, whatever channel it came from, and make future trips as visible as live ones. A ride that arrives by phone, one that arrives through your booking app and one that a regular customer arranged last week all have to land on the same screen, or the dispatcher ends up reconciling three sources under pressure and one of them loses. From there, three rules do most of the work: every trip has an owner, every trip has a status, and no trip is committed on a promise nobody else can see.

Automatic assignment absorbs ordinary volume by distance or availability. Manual assignment exists because your dispatcher knows things the software does not, like which driver knows that hospital entrance or who is ending a shift in twenty minutes. A local fleet needs both, and a platform that never lets a person override the machine will fight your operation instead of supporting it.

Driver shifts, coverage and turnover

Coverage is a scheduling problem before it is a hiring problem. Most fleets do not lack drivers overall; they lack drivers at the specific hours where demand spikes, usually early mornings, school runs, Friday nights and the airport waves. Look at where the gaps really are before you conclude you need more people. The things worth keeping in writing:

• Who is scheduled tonight, and who confirmed it
• Which hours you routinely refuse trips because nobody is free
• How long a new driver takes to be productive after joining
• Which drivers get the most repeat requests from customers
• What a driver has to do at the end of a shift, and whether it actually gets done

Turnover is expensive in a way that rarely shows up as a line item: every departure takes local knowledge with it and resets the training clock. Drivers who understand how trips are assigned, and who believe the assignment is fair, stay longer than drivers who suspect the good work goes to somebody's friend.

Vehicle availability and maintenance

A car in the shop on a Friday costs more than the repair. Fleet management means treating maintenance as scheduled downtime rather than as an emergency, which means planning it for the hours that produce the least work and knowing in advance which vehicle covers the gap. Keep a simple record per vehicle: mileage, last service, upcoming inspections, insurance dates and recurring faults. It does not need to be sophisticated, it needs to be current, and it needs to be somewhere other than one person's head.

Where do your bookings come from, and who owns the customer?

This is the question that decides what your fleet is worth in five years. When rides arrive through a marketplace, the platform brings demand but keeps the relationship: the customer belongs to the app, the trip history sits on the other side, and every ride carries a percentage. When rides arrive through your own phone line, your website or your own booking app, you earn the demand yourself, and you keep the customer, the history and the margin. Most local operators run both for a while and gradually shift the balance, which is a reasonable strategy as long as you know which direction the balance is moving.

Which numbers should a fleet owner review every week?

A handful, and the same ones every week, so you can see direction instead of noise. Most owners look at revenue only, which tells you whether last week was good but never why. These are the ones that point at a decision:

• Trips completed, versus trips requested and not covered
• Average time from request to assignment during your peak hour
• Cancellations, split by who cancelled
• How many riders booked more than once this month
• Trips per vehicle per shift, so you can see which cars are actually working
• Which accounts went quiet compared with last month

The last one is the most valuable and the most ignored. A corporate account that stops calling rarely complains first; it simply disappears, and you notice a quarter later.

When has the phone-and-notebook system run out of road?

When the cost of remembering exceeds the cost of recording. Concretely: when a trip promised for next week gets missed more than once, when two drivers show up for the same pickup, when the dispatcher cannot say who is free without making calls, or when nobody can reconstruct last month without scrolling a chat group. Any one of those is survivable. Two or three together mean the operation is now limited by its record-keeping rather than by its cars or its demand.

What software changes, and what it does not

Software fixes coordination, visibility and memory. It does not create demand, it does not make a driver polite, and it does not fix a service area that is too big for the number of cars you have. Being honest about that line saves money: a fleet with a marketing problem that buys a dispatch platform still has a marketing problem, now with better reports. The right sequence is usually to fix the operational leaks first, because a booking that arrives into a chaotic dispatch is a booking you paid for and then lost.

Where WayCab Plus fits

WayCab Plus develops, configures and maintains the rider app, driver app and dispatch panel that a transportation company runs under its own brand, on a monthly fee with no percentage per ride, unlimited drivers and technical support included 24/7. It addresses the coordination side of fleet management: one place where every trip lands, a dispatch view a local team can operate, and a booking experience that carries your name instead of somebody else's.

Frequently asked questions

How many dispatchers does a small taxi fleet need?

It depends on your peak hour, not on your fleet size. Count how many trips arrive in your busiest sixty minutes and how many channels they arrive through, because a dispatcher juggling phone, chat and a booking inbox saturates far earlier than one working from a single screen. Measure your own peak before hiring.

Can I run a taxi fleet with WhatsApp and a spreadsheet?

Yes, and many profitable fleets started exactly there. It breaks in a predictable place: scheduled trips. Live rides are self-correcting because someone is waiting and complains, while a reservation taken on Tuesday for Saturday fails silently until the customer calls. That is usually the moment to move.

What should I fix first if my dispatch is a mess?

Consolidate the channels. Until every trip lands in one place with a status and an owner, any other improvement is built on an incomplete picture. Once that is true for a full week, the numbers finally tell you what to fix next instead of you guessing.

Does a booking app replace my phone line?

No, and treating it as a replacement is how fleets lose their oldest customers. The app becomes an additional door, especially for corporate accounts and regulars who book ahead. The phone keeps working, and the dispatcher enters those calls into the same system so both paths end up in the same place.