"Could you wait five minutes at the pharmacy and then we'll carry on?" It's one of the most common phrases in a taxi and, at the same time, one that causes the most arguments at the end of the trip. The passenger thinks the stop was a quick favour; the driver feels they lost fifteen minutes without charging; and the fare the app showed at the start no longer resembles the one at the end. Nobody did anything wrong, but both end up annoyed.
The thesis of this article is that intermediate stops aren't a problem but a valuable service the fleet can offer and charge for clearly. What causes conflict isn't the stop but the lack of a rule. We'll look at what kinds of stops there are, how to charge for them fairly, how to tell the passenger before they happen, what to do about waiting time and when it's best to say no.
The kinds of stops that repeat most
Not all stops are the same, and treating them the same is part of the problem. A one-minute stop to pick someone up doesn't cost the same as waiting twenty minutes outside a bank. It's worth distinguishing at least these cases:
- Picking up or dropping off someone else along the way.
- A quick purchase: pharmacy, shop, cash machine.
- An errand with a wait: bank, office, clinic.
- Several destinations in the same trip, such as dropping off a group.
- A return trip with waiting at the destination.
- A detour that lengthens the original route.
Each case has a different cost for the driver: some only add distance, others add time standing still and others add both. If the fleet doesn't recognise this, the driver ends up absorbing that cost or negotiating it with the passenger, and neither option is good for the service.
How to charge for a stop fairly
The simplest way to charge for a stop is to separate what is travelled from what is waited. The extra distance is charged like any part of the trip, and the waiting is charged per minute after a certain grace period. That way the passenger pays for what they actually used and the driver receives a fair amount for their time.
The grace period matters more than it seems. Charging from the first second feels petty; never charging feels unfair to the driver. A reasonable middle ground is leaving a few minutes free per stop and charging for waiting from then on. What matters is that the rule is the same for all drivers and that the passenger knows it.
If your app lets passengers add stops when requesting the trip, the passenger can see from the start a fare that already includes the extra distance. In that case only the waiting remains to be resolved, added at the end according to the actual minutes. If the stop is requested halfway, the rule should be the same, even if the total changes from the one they saw at the start.
One last detail about charging: the passenger must be able to see at the end how much they paid for distance and how much for waiting. A receipt with that breakdown answers almost every question before it becomes a complaint, and gives the driver clear backing if someone questions the total. If your app shows that breakdown, remind drivers so they can point to it when needed.
Telling them before, not after
As with tolls or luggage, the golden rule is that the passenger learns about the cost before the stop happens. When they ask to stop, the driver can reply naturally: "Of course, happy to. Just so you know, after the first few minutes the waiting is charged per minute." That sentence doesn't sound like a charge, it sounds like transparency, and it avoids the surprise at the end.
It also helps if the rule is published in your service information or in the app's FAQ. Passengers who often request trips with stops, such as those running errands or taking their children to several places, appreciate knowing in advance how much it will cost and can plan their journeys better.
We had complaints almost every week about stops: the passenger said the driver had overcharged them and the driver said they'd waited half an hour. We set a simple rule, wrote it in the app and asked drivers to say it before every stop. Complaints on that subject practically disappeared.
When the wait gets longer
Long stops deserve a separate rule. Waiting half an hour outside a clinic or a bank isn't the same as a quick stop, because the driver stops receiving other trips during all that time. In those cases it's worth agreeing with the passenger, before the stop, whether the driver waits with per-minute charging or whether it's better to end the trip there and request another one for the return.
It's also reasonable to set a waiting limit. Beyond that limit, the driver can tell the passenger they need to leave and end the trip with what has been travelled and waited up to that point. Knowing this in advance avoids the awkward situation of a driver who doesn't know whether to wait longer or leave, and a passenger who comes out to find nobody there.
For return trips with waiting, such as taking someone to a medical appointment and bringing them back, some fleets prefer an hourly rate or a separate errands service. That way the passenger knows from the start how much they'll pay and the driver doesn't have to calculate anything on the spot.
In any case, the driver should be able to alert the dispatch centre when a wait runs longer than expected, so that someone in operations knows where they are and can help if the passenger doesn't come back.
When to say no
Not every stop can be accepted. A stop where the car can't be safely pulled over, a wait in an unsafe area at night or a stop that turns a short trip into a whole afternoon of errands can be politely declined. The fleet should back the driver in those cases and be clear about what alternative to offer the passenger.
It's also worth agreeing what happens with the passenger who asks for many stops in the same trip. Beyond a certain number, it may make more sense to offer them an hourly service than to keep adding stops. What matters is that the decision doesn't depend on the driver's mood, but on a rule everyone knows.
Reviewing stops to improve the rule
A stops rule isn't written once and forgotten. It's worth reviewing every so often how many trips include stops, how long they last on average and how many end in a complaint. Those numbers tell you whether the grace period is reasonable, whether per-minute charging feels fair or whether there's a kind of stop, such as at the bank at the end of the month, that deserves different treatment.
It's also worth listening to drivers. They know which stops make them lose the most trips, in which areas it's hard to pull over and which passengers often ask for stops. A short conversation at the fleet's monthly meeting can give more ideas for adjusting the rule than any report, and it also makes drivers feel the rule is theirs too.
And don't forget frequent passengers. If someone requests a trip with the same stops every week, such as taking their children to school and then going to work, you can offer them a fixed fare for that route or a scheduled trip. What is an exception for others is that passenger's routine, and turning it into a clear service is a simple way to earn their loyalty.
What to take away
Intermediate stops are a service passengers value highly and that, charged properly, also suits drivers. Conflict appears when there's no rule: when waiting isn't charged, when it's charged without warning or when each driver decides their own way. With a simple rule, said before each stop and written in your app, most arguments disappear.
If your fleet runs on its own app, review today how stops and waiting are added to your fares and whether the passenger can add stops when requesting the trip. A passenger who can sort out their errands in a single trip, without surprises at the end, is a passenger who orders with you again.
