Short answer: start with was the rideshare driver logged in, en route, or carrying a passenger and whether the claimant was the passenger, the driver, or a third party — those two signals carry the most weight before anything else in this article. Rideshare accidents introduce a layered insurance question that most standard auto-accident intake flows don’t account for, and getting it wrong misroutes genuinely high-value cases.
Quick Jump
Qualifying Factors & Entities
- Was the rideshare driver logged in, en route, or carrying a passenger
- Whether the claimant was the passenger, the driver, or a third party
- Rideshare company’s contingent or primary insurance phase at time of crash
- Injury severity and documentation
- Whether a police report names the rideshare vehicle
How This Case Type Feeds the Case Readiness Score
Rideshare’s tiered insurance coverage (offline, available, en route, in-trip) changes available policy limits dramatically, so a single qualifying question about driver status at the time of the crash can be the difference between a low-tier and high-tier score.
This factor sits alongside Wrongful Death Claims: Sensitive and Accurate Intake and How to Qualify a Car Accident Case for Intake in the Case-Type Qualification Guides cluster, and connects forward to What Is a Case Readiness Score and Why It Matters in Lead Scoring Methodology.
FAQ
Does this replace a human decision on case-type qualification guides?
No. It narrows down what a human reviews first. Signals like these route a submission into a priority tier; a staff member still makes the final call before a case is accepted.
Qualify Leads Like This Automatically
PI Intake Engine Pro scores every visitor on exactly these factors — instantly, on your own WordPress site.
Test the Free Demo →
