Rideshare Accident Intake: The Uber and Lyft Questions That Determine Liability on the First Call

A caller says their Uber driver ran a red light and hit another car. They were in the back seat. The other driver is at fault, the Uber driver is at fault, or both are. Uber’s insurance may apply, or it may not, depending on what the driver was doing in the app when the crash happened.

Your intake team has 90 seconds to capture the one fact that determines which of those scenarios is true. Most of them do not know to ask.

Rideshare accident cases are among the most complex personal injury matters a law firm handles. The liability chain can include the driver, the platform, a third-party vehicle, and multiple insurance policies that activate or deactivate based on a single variable: whether the driver had the app on, had accepted a ride, or had a passenger in the car at the moment of impact.

This article gives your intake team the framework to capture that variable — and every other piece of information that determines whether this case is worth taking and who is actually liable.

Why Rideshare Cases Break at Intake

The caller does not understand how rideshare insurance works. They know they were in an Uber or Lyft. They know there was a crash. They want to know if they have a case. What they do not know — and cannot tell you unless you ask directly — is what phase of the trip the driver was in.

That phase controls everything. Uber and Lyft both operate on a tiered insurance structure:

• App off: The driver’s personal insurance applies. Uber and Lyft have zero liability.
• App on, no ride accepted (Period 1): Limited contingent liability coverage kicks in — typically $50,000 per person/$100,000 per accident for bodily injury and $25,000 for property damage. This applies only if the driver’s personal policy denies the claim or is insufficient.
• Ride accepted, en route to pickup (Period 2): Full $1 million commercial liability policy applies. This is Uber’s or Lyft’s primary coverage.
• Passenger in the car (Period 3): Full $1 million commercial liability policy applies, plus uninsured/underinsured motorist coverage in many states.

Period 1 cases are the ones that get mishandled. The caller says “I was hit by an Uber driver.” You take the case assuming the $1 million policy applies. It does not. You are now chasing a $50,000 contingent policy — or worse, the driver’s personal insurer who will argue that commercial use voids coverage entirely.

The only way to know which period applied at the time of the crash is to ask the right questions at intake. The data disappears fast. Uber and Lyft app logs are timestamped, but accessing them requires preservation letters and litigation. The driver’s memory of their app status will shift. Ask now.

The 8 Questions That Determine Liability and Case Value

1. Were you a passenger in the rideshare vehicle, or were you in another vehicle that was hit?

This is not obvious over the phone. Rideshare accident calls come in from passengers, from pedestrians hit by rideshare vehicles, from drivers of other cars hit by rideshare vehicles, and occasionally from the rideshare driver themselves if they were struck by a third party while on a trip.

Each scenario has a different liable party and a different insurance path. Get this first before anything else.

2. Which platform — Uber, Lyft, or another service?

Insurance structures are similar between Uber and Lyft but not identical. Some states have different minimum coverage requirements for Transportation Network Companies. If the caller used a lesser-known platform, corporate backing and insurance limits may differ significantly. Flag this for the attorney.

3. Had the driver accepted a ride request before the crash, or were they waiting for one?

This is the Period 1 vs Period 2/3 question. Callers rarely know the answer immediately. Help them think through it: “Did the driver pick you up directly? Were they already on their way to get you?” If the caller was the passenger in the car, the answer is easy — they were in Period 3. If the caller is a third party hit by a rideshare vehicle, this question determines whether the $1 million policy or the $50,000 contingent policy applies.

4. Did you request the ride yourself, or were you a guest in someone else’s booked ride?

Uber and Lyft allow passengers to ride in vehicles booked by someone else. This matters for injury claims because the account holder’s trip data is what you will need to subpoena. If the caller did not book the ride, get the name and contact information of the account holder at intake.

5. What were the injuries, and were they treated the same day?

Rideshare cases with soft tissue injuries and delayed treatment look identical to exaggerated claims to an insurance adjuster. Ask: emergency room, urgent care, or did the caller wait? If they waited, you need to understand why — not to judge, but because you will be explaining it later. Document the answer now.

6. Did the police respond, and did anyone get a police report number?

Rideshare crashes in urban areas often involve multiple parties who all have the app running and conflicting accounts of what happened. The police report is the earliest third-party record of the app status, driver statements, and scene conditions. If a report was filed, get the jurisdiction and report number. If not, ask why — officers are often not called to minor rideshare incidents, and that absence will matter to the insurer.

7. Has anyone from Uber, Lyft, or an insurance company already been in contact?

Rideshare platforms have rapid response teams. Uber Safety, Lyft’s claims process, and their contracted insurers (James River Insurance for Uber in many states) move quickly after reported accidents. If the caller has already spoken to an adjuster or signed anything, that conversation and any documents need to be preserved immediately. This is a case-altering disclosure that needs to happen in the first call, not after the attorney reviews the file.

