Uber & Lyft Insurance Coverage Periods Explained

It depends on what the driver's app was doing at the moment of the crash.

Rideshare coverage runs in three windows, and each one points to a different policy.

App off, the driver is not working, so only their personal auto insurance applies.

App on and waiting for a request, a limited contingent policy kicks in.

A ride accepted or already underway, and a $1 million liability policy is in play.

The same three windows govern both Uber and Lyft, and the exact dollar figures vary by state.

Which policy pays your crash is decided by the driver's app status, and the rideshare company holds the data that proves it.

Understanding which window your crash fell in is the first step to knowing which insurer owes you, and how much coverage stands behind the ride.

Call (888) 713-6653 for a free case review. You Win or It's Free.

There is no single policy that answers this for every rideshare crash. The right answer turns on one fact: what the driver's app was doing when the collision happened.

Both Uber and Lyft structure their coverage around the driver's status, and they split a working day into three windows. Each window triggers a different layer of insurance, and the coverage between the first window and the third is worlds apart.

The three windows are the spine of every rideshare insurance question:

• Period 0: the app is off. The driver is off the clock. Only their personal auto insurance is on the hook, the same as any other private driver.
• Period 1: the app is on, waiting for a ride request. A limited contingent policy applies, with smaller limits than the trip period.
• Period 2 and 3: a ride is accepted, then the passenger is in the car. The full $1 million liability policy is active, the window that backs the largest recoveries.

The rest of this page walks each window in order. Which one applied to your crash decides which insurer answers for it, and the company that runs the app is the one holding the records that prove it.

If the driver was not logged into Uber or Lyft when the crash happened, the rideshare company is generally out of the picture. The driver is treated as an ordinary motorist, and their personal auto policy is the only coverage that applies.

That matters because personal policies are often thin. Plenty of drivers carry only their state's minimum liability limits, and a serious injury can blow past those numbers in a single hospital stay. A minimum-limits policy was never built to cover a catastrophic crash.

This window is also where rideshare carriers want to put a driver who was actually working. If the app records can be read to suggest the driver was logged off, the company sheds the larger policy and leaves you fighting over a small personal one. That is why the off-app claim is rarely as simple as it looks, and why the app data matters from day one.

When the only coverage is a thin personal policy, the gap often has to be filled from your own insurance, which the later sections cover.

Once a driver opens the app and starts waiting for a ride request, a different layer of coverage turns on. It is contingent coverage, meaning it sits behind the driver's personal insurance and applies in this in-between window before any rider is matched.

The limits in this window are far smaller than the trip-period policy. Uber and Lyft both list contingent liability minimums of about $50,000 per person and $100,000 per crash for bodily injury, plus roughly $25,000 for property damage, while the driver is logged on and waiting.^[2] Those are baseline figures, and the exact amounts vary by state. Some states, including Arizona, Nebraska, Maryland, and parts of New York, set their own rules, and the coverage there can look different.

The practical takeaway is the size of the drop. A claim that would reach a million-dollar policy on an active trip can fall to a fraction of that if the crash lands in the waiting window. That gap is exactly why proving the driver's precise status is worth fighting over.

The moment a driver accepts a ride request, the coverage changes again. From acceptance, through the pickup, and for the entire trip until the passenger is dropped off, the headline policy is active.

Uber maintains at least $1 million in third-party liability coverage once a ride is accepted or a passenger is in the car.^[1] Lyft carries a comparable $1 million liability policy across the same trip window, and both companies note that specific terms vary by state. This is the layer that lets a rideshare claim support a recovery an ordinary car crash rarely could.

That coverage typically reaches more than just a passenger:

• Injured passengers. A rider hurt while a trip is underway sits squarely inside the trip-period policy.
• People in other vehicles. A driver, passenger, or occupant of another car the rideshare driver hits during a trip can reach the same policy.
• Pedestrians and cyclists. Someone struck by a rideshare vehicle on an active trip is a covered third party as well.

A million-dollar policy is worth contesting, which is why these are the claims carriers fight hardest. The first move is often not a low offer at all. It is an argument that the big policy never applied because the driver was somehow in a lower-coverage window when the crash happened.

Everything on this page comes down to one question of fact: which window was the driver in at the instant of impact? Answer that, and you know which policy is supposed to pay. The trouble is that the answer lives inside the rideshare company's own systems.

Uber and Lyft track app status to the second. They know when a driver logged on, when a request was accepted, when the pickup happened, and when the trip ended. That data is decisive, and it is held by the party with the most reason to read it in the cheaper direction.

The fights that follow tend to look the same:

• Was the app even on? Pushing a working driver into the off-app window erases the company's coverage entirely.
• Waiting or on a trip? Moving the crash from the trip window into the waiting window can cut the available policy from a million dollars to a state-minimum figure.
• When exactly did the trip start or end? A few seconds on either side of acceptance or drop-off can decide which policy is on the hook.

Because the record sits with the company, it has to be requested and preserved early, before it ages out of the system. That single fact, the driver's status at the moment of the crash, often does more to set what a claim is worth than anything else. How those coverage layers translate into real money is covered in our look at what a rideshare claim is worth.

Two rideshare crashes can look identical at the scene and be worth completely different amounts, because one driver had a passenger and the other was a block away with the app on. The details matter, and we build the case around the unique circumstances of your case.

Even the trip-period policy is not always enough, and the contingent window often is not. When the available rideshare coverage cannot cover a serious injury, other policies have to fill the gap.

• Uninsured and underinsured motorist coverage. If a phantom driver caused the crash, or the at-fault policy is too thin for your injuries, your own uninsured and underinsured motorist coverage can become the difference between a partial recovery and a full one.
• No-fault and personal injury protection. In a no-fault state, your personal injury protection coverage pays your medical bills first, regardless of who caused the crash, which keeps treatment moving while the policy fight plays out.
• Multiple passengers, one policy. When several riders are hurt in the same vehicle, a single $1 million limit can be split among them, leaving each claim competing for a piece of the same pool.

Who you were in the crash also shapes which coverage you reach. A passenger injured in an Uber or Lyft has a different path to the policy than someone hit by an Uber driver from outside the vehicle. Finding every source of coverage that applies, beyond the obvious one, is part of protecting what you can collect.

Your deadline to file is set by your state's statute of limitations, and it varies. On a rideshare case, though, the filing clock is the slower of two threats.

The faster one is the app and trip data. The records that prove which coverage period applied are held by Uber or Lyft, and they have to be requested and preserved before they age out. That evidence is often what decides which policy pays and how much is available, so losing it can quietly shrink the case long before any filing deadline is near. Confirm your specific deadline early, and move to lock down the app data sooner than that.