An inspection problem is often a record-keeping problem. For London private hire operators, minicab owners and transport compliance managers, being unable to produce a complete, current record can turn routine verification into a stressful scramble. A practical review of your processes can help identify gaps before the next inspection or compliance request.
This guide sets out ten common failure causes and the concrete steps operators can take to address them. Requirements can vary according to the circumstances and current licensing rules, so check the latest applicable guidance when reviewing your procedures.
1. Documents are scattered across inboxes, messages and paper files
What goes wrong: A driver’s documents are split between email, WhatsApp, paper folders and someone’s personal phone. When a record is requested, staff cannot assemble a complete file quickly.
Why it happens: Documents arrive through different channels, and nobody is responsible for moving each item into an official record.
The fix: Create one central, access-controlled record for every driver and every vehicle. Set a clear process for receiving, checking and filing documents, and restrict access to people who need it for their role. Keep the record organised so staff can identify the current approved version without searching separate devices.
2. Expired documents are found after the lapse
What goes wrong: An insurance certificate, vehicle licence or other required document has expired, and the operator discovers the problem only when checking a file or responding to a request.
Why it happens: Expiry dates are noted inconsistently, or everyone assumes someone else is monitoring them.
The fix: Record each relevant expiry date in a shared tracking process. Set advance reminders at appropriate intervals and name a person responsible for following up. Make the process include checking that an updated document has been received and reviewed, not simply sending a reminder.
3. Right-to-work records are incomplete or out of date
What goes wrong: The file contains a scan but not enough information to show that a check was completed properly, when it took place or whether a repeat check is needed.
Why it happens: A copy of a document is treated as the whole record. In reality, right-to-work checks must be carried out and recorded correctly, with any required follow-up managed at the right intervals.
The fix: Use a consistent checklist to record the check date, method, evidence reviewed, result and any follow-up date that applies. Keep the record secure and make the responsible person clear. A shared drive of scanned documents is not the same as a maintained check record. Check current requirements for the individual’s circumstances and the applicable process.
4. Driver details do not match the vehicle or booking record
What goes wrong: The operator has driver records and booking records, but cannot reliably show which eligible driver completed a particular booking in which vehicle.
Why it happens: Driver eligibility, vehicle allocation and booking or dispatch details are maintained in separate workflows. Changes to an assignment are not reflected consistently.
The fix: Establish a reliable process for recording the relevant driver and vehicle against each booking, using the identifiers required for your operation. Reconcile assignments and booking records regularly. Where a booking changes hands or a vehicle is substituted, ensure the final record reflects what actually happened.
5. Vehicle documents are not connected to driver assignments
What goes wrong: Insurance, MOT, vehicle licence and testing records are filed against a vehicle, but staff cannot establish which drivers were assigned to it during the relevant period.
Why it happens: Vehicle checks and driver checks are managed as separate administrative tasks, with no routine cross-check.
The fix: Maintain a record for each vehicle and a clear history of driver assignments. At the point of allocation, confirm that the relevant vehicle and driver records are current and correspond to the planned work. Review exceptions, including temporary substitutions and changes in assignment, so the record trail remains coherent.
6. There is no audit trail for document decisions
What goes wrong: A document is present, but the operator cannot show when it arrived, who reviewed it or whether it was accepted, queried or replaced.
Why it happens: Staff save files without recording the decisions and actions that followed.
The fix: Record receipt, review and approval details, including dates and the name or role of the person responsible. Keep superseded versions identifiable rather than allowing them to be mistaken for current documents. A clear audit trail helps demonstrate that a process was followed, not merely that a file exists.

