Suing Uber in California: How TNC Period Liability Shapes Your Case

An Uber accident is not a routine motor-vehicle case. From the moment of impact, California’s Transportation Network Company framework — codified at Cal. Pub. Util. Code §§ 5430–5445 — controls the coverage structure, and that structure is built on four discrete status windows. Which window was open when the crash happened determines whether an injured victim confronts a $50,000 per-person cap or Uber’s full $1 million commercial policy. That single determination has more practical impact on a case’s settlement value than almost any other variable, and it is almost always disputed.

The Four Coverage Periods That Control Every Uber Injury Claim

Before 2013, TNC drivers operated in a dangerous insurance gap. Personal auto policies typically exclude commercial use, meaning drivers carrying passengers for hire were effectively uninsured. The legislature closed that gap with a mandatory tiered coverage structure tied to driver status on the platform.

Period 0 — App Off. When a driver has not activated the Uber driver application, the company’s commercial policies do not apply. Liability is governed solely by the driver’s personal auto policy, which in California must carry at least $15,000 per person / $30,000 per incident. Those minimums are grossly inadequate for any serious injury. Uber’s position in Period 0 cases is straightforward: the platform was not in use, this was a private-citizen collision, and the company owes nothing beyond what ordinary tort law would require of any entity that onboarded a driver.

Period 1 — App On, No Accepted Request. The driver is logged in and visible to potential passengers but has not yet accepted a trip. Under § 5432, Uber must carry contingent liability of at least $50,000 per person / $100,000 per incident / $25,000 for property damage. “Contingent” means this coverage steps in only if the driver’s personal policy first denies the claim or is insufficient. Because personal policies exclude commercial activity, Uber’s Period 1 layer almost always becomes the operative coverage. The cap is real, however: serious injuries that generate $150,000 or more in medical costs are not fully compensated by a $50,000-per-person limit.

Period 2 — Ride Accepted, En Route to Pickup. Once a driver accepts a request and is traveling to collect the passenger, the full $1 million commercial policy activates. This is the coverage floor — umbrella layers may stack beyond this in some claim configurations.

Period 3 — Passenger On Board. The same $1 million policy continues through the ride until the passenger exits the vehicle. Uber’s UM/UIM coverage is also available during Periods 2 and 3, which matters significantly when an underinsured third-party driver causes the collision.

The transition between periods is logged in real time in Uber’s backend systems. Disputes almost always center on the Period 0 / Period 1 boundary — driver claims the app was off — or the Period 1 / Period 2 boundary, where the timing of trip acceptance relative to the crash is scrutinized.

The California Statutes and Cases That Govern TNC Liability

Cal. Pub. Util. Code §§ 5430–5434 define TNCs, establish permit requirements, mandate background checks, and impose the tiered insurance obligations above. Section 5440 requires a zero-tolerance drug and alcohol policy for drivers — relevant to any impairment allegation and discoverable as part of Uber’s compliance record.

The independent contractor question. Uber classifies its drivers as independent contractors, not employees. Under traditional common law, that classification would generally preclude respondeat superior liability — an employer is vicariously liable for an employee’s negligence within the scope of employment, but typically not a contractor’s. This matters when a plaintiff attempts to hold Uber directly liable beyond merely accessing the statutory coverage.

The worker-classification dispute has deep California roots. In Cotter v. Lyft (N.D. Cal., 2015), a federal district court handling a driver class action described the gig-economy contractor model as a “square peg” being forced into a “round hole” of existing employment law — recognizing that the traditional employee/contractor binary was not designed for platform-mediated work. The case settled in 2016, but the underlying doctrinal tension it exposed shaped how practitioners think about TNC control and liability.

In 2018, the California Supreme Court’s decision in Dynamex Operations West, Inc. v. Superior Court imposed the ABC test for worker classification, establishing a presumption of employment. AB 5 (Labor Code § 2775 et seq.) codified Dynamex in 2019. Proposition 22 (November 2020) reversed course specifically for TNCs: app-based drivers are classified as independent contractors for labor law and benefits purposes under state law. Proposition 22 did not amend the PUC’s TNC framework, however. The tiered $1M / $50k coverage obligations survive intact, and the IC classification does not insulate Uber from direct negligence claims based on negligent hiring, negligent retention, or failure to deactivate a driver with a disqualifying history.

In practice, the insurance coverage question (governed by the PUC framework) and the vicarious liability question (governed by common law and Proposition 22) are distinct inquiries. Many serious-injury claims resolve on the coverage structure alone without requiring any employer-employee determination.

App Logs, Ride Records, and the Evidence Playbook in TNC Cases

The evidentiary centerpiece of every Uber case is the trip log.

