Gig, rideshare, and delivery driver injuries: screening questions that sort WC from PI

“I drive for one of the apps and got hit.” That sentence can describe a workers’ compensation claim, a third-party injury claim, both, or neither. It depends on who pays the driver, what the app showed at the moment of the crash, whose car it was, and who caused it. Intake that stops at “rideshare accident” is guessing.

Classification decides whether comp is even on the table

Workers’ comp generally covers employees. Most rideshare and food-delivery platforms treat drivers as independent contractors, and in many states that means no comp claim against the platform. That classification may or may not hold up, which is a question for the firm’s attorneys. We cover how intake should flag it in our piece on independent contractor misclassification.

Package delivery is often different. Many drivers in branded vans work for a delivery service partner or contractor company, a small business that may employ them on a W-2. That driver may have a comp claim against the contractor company even though the brand on the van belongs to someone else. Intake that hears the brand name and assumes “contractor, no comp” can miss it entirely.

App status drives the coverage picture

Insurance available through a platform often depends on what the driver was doing in the app at the time: offline, logged in and waiting for a request, en route to a pickup, or carrying a passenger or order. The coverage that applies in each phase varies by platform and by state, and it changes over time. Intake does not need to know the policy terms. It needs to capture the status accurately so the attorneys can.

The driver’s own personal auto policy matters too. Many personal policies exclude or limit coverage for commercial use, so a driver who assumes their own carrier will handle it may be wrong. And passengers injured in a rideshare are a personal injury matter, not a comp matter, regardless of how the driver is classified.

Eight screening questions

Sorting the outcome

The answers usually land the caller in one of four lanes:

• Likely comp: W-2 employee of a delivery contractor, injured on the job, no other party at fault.
• Likely PI: a passenger, or a 1099 driver hit by another vehicle.
• Both: an employed driver hit by a third party. Route it the way you would any on-the-job crash with a liability claim.
• Needs attorney review: unclear pay structure, multiple apps active, or a classification that looks questionable.

The lane is a routing decision, not a legal conclusion. When in doubt, send it to review rather than rejecting it.

Capture app records early

Ask the caller to screenshot the trip or delivery in the app, save any earnings statements for that day, and keep the messages they exchanged with the platform. App histories can be hard to retrieve later, and the driver’s status at the moment of the crash is often the fact everything else depends on. Note on the intake record what the caller has and what still needs to be requested.

Screening gig drivers before the lead reaches you

Case Leads Pro screening flows ask these questions before a lead is delivered, using criteria written with your intake team before launch. Every phone number is SMS-verified, and records arrive in real time with pay structure, app status, and vehicle facts already captured. Leads can route to your workers’ compensation or personal injury team, or both. Screening is not a guarantee of a signed case, but it gets your team to the right questions faster. To walk through how this would fit your intake, set up a 20-minute call.