From JDSupra, Steven M. Sweat discusses in intricacies of litigating rideshare disputes and how pedestrians and other possible injuries parties may never have signed an arbitration agreement prevent rideshare companies from compelling arbitration. Steven writes:
When a rideshare vehicle causes a serious crash, the first fight in the case is often not about fault, damages, or insurance. It is about the forum. Uber’s terms of use — accepted with a tap when a rider creates or updates an account — contain a broad arbitration provision, and the company’s first procedural move in injury litigation is frequently a motion to compel arbitration. Whether that motion succeeds turns on a question courts have been refining for more than a decade: who, exactly, agreed to arbitrate?
The answer matters enormously, because a rideshare collision routinely injures people standing in very different contractual positions. The passenger in the back seat clicked through the app’s terms. The pedestrian in the crosswalk, the cyclist in the bike lane, and the driver of the other car never did. For practitioners evaluating how an Uber accident lawsuit actually proceeds in California, the arbitration analysis is the fork in the road that determines everything downstream — discovery scope, motion practice, the availability of a jury, and settlement leverage. This article maps that analysis claimant by claimant: the account holder, the true third party, the heirs in a wrongful death action, and the bystander struck by a delivery driver working an adjacent platform.
The Account Holder: Contract Formation Is the Battleground
For riders, the enforceability fight usually centers on contract formation rather than unconscionability. An arbitration agreement, like any contract, requires mutual assent — and in the app context, assent is a factual question about screens. Courts applying California law have repeatedly examined whether a sign-up or update flow put a reasonable user on inquiry notice of the terms: the size, color, and placement of the hyperlink to the terms of use; whether the disclosure was visible without scrolling; whether the user was required to take an affirmative act — checking a box, tapping a clearly labeled button — that a reasonable person would understand as agreement; and whether the interface was cluttered with competing visual elements that buried the disclosure.
The case law rewards granular, screen-by-screen evidence: what the interface looked like on the date of the alleged assent, on the plaintiff’s device type, in the plaintiff’s language — not what the app looks like today. Platforms revise their sign-up flows constantly, and each revision generates a new formation record. Plaintiffs’ counsel should therefore treat the motion to compel as a discovery event, not a formality. Courts have discretion to permit limited discovery directed at formation before ruling, and that discovery should demand the specific screens displayed to this user, the click-through logs the platform relies on, records of subsequent terms updates and how they were presented, and the declarations’ underlying data — not merely the exemplar screenshots the defense attaches to its motion. A surprising number of compelled-arbitration orders rest on an evidentiary record the plaintiff never tested.
Where formation is established, unconscionability remains a second line of defense, though a narrower one. California analyzes procedural and substantive unconscionability on a sliding scale under the framework the Supreme Court articulated in Armendariz v. Foundation Health Psychcare Services, Inc. (2000) 24 Cal.4th 83 — adhesion and surprise on the procedural side, overly harsh or one-sided terms on the substantive side. Modern consumer arbitration clauses are drafted with that framework in mind, so wholesale invalidation is rare. But specific terms — cost-shifting provisions, truncated limitations periods, remedy waivers — remain vulnerable, and under McGill v. Citibank, N.A. (2017) 2 Cal.5th 945, a provision that waives the right to seek public injunctive relief in any forum is unenforceable in California.
Even where the clause survives, California procedure gives claimants meaningful leverage that did not exist a decade ago. Code of Civil Procedure sections 1281.97 and 1281.98 treat a drafting party’s failure to pay arbitration fees within 30 days of the due date as a material breach, allowing the claimant to withdraw from arbitration and return to court — with sanctions available. And since the Legislature amended section 1294 effective 2024, an appeal from an order denying a motion to compel no longer automatically stays trial court proceedings. The days when an arbitration appeal froze an injury case for two years are over. Counsel who calendar the fee deadlines and press forward during any appeal convert what was once pure delay into litigation momentum.
The Third Party: No Signature, No Arbitration
The cleanest cases are those brought by people outside the app relationship entirely. A pedestrian, a cyclist, or an occupant of another vehicle struck by a rideshare driver has no contract with the platform and cannot ordinarily be compelled into its arbitral forum. Arbitration is a matter of consent, and the doctrines defendants use to bind non-signatories — equitable estoppel, third-party beneficiary status, agency — fit poorly where the injured person never sought or received any benefit from the agreement containing the clause and asserts tort claims that exist independent of it. A pedestrian’s negligence claim does not “rely on” the terms of use in any sense the estoppel doctrine recognizes; it relies on the duty every driver owes everyone on the road.
For these plaintiffs, the claim proceeds in Superior Court like any other negligence action, with the platform’s statutory coverage obligations layered on top — and with the practical complication that multiple policies may respond depending on the driver’s app status at the moment of impact. The framework governing claims where another motorist causes a rideshare-involved collision illustrates how these third-party scenarios interact with the layered coverage: the at-fault driver’s personal policy, the TNC’s period-based coverage, and the injured person’s own uninsured/underinsured motorist protection can all be in play in a single crash, each with its own notice requirements and settlement-consent traps.
Two further categories deserve attention. First, minors. California law has long permitted minors to disaffirm most contracts, and a rider account created by a teenager — or a minor riding on a parent’s account — presents formation and disaffirmance questions the standard motion to compel does not answer. Second, wrongful death. Under Code of Civil Procedure section 377.60, a California wrongful death claim belongs to the decedent’s heirs in their own right; it is not inherited from the decedent. Absent a statutory exception, an heir who never signed the platform’s terms is not automatically bound by the decedent’s assent, and courts scrutinize attempts to sweep independent statutory claims into a contract the claimant never saw. Survival claims brought on behalf of the estate stand on different footing — which means a single fatal crash can generate claims on both sides of the arbitration line, a wrinkle that should inform how the complaint is structured from the outset.
The Classification Question Is Usually a Detour
Much public attention has focused on Proposition 22, which the California Supreme Court upheld in 2024, preserving app-based drivers’ independent-contractor classification. Defendants invoke classification to resist respondeat superior liability, and commentators sometimes describe it as the dispositive issue in rideshare litigation. Experienced counsel know better. California’s Transportation Network Company statutes mandate insurance coverage — up to one million dollars during an active trip — that applies regardless of how the driver is classified. The coverage framework, not the employment label, is where most recoveries actually come from.
Direct negligence theories against the platform remain available on their own facts: negligent hiring where the background check process failed, negligent retention where complaints accumulated without action, and safety-program failures where the platform’s own standards were not followed. These claims do not depend on an employment relationship at all — they rest on the platform’s own conduct. The strategic question in most cases is therefore not whether the driver was an employee; it is which coverage period applies and what the platform knew.
Where the claimant was riding in the vehicle when the crash occurred, the analysis has its own contours — passengers are almost never comparatively at fault, and the full trip-period policy is typically in play. A practitioner-oriented treatment of injury claims brought by Uber passengers addresses the coverage-period proof problems — app status, trip logs, GPS records — that decide these cases, and the documentation a claimant should secure before the platform’s data-retention clock runs. Where fault is shared among multiple actors, California’s pure comparative negligence rule under Li v. Yellow Cab Co. (1975) 13 Cal.3d 804 allocates responsibility proportionally rather than barring recovery — an allocation fight that plays out very differently before a jury than before a single arbitrator.
Forum Shapes Value — Which Is Why the Fight Is Worth Having
Practitioners sometimes ask whether the arbitration fight is worth the motion practice, since the same negligence claim can nominally be pursued in either forum. It is. The forum determines the breadth of discovery into the platform’s safety data and internal communications, the availability of a Los Angeles County jury for a catastrophic injury presentation, the public visibility of the proceeding, and — through all of those — the settlement calculus. Arbitration’s compressed discovery and private character systematically favor the repeat institutional player. The forum also affects how uninsured and underinsured motorist issues are resolved when the at-fault party carries minimal coverage, since UM/UIM disputes carry their own contractual arbitration provisions that operate independently of the platform’s terms and follow their own procedural track. Conceding the forum concedes leverage, and in a serious injury case that concession has a price measured in the recovery itself.
Delivery Platforms: A Different Contract, a Different Statute
The arbitration analysis becomes stranger — and the coverage analysis newer — when the vehicle was working a delivery app rather than carrying a passenger. Delivery terms of service are distinct contracts from rideshare terms, sometimes housed in different corporate entities, and the person struck by a delivery driver is almost never a party to either. Yet delivery cases have produced some of the most aggressive non-signatory arbitration arguments in recent consumer litigation, with platforms contending that a customer’s food-ordering account binds claims arising from a later traffic collision. Counsel should map every account relationship in the household before assuming the third-party analysis is clean.
On the liability side, California’s Assembly Bill 375 has reshaped the landscape for food-delivery platforms, creating a route to direct claims against companies like Uber Eats and DoorDash that bypasses the independent-contractor defense in defined circumstances — including account-sharing scenarios where the person actually driving was never the person the platform vetted. The statute converts what used to be a coverage dead end into a claim against the platform itself, and it pairs naturally with discovery into the platform’s account-verification practices.
Why Platform Identity Changes the Playbook
Finally, counsel should resist treating the two major rideshare platforms as interchangeable defendants. Their arbitration provisions have different drafting histories and different litigation track records in California courts; their delivery arms have different coverage structures; and their safety programs generate different direct-negligence evidence. A comparative review of the legal differences between Uber and Lyft accident claims is a useful starting point for tailoring the complaint, the discovery plan, and the response to the inevitable motion to compel. The practical checklist at intake is short but unforgiving:
- Identify every claimant’s contractual position — account holder, non-signatory, minor, heir — before filing, and structure the complaint accordingly.
- Preserve the formation record early: account creation date, device, app version, and any terms-update notices.
- Calendar the arbitration fee deadlines under sections 1281.97 and 1281.98 from the moment a demand is filed.
- Pin down the driver’s app status and coverage period with a preservation demand for trip logs and telematics before the retention window closes.
The throughline is simple. An arbitration clause is a contract defense, and contract defenses reach only parties to the contract. The modern rideshare case begins by asking not “what happened on the road,” but “who tapped what, and when.” Getting that question right — before the opposition brief is due — is often worth more to the injured client than any argument about the crash itself.