7. Records are unreadable, misnamed or duplicated
What goes wrong: A scan is blurred, a file name reveals little about its contents, or several versions appear to be current. Staff lose time verifying which record is relevant.
Why it happens: Documents are uploaded without basic quality checks or naming conventions.
The fix: Check each file for legibility, completeness and correct association with the driver or vehicle before filing. Use consistent names that help identify the subject, document type and date. Mark replaced files clearly and avoid keeping confusing duplicates in the active record. Retain records according to the applicable requirements and your organisation’s retention policy.
8. Staff are not prepared to produce records on demand
What goes wrong: A compliance request arrives and the person answering does not know where records are held, who can retrieve them or how to respond accurately.
Why it happens: Inspection readiness is treated as the compliance manager’s job alone, rather than a process that office staff should understand.
The fix: Train relevant staff on where records are stored, how to retrieve them, who approves a response and how to escalate a missing or unclear item. Run a practice request: ask a staff member to locate a sample driver record, vehicle record and booking entry. Use the results to identify access or training gaps.
9. Partner and subcontracted drivers or vehicles are left out
What goes wrong: The operator’s own records are organised, but partner or subcontracted drivers and vehicles are not covered by the same checks and record-keeping process.
Why it happens: Third-party arrangements are treated as outside the operator’s compliance picture, or responsibilities are assumed rather than agreed.
The fix: Define, before work begins, which records must be provided, who checks them and how changes are reported. Apply a consistent process to relevant partner drivers and vehicles, and retain evidence of checks and assignments in the appropriate records. Confirm that responsibilities are understood by both parties.
10. Fixes after an inspection are not made repeatable
What goes wrong: A missing record is found and corrected, but the same type of gap returns at the next inspection.
Why it happens: The immediate issue is fixed without identifying the process failure behind it.
The fix: For each finding, record the cause, corrective action, owner and review date. Update the relevant checklist or procedure, then test whether the new step is being followed. Review repeat issues with the people responsible for the process. A documented corrective action turns a one-off response into a lasting improvement.

A one-week pre-inspection readiness checklist
Use this as a focused working plan. Adapt it to your operation and check current requirements for records and formats.
- Day 1: Confirm the inspection scope, identify the responsible coordinator and list the records likely to be requested.
- Day 2: Sample driver files. Check eligibility details, right-to-work checks, document dates, legibility and review history.
- Day 3: Sample vehicle files. Check relevant insurance, MOT, vehicle licensing and testing documents, then review driver-to-vehicle assignments.
- Day 4: Test booking and dispatch records. Confirm that the relevant people, driver and vehicle can be identified in line with current requirements.
- Day 5: Review expiry tracking, partner records and any open document requests. Assign owners to missing items and follow them up.
- Day 6: Ask a trained colleague to retrieve sample records without assistance. Note anything that takes too long or cannot be verified.
- Day 7: Close priority gaps, document corrective actions and brief relevant staff on the response and escalation process.
What good records look like
Good records are complete, current, legible, attributable to a named person, time-stamped and retrievable in minutes. Each record should make clear who or what it relates to, what was checked, when it was checked and who handled the review. The aim is not to collect files for their own sake. It is to make the operator’s decisions and processes verifiable.
Where a document management system fits
A TFL document management system can support this work by bringing driver and vehicle records into one controlled place. Driver uploads, expiry reminders, role-based access and audit history can help staff follow the same process and retrieve the right record more efficiently. The system supports the operator’s controls; it does not replace the need for accurate checks, clear responsibility or review of current requirements. Learn more about B2B IT Solutions’ TFL Document Managing System.
A compliance request or driver query may also arrive outside normal office hours, or during a period when the team is handling a high volume of calls. A 24/7 call centre partner can help keep the phone line and compliance mailbox answered, capture the request and route it to the responsible person. Clear escalation instructions are essential: support staff should know how to record and pass on a query, while compliance decisions remain with authorised personnel.
Prepare the process, not just the files
Inspection readiness is built through consistent habits: clear ownership, accurate records, timely reviews and staff who know how to retrieve information. For support with document workflows or around-the-clock enquiry handling, contact B2B IT Solutions to discuss your operational needs.

