Thousands of Uber and Lyft trips move through Denver every day — airport runs on Peña Boulevard, weekend surges around LoDo and RiNo, steady traffic across the downtown grid. When one of those trips ends in a crash, injured people discover something frustrating: rideshare claims are layered in a way ordinary car accident claims are not, and the companies' insurers are practiced at steering victims toward the thinnest available layer.
Whether you were a passenger, a driver or pedestrian hit by a rideshare vehicle, or a rideshare driver yourself, the coverage that applies turns on the driver's app status at the moment of the crash — offline, waiting for a ride request, or actively en route or carrying a passenger. Each status triggers different insurance, with dramatically different limits.
Whiteford Mountain West handles rideshare injury claims from our Denver office, backed by Whiteford's national trial platform. This page explains the coverage periods, the games insurers play with them, and how to protect a claim from day one.
The three app periods — and why the moment of impact matters
Rideshare insurance works in tiers. When the driver's app is off, they're just a private driver, and only their personal auto policy applies. When the app is on and the driver is waiting for a request, the rideshare company provides an intermediate layer of contingent coverage. And once the driver accepts a trip — through pickup, the ride itself, and drop-off — the companies' largest commercial-grade coverage applies, at limits far above typical personal policies.
Those boundaries create the central fight in many Denver rideshare cases: establishing exactly what the app was doing at impact. Trip records, app data, and dispatch logs answer the question definitively — but that data lives with the rideshare company, and preserving and obtaining it is attorney's work. Insurers on every side have an incentive to push the claim into someone else's period.
- App off: only the driver's personal auto policy — which may exclude commercial activity
- App on, waiting for a request: intermediate contingent coverage from the rideshare company
- Trip accepted through drop-off: the company's largest commercial-grade coverage layer
- App status is proven by trip and dispatch data the company controls
- Uninsured motorist protection may add another layer, depending on the period and your own policy
Passengers, third parties, and drivers — three different claims
Rideshare passengers are usually the strongest claimants: they bear no fault for the crash, and the trip-active coverage applies to them regardless of whether their driver or another motorist caused it. The complication is when both drivers share blame — then multiple insurers point at each other, and Colorado's comparative-fault rules govern how responsibility, and payment, gets divided among them.
Third parties — occupants of other cars, cyclists, pedestrians — must first pin down the rideshare driver's app status, since it controls which coverage responds. Rideshare drivers injured by other motorists have their own maze: the at-fault driver's policy, the company's coverage for their period, and possibly their own underinsured motorist protection.
How we handle Denver rideshare cases
We move early to preserve what decides these cases: trip and app data, dash camera footage, vehicle data, and witness accounts from scenes that clear quickly on busy corridors like Speer, Broadway, and the downtown grid. Then we identify every applicable coverage layer — rideshare, personal, uninsured motorist — before any insurer frames the claim around the cheapest one.
Because Whiteford Mountain West pairs Denver-based counsel with a national trial platform, rideshare insurers can't price our cases on the assumption we'll take the early offer. Damages get documented fully — treatment, future care, lost income, and the human losses Colorado's 2025 damages-law changes made more significant. Start with a free consultation, or try our free case estimator for an honest first read on where your claim stands.
