Legal Technologyrideshare accidentcase intakeUber Lyft claims

    Rideshare Accident Case Intake Red Flags: 12 Questions That Screen Out Losers

    A $180K rideshare rear-end looks strong until you realize the driver was off-app, the passenger delayed treatment 11 days, and the crash photos show 2 inches of bumper scuff. Twelve intake questions that catch these problems before you spend a dollar on discovery.

    Silent Witness TeamPublished June 11, 202610 min read
    Rideshare Accident Case Intake Red Flags: 12 Questions That Screen Out Losers

    The $180K Rideshare File That Should Have Died at Intake

    It's Tuesday at 9:40am. A potential client calls your office describing a rear-end collision while riding in an Uber. She says her neck hurts, she missed three weeks of work, and the Uber driver ran a red light. She's already been to the ER. The specials look like they'll clear $45K. You're thinking six figures.

    Six months later, you've spent $14,000 on medical records, an accident reconstructionist, and a biomechanical expert. Then you learn the driver's app status toggled to "offline" 90 seconds before impact. The TNC's commercial policy doesn't apply. The driver's personal policy has a $25K limit and an explicit rideshare exclusion. Your client's own UM/UIM coverage is $50K. The case that looked like $180K is now worth maybe $35K, minus your costs.

    This happens more often than most PI firms admit. Rideshare accident case intake red flags are different from standard MVA red flags because the insurance layer is different, the evidence is more volatile, and the liable parties shift based on app status at the moment of impact. Not five minutes before. Not when the ride was requested. At impact.

    Here are twelve questions that would have caught this case before you opened a file.

    App Status Is the Entire Case

    Before you ask about injuries, before you ask about treatment, ask this: was the driver logged into the app at the time of the crash? And if so, what phase were they in?

    Uber and Lyft both operate under a three-period insurance framework that's now codified in most states' TNC statutes. Period 1 (app on, no ride request) carries minimal coverage, often $50K/$100K liability. Period 2 (ride accepted, en route to pickup) triggers the TNC's commercial policy, typically $1M. Period 3 (passenger in the vehicle) keeps that $1M policy active.

    The difference between Period 1 and Period 2 is the difference between a $50K case and a $1M policy. Your first intake question needs to establish which period applied. Ask the client if they had a ride confirmation screen. Ask if they were in the car or waiting for pickup. Ask if they have screenshots of the ride receipt, which timestamps pickup and dropoff.

    If your client was the driver and the app was off, there is no TNC coverage. Period. The driver's personal auto policy likely excludes commercial use. You may have a case worth pursuing, but the available coverage just collapsed by 95%.

    The Screenshot Window Is 72 Hours

    Uber's ride history stays in the app, but the detailed trip data, including the driver's route, the exact pickup and dropoff times, and the fare breakdown, can change or become harder to access as time passes. Lyft's is similar. Both companies have litigation hold procedures, but you need to trigger them.

    At intake, ask the client if they still have the ride confirmation notification on their phone. Ask them to screenshot the trip detail screen before they do anything else. If the client is calling you four weeks post-crash and never saved anything, that's a red flag. Not fatal, but it means you'll be relying on a subpoena to the TNC for trip data, which takes 60 to 90 days and sometimes comes back incomplete.

    Better intake question: "Can you open the Uber or Lyft app right now and read me what it says about the trip on [date]?" If they can, you've just preserved the most important piece of evidence in the case.

    Whose Insurance Actually Responds

    Rideshare cases can involve up to five insurance layers. The TNC's commercial policy (through James River, Progressive Commercial, or similar). The driver's personal auto policy. The client's own UM/UIM coverage. The at-fault third party's liability policy, if there is one. And potentially the client's health insurance for medical payments.

    At intake, you need to identify which layers exist and which ones will actually respond. Ask these questions:

    • "Did the police report name the rideshare company?" If the officer listed it as a private vehicle, the TNC's insurer may not even know about the claim.
    • "Have you heard from any insurance company since the crash?" If the TNC's insurer has already contacted your client, the company knows. If they haven't, you need to put them on notice.
    • "Do you have uninsured or underinsured motorist coverage on your own auto policy?" Many rideshare passengers assume they don't need UM/UIM. In cases where app status is disputed, your client's own UM/UIM may be the only reliable coverage.

    "The single biggest intake mistake in rideshare cases is assuming the million-dollar policy applies. Half the time, it doesn't, and by the time you figure that out, you've already fronted five figures in costs." - a senior PI partner at a firm handling 200+ TNC cases annually

    Treatment Gaps Hit Harder in Rideshare Cases

    Treatment gaps are a red flag in any PI case. In rideshare cases, they're worse. Defense counsel for TNCs and their insurers are aggressive about causation challenges. James River and the carriers writing TNC commercial policies have dedicated defense panels. They've seen thousands of these claims. They know exactly what to look for.

    At intake, ask when the crash happened and when the client first sought treatment. If the gap is more than 72 hours, ask why. A 14-day gap between a rear-end collision and a first chiropractic visit is a red flag in any BI claim. In a rideshare case against a well-funded TNC defense, it's potentially fatal to your causation argument.

    Then ask about the treatment itself. Is the client treating with a physician, or only with a chiropractor? Has anyone ordered imaging? A cervical MRI showing disc pathology supports an AIS 2 or AIS 3 injury classification. Six weeks of chiropractic with no imaging and no MD involvement gives defense biomechanical experts room to argue the forces were insufficient to cause the claimed injuries, especially in cases with minimal vehicle damage.

    This is where having objective biomechanical data early changes your intake calculus. If the crash photos show minor cosmetic damage but the Delta-V analysis reveals a 12 mph speed change, you have a scientific basis for the injury claim that survives a MIST defense. If the Delta-V comes back at 4 mph with a crash pulse under 8g, you know the case is going to be a fight on causation regardless of what the MRI shows.

    Multiple Passengers, Multiple Problems

    Rideshare vehicles frequently carry more than one passenger. At intake, ask how many people were in the car. Ask if the other passengers are also claiming injuries. Ask if any of them have already retained counsel.

    Multiple claimants against the same policy create stacking problems. Even a $1M commercial policy gets thin when four passengers each claim $250K in damages. And if one of those passengers has a catastrophic injury (an AIS 4 or higher cervical fracture, for instance), the policy may exhaust on that claimant alone, leaving your client with a UM/UIM claim against their own carrier.

    Also ask about seating position. A right-rear passenger in a left-front impact experiences different occupant kinematics than the passenger directly behind the driver. The injury pattern should match the seating position and the principal direction of force. If your client was in the back seat on the far side from a T-bone impact and claims a left shoulder injury, that's a biomechanical inconsistency that defense experts will find.

    The Police Report Tells You Less Than You Think

    In rideshare crashes, police reports frequently misidentify the driver's employment status, omit the TNC entirely, or list the vehicle as a personal-use sedan. Don't rely on the report for insurance information.

    Ask the client if the driver mentioned working for Uber or Lyft at the scene. Ask if there was a TNC placard or decal on the vehicle. Ask if the driver was using a phone mount with the app visible. These details matter because they establish the commercial nature of the trip, which triggers the TNC's duty to indemnify.

    If your client was the rideshare driver and was hit by a third party, the analysis flips. Now you need to determine whether the at-fault driver has adequate coverage and whether the TNC's policy provides any supplemental UM/UIM benefit. According to NHTSA's vehicle safety data, urban intersections where rideshare pickups and dropoffs concentrate show higher crash frequency per vehicle-mile than highway segments. The crash circumstances matter for liability, but the coverage question matters more for whether the case is economically viable.

    Damage Photos Need to Happen at Intake

    Ask the client if they have photos of the vehicles. Ask if they took them at the scene. If not, ask if the vehicle has already been repaired.

    In a standard MVA, you can often get repair photos from the body shop or the insurer's appraisal. In a rideshare case, the TNC may have pulled the vehicle from service and had it repaired within days. Uber and Lyft both have rapid repair programs designed to minimize driver downtime. That speed is great for the driver. It's terrible for your evidence.

    If you have crash photos, you can run a Delta-V estimate before you even sign the retainer. A quick severity assessment tells you whether the crash forces are consistent with the claimed injuries. If the photos show significant structural deformation (a crushed quarter panel, deployed side curtain airbags), you're likely looking at a Delta-V above 15 mph and AIS 2+ injury probabilities that support a six-figure demand. If the photos show a scuffed bumper cover with no structural involvement, you need to decide early whether the case economics justify the fight.

    Comparative Fault in the Rideshare Context

    Your client was a passenger. Passengers are rarely at fault. But "rarely" isn't "never."

    Ask if the client was wearing a seatbelt. FMVSS 208 requires seatbelts in all seating positions, and IIHS data consistently shows that unbelted rear-seat occupants face significantly higher injury risk and severity. In a comp fault state, an unbelted passenger may see a 10% to 30% reduction. In a contributory negligence jurisdiction (Virginia, Maryland, Alabama, DC, North Carolina), being unbelted could bar recovery entirely.

    Also ask if the client did anything that contributed to the crash. Were they distracting the driver? Did they direct the driver to make an illegal U-turn? These sound unlikely, but TNC defense counsel will look at in-app messages, GPS route data, and any communication between passenger and driver to find a comp fault argument. Know this at intake, not at deposition.

    The Twelve Questions, Consolidated

    Here's what your intake sheet needs for every rideshare case:

    • Was the driver logged into the Uber or Lyft app at the time of the crash, and what phase (waiting, en route, or active ride)?
    • Does the client have the ride confirmation, trip receipt, or app notification still accessible?
    • How many passengers were in the vehicle, and has anyone else retained counsel?
    • Where was the client sitting in the vehicle?
    • Was the client wearing a seatbelt?
    • When did the crash occur, and when did the client first seek medical treatment?
    • What kind of treatment (ER, urgent care, primary care, chiropractic only)?
    • Has any imaging been ordered or completed?
    • Does the client have photos of the vehicles from the scene?
    • Has the rideshare vehicle already been repaired?
    • Does the client carry UM/UIM on their own auto policy, and what are the limits?
    • Did the police report identify the driver as a rideshare driver or the vehicle as a TNC vehicle?

    If you get negative answers on three or more of these, the case isn't necessarily bad. But it needs a harder look before you commit resources. Running the crash photos through a biomechanical analysis, checking the validated methodology against the claimed injuries, and confirming available coverage will tell you in 30 minutes whether this file deserves a retainer or a referral.

    What Good Screening Makes Possible

    The rideshare accident case intake red flags listed here aren't exotic. They're the same causation, coverage, and evidence-preservation issues that exist in every PI case, amplified by the layered insurance structure and rapid evidence decay that TNC cases create.

    Catching them early means you spend your litigation budget on cases with real coverage, clean causation, and provable damages. It means your demand packages land with force because the crash biomechanics match the injury claims and the policy limits are real. It means you stop subsidizing $180K files that were always $35K files wearing a better outfit.

    If you want to pressure-test a rideshare intake before you open the file, the free Delta-V calculator takes three crash photos and about two minutes.

    This content is for informational purposes and does not constitute legal or medical advice.

    This content is for informational purposes and does not constitute legal, medical, or professional advice. Consult a qualified professional for advice specific to your situation.

    Frequently Asked Questions

    Coverage depends on the driver's app status at the moment of impact. If the driver was in Period 3 (active ride with passenger), the TNC's commercial policy, typically $1M, applies. If the app was off, only the driver's personal auto policy responds, which often excludes rideshare use.

    See how Silent Witness scores your crash

    Upload three photos. Get a Delta-V range, PDOF, and injury probability in about two minutes. Free, no account required.