App status data. Uber maintains real-time logs of when each driver’s app was active, when requests were received, when they were accepted, when the driver arrived at pickup, when the trip started, and when it ended. These timestamps are the authoritative record of which period governed at impact. Requests for this data must be sent to Uber’s legal department early — retention windows for detailed log data can be as short as 90 to 180 days depending on the data category.

GPS and route data. Uber’s backend captures continuous GPS coordinates during Periods 1 through 3. In a crash-causation dispute, this data can reveal speed, routing, sudden deceleration, and driver position relative to known hazards. If a driver claims Period 0 status but GPS pings show continuous movement along a route consistent with a trip, that contradiction is potent.

Driver records. Uber conducts background checks through third-party providers before activating drivers. If the driver had a prior DUI, prior at-fault accident history, or a suspended license that should have triggered disqualification, and Uber activated or retained them anyway, those records support a direct negligence claim against the company. California law requires periodic background re-checks; gaps in that process are discoverable.

Passenger-side trip records. If the injured party was a passenger, the Uber app maintains an independent record of the trip from the passenger’s account. This independently corroborates the driver’s period status and the route taken, and it is not subject to disputes about when the driver’s app was active.

Third-party dashcam and intersection footage. Uber’s internal data establishes driver status; external camera footage establishes what happened at the scene. Preservation letters to nearby businesses, transit agencies operating fixed-route cameras, and witness vehicles identified on CHP reports should be sent within days of the incident.

Case Value and Recovery Dynamics in TNC Claims

Coverage period is the single largest driver of settlement value in Uber cases, more than in almost any other vehicle-accident category.

Period 1 claims present a structural problem. The $50,000 per-person cap is frequently inadequate for injuries involving surgery, imaging, or extended rehabilitation. Economic Damages Calculation establishes a baseline for medical and income losses alone; where those losses approach or exceed the cap, the deficit falls to the driver’s personal assets — which are typically limited. The practical result is that Period 1 victims with serious injuries often recover far less than Period 2–3 victims with comparable injuries, which makes the period boundary dispute financially determinative.

Period 2 and 3 claims offer substantially more leverage. With a $1 million commercial policy in play, large-injury cases — Traumatic Brain Injury, spinal cord damage, Herniated Disc — can be negotiated against the full policy without an immediate cap problem. Uber’s claims-management approach in Period 2–3 cases is structured: the company generally acknowledges coverage and shifts the dispute to comparative fault, damages quantum, and causation.

Pain And Suffering Damages are typically the largest component of recovery in TNC cases involving serious injuries. California’s Comparative Fault doctrine applies — any contributory negligence by the plaintiff reduces but does not eliminate recovery. This matters in cases where a passenger’s behavior contributed to the incident.

Cases involving multiple injured parties require attention to aggregate policy limits. The $1 million figure is a per-occurrence number. In a multi-victim crash, the total available pool may require structured allocation, which is why identifying umbrella policies and any third-party liability coverage early is essential.

How Uber Defends Period-Disputed Claims

Uber’s defense strategy is more systematic than most individual-defendant litigation, reflecting the company’s scale and the volume of claims it manages nationally.

Period reclassification. The primary defense move in any Uber case is pushing the crash into the lowest possible coverage period. Shifting from Period 2 to Period 1 drops the per-person limit from $1M to $50k. Establishing Period 0 eliminates direct TNC coverage entirely. Defense counsel will challenge trip-log data, argue timestamp discrepancies, and in some cases assert that the driver’s app was open for navigation or personal purposes unrelated to the platform — attempting to sever the connection between app activity and TNC coverage.

Independent contractor insulation. Where a plaintiff seeks to hold Uber directly liable beyond the coverage structure, the company asserts IC classification under Proposition 22. The argument is that Uber exercised insufficient day-to-day control over the driver’s work to create a principal-agent relationship supporting vicarious liability. Whether this succeeds depends on the specific facts and on whether a direct negligence theory — hiring, retention, supervision — can be established independently.

Comparative fault offsets. In passenger claims, Uber’s defense team investigates whether the passenger distracted the driver. In third-party claims — injured occupants of other vehicles, pedestrians — the defense develops evidence attributing causation to the other driver, reducing Uber’s proportional share under California’s Comparative Fault framework.

Damages minimization. Where coverage and liability are conceded, the defense focuses on quantum: disputing causation between the crash and claimed injuries, the medical necessity of specific treatments, and the reliability of future cost projections. Cases involving pre-existing conditions receive heightened scrutiny from Uber’s medical review teams.

Uber maintains a structured in-house claims operation and a preferred panel of outside defense counsel. Claimants who attempt direct negotiation without an attorney frequently receive early settlement offers framed as fast resolution — a pattern that is particularly problematic in Period 2–3 cases where the policy limit is not the binding constraint and damages may significantly exceed the initial offer.