What Your Private Hire Operator Licence Requires From Your Booking System

Most operators think of their booking system as an operational tool. Your licensing authority thinks of it as evidence.

If you hold a private hire operator licence in England and Wales, the records your system produces are a condition of that licence. An authorised officer can ask to see them without notice. Getting this wrong is not a productivity problem — it is a licence problem, and it is one of the more common reasons operators find themselves in front of a licensing committee.

The good news: if you record bookings properly in a decent system, you are already compliant and you will never think about it again. This article is about what “properly” means.

The most important thing to understand first

There is no single national rule. Operator licence conditions are set by each licensing authority, and they differ — sometimes substantially — between neighbouring councils.

So treat everything below as a worked example of the shape of the requirements, not as your rulebook. Your obligations are whatever your own council has published in its private hire operator conditions. If you operate across boundaries, you may be subject to more than one set.

Go and read yours. It is usually a PDF on the licensing pages, it is usually about fifteen pages, and it will take you twenty minutes.

A worked example: what a council actually asks for

Leeds City Council’s private hire operator conditions are a useful illustration because they are specific. At the time each booking is received, the operator must record:

• The time and date of the booking and the time required — using the 24-hour clock
• The full name of the hirer and the contact number used to make the booking
• A detailed point of pick-up — explicitly not just “Boar Lane” or “Headingley”
• The specific destination address
• The driver’s identifying number or name
• The plate number of the vehicle and the badge number of the driver

Three details in that list catch operators out.

“At the time the booking is received.” Not later that day, not reconstructed at the end of the week. The record is contemporaneous. A system that captures the booking as it arrives satisfies this by definition; a notebook written up on Friday does not.

“Detailed point of pick-up.” A street name or district is explicitly insufficient. This one appears in enforcement cases regularly, because “Headingley” is exactly what a rushed dispatcher types.

Vehicle plate and driver badge number. Not just “Dave”. The record has to tie the job to a licensed driver and a licensed vehicle — which means your driver and vehicle records need to be in the system too, not in a folder.

How long you must keep them

In Leeds, records must be kept in English and securely retained for at least 12 months following the date of the last entry, and must remain available for inspection at all reasonable times without notice by an authorised officer, the police or VOSA — who may remove records from the premises or request copies.

Other authorities require longer. Two years is common, and some conditions allow an authorised officer to require a longer period. Again: check yours.

Two practical points that follow from “without notice”:

1. Retrievable is part of the requirement. Records that exist but take you three days to assemble from a spreadsheet, a phone and an email archive are not meaningfully available for inspection.
2. Your retention period outlives your software contract. If you switch systems, you must still be able to produce the old records for the rest of the period. Export before you cancel, not after.

The requirement most operators have never read: system by fleet size

This is where it gets genuinely important for software choice. Leeds sets different requirements for newly licensed operators depending on size:

• Sole operator, or 2–9 vehicles — paper records are acceptable
• 10–19 vehicles — an approved computerised system is required
• Over 20 vehicles — a booking and despatch system is required

There is also a requirement for non-sole operators to use an approved voice recording system for incoming advance bookings, with the recordings corresponding to the booking record details.

Read that again if you are growing. Crossing ten vehicles can change your legal obligations, not just your workload. Operators who scale from eight cars to twelve without checking their conditions can find themselves non-compliant purely by growing — and “we didn’t know” is not a defence that plays well at a hearing.

It also means the phrase “approved computerised system” matters. Approval is by your authority, not by the software vendor. A vendor cannot truthfully tell you their product is approved in your area unless your council has actually said so — treat that claim with scepticism and confirm it with your licensing team directly.

Where poor records actually bite

Enforcement is rarely a random audit. Records get examined because something else happened, and then the records make it better or much worse:

• A complaint about a driver. Who was allocated to that job, in which vehicle? If you can answer in thirty seconds with a timestamped record, you look like a well-run operator. If you cannot, the complaint becomes a competence question.
• A police request. Something happened in a vehicle on a Saturday night. They need the booking, the driver and the plate.
• Licence renewal. Your history is in front of the committee.
• An insurance claim. The insurer wants to see that the job was properly recorded and the driver properly allocated.
• A dispute over a fare. Your record of what was agreed, and when, is the whole argument.

In each case the question is the same: can you produce the complete record for that job, quickly, without reconstructing it?

The five-minute audit

Try this now.

1. Pick a date eight months ago.
2. Produce every booking taken that day, with: time and date of booking, hirer’s name and contact number, detailed pick-up, specific destination, driver, badge number and plate.
3. Time yourself.

Under two minutes: you are in good shape. Over twenty, or you cannot do it at all: that is your exposure, and you found it before an authorised officer did.

Then repeat the test for a driver who no longer works for you. That is where most systems fall apart — deleted records, or a driver record removed along with their access.

What this means when you choose software

Judge candidates on the boring things:

• Does it capture the booking at the moment it arrives, with a timestamp you did not type?
• Does it hold the full record — hirer, contact, detailed pick-up, specific destination, allocated driver, vehicle, badge and plate — as structured fields rather than a free-text note?
• Can you export a date range yourself, on demand, without contacting support?
• Does the record survive a driver leaving or a vehicle being sold?
• Can it produce a clean printed or PDF record for an officer who wants a copy?
• Does it cover every channel? Phone bookings and WhatsApp jobs need records too. A system that only records web bookings leaves a hole exactly where enforcement looks.

That last point is the one to press hardest. Most operators take a meaningful share of work by phone and WhatsApp, and that is precisely the work that ends up unrecorded.

What we can and cannot promise you

RideDesk records every booking as it arrives — timestamped, with the customer, the pick-up and destination, and the driver and vehicle allocated to the job — regardless of whether it came from your website, the phone, email or WhatsApp, because all of those land in the same board. Customer and driver records persist, and you can export your data yourself. One deliberate choice worth knowing: the activity log — the record of who did what and when, across every booking — is on every plan including the free one, because an audit trail is a compliance need, not an upsell.

Two honest caveats. We are not your licensing authority, and no software can promise compliance with conditions we have not read — check your own council’s requirements and confirm anything described as “approved” with them directly. And RideDesk does not provide the voice recording that some authorities require for telephone advance bookings; that is a separate system.

What it does do is make the record a by-product of running the job properly, which is the only version of compliance that survives a busy Friday.

If you want to see whether it would satisfy your own conditions, send us your council’s operator conditions and we will go through them with you honestly — including the parts it does not cover.

But do the five-minute audit before you talk to any supplier, including us. Pick a date eight months back, try to produce every booking with its allocated driver, and time yourself. Whatever that exercise reveals is your real position — and if it goes badly, the fix might be a process change rather than a purchase. Then go and read your own council’s operator conditions. Twenty minutes with that PDF is worth more than any article about it, this one included.

This article is general information about the shape of typical operator licence conditions, illustrated with published Leeds City Council conditions. It is not legal advice, and requirements vary by licensing authority. Always work from your own council’s published conditions, and speak to your licensing officer if anything is unclear.