TfL Compliance: What Every London PHV Operator Needs to Know

If you run a Private Hire Vehicle (PHV) operation inside Greater London, Transport for London is your most important regulator — more important than HMRC, more important than your insurer, more important than any payment processor. Lose your TfL Operator Licence and your business stops the same day.

And yet, the rules are scattered across the TfL website, periodic Operator Bulletins, the Private Hire Vehicles (London) Act 1998, and a dozen amended Statutory Instruments. This guide pulls the 2026 picture into one place, in plain English, and shows you how modern TfL compliant taxi software turns compliance from a 4-hour-a-week paper exercise into a background process you barely notice.

The Three Licences You Need to Understand

London PHV regulation runs on three separate, individually-licensed assets:

• The Operator Licence — held by the business that accepts bookings. Issued for 5 years. This is yours.
• The Driver Licence — held by each individual driver. Issued for 3 years. Each driver applies and renews personally; you, the operator, must verify currency.
• The Vehicle Licence — held against each vehicle, issued for 1 year. Tied to MOT, insurance, and emissions standards.

You cannot dispatch a job legally unless all three licences — operator, driver, vehicle — are current at the moment of booking. Dispatch a single ride to an expired driver and you have, technically, accepted a booking you were not entitled to fulfil.

What TfL Actually Wants From You as an Operator

Strip away the legalese and TfL's expectations of an Operator come down to seven obligations:

1. Accept bookings only from a licensed operating centre using the address listed on your Operator Licence.
2. Dispatch only to licensed PHV drivers in licensed PHV vehicles. Currency is your responsibility, not the driver's.
3. Keep a complete booking record for every job for 12 months. Passenger name, pickup, destination, time of booking, time of journey, driver, vehicle, fare.
4. Keep a complaints log with date, complainant, nature of complaint, action taken, and outcome.
5. Make records available to TfL within a reasonable period (in practice, 72 hours of written notice).
6. Comply with UK GDPR for passenger and driver personal data — lawful basis, retention limits, breach reporting.
7. Notify TfL of material changes — directors, operating address, fleet expansion to a new operating centre.

Everything else — pricing rules, app-based booking disclosures, driver welfare standards, accessibility — flows from these seven.

The Booking Record: TfL's Single Most-Audited Item

If you remember nothing else from this guide, remember this: the single most common cause of operator licence variations and suspensions in London is incomplete or inaccessible booking records. Spot-check inspectors will pick a date 3–9 months in the past, give you a window of 72 hours, and ask for every booking on that day with the seven mandatory fields. If even 5–10% of records are missing fields, you have a finding.

The fix is structural, not heroic: log every booking through dispatch software, never accept jobs over WhatsApp or phone without immediately entering them, and run a monthly self-audit of 50 random bookings to catch field gaps before TfL does.

Driver Compliance: What You Must Verify, and How Often

Before a driver takes a single job for you, and on a continuing basis, you must hold copies of:

• Current PHV driver licence (3-year expiry).
• Enhanced DBS check, registered with the Update Service.
• DVLA driving licence, with periodic re-checks against the DVLA Share Driving Licence service.
• Medical (Group 2) certificate, where required.
• Right to work documentation.
• Evidence of English-language standard (now mandatory for all new and renewing drivers).
• SERU (Safety, Equality and Regulatory Understanding) assessment pass — required at first application and renewal.

Practically, this means your software must store an expiry date for each of those documents per driver and refuse to dispatch a job to anyone with a lapsed credential. Manual spreadsheets fail this test inside 6 months on any fleet over 25 drivers.

Vehicle Compliance: ULEZ, MOT, Inspection, Signage

Every PHV in London must hold:

• A current TfL PHV Vehicle Licence (1-year expiry).
• A valid MOT certificate appropriate to its age.
• Hire-and-reward insurance — private-use insurance does not cover PHV work.
• ULEZ-compliant emissions standards (Euro 6 diesel / Euro 4 petrol minimum) or the £12.50 daily charge.
• TfL-issued PHV roundels displayed front and rear.

