The single most consequential question in a rideshare crash case is also the most boring one: what was the driver's app status at the moment of impact? Period 0, Period 1, Period 2, or Period 3 — the answer determines which insurance policy applies, what the limits are, and whether the rideshare platform writes the check or fights the claim. This post is the plain-English version of the framework.
Rideshare crashes look like any other crash from the curb. A vehicle is upside down, a passenger is on a stretcher, a tow truck pulls up. The complexity comes when the insurance carriers arrive on the phone an hour later. Whose policy responds? Whose limits apply? Why is the rideshare platform's adjuster saying the driver "was not in our system"? The answer almost always reduces to one variable: what the driver's app was doing at the moment of impact.
Uber, Lyft, and the major state-level rideshare statutes have all settled on the same four-period framework. The framework is straightforward when explained, but it is a trap for the unwary because the wrong theory of which policy applies, asserted at the start of a case, can kill the recovery before discovery even opens.
When the rideshare app is closed or in passenger mode, the driver is not "working" for the platform. They are an ordinary driver. The personal auto policy applies. The platform's commercial coverage does not.
This sounds simple, but it generates more disputes than the other three periods combined. Many personal auto policies exclude "commercial use" or "transportation network company use" from coverage. A driver who has been working as a rideshare driver may have an exclusion that the carrier invokes even in Period 0, on the theory that the vehicle is being used commercially "generally." Litigating those exclusions is fact-intensive and depends on the specific policy wording, state law, and the driver's pattern of use. A few states have legislated around the exclusion. Most have not.
The driver opens the app and is logged in as available. No ride request has been accepted yet. They are driving around (or parked) waiting for a request to come in. In this period, both Uber and Lyft provide contingent liability coverage at lower limits than the full commercial policy that applies once a ride has been accepted — state-mandated minimums vary, and the specific limits in effect are documented in each platform's publicly available insurance coverage policy.
"Contingent" is the key word. The platform's coverage usually steps in only after the driver's personal auto policy has either paid its limits or denied coverage entirely. The order-of-operations dispute (which carrier responds first) creates delays and, in practice, requires the lawyer to make formal claims under both policies simultaneously.
The driver has accepted a ride request and is on the way to pick up the passenger. No passenger is in the vehicle yet. This is where the platform's primary commercial third-party liability policy applies. Both Uber and Lyft publish the policy structure and limits for each period on their corporate insurance pages, and that documentation is the starting point for verifying which coverage layer is in play.
Period 2 cases often involve a third party — another driver, a pedestrian, a cyclist — struck by a rideshare driver who was rushing to a pickup. The platform almost always tries to characterize ambiguous fact patterns as Period 1 (lower limits) rather than Period 2. Proving the precise app status at impact, often down to the second, requires the platform's own records.
The passenger is in the car. The trip is in progress. The primary commercial third-party liability policy continues to apply. In addition, the platform's policy includes uninsured and underinsured motorist coverage that protects the passenger if another driver causes the crash and that driver is uninsured or underinsured. This UM/UIM layer is one of the most important protections passengers do not know they have.
Period 3 is also where the most common rideshare-injury fact pattern lives: a passenger sitting in the back seat, ordinary trip in progress, another driver runs a light or drifts a lane and the rideshare vehicle is hit. The passenger then has to navigate a claim against the at-fault driver's insurance (which is often inadequate to cover catastrophic injuries) and a claim against the rideshare platform's UM/UIM coverage.
Every rideshare trip generates a digital fingerprint on the platform's servers. Trip ID. Driver ID. Acceptance timestamp. Pickup timestamp. Drop-off timestamp. GPS track. App state changes second by second. The platform has all of this from the moment of the trip. Securing it is a matter of:
The most common error in rideshare cases is filing against the wrong insurer in the wrong sequence. A passenger who only files against the at-fault driver and exhausts (or fails to exhaust) those limits may miss the deadline to file against the rideshare platform's UM/UIM coverage. A driver who pursues the personal auto carrier without putting the rideshare platform on notice may waive contingent coverage in Period 1.
The Alvarez Law Firm's approach in every rideshare catastrophic injury case is to identify all four potential layers of coverage on intake and serve preservation letters to each. The layers, in order, are usually:
Each layer has its own notice requirements, its own deadlines, and its own coverage triggers. Coordinating all of them is the work of the case — and the reason these cases do not get handled like ordinary auto wrecks.
If you were a passenger, save the trip in your app. Screenshot the receipt, the driver name, the trip ID, the timestamps. Do not delete the trip from your trip history. If you were another driver or a pedestrian, get the rideshare driver's name and the platform from the report. Either way, the next call is to a lawyer who has actually handled a rideshare case — not because the medicine is different, but because the insurance map is.
Period 0 is when the app is off; the driver's personal auto policy applies and the rideshare platform's coverage does not. Period 1 is when the app is on and the driver is waiting for a ride request; the platform provides limited contingent liability coverage subject to state-mandated minimums. Period 2 is when the driver has accepted a ride and is en route to pick up the passenger; the platform's primary commercial liability policy applies. Period 3 is when a passenger is in the vehicle; the primary commercial liability policy continues to apply, and the passenger is also protected by uninsured and underinsured motorist coverage.
Uber and Lyft both retain detailed logs of every driver's app status, ride acceptance, pick-up time, drop-off time, GPS track, and trip ID. That data is in the platform's possession from the moment of the trip. The platform produces it in litigation but rarely produces it informally, and the data must be requested in writing through a preservation letter and then again through formal discovery. Driver phone records, passenger app screenshots, and contemporaneous text messages can corroborate the platform's records.
Period 0 — the app is off, personal auto insurance applies. The same is true of any personal errand while the app is off. Many personal auto policies exclude coverage for commercial use, so an off-app rideshare driver may have a coverage dispute with their own carrier. The plaintiff's path to recovery in that scenario depends on state law, the wording of the personal policy, and whether any other coverage (an umbrella policy, an excess policy, the platform's catch-all contingent coverage in limited circumstances) applies.
When a passenger is in an Uber or Lyft and the crash is caused by another driver who is uninsured or underinsured, the rideshare platform's policy includes uninsured and underinsured motorist coverage that protects the passenger. Both major platforms publish the structure and limits of that UM/UIM coverage on their corporate insurance pages. The mechanics of triggering the coverage require formal notice, documentation, and (often) litigation.
The full case-type page on rideshare catastrophic injuries.
Why platform preservation letters have to go out on day one.
Vehicle EDR data corroborates the platform's app-status records.
The non-rideshare counterpart — ordinary motor-vehicle insurance.
The most common catastrophic injury seen in rideshare passengers.
Brain injury is the most common catastrophic finding in rideshare-passenger cases.
If you were injured in or by an Uber or Lyft vehicle, the insurance map is layered and the deadlines are unforgiving. Free, confidential case review. We will map every coverage layer that may apply.
