UK cities
45+
Direct coverage
Uber UK driver and passenger
Uber UK accident claims for drivers and passengers
Platform-specific accident management for UK Uber drivers and Uber passengers. Covers the Uber London Limited and Uber Britannia Limited operator structure, the three driver insurance states (App Off, App On, Trip Accepted), the in-app Report incident flow, account deactivation, loss-of-earnings on Uber Pro earnings statements and the UberEats courier distinction.
- Uber driver dispatch 24/7
- Licensed PHV like-for-like
- Independent engineer
- Non-regulated accident support
24/7
UK response
Recovery dispatch and live claim handlers, 365 days a year.
Response
<60m
First contact SLA
Cost
£0
Upfront to driver
Uber is the largest single private hire platform on UK roads and the platform most commonly involved in PHV collisions handled by accident-management firms. This page is the Uber-specific extension of the wider UK minicab / PHV accident claims hub. It explains Uber’s UK operating model, the three driver-insurance states, the role of the driver’s own hire-and-reward policy, Uber’s in-app Report incident flow, the temporary account deactivation playbook, the passenger’s route to recovery, the UberEats courier carve-out and how loss of earnings is proved from Uber Pro app data. Every load-bearing fact is taken from a primary source: the relevant UK statute, the Supreme Court judgment in Uber BV v Aslam, the TfL licence checker or the published Uber UK help pages. Where Uber’s arrangements have moved, the page reflects the position as published on uber.com/gb at the date of last review.
Uber’s UK operating model: ULL, Uber Britannia and the worker-status overlay
Uber operates in the United Kingdom through two regulated entities. Inside Greater London the operator is Uber London Limited (ULL), Companies House company number 08014782, which holds Transport for London private hire operator licence number 0017005 and is regulated under the Private Hire Vehicles (London) Act 1998. Outside Greater London the operator is Uber Britannia Limited, Companies House company number 08823469, which holds a private hire operator’s licence with each district council where Uber runs services, under Part II of the Local Government (Miscellaneous Provisions) Act 1976. The booking confirmation and the in-app receipt always identify which entity accepted the booking, and section 56 of LGMPA 1976 deems that operator to be the contracting party with the passenger.
The driver, by contrast, is neither an employee of Uber nor a conventional self-employed contractor. In Uber BV v Aslam [2021] UKSC 5 the Supreme Court held unanimously that Uber UK drivers are “workers” within section 230(3)(b) of the Employment Rights Act 1996 from the moment the Driver app is switched on and the driver is willing and able to accept trips. The ruling concerns minimum wage, working time and holiday pay. It does not transfer motor accident liability to Uber and it does not make Uber the insurer of the vehicle. The driver remains the registered keeper, the insured under the hire-and-reward certificate of motor insurance and the holder of the PHV driver licence - those obligations sit with the individual driver irrespective of worker status.
The practical consequence for an accident file is that the contractual layer to pursue depends on the question being asked. For damages arising from the driving of the vehicle, the parties to look at are the driver, the driver’s hire-and-reward insurer and the at-fault third party (where one exists). For breach-of-licensee-duty arguments - failure to investigate, failure to preserve trip data, defective passenger protection - the party to look at is the operator (ULL or Uber Britannia). For supplementary benefits to the injured driver, the party to look at is the Partner Protection underwriter (Allianz Partners). All three layers may run in parallel on the same incident.
CityGrip’s intake process records the operator on the booking, the driver identifier and the certificate of motor insurance separately, because each identifier unlocks a different recovery route. The same record-keeping discipline lets us push back against the not-uncommon scenario where one party (often the operator) seeks to deflect responsibility to another (usually the underwriter) without first preserving the evidence the recovery actually depends on.
Uber’s UK driver insurance arrangement and Partner Protection
Uber does not itself underwrite the driver’s motor risk in the UK. The driver provides the certificate of motor insurance. Uber’s published help pages at uber.com/gb/en/drive/insurance/ tell every UK driver that a valid private hire (hire-and-reward) policy is a precondition of activating the account and remaining online. Common UK underwriters and managing general agents in the Uber-driver segment include Aviva-backed schemes, Zego, Inshur, Markel and Acorn Insurance. Premium is rated against the driver’s personal claims history, the mileage on the vehicle, the geography of the work and (on the leading insurtech products) telematics. Cover is sold on rolling thirty-day, quarterly or annual terms.
On top of the driver’s own motor cover, Uber adds a non-motor supplementary benefit called Partner Protection, underwritten through Allianz Partners. Partner Protection is an accident, sickness and hospitalisation product. It pays defined benefits to the driver - in events such as on-trip injury, hospitalisation or temporary disability - at the rates and qualifying windows set out by Uber. It is not third-party motor liability cover. It does not pay the third party’s damage claim. It does not replace the driver’s hire-and-reward policy. The two operate on parallel tracks: the motor claim runs through the certificate of motor insurance and section 151 of the Road Traffic Act 1988; the Partner Protection claim runs through Allianz Partners’ in-app benefit flow.
The single point of confusion most often raised by drivers is whether Uber “has my back” for an accident. The answer is layered. For the injury-to-driver layer Partner Protection responds. For the damage-to-vehicle and third-party-injury layer the driver’s own hire-and-reward insurer responds. For the trip data, the booking record and the passenger evidence the operator (ULL or Uber Britannia) preserves and provides the record. None of these layers is a substitute for the others. A driver who relies on Partner Protection alone is materially exposed on the third-party side; a driver who relies on the hire-and-reward policy alone is materially exposed on the personal-injury benefit side. We file all three layers on a serious-injury Uber file as a matter of course.
The driver’s hire-and-reward policy must remain in force throughout the period of work. Uber will not pay claims that arise out of an uninsured trip and Aviva and the other UK PHV underwriters do not retroactively cover periods when the certificate of motor insurance was off-risk. Lapsed cover is the single most common reason a notification fails. The certificate, including the start and expiry dates, should be ready in the in-app document store on the day of any collision.
The three insurance states: App Off, App On (Period 1), Trip Active (Periods 2 and 3)
In the working life of an Uber driver the vehicle is in one of three insurance states. App Off: the Driver app is closed. The vehicle is being used privately. Only the driver’s own motor policy responds - either the private hire (hire-and-reward) certificate under its social, domestic and pleasure endorsement if it has one, or a separate household SD&P policy on a vehicle that is registered for occasional PHV use. There is no Uber-side cover when the app is off.
App On, waiting for a trip - commonly called Period 1: the driver is logged into the Uber Driver app, is available to accept a request and has not yet accepted one. The vehicle is on the road in a working capacity. The driver’s hire-and-reward policy is the responding layer; Uber’s public help pages require the hire-and-reward policy to be live in this state. On some specialist schemes the Period 1 state is covered without endorsement; on others a specific “app on, no booking” endorsement is required. Drivers should test the policy wording against Period 1 at renewal - this is the most common coverage gap in the UK PHV market.
Trip accepted / en route / trip active - commonly called Periods 2 and 3: the driver has accepted a request and is either driving to pick up the rider (Period 2) or is on a trip with the rider in the vehicle (Period 3). The exposure is at its highest in these states because the vehicle is being used to carry a paying passenger. The driver’s hire-and-reward policy continues to respond. Partner Protection coverage windows are typically anchored to these states; the exact qualifying windows are set out by Allianz Partners under the Partner Protection product summary and may include a short post-drop-off window.
For a non-fault claim against an at-fault third-party driver, the Uber state is relevant primarily for the loss-of-earnings calculation (when was the driver actually earning?) and for Partner Protection eligibility. The third-party insurer’s primary liability for the loss it caused is unaffected by which state the Uber vehicle was in. For a fault or partially-faulted claim, the Uber state becomes decisive: it controls which of the driver’s policies responds, whether a Period 1 endorsement is needed, and whether the operator can preserve the relevant trip telemetry. CityGrip records the Uber state on the day-one intake call, with the trip identifier and the GPS pings, before any evidence is at risk of being archived by the platform’s rolling retention windows.
How to notify after an Uber collision: in-app Safety Toolkit, insurer, regulator
Uber’s published Report incident flow in the Driver app Safety Toolkit is the primary channel for notifying the operator. Uber’s UK help pages tell drivers to use the flow as soon as it is reasonable to do so. The flow captures the trip reference (the in-progress trip or the immediately preceding one), a short narrative, the other driver’s details, the police incident reference, the damage photographs and the dashcam clip where one is fitted. The trip GPS pings are captured automatically by the platform and stored against the report. The operator licence conditions, both in London under PHV(L)A 1998 and outside London under LGMPA 1976, expect notification “quickly” - the industry norm and the wording in most onboarding terms is inside 24 hours.
The next notification, in parallel, is to the driver’s own hire-and-reward insurer. This is the policy that actually responds on damage to the vehicle and to a third-party indemnity if a claim is later brought against the driver. The hire-and-reward insurer’s claims line typically operates 24/7 and the evidence pack to send is the same pack sent to Uber: photographs, dashcam, the other driver’s section 170 details, the police reference and a one-page factual narrative.
The third notification is to the licensing authority. For a TfL-licensed PHV the published licensee responsibilities require the owner to notify TfL of any collision that materially affects the safety, performance, appearance or comfort of the vehicle within 72 hours, with re-inspection as a precondition for putting the vehicle back on the road. Outside London the position is set by the individual district council’s licence conditions; many councils mirror the 72-hour rule, some require notification by the next working day and a few impose a tighter window for serious damage. Failure to notify can lead to suspension of the vehicle plate independently of any operator decision on the driver account.
The order matters. Uber first, because the in-app trip data is on a rolling retention window and timely notification preserves it. The hire-and-reward insurer second, because the policy wording requires notification regardless of fault and many policies treat seven days as a backstop. The licensing authority third, because the licensing deadline is the slowest of the three. Drivers who invert the order - insurer first, Uber later - frequently find Uber has triggered an automatic temporary deactivation in the meantime because the platform’s safety system flagged a damaged vehicle on the road, which is the next section.
UBER
03
Section 3 of the walkthrough.
Uber’s account-deactivation playbook and how to get back online faster
Uber may temporarily deactivate a driver account after a reported collision while it reviews the incident. The power flows from Uber’s Community Guidelines, the UK operator licence conditions and the standard onboarding contract. It is exercised most often where a passenger has alleged unsafe driving, where a serious injury has been reported, where the police are involved or where the vehicle has been removed from the road and Uber cannot verify roadworthiness. Deactivation is ordinarily framed as temporary “pending review” rather than a permanent removal.
The route back online is evidence-led. The fastest reactivations follow a complete evidence pack submitted within 24 hours of the deactivation: the certificate of motor insurance (still valid), the police incident reference where one applies, a signed factual narrative, photographs of the damage in situ, the dashcam clip where fitted and the proof that the vehicle has been recovered to a repairer or that an engineer inspection has been booked. Where TfL or the district council has indicated that the vehicle is fit to remain plated, that determination should be in the pack. Where the bodyshop has issued a Vehicle Damage Report under section 170 procedure that is also in the pack.
Where deactivation drags on past the period that is reasonable for the review described, the escalation route is via Uber’s in-app support. Drivers who hold a TfL licence have a parallel route through the TfL complaints process if the operator’s behaviour materially affects their ability to work. Outside London the parallel route is to the district council that issued the driver licence. Court proceedings against the operator are a last resort; they are unusual in this fact-pattern but not unknown where the loss of earnings has been severe and the operator’s investigation has been demonstrably defective.
Throughout the deactivation period the loss-of-earnings clock continues to run against the at-fault driver’s insurer (where a non-fault claim is in play) or against the driver’s own first-party loss-of-use cover (where one is purchased on the policy). The deactivation is not the legal cause of the loss - the collision is - and the period of loss is measured from the date of the collision to the date the driver is realistically able to return to work, which in turn depends on the vehicle, the licence and the account all being available.
The Uber passenger’s claim: a third-party route, with the Uber app as evidence
A passenger injured in an Uber trip has the same rights as any other road traffic victim. The claim is brought against the at-fault driver’s insurer, whoever that driver is. If the third-party driver in another vehicle was at fault, the passenger’s claim goes against that driver’s insurer under section 151 of the Road Traffic Act 1988. If the Uber driver was at fault, the claim goes against the Uber driver’s own hire-and-reward insurer named on the certificate of motor insurance. The certificate is requested through Uber’s support process where it cannot be obtained from the driver directly.
The Uber app is the evidential backbone of the passenger’s claim. It records the trip - start, end, vehicle, driver, GPS pings - automatically. It is the single source most likely to disprove the “you weren’t in the car” defence sometimes raised by an at-fault driver’s insurer. The passenger’s first step is to keep the trip receipt and to download the trip history. The second step is the in-app Help screen, which routes serious-injury reports to Uber’s safety team. The third step is the medical record - A&E attendance the same day where injury is suspected, a GP visit within 72 hours where it is not.
For pain, suffering and loss of amenity up to £5,000, the procedural route is the Official Injury Claim portal at officialinjuryclaim.org.uk under the Civil Liability Act 2018 reforms. The duration-banded whiplash compensation tariff is fixed by regulation. Above the small-claims threshold the route is the conventional pre-action protocol for personal injury claims, the OIC portal does not apply and the claimant is typically represented by a solicitor on a no win, no fee conditional fee agreement - our wider hub on a personal injury claim after a car accident covers the quantum heads. Where the at-fault driver was uninsured, the file routes through a MIB uninsured driver claim; where they fled before details were exchanged, through a MIB untraced driver claim. The same three-year limitation period runs whichever route applies. Property loss - phones, watches, work equipment lost in the collision - runs in parallel as a six-year claim under section 2 of the Limitation Act 1980.
Uber’s in-app safety contact is the appropriate first message for a passenger who wants to flag an incident with the platform, but the claim itself is not adjudicated by Uber. The platform’s role is evidential preservation and regulator-facing reporting; the substantive recovery is run between the passenger (or their solicitor) and the at-fault insurer. CityGrip works with the passenger in tandem with the driver, where instructions are taken from both, with conflicts managed under standard intake protocols.
UberEats and the courier carve-out: a different insurer, a different file
UberEats is a separate vertical. A courier on UberEats - typically on a moped, scooter, motorbike, e-bike or bicycle - is not on a private hire vehicle policy because they are not carrying paying passengers. They need hire-and-reward delivery cover, which is a different insurance class from PHV. The most widely used product in the UK courier-on-UberEats segment is Zego’s pay-as-you-go food delivery cover, which integrates directly with the UberEats Courier app on a per-minute basis with a minimum one-hour activation. Other UK courier insurers include Acorn, Aviva (under its commercial vehicle product) and a number of insurtech entrants.
The implication for an accident file is that an UberEats courier is not covered by the Uber UK private hire insurance arrangements described above. A moped courier injured on an UberEats trip notifies the courier insurer, not the Uber-driver insurer. Partner Protection is not available to UberEats couriers on the same terms as Uber-driver Partner Protection; Uber’s separate delivery partner support runs a different scheme. The trip data captured on the UberEats Courier app is still recoverable via the Uber group’s data-subject access process, which is helpful where the courier needs to evidence that the trip was in progress at the moment of collision.
Where the two worlds collide - for example where a moped courier collides with a UberX passenger vehicle - both files run in parallel: the courier-side claim under the courier policy, the passenger-side claim under the at-fault driver’s insurer. CityGrip’s practice is to record which platform side each party was on at the moment of collision and to instruct the correct hire-and-reward underwriter accordingly.
Proving loss of earnings on Uber Pro: app earnings statement, commission and net pay
The Uber Pro earnings statement is the primary evidence for a UK Uber driver’s loss-of-earnings claim. It is downloadable from the Driver app in PDF or CSV form and gives, per trip and per week, the gross fare, the Uber service fee, the booking fee, any quest or incentive payments, and the net pay to the driver. The Uber service fee on UberX is widely reported at around 25%, with variation by product (Uber Lux / Premier carries a higher fee structure) and by promotional period. The booking fee is a fixed per-trip charge. Quests and incentives are contingent on hitting trip-volume or acceptance-rate targets.
The build sequence for the loss-of-earnings file is: pull the last six to eight weeks of earnings statements before the collision; reconcile to the bank credits from Uber; deduct fuel at actual receipts; deduct an apportionment of the vehicle’s fixed costs (rental or finance, hire-and-reward insurance, MOT, servicing) across the hours actually driven; deduct vehicle depreciation on a reasonable basis (a few pence per mile is the conventional figure); and finally deduct Class 2 and Class 4 National Insurance and the income-tax band the driver is in. What is left is the driver’s net hourly take. Multiply by the hours the driver would have worked in the off-road period and the result is the special-damages figure that goes into the schedule of loss.
The credibility tests an at-fault insurer will run against the figure are predictable. The platform statement should reconcile with the bank statements cent-for-cent. The hours claimed should reconcile with the trip timestamps. The fuel receipts should reconcile with the mileage on the earnings statements. The SA302 tax calculation should reconcile with the gross fares net of operator commission. Where any of those checks fails, the claim is at risk of being discounted. Where they pass, the at-fault insurer’s engineer and claims team have very little to push back on.
The duty to mitigate is real. The driver must return to work as soon as it is safe to do so, on a replacement hire-and-reward licensed vehicle where one can be sourced. The period over which loss of earnings runs is the period from the collision to the date the driver is realistically back at work, not the date the bodyshop hands the original vehicle back. Where a re-inspection is required by the licensing authority, the period runs through to the re-inspection pass date.
Cross-border PHV work on Uber and the Deregulation Act 2015
Uber’s UK platform spans both Greater London and the rest of England and Wales. A driver licensed in Manchester can pick up a job in Salford; a driver licensed in Birmingham can drop off in Solihull. The legal basis is the Deregulation Act 2015, which standardised PHV licence durations, and the sub-contracting machinery in section 55B of the Local Government (Miscellaneous Provisions) Act 1976, which allows operators in different licensing areas to pass work between each other. The combined effect is that pre-booked private hire work can be performed across local-authority boundaries in England and Wales, provided the driver, vehicle and operator licences are all held in the same authority area - the so-called Triple Lock.
The Triple Lock is the constraint that matters for an accident file. The licensing authority that issued the plate on the back of the vehicle is the authority the driver must notify after a collision, even if the collision happened in a different council’s area. That authority is responsible for the re-inspection. That authority decides whether a Cat S or Cat N salvage vehicle can be relicensed. That authority hears any appeal against a suspension or revocation. The local authority where the collision happened has only a limited enforcement role for out-of-area vehicles, which is a recognised gap in the cross-border framework and the subject of ongoing reform discussion in Parliament.
For an Uber driver this has two practical consequences. First, the operator on the booking - ULL inside Greater London, Uber Britannia outside - does not change with the geography of the trip; the operator is fixed by where the driver’s account is registered. Second, the recovery and re-inspection arrangements should be planned around the licensing authority, not the geography of the collision. A Manchester-plated Uber that crashes in Liverpool is recovered to a Manchester bodyshop and re-inspected by Manchester City Council’s licensing examiner. A TfL-plated Uber that crashes in Watford is recovered to a London bodyshop and re-inspected by TfL. CityGrip’s dispatch process locks the recovery destination to the licensing authority on the intake call.
The cross-border picture matters for passengers too. A passenger who books an Uber in Liverpool but is collected by a Manchester-plated vehicle is contracting with Uber Britannia Limited and (on the cross-border position) the driver is operating lawfully under the Triple Lock. The fact that the vehicle does not display the local council’s plate is not a defect - it is a consequence of the 2015 framework. Any liability claim still runs through the at-fault driver’s insurer in the usual way.
Continue inside the UK PHV vertical
Uber-specific files often need a sister page open at the same time - the wider minicab hub for the cross-platform comparison, the platform-specific Bolt or FreeNow pages where a driver runs more than one app, or the hire-and-reward insurance and TfL licence pages for the underwriter-side and regulator-side questions. The pages below sit alongside this one.
Up to the hub
Lateral topics
Six-step post-Uber-accident notification flow
Step 1
Make the scene safe and meet the duty under section 170 of the Road Traffic Act 1988
Stop the vehicle. Turn on hazards. Check the passenger and any other vehicle occupants. Exchange names, addresses, vehicle registrations and insurance details with every driver involved. If anyone is injured, if details are not exchanged at the scene, or if any animal listed in section 170(8) is hurt, the collision must be reported to a police station or constable as soon as reasonably practicable and in any event within 24 hours. Note the dashcam timestamp before vehicles are moved.
Step 2
Open the Uber Driver app and start the in-app Report incident flow
Open the Uber Driver app, tap the shield Safety Toolkit, and select Report an incident. Provide the trip reference (the in-progress trip or the immediately preceding trip), a short factual narrative, the other driver's name, registration and insurer, the police incident reference where one exists and photographs of the damage and the scene. Uber's published help pages tell drivers to use this flow as soon as it is reasonable to do so and the operator licence conditions expect notification quickly so trip telemetry is preserved.
Step 3
Notify your own hire-and-reward insurer in writing
Uber requires drivers to hold a valid private hire (hire-and-reward) policy from a UK insurer - common names include Zego, Inshur, Markel, Acorn Insurance and Aviva-backed PHV schemes. Notify the insurer in writing the same day or the next working day, regardless of fault, attaching the same evidence pack you sent to Uber. Late notification can prejudice both first-party cover for your own vehicle and any third-party indemnity if a claim is later brought against you.
Step 4
Notify the licensing authority - TfL inside London, the district council outside
TfL-licensed PHV owners must notify TfL of any collision that materially affects the safety, performance, appearance or comfort of the vehicle within 72 hours, under the licensee responsibilities published by TfL under the Private Hire Vehicles (London) Act 1998. Outside London, the district council's licence conditions issued under Part II of LGMPA 1976 normally impose a similar duty - often within 72 hours or by the next working day - and may require the vehicle to be re-inspected before it carries paying passengers again.
Step 5
Open the third-party claim against the at-fault driver's insurer
Open a claim against the at-fault driver's insurer using the certificate of motor insurance details collected at the scene. For a non-fault PHV driver the at-fault insurer pays for the vehicle damage, the loss of net earnings on platform-data evidence and a like-for-like licensed PHV replacement under Dimond v Lovell [2000] UKHL 27 and Lagden v O'Connor [2003] UKHL 64. If the at-fault driver is uninsured, the route is the MIB Uninsured Drivers' Agreement 2015.
Step 6
Engage on Uber's account-deactivation review and prepare the loss-of-earnings file
If Uber has temporarily deactivated the account, escalate inside the app and provide the certificate of motor insurance, police reference, dashcam clip and a one-page narrative. Pull eight weeks of Uber Pro earnings statements, the corresponding bank credits, fuel receipts and the SA302 to build the net loss-of-earnings file. Keep all original documents. Where the account is reactivated faster than the vehicle is back on the road, source a hire-and-reward licensed replacement vehicle through a credit hire provider so the earnings curve restarts as quickly as possible.
Uber UK accident claim FAQs
- What does Uber's Aviva insurance cover during Period 1 vs Period 2 vs Period 3?
- Uber's UK driver insurance model is built around three operating states. App Off - the driver app is closed and only the driver's own social, domestic and pleasure or private hire-and-reward policy responds. App On waiting for a trip (commonly called Period 1) - the driver is logged into the Uber Driver app but has no accepted trip; the driver's hire-and-reward policy is the responding layer and Uber's published help pages require that policy to be in force. Trip accepted and en route or trip active (Periods 2 and 3) - the driver has accepted a request and is driving to pick up, has the passenger in the car, or is completing the drop-off; the driver's hire-and-reward policy continues to respond and any supplementary platform cover (including Uber's Partner Protection benefit underwritten through Allianz Partners) is in play. The exact wording on uber.com/gb governs in any individual claim, so check the certificate of motor insurance, the Uber help-page summary on the day of loss and the platform's incident notification.
- Will Uber suspend my account after an accident?
- Uber may temporarily deactivate a driver account after a reported collision while it reviews the incident. The published Community Guidelines, the UK operator licence conditions and Uber's safety processes give it that power and it tends to exercise it where a passenger has alleged unsafe driving, where the police are involved or where the vehicle has been removed from the road. Reactivation is typically conditional on the driver providing a written incident report, the certificate of motor insurance, the police reference (where one exists), photographs and the dashcam clip. Submitting a complete evidence pack inside 24 hours is the fastest way back online. Where the suspension is unreasonable or the evidence has been ignored, the appeal route is via Uber's in-app support escalation and, for TfL-licensed drivers, the licensing authority's complaint mechanism.
- Can I make a passenger injury claim through the Uber app?
- The Uber app is the right place to report a collision and to start a safety contact, but a personal injury claim is not adjudicated by Uber. If the Uber driver was at fault, the claim is run against the driver's hire-and-reward insurer (the certificate of motor insurance names the underwriter - common UK names are Zego, Inshur, Markel, Acorn and Aviva-backed schemes). If a third-party driver was at fault, the claim is run against that driver's insurer. For low-value injury (pain, suffering and loss of amenity up to £5,000) the route is the Official Injury Claim portal at officialinjuryclaim.org.uk under the Civil Liability Act 2018. Uber's role is evidential - preserving the trip record, the dashcam where one is fitted, and the driver and vehicle details - not deciding liability or paying the damages.
- Which Uber entity is on the contract - Uber London Limited or Uber Britannia Limited?
- Inside Greater London the operator is Uber London Limited (Companies House company number 08014782), which holds the Transport for London private hire operator licence and is regulated under the Private Hire Vehicles (London) Act 1998. Outside Greater London the operator is Uber Britannia Limited (Companies House company number 08823469), which holds a private hire operator's licence in each of the district councils where Uber runs outside London, under Part II of the Local Government (Miscellaneous Provisions) Act 1976. The booking confirmation and the in-app receipt identify which entity accepted the booking. Section 56 of LGMPA 1976 deems the booking contract to be with the operator who accepted it.
- Is Uber's TfL operator licence still in force?
- Yes. Following an appeal history in 2017 and 2019, Uber London Limited holds a current TfL private hire operator licence. The licence and its scope are searchable on the TfL licence checker; the operator licence number for ULL is 0017005. Where this page is read after the most recent renewal cycle ends, the licence checker on tfl.gov.uk is the authoritative source.
- Was the driver an employee of Uber when the accident happened?
- No, but the driver's contractual position is more nuanced than ordinary self-employment. In Uber BV v Aslam [2021] UKSC 5 the Supreme Court held that Uber UK drivers are workers under section 230(3)(b) of the Employment Rights Act 1996 from the moment the app is switched on and they are willing and able to accept trips. That ruling is about minimum wage, working time and holiday pay - it does not make Uber the employer for the purpose of motor accident liability and it does not transfer the driver's hire-and-reward insurance obligation to Uber. The driver is still the owner-operator of the vehicle and the holder of the certificate of motor insurance.
- What is Uber Partner Protection and who underwrites it?
- Uber Partner Protection is a supplementary accident, sickness and hospitalisation benefit for drivers on UK trips. The underlying cover is provided through Allianz Partners. It is not motor third-party insurance - it does not replace the driver's hire-and-reward policy and it does not pay third-party damage claims. It pays defined benefits to the driver in events such as injury or hospitalisation on a covered trip. The exact terms, eligibility windows and benefit amounts are set out by Uber on the Uber help pages and on the Partner Protection product summary.
- Am I covered as an UberEats moped courier on the Uber accident insurance?
- No. UberEats couriers operate under a separate insurance arrangement from the UberX / private hire side. A moped or scooter courier delivering food on UberEats is not on a private hire vehicle policy; the courier needs hire-and-reward delivery cover, typically arranged through Zego's pay-as-you-go scooter and moped products which are integrated with UberEats. If you were injured as a moped UberEats courier you should notify the courier-side insurer, not the UberX private hire insurer. If you were injured as a passenger of an UberEats moped - UberEats does not generally carry passengers - that is an unusual case and should be discussed with a handler before notifying any party.
- What evidence does Uber want after a collision?
- Uber's in-app Report incident flow asks for the date, time and location of the collision, a short account of what happened, the trip reference where one applies, the other driver's name and registration, the police incident reference where police attended and photographs of the damage. The Driver Safety Toolkit also captures GPS pings and trip telemetry from the Uber side automatically. Provide the dashcam clip voluntarily - front, rear and cabin where fitted - because the operator will weigh up the passenger account, the driver account and the dashcam together when deciding whether to suspend the account.
- How do I prove loss of earnings on Uber app data?
- Pull the Uber Pro earnings statement for the eight weeks before the collision; this gives gross fares, the Uber service fee, the booking fee, any incentives or quests and the net pay to the driver. Cross-reference with the bank credits, the fuel receipts and the SA302 tax calculation. From the gross fares deduct the Uber service fee, booking fee, fuel at actual receipts, an apportionment of the rental or finance and insurance, vehicle depreciation on a reasonable basis and Class 2 / Class 4 National Insurance. The figure that emerges is the net hourly take. Multiply by the hours worked in a representative week and you have the weekly net loss. The driver has a duty to mitigate by going back to work as soon as it is safe to do so, on a replacement hire-and-reward licensed vehicle where one can be sourced.
- Can I work on Uber in a different city from where my licence was issued?
- Cross-border PHV work is permitted in England and Wales as a consequence of the Deregulation Act 2015 and the sub-contracting provisions in section 55B of the Local Government (Miscellaneous Provisions) Act 1976 (outside London) read with the Private Hire Vehicles (London) Act 1998 for any London-issued plate. Driver, vehicle and operator licence must all be issued by the same authority - the so-called Triple Lock - but the work itself can be performed across local-authority boundaries on pre-booked journeys. The licensing authority that matters for accident reporting is the one that issued the plate on the back of the car, not the local authority where the collision happened.
- What is the deadline for an Uber passenger injury claim?
- Three years from the date of the accident, or from the date of knowledge of the injury where that is later, under section 11 of the Limitation Act 1980. The court has a residual discretion to extend that period under section 33 of the same Act but extension is not something a claimant should plan around. For low-value injury under £5,000 (pain, suffering and loss of amenity) the route is the Official Injury Claim portal at officialinjuryclaim.org.uk under the Civil Liability Act 2018 reforms. Property damage to belongings carries a six-year limit under section 2 of the Limitation Act 1980.
- If the at-fault driver was uninsured, can I still recover?
- Yes. The Motor Insurers' Bureau Uninsured Drivers' Agreement 2015 stands behind unsatisfied judgments against uninsured drivers for collisions on or after 1 August 2015. The MIB will meet the personal injury element without limit and the property damage element subject to a £1 million property-damage limit. The Agreement has strict notice and procedural conditions - early notice, naming MIB as a defendant from the outset of proceedings, and giving the documents the Agreement requires. The parallel Untraced Drivers' Agreement applies to hit-and-run cases.
Talk to a real person
Open an Uber UK accident fileUK accident support, end-to-end.
Uber driver and Uber passenger accident management - recovery, hire-and-reward licensed replacement, independent engineer, Uber Pro loss-of-earnings build and direct dialogue with the at-fault driver's insurer. CityGrip Accident Claims (Citygrip LTD).
Calls may be recorded for quality and compliance. We do not provide legal advice. Personal injury enquiries are referred only with your consent to authorised partners.
Visit our team
London office
124 City Road
London, EC1V 2NX
Coverage
- Phone & accident form24 / 7
- Recovery dispatch24 / 7
- Repair coordinationMon-Sat 8:00 - 18:00
- SundaysEmergency only
45+UK cities
9vehicle types
GDPRcompliant
Tip: submit the accident form first - our team will call back with a reference and next steps.