Tip: most operators we work with run a 12-month forward calendar of every vehicle's PHV licence, MOT, and insurance expiry. The small admin time invested up front saves the much larger cost of a vehicle being pulled out of service the morning of a busy Friday.

Data Protection: UK GDPR for PHV Operators

You hold passenger names, phone numbers, addresses, journey histories, and payment data. Under UK GDPR you must have:

• A documented lawful basis for processing — contract performance for booking data, legitimate interest for fraud screening.
• Clear retention periods — TfL's 12-month booking record requirement is your floor, not your ceiling.
• A passenger-facing privacy notice on your website and app.
• A breach-notification process: serious breaches must be reported to the ICO within 72 hours.
• Reasonable technical safeguards: TLS in transit, encryption at rest, access controls on dispatch consoles.

Modern private hire software bakes most of this in: encrypted databases, role-based access, configurable retention, and exportable subject-access logs.

Complaints Handling: The Fastest Way to Lose Your Licence

TfL's complaint pipeline is direct: a passenger can email tph.complaints@tfl.gov.uk and TfL will forward the complaint to you with a deadline (typically 21 days) for substantive response. A pattern of unanswered or poorly-handled complaints — particularly anything relating to safeguarding, sexual harassment, racial discrimination, or unsafe driving — is the single fastest path to licence revocation.

The minimum viable complaints workflow: log the complaint within 24 hours; acknowledge to passenger within 48 hours; investigate by reviewing the booking record, driver, and journey audit trail; respond substantively within TfL's deadline; record outcome in your complaints log. Software that ties bookings, drivers, GPS traces, and messaging into a single record makes a one-hour investigation out of what would otherwise take a day.

The 2024–2026 Rule Changes Most Operators Are Missing

• SERU and English-language standards — every new and renewing driver must pass.
• ULEZ expansion — applies London-wide, not just Inner London.
• Safeguarding training — TfL is increasingly expecting documented safeguarding awareness for drivers, not just a clean DBS.
• App pricing transparency — ongoing TfL consultation on disclosure of dynamic pricing and booking fees.
• Enhanced data-sharing with HMRC for tax compliance — relevant where drivers are self-employed contractors.

What "TfL Compliant Taxi Software" Actually Means

The phrase gets thrown around loosely. Here is the practical checklist of capabilities any platform marketing itself as TfL compliant taxi software must deliver:

• Mandatory 7-field booking record captured on every job, immutable after acceptance.
• 12-month minimum retention with one-click export to CSV/PDF for TfL inspection.
• Per-driver document vault with expiry tracking and dispatch blocking on lapse.
• Per-vehicle document vault: PHV licence, MOT, insurance, ULEZ status.
• Complaints module with timestamped status changes and TfL deadline calendar.
• UK GDPR features: encryption, role-based access, retention policy enforcement, subject-access export.
• Audit log of every dispatch, edit, and admin action, retained at minimum 12 months.
• UK-hosted data, ideally with documented data-residency and ISO 27001-aligned controls.

Anything missing from that list is not, in any meaningful sense, TfL compliant — it is simply taxi software that happens to operate in London.

Practical Compliance Routine: What Good Operators Do Weekly, Monthly, Quarterly

Weekly: review last 7 days of complaints; spot-check 20 random bookings for field completeness; review any documents expiring in next 30 days.

Monthly: reconcile dispatched jobs vs invoiced jobs; review fleet ULEZ status; review driver/vehicle licence pipeline 90 days forward; back up data exports.

Quarterly: internal mini-audit — pick a random day from the previous quarter and produce the full inspection pack as if TfL had asked. Time it. If it takes more than 4 hours, your software or process needs work.

The Bottom Line for London PHV Operators

TfL compliance is not a one-time project. It is a continuous, low-grade discipline that the right software almost entirely automates. The operators we see thriving in 2026 — whether they're 5-vehicle independents or 200-vehicle executive fleets — share two traits: they treat compliance as a feature of their dispatch system rather than a separate admin job, and they routinely test their inspection-readiness instead of waiting to be tested.

If you want to see what fully TfL-aligned dispatch looks like in practice, see the dedicated feature breakdown at TfL compliant taxi software, or read more on the wider private hire software and London taxi software stack.