Key takeaways
- Coverage turns on what the driver's app was doing at the moment of impact: off, on and waiting, heading to a pickup, or carrying a passenger[1].
- In California the floor rises from $50,000 per person while waiting to $1,000,000 once a ride is accepted[1]; in New York from $75,000 to $1.25 million[2].
- Trip receipts, in-app messages and the driver's profile are the quickest evidence of app status. Ask for them on the first call.
- Who is calling, whether rider, driver, other motorist or pedestrian, changes every question after the first few.
The one fact that sorts the file
Every rideshare crash call turns on a detail the caller may not realize they hold: what the driver's app was doing at the moment of impact. Regulators split it into periods. California's Public Utilities Commission uses three: Period 1, app open and waiting for a match; Period 2, match accepted with the passenger not yet picked up; Period 3, passenger in the vehicle until they get out[1]. New York defines the trip itself as beginning when the driver accepts a passenger's request and ending when the last requesting passenger leaves the vehicle[3]. With the app off, the driver is just another motorist.
The required insurance changes sharply between those periods. In California, Period 1 needs primary coverage of at least $50,000 per person and $100,000 per incident for injury and death, $30,000 for property damage and $200,000 of excess coverage; Periods 2 and 3 need $1,000,000 of primary commercial coverage[1]. New York requires $75,000 per person and $150,000 per accident while the driver is logged on without a trip, and $1,250,000 while on a trip, plus the same amount of supplementary uninsured and underinsured motorist coverage[2].
Source: California Public Utilities Commission, 2026[1]
Show the data
| App status | Minimum coverage |
|---|---|
| App on, waiting (Period 1) | $100,000 |
| Ride accepted to drop-off (Periods 2-3) | $1,000,000 |
| App status | California minimum | New York minimum | Intake asks |
|---|---|---|---|
| App off | Driver's personal auto policy | Driver's personal auto policy | Was the driver working for an app at all? |
| Logged on, waiting for a request | $50,000 per person, $100,000 per incident, $30,000 property, $200,000 excess | $75,000 per person, $150,000 per accident, $25,000 property | Did the driver say they were online or about to get a ride? |
| Request accepted, heading to pickup | $1,000,000 primary commercial | $1,250,000 per occurrence | Was someone waiting to be picked up? |
| Passenger on board | $1,000,000 primary commercial; uninsured/underinsured $60,000 per person, $300,000 per incident | $1,250,000 per occurrence plus $1,250,000 supplementary uninsured/underinsured | Who requested the ride, from which account, and when did the trip end? |
Who is calling: four rideshare branches
Rideshare use is common enough that these calls are routine. In Pew's fall 2018 survey, 36% of US adults had used a ride-hailing app, up from 15% three years earlier, and the share was 51% among adults aged 18 to 29 and 45% among urban residents[4]. The callers fall into four groups, and the questions split after the basics.
- The passenger. Usually the clearest case for app status, because a trip was under way. Ask who requested the ride; a guest riding on a friend's account still needs the account holder's name and the trip record.
- The rideshare driver. Their own injuries, and possibly a claim against another motorist. Their personal policy may not cover them while logged on, and their status matters for every other source of payment. Flag it for the attorney rather than guessing.
- The other motorist. Hit by a car that was or may have been working for an app. They will not know the app status, so ask what they saw: a trade dress sticker, a passenger in the back, the driver checking a phone mount.
- The pedestrian or cyclist. Hit by a rideshare vehicle. Run the pedestrian and bicycle intake checklist and add the app questions below.
Two people from the same crash may call the same firm: a passenger and the driver, or two passengers. Their interests can conflict, so take every name for the conflict check before the fact interview goes deep.
First-call questions
Screen first
Do you already have a lawyer for this crash? Date, time, city and state. Are you hurt, and have you been seen by a doctor?
Pin down the app status
Which app? Were you a passenger on a trip, waiting for a pickup, driving for the app, or in another vehicle? Did the trip show as active, ended or cancelled?
Identify the trip
Who requested it, from which account, the pickup and drop-off points, the time on the receipt, and the driver's name and vehicle as shown in the app.
Crash facts
How it happened in the caller's words, other vehicles and drivers, where the caller was sitting, seat belt use, and what anyone said at the scene.
Reports and claims
Police agency and report number. Did anyone report the crash in the app, and has an insurer or the app's claims team contacted the caller or given a claim number?
The caller's own coverage
Their auto policy if they have one, the policies of people they live with, and their health coverage. Record company and policy numbers from cards, not memory.
Script for the app-status question: "These crashes are handled differently depending on what the driver's app was doing at the time. Were you on a trip, waiting to be picked up, or were you in a different car? If you're not sure, that's fine; the trip receipt usually shows it."
Records worth asking for today
Most of the proof sits on someone's phone. Ask the caller to screenshot it now and keep the originals, because accounts get closed and messages get deleted.
- The trip receipt or ride history entry: pickup and drop-off times and places, route map, fare and trip status.
- The driver's profile as shown in the app: name, photo, vehicle and plate.
- In-app messages and call logs with the driver, and any crash report submitted through the app with its reference number.
- For drivers: the driver app's trip log or earnings screen around the time of the crash, showing whether they were online, en route or on a trip.
- Dash camera footage if the driver ran one, and photos of all vehicles, the scene and injuries.
- Insurance shown at the scene. California requires drivers to provide proof of both their personal and the commercial insurance after an accident[5], so ask whether the driver showed both and photograph whatever was handed over.
Driver callers have one more early question: damage to their own car. California requires app companies to tell drivers that their personal policy will not provide collision or comprehensive coverage while they are logged on[5]. Record what coverage the driver believes they have and leave the analysis to the attorney. For the full insurance sequence on any crash, see insurance details to collect in accident cases.
Driver callers: their own set of questions
A rideshare driver who calls about their own injuries needs a longer status section than a passenger, because their answers decide which policy is even in play. Ask in the same order every time and write down the source of each answer: the driver's memory, a screenshot, or a message from the app company.
- Which apps were open at the time. Some drivers keep more than one platform running, so ask about each one, not just the one that sent the last ride.
- Status in each app at the moment of the crash: offline, online and waiting, heading to a pickup, or carrying a passenger. The trip log or earnings screen usually shows it.
- Whose car it was: owned, leased, borrowed or rented, and whose name is on the insurance card.
- What the driver's own insurer has been told, and whether the policy has a rideshare endorsement. If the driver does not know, record that and ask them to find the declarations page.
- Time off the road since the crash, weekly hours before it, and any change to their account status with the app.
- Every passenger's name, if there were any, for the conflict check.
Whether any work-injury benefit applies to an app driver depends on state law and the driver's status, which is a question for the attorney. Intake's job is to capture the facts that let the attorney answer it quickly: the apps, the statuses, the times and the documents.
When the app status is unclear
Plenty of calls leave the status open. The driver said he was heading home. The trip ended two minutes before the crash, or was cancelled as the car pulled up. The caller rode on a friend's account and has no receipt. Intake's job is to record what is known, mark what is not, and note where the answer can be found: whose phone, which account, which email inbox.
Other drivers' coverage matters as well. When a third vehicle caused the crash, its insurance comes into play, and in 2023 an estimated 15.4% of US drivers were uninsured[6]. California's Period 3 rules add uninsured and underinsured motorist coverage of $60,000 per person and $300,000 per incident[1]. None of that is intake's to weigh, but each fact decides which letters the attorney sends first.
Example (fictional): a passenger calls on a Sunday night. Her rideshare car was rear-ended at a light by a pickup truck at 11:20 pm, about four minutes from her apartment. She has the trip receipt showing the ride still active, the driver's profile screenshot, the pickup truck's plate from a photo, and a police incident number. She booked the ride on her own account and does not own a car; her partner, who lives with her, has an auto policy. Intake records all of it, takes the names of both drivers and her partner for the conflict check, and books her consultation for Monday morning. The attorney starts the day knowing it was an active trip, with two vehicles' insurance to identify.
Intake mistakes that cost weeks
- Writing "rideshare crash" without the app status. The single most important fact goes missing and the attorney starts with a callback.
- Taking the time from memory instead of the trip receipt. A few minutes can move a crash from one period to another.
- Missing the account holder when a passenger rode on someone else's account, so nobody can pull the trip record.
- Asking only about the rideshare driver's insurance and forgetting the third vehicle, the caller's own policy and the household's.
- Interviewing two people from the same crash before running the conflict check on both.
Each of these is fixed the same way: required fields on the intake form, in a fixed order, with "unknown" as an allowed answer so staff never guess to fill a box.
Covering the calls that come in at night
- Caller
- SI Employee
- System
- Your team
01Caller
Passenger calls
Late evening, after the police leave the scene or after the ER.
02SI Employee
App-status questions
Trip active or ended, who booked it, driver and vehicle from the app.
03SI Employee
Conflict names taken
Both drivers, vehicle owners, other passengers.
04SI Employee
Consultation booked
Into the consultation calendar, or a request the team confirms.
05System
Summary to intake
Recording, transcript and summary in the account; the right person is notified.
06Your team
Screenshots collected
Intake follows up for the receipt and profile through the firm's secure channel.
Example sequence. The screenshots are requested by staff the next morning, not by the phone line.
Rideshare trips cluster in the evenings and at weekends, and so do the calls that follow them. An SI Employee can answer when the line is forwarded after hours, ask your approved rideshare questions in order, take the conflict-check names and book the consultation, so the file is waiting with a recording and transcript when intake opens. You can try a call yourself, and the solo injury lawyer example shows how a small firm's evening gap is modelled. For the rest of the crash questions, the car accident intake checklist still applies.
Frequently asked questions
The driver had no passenger at the time. Does the app's insurance still matter?
It can. In California, Period 1 (app open, waiting for a match) has its own minimum coverage of $50,000 per person and $100,000 per incident plus $200,000 of excess[1]. With the app off, the driver's personal policy is the starting point. Record what the caller knows and let the attorney confirm.
Do these coverage amounts apply in every state?
No. Each state sets its own requirements. California's and New York's are shown here as examples[1][2]; the attorney checks the rules for the state where the crash happened.
The caller rode on a friend's account. Is that a problem for intake?
It just changes where the records are. Take the account holder's name and contact details and ask the caller to have the friend screenshot the trip receipt and driver profile.
Can the firm talk to both the passenger and the rideshare driver from the same crash?
Their interests may conflict. Take both names for the conflict check before the fact interview goes deep, and let the attorney decide whether the firm can speak with each of them.
Should the caller report the crash in the app before calling a lawyer?
Intake should not advise either way. Record whether a report was made, when and its reference number, and note it for the attorney's first conversation.
References
California Public Utilities Commission (2026). Insurance Requirements for TNCs (opens in a new tab) ↑
The New York State Senate (2026). New York Vehicle and Traffic Law § 1693: Financial responsibility of transportation network companies (opens in a new tab) ↑
The New York State Senate (2026). New York Vehicle and Traffic Law § 1691: Definitions (opens in a new tab) ↑
Pew Research Center (2019). More Americans are using ride-hailing apps (opens in a new tab) ↑
California Public Utilities Commission (2026). Insurance Requirements for TNCs: driver disclosures and proof of insurance (opens in a new tab) ↑
Insurance Research Council (2025). One in Three Drivers are Either Uninsured or Underinsured in the U.S. (news release on Uninsured and Underinsured Motorists: 2017-2023) (opens in a new tab) ↑