Case study · Birmingham · UK

Brum Cars Birmingham: 96-driver Cordic → TaxiCloud cutover with structural CAZ-aware routing.

96 drivers · 102 vehicles · migrated from Cordic in 8 working days · live since 2025-08.

Brum Cars is a 96-driver combined Hackney + PHV operator covering central Birmingham and the M6/M42 corridor. They migrated off Cordic in 8 working days in August 2025, lifted CAZ-related operating cost recovery 19% in the first quarter via structural vehicle-class routing, and cut Birmingham City Council quarterly compliance prep from 6 hours to under 30 minutes.

  • +19%

    CAZ operating cost recovery

    Structural CAZ-aware routing biases non-compliant vehicles outside the zone.

  • −95%

    BCC compliance prep time

    6 hours/quarter → under 30 minutes via pre-configured templates.

  • +24%

    BHX airport acceptance rate

    FlightAware live ingest + AI Copilot SMS drafts.

The migration

How Brum Cars migrated off Cordic.

Brum Cars runs out of Digbeth with a fleet split roughly 60/40 between PHV and Hackney work. The fleet sat on Cordic for four years before the migration. Their migration trigger was the Birmingham CAZ — Cordic's vehicle-class flagging was dispatcher-discretion text-notes rather than structural records, and the daily-charge accruals on non-CAZ-compliant vehicles entering the central CAZ were leaking £400-£600/month per non-compliant vehicle that the dispatch system had no structural visibility on.

TaxiCloud migration ran over 8 working days. Drivers (96 active), vehicles with CAZ-compliance flags (102), customer accounts (3,400), pricing rules with CAZ surcharges (24), and a 180-day historic booking window all imported. Drivers onboarded in three cohorts (city centre PHV, Hackney + rank work, M6/M42 corridor) over the cutover week.

First quarter on TaxiCloud: 19% lift in CAZ-related operating cost recovery (vehicle CAZ-compliance now structurally enforced with route bias keeping non-compliant vehicles outside the zone), 95% reduction in Birmingham City Council compliance prep time (6 hours → under 30 minutes), 24% lift in BHX airport job acceptance rate (FlightAware live ingest reshuffles ETAs, AI Copilot drafts SMS).

“Cordic flagged vehicle CAZ-compliance as a dispatcher-text-note. Drivers crossed the boundary every day on bookings the dispatch system thought were fine. TaxiCloud made the compliance flag structural and the CAZ daily-charge leakage stopped that week.”

Joel Whittaker

Operations Manager, Brum Cars

Frequently asked

Questions about the Brum Cars migration.

  • How long did Brum Cars' Cordic → TaxiCloud migration take?

    Eight working days. Drivers, vehicles with CAZ-compliance flags, customers, pricing rules, and historic bookings imported. Cordic ran in parallel for the first 4 days.

  • What drove the 19% CAZ operating cost recovery lift?

    Vehicle CAZ-compliance status became a first-class record field with structural route-bias logic. Non-compliant vehicles now route around the central CAZ; daily-charge leakage stopped.

  • How does TaxiCloud handle Birmingham CAZ surcharging?

    Booking widget surcharges based on CAZ entry; surcharge posts to the booking record automatically; dispatch board flags non-compliant vehicles before crossing the boundary.

  • Did Brum Cars retain its Hackney rank work post-migration?

    Yes. Both Hackney and PHV licence classes operate as first-class driver-record fields on TaxiCloud; quarterly compliance returns generate per licence class automatically.

Other case studies

Ready when you are

Dispatch on autopilot.

14-day free trial. No card. Cancel anytime.

47 fleets joined this month · Talk to sales