When a rideshare driver causes a Washington collision, fault is only the start. App status, commercial coverage and the evidence of injury still control the claim.
When an Uber or Lyft driver causes a collision in Washington, fault is only the first part of the claim. The next questions are what the driver was doing in the app, which commercial policy applied, and what evidence connects the crash to the injuries being claimed.
Start With the Driver, Then Identify the Policy
A passenger claim still begins with ordinary negligence: did the rideshare driver speed, follow too closely, make an unsafe turn, drive while distracted, or otherwise fail to use reasonable care? The fact that the trip was booked through an app does not replace that analysis.
What rideshare changes is the insurance layer. Washington ties transportation-network-company coverage to the driver's app status. During a prearranged ride, state law requires a commercial liability policy with a $1 million combined single limit. That ride begins when the driver accepts the request and continues through the passenger's exit from the vehicle.
The $1 Million Limit Is Not an Automatic Settlement
A policy limit tells you the maximum coverage potentially available under that policy. It does not establish what a claim is worth. The insurer can still examine causation, treatment, wage loss, prior medical history, comparative fault, and the extent of any permanent harm.
That distinction matters in multi-vehicle crashes. A rideshare driver can be at fault, another driver can share fault, and several injured people can be making claims against the same policy. Washington's pure comparative-fault system allows responsibility to be divided by percentage rather than forcing every case into a single-driver story.
Passengers, Cyclists, Pedestrians and Other Motorists Can All Have Claims
The commercial liability policy is not only for the person sitting in the back seat. If a working rideshare driver negligently hits another vehicle, a cyclist, or a pedestrian, those injured people may also have claims against the applicable policy. The key coverage fact is usually the driver's rideshare status at the time of impact.
Save the Digital Evidence Early
Rideshare collisions generate records that ordinary crashes may not: trip receipts, route information, timestamps, pickup and drop-off locations, driver identity, app status, support messages and sometimes dashcam footage. Save screenshots before the app interface changes and keep the original receipt email.
Photos, witness information, the police collision report, medical records and wage documentation still matter too. Digital trip data is powerful, but it works best as part of a complete accident record rather than as a substitute for one.
A Claim Under the Rideshare Policy Is Different From a Direct Lawsuit Against Uber or Lyft
People often use the phrase “suing Uber” to describe any rideshare claim. Legally, those can be different things. A passenger may pursue compensation under commercial coverage because Washington requires that coverage for the ride. A separate claim alleging that the platform itself committed a tort requires its own facts and legal theory.
That is why the first practical task after a Seattle rideshare crash is usually narrower: identify who caused the collision, preserve the trip status, locate every policy that may apply, and document the injury before the insurers start arguing about the rest.
Join the Conversation
Comments are moderated before publication. Keep it relevant, civil, and respectful of the people involved.