Rideshare Accident Lawyer in Colorado

Colorado's statute of limitations for rideshare accident personal injury claims is three years from the date of the crash under C.R.S. § 13-80-101(1)(n) — the general motor-vehicle SOL applies because there is no rideshare-specific deadline in the TNC Act at C.R.S. §§ 40-10.1-601 et seq. Colorado's modified comparative negligence rule under C.R.S. § 13-21-111 applies with full force to rideshare crashes: if a jury assigns the plaintiff fault that is 'as great as' the defendant's — 50% or more — the plaintiff recovers nothing. In a rideshare crash, 'the defendant' may be the TNC driver, a third-party driver who caused the collision, or both. Fault allocation among multiple parties is common in rideshare cases, and the plaintiff needs to ensure their own share stays below the strict 50% bar against each relevant defendant. The three-year window provides time to investigate, but the critical evidence in a rideshare case is uniquely perishable. Dashcam footage from the TNC vehicle — if the driver was using one — may be stored on a local device that gets overwritten. Ride data from the TNC app (Uber or Lyft) — including the driver's login status, trip acceptance time, route, speed data, and passenger ratings — must be preserved through a spoliation letter to the TNC's legal department. Without that letter, the TNC has no obligation to preserve the data beyond its standard retention period, which may be as short as 90 days for certain data categories.

Colorado's TNC insurance framework under C.R.S. § 40-10.1-604 creates three coverage periods that determine the available policy limits, and identifying the correct period is the single most important factual question in any Colorado rideshare injury case. Period 1 — when the driver is offline or not logged into the TNC app — is covered only by the driver's personal auto policy. The TNC has no coverage obligation during this period, and Colorado's standard 25/50/15 auto minimums under C.R.S. § 10-4-620 are the floor. Period 2 — when the driver is logged into the TNC digital network and available for ride requests but has not accepted a ride — requires the TNC to maintain primary liability coverage of at least $50,000 per person bodily injury, $100,000 per accident bodily injury, and $30,000 property damage. Period 3 — from ride acceptance through ride completion, including driving to pick up the passenger — requires primary liability coverage of at least $1,000,000 combined single limit per occurrence. The statute specifies that the Period 3 policy must provide coverage 'at all times the driver is engaged in a prearranged ride.' The difference between Period 1 and Period 3 is the difference between $25,000 in personal-auto minimums and $1,000,000 in TNC commercial coverage — a 40x multiplier. An adjuster who can argue the driver was in Period 1 rather than Period 2 or 3 dramatically reduces the TNC's exposure.

Colorado's TNC statute closes the critical gap left by standard personal-auto livery exclusions — a gap that leaves rideshare drivers in many states functionally uninsured during certain periods. Under C.R.S. § 40-10.1-604(2)-(3), the TNC-procured or driver-procured Period 2 and Period 3 coverage is statutorily primary during those periods. This means the TNC's commercial policy — not the driver's personal auto policy — is the first-dollar responder for claims during Periods 2 and 3. Personal auto carriers in Colorado may exclude coverage when the driver is using the vehicle for TNC purposes, and virtually all standard personal-auto policies in Colorado contain a livery exclusion that does exactly this. The result is that during Periods 2 and 3, the TNC's commercial policy is typically the only available coverage for the crash. UM/UIM coverage must be offered on every Colorado auto policy under C.R.S. § 10-4-609 (with written waiver if declined), and the Period 3 $1,000,000 TNC commercial policies issued in Colorado typically include UM/UIM at the same combined single limit. A local Colorado rideshare attorney will map every available policy layer: the TNC's commercial coverage for the applicable period, the driver's personal auto (relevant only in Period 1), the plaintiff's own UM/UIM coverage, and any applicable umbrella or employer policies if the plaintiff was on a work trip.

Colorado statutorily classifies TNC drivers as independent contractors — not employees — under C.R.S. § 40-10.1-605, provided the TNC does not unilaterally prescribe specific hours during which the driver must be logged on, the driver provides the vehicle, and other statutory conditions are met. This classification is significant because Colorado has no Prop 22-style ballot measure (as California enacted) and no AB 5-style ABC test that would override the statutory classification. The practical litigation effect is that the TNC — Uber or Lyft — is generally not vicariously liable for the driver's negligence under a respondeat superior theory, because the driver is not an employee. The plaintiff's claim against the TNC itself typically runs through the TNC's statutory insurance obligations under C.R.S. § 40-10.1-604, not through an employment-based vicarious liability theory. However, the Colorado Public Utilities Commission — which handles TNC permitting, insurance filings, and background-check compliance under C.R.S. §§ 40-10.1-601 et seq. and the implementing rules in 4 CCR 723-6 — maintains records that are a significantly underused discovery resource for plaintiffs in Colorado rideshare litigation. PUC discovery records, including TNC permit files, insurance compliance filings, background-check audit results, and any regulatory enforcement actions, can reveal whether the TNC met its statutory obligations regarding the specific driver involved in the crash. If the TNC failed to conduct a required background check, or allowed a driver with a disqualifying record to remain on the platform, that failure creates a direct-negligence theory against the TNC itself.