8. Is the caller able to identify the driver by name, vehicle, or screenshot?

The Uber and Lyft apps display the driver’s name, photo, vehicle make and model, and license plate before and during a trip. Callers who are passengers usually have this information in their trip history. Third-party claimants often do not. Ask the caller to check their app trip history now, while they are on the phone, and capture the driver’s name and vehicle description. This information disappears from easy access as platform data retention policies vary.

The Insurance Maze: What Your Intake Team Needs to Know

Whoever picks up the phone does not need to be an insurance expert. They need to know two things: which tier applies, and who the potential defendants are. Here is the plain version:

If the driver had no passenger and no accepted ride at the time of impact, the case is against the driver individually and their personal insurer. Uber or Lyft may face negligent entrustment claims if the driver had a disqualifying history the platform should have caught, but that is attorney territory, not intake.

If the driver had accepted a ride or had a passenger in the car, the $1 million Uber or Lyft commercial policy is in play. This changes the economic calculus of the case significantly and expands your potential defendants to include the platform itself.

If a third-party vehicle caused the accident and the rideshare platform was not at fault, the case may still be valuable if the rideshare passenger was injured. The passenger has a claim against the third-party driver, and depending on state law, may be able to access the rideshare platform’s UIM coverage if the third-party driver is underinsured.

Your intake team does not need to resolve these questions. They need to capture enough information that your attorney can make the determination in under ten minutes.

Evidence That Disappears Fast

Rideshare cases have a shorter evidence window than standard auto cases. Brief your intake team on what to flag for immediate preservation:

• Trip receipts and in-app data: Passengers can export their trip history from the Uber or Lyft app. This includes start and end times, route, driver information, and payment. Tell the caller to do this before they hang up — or at least before the end of the day.
• App screenshots: The trip summary screen in both apps disappears into trip history quickly. If the caller still has the app open, screenshot the driver information and post-trip summary now.
• Dashcam footage: Many rideshare drivers run dashcams. Some platforms allow drivers to delete footage. A preservation letter to the driver and platform within 24 hours is worth sending even before you have agreed to take the case.
• Platform communication: Both Uber and Lyft send in-app and email communications after reported accidents. Have the caller forward these immediately.
• Medical records authorization: Get a HIPAA authorization signed at the intake stage or before the first attorney call. Rideshare insurers move fast, and having treatment records ready changes your first negotiation position.

When to Pass on a Rideshare Case at Intake

Not every rideshare call is a case. Your intake team needs clear criteria for when to route to an attorney versus when the economics do not work:

Pass signals:

• Driver’s app was off at time of impact (personal auto case, probably low-limit, standard intake criteria apply)
• No documented injuries and caller seeking only property damage
• Caller was the Uber or Lyft driver and seeking compensation for their own vehicle damage (platform insurance does not cover the driver’s own vehicle in a standard policy)
• Incident occurred more than two years ago (statute of limitations for personal injury in most states — verify by jurisdiction)

Escalate immediately signals:

• Passenger in the car during an accepted trip with any injury requiring medical care
• Third party struck by a rideshare vehicle during Period 2 or 3
• Multiple passengers injured in the same incident
• Caller has already been contacted by the platform’s insurance team
• Any fatality or traumatic brain injury mentioned

The Intake Script

Give whoever picks up the phone a script they can follow without knowing insurance law. Six questions, in this order:

“Were you a passenger in the vehicle, or were you in a different car that got hit?”

“Which service — Uber, Lyft, or something else?”

“Did the driver have you as a passenger when it happened, or were they on their way to pick you up?”

“Have you been to the doctor or emergency room?”

“Has anyone from the rideshare company or their insurance called you yet?”

“Can you check your app right now and tell me the driver’s name? We want to capture that before it gets harder to find.”

Every answer maps directly to the liability framework. Train whoever answers the phone to listen for “app was on” and “had a passenger” as the two phrases that mean this case has real insurance coverage behind it. If they hear those phrases, the call escalates. If the driver was offline, it is a standard auto intake.

What eNZeTi Captures That Phone-Only Intake Misses

The problem with rideshare intake is not that your team does not care — it is that the questions are counterintuitive. “Was the driver logged into the app?” is not a question anyone would think to ask without knowing the insurance structure behind it. Your front desk should not have to know insurance law. eNZeTi does.

eNZeTi’s intake AI runs the rideshare liability decision tree in real time. It captures app status, trip phase, injury severity, evidence availability, and prior insurer contact — and routes the call accordingly. By the time the attorney opens the file, the liability tier is already flagged and the preservation checklist is in the notes.

The $1 million case does not become a $50,000 case because your attorney was not available when the call came in. It gets captured at intake — or it does not get captured at all.

If your firm handles personal injury and has not built a rideshare-specific intake protocol, schedule a call with eNZeTi. We will show you exactly what the intake AI captures that your current process is missing.