Taxi no-show and cancellation fee policy — a UK + Ireland operator's guide for 2026

A no-show costs more than the missed fare. The driver has spent wait time and fuel getting to the pickup, the vehicle was unavailable for another job during that window, and if the address is far from the fleet's working area, the empty return leg compounds the loss. Multiply that across a fleet running even a modest volume of pre-booked and account jobs and a policy-free approach to no-shows is a structural revenue leak, not an occasional annoyance.

Most operators can describe their no-show policy in a sentence when asked, but few can say how consistently it was actually charged last month, because enforcement has historically depended on a controller remembering to raise a manual charge after the fact — a step that gets skipped under normal shift pressure. The fix is not a stricter policy; it's a policy specific enough to apply automatically and a payment mechanism that doesn't need a human to remember to act on it.

A no-show and a late cancellation are different events and should carry different treatment. A no-show is when the driver arrives, waits out the agreed grace period, and the passenger never appears or cancels; a late cancellation is when the passenger actively cancels inside a window close enough to the pickup time that the slot likely couldn't be refilled. Treating both the same in the written policy — or worse, not distinguishing them at all — is the single most common source of a passenger dispute, because a passenger who cancelled 90 seconds before pickup feels entitled to argue they didn't 'no-show'.

A common structure UK and Ireland operators use: free cancellation up to a set window before pickup (commonly 15-60 minutes depending on booking type — pre-booked airport runs typically get a longer free-cancellation window than an on-demand city job), a reduced late-cancellation fee inside that window, and a full no-show fee once the driver has arrived and waited out a defined grace period (commonly 5-10 minutes for a standard pickup, sometimes longer for accessible-vehicle or multi-passenger jobs where a delay is more likely to be genuine).

Write the grace period as a number in the policy, not a description like 'a reasonable amount of time' — a specific figure is what a dispatcher, driver, and passenger can all point to when a charge is disputed, and it's what lets the dispatch platform apply the fee automatically once the timer expires rather than waiting on a judgement call.

A no-show fee that has to be invoiced separately and chased for payment after the fact is rarely worth the admin time it costs to collect — most operators who rely on manual invoicing for no-show fees report collecting only a fraction of what was actually charged, because passengers who never paid a card upfront have little incentive to settle a follow-up invoice for a trip that never happened. Card-on-file capture at booking — required before a job confirms, not optional — turns the fee from a collections problem into an automatic transaction the moment the no-show or late-cancellation condition is met.

This only works if the authorisation happens at booking, not at pickup. A driver arriving to find the passenger's card details were never captured has no enforcement mechanism at all — the fee exists on paper but not in practice. Confirm your booking flow (web widget, customer app, and phone-call bookings taken by a controller) all capture and validate a card before the job is confirmed, not just the self-serve app channel.

Set the fee amount transparently in the booking confirmation, not buried in a terms-and-conditions link nobody opens. A passenger who was told the exact no-show fee amount at the point of booking is far less likely to dispute the charge than one discovering it for the first time on a bank statement.

A chargeback or a passenger complaint is where a loosely written policy gets expensive — a bank's chargeback process typically sides with the cardholder unless the operator can produce specific evidence, and 'our policy says so' without supporting detail rarely satisfies that bar. Evidence that holds up: the driver's GPS arrival timestamp at the pickup address, the wait-time log showing the grace period elapsed, and the exact fee amount and policy wording the passenger agreed to at booking.

This is where the dispatch platform matters more than the T&Cs document itself. A job record that automatically timestamps driver arrival and captures elapsed wait time gives dispatch and finance a defensible, contemporaneous record instead of a driver's after-the-fact recollection reconstructed for a chargeback response weeks later. Keep the policy text itself short and specific — grace period, fee amount by job type, and the fact that a card is required at booking — rather than a long legal document a passenger is unlikely to read before agreeing to it.

Retail no-show policy doesn't map cleanly onto corporate and account business — a corporate traveller who no-shows a pre-booked airport run is usually a genuine flight change or meeting overrun, not a cancellation the passenger controls in the way a retail booking is. Most operators negotiate a separate no-show clause into the corporate account agreement itself: a defined monthly allowance of no-fee cancellations, a reduced fee structure past that allowance, and billing the fee to the account rather than a personal card, since the traveller rarely holds the payment relationship directly.

Get this written into the account agreement at onboarding, not improvised the first time a finance controller disputes a line item on a monthly statement. A corporate client who was never told a no-show clause existed will contest every charge on principle, even reasonable ones — the same transparency-at-signup logic that applies to retail passengers applies here, just negotiated once per account rather than disclosed per booking.

Ask whether the platform can capture and validate a payment card at booking across every channel you take bookings through — web widget, customer app, and phone bookings entered by a controller — not just the self-serve app. A platform that only enforces card-on-file on one channel leaves the others as an enforcement gap a controller has to remember manually.

Ask whether the grace-period timer and no-show fee trigger automatically off the driver's GPS arrival event, or whether a controller has to manually flag the job as a no-show and raise the charge themselves. Manual triggering is where enforcement quietly erodes under normal shift workload — the fee exists in policy but stops being applied consistently within weeks of go-live.

Ask what evidence the platform retains and can export per no-show or late-cancellation charge — arrival timestamp, wait-time log, fee amount, and the passenger's booking-time acknowledgement of the policy. If a vendor can't produce a sample export for a disputed charge on request, the enforcement mechanism likely stops at 'we charged the card' with nothing to back it up if that charge is challenged.

TaxiCloud requires card-on-file capture at booking across the web widget, customer app, and controller-entered phone bookings, so the enforcement mechanism is consistent regardless of how the job was created. Grace-period timers run automatically off the driver app's GPS arrival event, and once the timer expires without pickup, the configured no-show fee charges the card on file without a controller needing to remember to raise it — late-cancellation fees inside the free-cancellation window apply the same way.

Every no-show and late-cancellation charge retains an exportable record — arrival timestamp, elapsed wait time, fee amount, and the policy text the passenger saw at booking — attached to the job, so finance or a controller can produce evidence directly if a passenger disputes a charge or a chargeback is raised. Corporate accounts can be configured with a separate no-show allowance and fee schedule at the account level, billed to the account rather than a personal card, set once at onboarding rather than negotiated case by case.