UK cities
Direct coverage
Former Ola UK - residual claims
Ola Cabs ceased UK booking on 12 April 2024. The at-fault driver's motor insurer remains liable for any collision during the operational period, subject to the Limitation Act 1980 three-year personal-injury and six-year property-damage time-bars. This page covers the residual claim position for former Ola drivers and passengers.
UK response
Recovery dispatch and live claim handlers, 365 days a year.
UK cities
Direct coverage
Response
First contact SLA
Cost
Upfront to driver
Ola Cabs withdrew from the UK ride-hailing market on 12 April 2024, ending a roughly five-and-a-half-year UK operating period that began in Cardiff in August 2018 and reached London in February 2020. The withdrawal closed the consumer app and the driver platform, but it did not extinguish any motor-insurance liability for collisions that occurred while Ola was operating. The at-fault driver's insurer remains liable; the driver's own hire-and-reward policy remains in force for the period covered; and the Limitation Act 1980 time-bars run from the date of the accident, not the date of the platform exit. This page is the residual- claim route map for former Ola drivers and former Ola passengers.
Ola entered the UK in August 2018. The first city was Cardiff, chosen partly because the regulatory environment for a new private hire operator outside London is set by the local district council under Part II of the Local Government (Miscellaneous Provisions) Act 1976 rather than by TfL - a section 55 operator licence and section 51 / section 48 driver and vehicle licences can be sought district by district, which is faster for a multi-city challenger brand than the single, more prescriptive London process. From Cardiff, Ola expanded into Bristol and the wider South West (Bath, Exeter, North Somerset, South Gloucestershire), into the West Midlands (Birmingham, Dudley, Sandwell, Solihull, Walsall, Wolverhampton), into Merseyside (Liverpool, Sefton, St Helens, Knowsley, the Wirral) and into Reading.
The London licence was the headline. In July 2019 TfL granted Ola a 15-month London PHV operator's licence under section 3 of the Private Hire Vehicles (London) Act 1998. Service in London launched on 10 February 2020. The London entry coincided with a difficult period for Uber's London licensing - TfL had declined Uber's renewal in November 2019, prompting an appeal that ultimately succeeded - so Ola's London debut was widely framed as a moment of competitive pressure on Uber. The Indian press at the time described Ola as Uber's “new nightmare” on London streets, which was hyperbole but reflected a real opening for a second meaningful UK challenger.
The trajectory turned in October 2020 when TfL refused to renew Ola's London operator's licence, citing significant concerns with the company's systems and processes for reporting safety-relevant information about drivers. Ola continued to operate during the statutory appeal window - which is the standard position for any operator with a pending appeal - and on 14 December 2021 Deputy Chief Magistrate Tan Ikram, sitting at Westminster Magistrates' Court, allowed the appeal and granted Ola a fresh 15-month London operator's licence subject to strict conditions, including enhanced driver-reporting procedures and compliance with the High Court ruling that PHV operators must contract directly with passengers rather than act merely as an agent for drivers. Ola continued to operate in London and across its regional footprint until April 2024.
On 9 April 2024 ANI Technologies Private Limited - the Bangalore-based parent company of the Ola Cabs brand, CIN U72900KA2010PTC086596, incorporated 3 December 2010 at the Registrar of Companies, Bangalore - announced that it would shut its ride-hailing operations in the United Kingdom, Australia and New Zealand and refocus on the Indian market. The decision was reported by TechCrunch, The Register and the Indian business press inside 48 hours of the statement. Bookings on the UK Ola app ceased on 12 April 2024. Drivers were instructed by email to destroy any Ola materials, stickers and labels and to remove all Ola branding from their vehicles; the consumer app was withdrawn from the App Store and Google Play in stages and was no longer available for download after 11 May 2024.
The note for any claimant: a brief calibration is required. The user-facing instructions for this page referred to a March 2024 withdrawal; the contemporary press and corporate statements all date the announcement to 9 April 2024 and the cessation of bookings to 12 April 2024. The page is written to the verified April 2024 date. Anyone working from an earlier internal note should update.
The corporate-shell position is more subtle. OLA UK PRIVATE LIMITED, company number 11154418, was incorporated at Companies House on 17 January 2018 and at the time this page was reviewed remained filed as Active, with its registered office at 8th Floor Becket House, 36 Old Jewry, London EC2R 8DD. The company has continued to file accounts after the operational withdrawal - the last filed accounts were made up to 31 March 2025 and the next accounts to 31 March 2026 were due by 31 December 2026 at the time of review. Active status at Companies House is not the same as operational ride-hailing. Ola has not booked a UK ride since 12 April 2024. But the entity remains in existence for service of any proceedings and for any runoff matters. Always confirm the current status at find-and-update.company-information.service.gov.uk/company/11154418 before issuing any pleading naming Ola UK Private Limited as a party.
UK retail motor insurance - including the hire-and-reward policies a private hire driver buys from Zego, Inshur, Markel, Acorn, Patons, Aviva-backed schemes and the other specialist underwriters - is written on what insurance practitioners call a claims-occurring trigger. The policy responds to losses that occurred during the policy period stated on the certificate, regardless of when the claim is later notified. This is the opposite of the claims-made trigger common in professional indemnity, where the policy responds to claims notified during the policy period regardless of when the underlying loss occurred. The distinction matters because it is the claims-occurring trigger that protects an Ola-period claimant after the platform exit.
Practically: if you were the Ola driver and you suffered a collision on, say, 15 March 2023 while your then-current 12-month hire-and-reward policy was in force, that policy responds to that collision today. The underwriter's obligation crystallised at the moment of the loss; the platform was the booking channel, not the insurer; and the platform's later withdrawal does not unwind the policy. Similarly, if you were a passenger in an Ola-booked car on 1 December 2022 and the other driver caused the collision, the other driver's section 143 Road Traffic Act 1988 motor policy that was in force on that date responds today. Section 151 of the same Act imposes a statutory duty on the insurer to satisfy any judgment obtained, subject to limited statutory defences. The insurer cannot point to Ola's exit as a defence.
There is one indirect runoff question worth flagging. Where an Ola driver also relied on a top-up benefit that was procured by Ola itself (Ola did not in fact publish a UK equivalent of Uber's Partner Protection in any consistent form, but some regional driver communications did reference supplementary cover), that benefit was contractual with Ola and may not survive the platform's withdrawal. The driver's own hire-and-reward policy remains the primary cover in any event; the question is whether the supplementary benefit can be pursued, and that is a question of the contract terms between the driver and Ola at the time, not of motor insurance law.
For the duration of Ola's UK operations, the underlying motor insurance on every Ola-driven vehicle was the driver's own hire-and-reward certificate. The section 143 Road Traffic Act 1988 cover required to put a car on a UK road for fare-paying passenger work attaches to the driver and the vehicle, not to the booking platform. A social, domestic and pleasure policy does not satisfy the section 143 requirement when fare-paying passengers are in the vehicle; driving on SD&P with passengers for hire is uninsured for the purpose of s.143 and is a six-points-plus-fine offence under section 143(2). The driver therefore had to buy hire-and-reward from a specialist insurer - Zego (including the telematics-rated Zego Sense product), Inshur, Markel, Acorn, Patons, an Aviva-backed scheme or the equivalent.
That policy was - and where the period of cover remains within the limitation period, still is - the first port of call after a collision. The driver notifies the insurer named on the certificate as soon as reasonably practicable irrespective of fault. The insurer either deals with the claim under its own-damage and third-party heads or, more often for a non-fault loss, refers the claim to an accident-management process where credit hire of a like-for-like licensed replacement, recovery, storage, engineer inspection and the third-party recovery are coordinated. CityGrip Accident Claims operates inside that process: it does not underwrite, it coordinates.
The wider lesson - and one that any minicab driver reading this page in 2026 should hear - is that the hire-and-reward policy is the cover that survives platform events. Drivers should hold their own hire-and-reward irrespective of the platform they currently work on. The cover is not contingent on Uber, on Bolt, on Free Now or on a local operator continuing to operate. It is the driver's contract with the insurer, and it is the contract that puts the car on the road lawfully.
The two limitation periods that matter for a residual Ola-period claim are section 11 and section 5 of the Limitation Act 1980. Section 11 imposes a three-year limit on personal-injury actions, running from the date of the accident or the date of knowledge if later. Section 5 imposes a six-year limit on actions founded on simple contract - the conventional analysis for property-damage claims. The court has a residual discretion under section 33 to extend the personal-injury period in exceptional cases, but discretionary extension is not something a claimant should plan around.
Applying those periods to the Ola operational window: most Ola-period accidents occurred between August 2018 and 12 April 2024. At the date this page was reviewed (May 2026), the personal-injury limitation had already expired for accidents up to and including approximately May 2023, and was running on for incidents from May 2023 onward through to the platform exit. The property-damage limitation under section 5 remained available for all incidents from May 2020 onward and would continue to run until 2030 for accidents on the last days of the operational period. The practical consequence is that a former Ola driver with personal injuries from a 2023 or early-2024 collision should issue proceedings well before the third anniversary, not delay on the assumption that the platform exit somehow tolls the clock - it does not.
For passenger injury below the £5,000 small-claims-track threshold under the Civil Liability Act 2018 the route is the Official Injury Claim portal at officialinjuryclaim.org.uk. The fixed whiplash tariff under the Whiplash Injury Regulations applies to qualifying accidents on or after 31 May 2021, which captures most Ola operational-period passenger injuries. The portal-route limitation is the same three-year section 11 period.
Most former Ola drivers in the UK simply registered with another platform. Uber, Bolt and Free Now were the headline national alternatives; many drivers also signed up with a local minicab firm in their authority area, particularly outside London where the local-operator market is still strong. The onboarding cost was usually modest: each operator requires an account application, evidence of the existing PHV driver licence and the vehicle licence, an upload of the hire-and-reward certificate, sometimes a vehicle photograph for app display and, in some authority areas, evidence of a topographical knowledge test where the council requires one. In London the full TfL Knowledge of London is a Black-cab requirement and is irrelevant to PHV onboarding, although TfL's English-language and topographical assessment continues to apply to new PHV drivers.
The Addison Lee route was structurally different and is worth mentioning for comparison. Addison Lee rents vehicles to its drivers on an inclusive package that bundles fleet insurance, MOT, servicing and maintenance, so a former Ola driver moving to Addison Lee would have left their personal hire-and-reward policy behind in favour of Addison Lee's fleet policy. Most Ola drivers, however, owned or financed their own vehicles and so moved to Uber, Bolt or Free Now where the vehicle and the insurance stayed in the driver's hands.
The cost of the pivot - onboarding fees, time spent re-registering, branding changes on the vehicle - is generally not a recoverable head of loss against the at-fault driver's insurer arising from a separate earlier collision, because the pivot is caused by Ola's exit (a corporate event) and not by the collision. If the collision itself caused a write-off, the cost of acquiring a replacement vehicle is recoverable, but that is a separate question. The pivot itself is a commercial cost the driver bears, mitigated by the simple expedient of being on more than one platform at once - multi-app working.
OLA
Section 3 of the walkthrough.
A passenger injured in an Ola-booked car between August 2018 and 12 April 2024 has two principal routes depending on who caused the collision. If the at-fault driver was a third party - another road user who hit the Ola car - the claim goes against that third party's section 143 Road Traffic Act 1988 motor insurer in the ordinary way. The Ola driver is a witness; the passenger is a claimant; the Ola booking platform is largely irrelevant to liability. The passenger's injury claim falls within the Civil Liability Act 2018 portal route for low-value pain, suffering and loss of amenity below £5,000 and within the conventional Pre-Action Protocol for personal injury claims above that threshold.
If the at-fault driver was the Ola driver who was carrying the passenger - for instance, the Ola driver pulled out at a junction without seeing the right-of- way vehicle and the passenger sustained whiplash - the claim goes against the Ola driver's own hire-and-reward insurer named on the certificate of motor insurance in force on the date of the collision. The fact that Ola has since withdrawn from the UK is irrelevant. The insurer remains on risk for the policy period; section 151 RTA 1988 imposes a statutory duty to satisfy any judgment; and the passenger can recover in the ordinary way. CityGrip's practice is to identify the certificate of motor insurance for the Ola driver at the date of the collision, write to the insurer with the letter of claim, and pursue the recovery through to settlement or court.
Ola itself did not act as a passenger insurer. There was no direct passenger- insurance product layered between the driver's hire-and-reward policy and the passenger. Section 56 LGMPA 1976 deems the booking contract to be with the operator who accepted the booking, which creates a contractual route for a passenger to sue Ola UK Private Limited in contract - but the practical claim for personal injury and consequential losses is against the at-fault motor insurer, not the operator. An operator-side claim is unusual on the facts of a straightforward road traffic collision.
The Ola consumer app was withdrawn from the App Store and Google Play in stages after 12 April 2024 and was no longer available for download after 11 May 2024. Historical trip records that lived only inside the app are no longer accessible. For any residual Ola-period claim the documentary record therefore rests in three places: the email account the passenger or driver registered with Ola, the bank account that paid for the ride (passenger) or received the payout (driver), and any personal photographs or dashcam clips saved at the time of the incident. A passenger should locate the original booking confirmation email, the corresponding payment-receipt email, and any scene photographs taken with the phone. A driver should locate the platform earnings statements downloaded before exit, the hire-and-reward certificate that was in force on the date of the collision, the TfL or local-council driver and vehicle licence record, and any messages exchanged with Ola driver support at the time.
For passengers in particular the booking confirmation email is the document that proves you were in the car. It records the pick-up time and address, the drop-off, the driver's name and (on most variants of the email) the vehicle registration. Without it the link between you and the trip becomes a question of inference rather than evidence. We strongly recommend exporting these emails from any mailbox you are likely to close in the next few years to a durable archive (PDF or paper) while the limitation period is still running.
Where the evidence pack is incomplete, alternative routes are available. The police incident reference where police attended is often the most useful anchor. A section 170 RTA 1988 exchange - the names, addresses, vehicle registrations and insurance details exchanged at the scene - is the next. MID enquiries via askMID let you confirm the at-fault driver's insurer where you have the registration. CityGrip's intake team will build the evidence pack with you on a call and identify which routes apply on the facts of your particular Ola-period collision.
A particular subset of Ola drivers were already running a loss-of-earnings claim at the moment Ola announced its withdrawal in April 2024. The mechanic of the typical loss-of-earnings claim for a self-employed PHV driver is to evidence the net hourly take from the six-to-eight weeks of platform earnings preceding the collision, multiply by the hours that would have been worked in the off-road period and adjust for the duty to mitigate. The platform exit throws a complication into that schedule because the driver's pre-collision earnings base was substantially or entirely Ola fares, and Ola fares ceased to exist on 12 April 2024.
The legal position is that the platform exit is not the at-fault driver's fault. The recoverable head of loss is the loss the at-fault driver caused, measured against the counter-factual world in which the collision did not happen. In that counter-factual world the driver would still have lost the Ola platform on 12 April 2024 because Ola's exit is independent of the collision. The proper measure of loss is therefore the earnings the driver would have made on Ola through to 12 April 2024 plus the earnings the driver would reasonably have made on a substitute platform (Uber, Bolt, Free Now, local operator) from 12 April 2024 onward. The pivot to the substitute platform is part of the mitigation analysis, not a deduction against the head of loss.
In practice the at-fault insurer's loss-adjusters will sometimes seek to argue that the platform exit breaks the chain of causation, or that the driver's inability to return to Ola limits the loss. Both arguments are weak: the inability to return to Ola is caused by Ola's exit, not by the collision, and the driver's mitigation duty is satisfied by returning to PHV work on whichever substitute platform is available at competitive earnings. The schedule is built on the platform data that does exist, projected forward on reasonable assumptions, and the insurer is invited to point to specific evidence rather than generic objections.
Ola's April 2024 UK withdrawal is the clearest recent illustration of a wider truth about gig-economy driving in the UK: the platform is not the same as the business. A self-employed PHV driver who relies on a single platform for all their booking volume is exposed to a real commercial risk that the platform may withdraw, fail, lose its operator licence, change its terms unilaterally or deactivate the driver's account on a single-customer complaint with limited review. None of those risks are hypothetical. Uber's London licence was revoked in 2017, again in 2019, restored on appeal in 2020 and granted on renewal in 2022. Ola was refused in October 2020 and reinstated in December 2021 before its 2024 exit. Free Now (formerly mytaxi and Hailo) has reshaped its UK product several times. Local operators come and go.
The countermeasure is multi-app working. Holding active driver accounts on more than one platform simultaneously means that a platform-specific event does not eliminate the driver's earnings stream. It also makes loss-of-earnings schedules easier to build in any future claim, because the platform-data spread acts as its own audit trail - the at-fault insurer cannot credibly argue that the driver could not have replaced the lost shifts when the data shows the driver was already running parallel shifts on a second platform. For new drivers entering the UK PHV market in 2026, the practical advice from the Ola precedent is: sign up to the platform you prefer first, but also register a secondary platform in the same authority area as a hedge.
The same logic applies to insurance. The driver's hire-and-reward policy is the contract that puts the car on the road. It is not contingent on any platform continuing to operate. Drivers should hold the cover irrespective of which platform they currently log into, renew it through the specialist hire-and-reward market and keep the certificate, the renewal correspondence and the SA302 tax returns somewhere they can find them. The Ola experience shows what happens when a driver structures their working life around a single platform that then exits. The corrective is to structure the working life around the driver, the vehicle and the cover - none of which any platform controls.
For platform-specific pages on Ola's surviving UK competitors, the hire-and-reward insurance position and the wider private hire claim landscape, continue with the linked pages below. The Ola page is part of a longer vertical that covers each major UK ride-hailing operator and the cross-cutting questions (insurance, replacement vehicle, loss of earnings, injury referral) that apply across all of them.
Step 1
Confirm the accident date and the surviving evidence
Pin down the date, time, location and circumstances of the Ola-period incident. Recover the original Ola booking confirmation email or SMS, the payment receipt sent to your registered email and any scene photographs, dashcam clips or witness contact details you saved at the time. The Ola consumer app was removed from the platforms after 11 May 2024 so in-app trip records are no longer retrievable - your email account, bank statements and personal media are now the primary record.
Step 2
Identify the at-fault driver's motor insurer
Locate the section 170 Road Traffic Act 1988 exchange details for the at-fault driver: name, address, vehicle registration and certificate of motor insurance. If you no longer have them, ask the police (where police attended), the at-fault driver directly or pay for a MID (askMID) enquiry. The at-fault driver's motor insurer - not Ola, not the platform - is the defendant for the recoverable heads of loss.
Step 3
Notify your own hire-and-reward insurer (driver) or pursue the OIC portal (passenger small-claims)
If you were the Ola driver and the collision was not your fault, notify the hire-and-reward insurer named on the certificate that was in force on the date of the collision - Zego, Inshur, Markel, Acorn, an Aviva-backed scheme or the named insurer on your then-current cover. Most policies require notification as soon as reasonably practicable irrespective of fault. If you were the passenger, the small-claims route for injury below the £5,000 Civil Liability Act 2018 threshold is the Official Injury Claim portal at officialinjuryclaim.org.uk.
Step 4
Open a claim against the at-fault driver's insurer
Write to the at-fault driver's insurer with a short factual letter of claim, the evidence pack and your particulars of loss. For vehicle damage the recoverable heads include repair (or pre-accident market value plus salvage where total-loss), credit hire of a like-for-like replacement, recovery and storage, an independent engineer's report and uninsured losses (excess, hire deposit, courtesy items). For personal injury the recoverable heads include general damages for pain, suffering and loss of amenity, treatment costs and loss of earnings.
Step 5
Build the loss-of-earnings schedule on the surviving platform data
If you were a self-employed Ola driver, build the loss-of-earnings schedule on the six-to-eight weeks of platform earnings data, bank statements and Self Assessment SA302s that pre-date the collision. The platform-change pivot (Ola to Uber, Bolt, Free Now or local operator) is not the at-fault driver's responsibility and is not generally deducted from the loss - your duty to mitigate is to return to PHV work as soon as it is safe, on whichever platform is available. Earnings on the replacement platform during the off-road period reduce the loss pound-for-pound.
Step 6
Watch the Limitation Act 1980 time-bar and issue proceedings if liability is denied
Personal injury claims must be issued within three years of the date of the accident under section 11 of the Limitation Act 1980; property damage must be issued within six years under section 5. If the at-fault insurer denies liability or refuses to settle on reasonable terms, court proceedings must be issued before the limitation date expires. Most Ola-period accidents that occurred from May 2023 onward remained within the personal-injury limitation period at the time this page was reviewed.
Residual Ola-period claim handling for former Ola drivers and passengers, with the multi-platform pivot to Uber, Bolt or Free Now supported. The at-fault insurer remains liable irrespective of Ola's withdrawal, subject to the Limitation Act 1980 time-bar. 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