Amazon Prime's same-day delivery promise and DoorDash's thirty-minute guarantee have put millions of personal vehicles on the road performing commercial work. When one of those vehicles collides with your client, the coverage picture looks nothing like a standard auto case, and the defendants potentially standing behind the driver are more varied than most PI practitioners expect.
The Delivery Driver Is Not the Rideshare Driver
The legal framework for delivery driver crashes shares a family resemblance with rideshare law, but the two are not interchangeable. California's SB 371 and its counterparts in other states addressed transportation network companies (TNCs) moving passengers. Delivery platforms, including Amazon Flex, DoorDash, Instacart, GrubHub, and Shipt, largely fall outside TNC-specific legislation. That gap means coverage periods, platform liability exposure, and statutory duties differ substantially.
Unlike rideshare, where most states now mandate specific coverage floors for Period 1 (app on, no passenger) and Period 2 (en route to pickup), delivery platforms operate under policy language negotiated between the platform, the driver's personal carrier, and sometimes a commercial excess layer. There is no federal floor for delivery-driver coverage, and state-level requirements vary sharply.
How the Coverage Tiers Work
Most delivery platform agreements create a de facto two-period structure, even if the contracts do not label them that way:
- Period A (logged in, no active order): The driver's personal auto policy is primary. Most personal auto policies contain a business-use exclusion that, when triggered, leaves a gap. The platform's contingent liability coverage, if any, may backstop only at high limits and only after the personal policy exhausts or disclaims.
- Period B (active delivery, from order acceptance through drop-off): The platform's commercial automobile policy, or a hired/non-owned auto endorsement, typically becomes primary. Amazon Flex maintains a commercial auto policy providing $1 million per occurrence during active delivery windows. DoorDash and Instacart offer similar structures, though the exact terms shift as platforms renegotiate annually.
The critical threshold question in any delivery driver crash is whether the driver was holding an active order at the moment of impact. Platforms record this data. The driver's app session, the order timestamp, the GPS route, and the customer confirmation all generate electronic records that fix the driver's status at the time of the crash. Send the preservation demand to the platform's legal department within 72 hours, because most platforms overwrite route data on a rolling 30-day cycle.
Naming the Platform as a Defendant
Delivery platforms defend on independent contractor status vigorously, and in many jurisdictions they have succeeded. But independent contractor classification does not end the inquiry for a plaintiff. Three theories have produced verdicts or favorable settlements against the platforms directly.
Apparent Agency and the Holding-Out Doctrine
When the driver's vehicle carries a platform logo, the driver wears a branded bag or vest, and the platform app guided the driver to the delivery point, courts have found a triable issue on apparent agency. The plaintiff's reliance on that apparent authority is typically satisfied by the existence of the order itself. Plaintiffs injured at or near the delivery address, such as pedestrians or bystanders, have the stronger holding-out argument.
Non-Delegable Duty
Where the platform performs a function the law deems inherently hazardous, such as high-volume urban deliveries under time pressure, a non-delegable duty theory is available in some states. Most courts have declined to extend it to general commercial delivery absent a specific statutory hook, but the argument is worth preserving for appeal in jurisdictions with active appellate development on the issue.
Negligent Hiring, Retention, and Supervision
Platforms conduct background checks on drivers at onboarding, but many do not run periodic re-checks. A driver with a post-onboarding DUI or a pattern of moving violations who later causes a serious crash gives rise to a negligent retention claim. The platform's onboarding records, MVR pull dates, and internal safety scores are discoverable. Platforms sometimes resist producing safety-scoring algorithms under trade secret designations. Push back with a protective order rather than abandoning the request.
Discovery Checklist
Once the crash is reported and the preservation letter is served, the following platform records are priorities in auto accident coverage disputes involving delivery drivers:
- Driver application, background check results, and MVR pull history
- Order acceptance log for the date of the crash, with full timestamps
- GPS breadcrumb data for the delivery route
- In-app safety alerts or speed warnings triggered during the shift
- Platform's commercial auto policy declarations and any excess or umbrella layers
- Driver's personal auto policy declarations page and any business-use endorsement
- All prior incidents or claims involving the same driver on the platform
The platform's insurance certificate identifies the commercial carrier. Pull the ACORD certificate directly from the driver's onboarding file if the platform resists producing the policy in discovery. The commercial carrier needs to be on notice of the claim well before you file, because late notice is a coverage defense the carrier will assert against any demand that arrives after litigation begins.
Stacking the Recovery
If your client carries MedPay or a health policy that paid early medical expenses, and the platform's commercial policy ultimately covers the loss, track the subrogation exposure before disbursement. MedPay reimbursement rights and the made-whole rule vary by state. In lien-heavy cases, the presence of a $1 million commercial policy changes the math considerably compared to a personal-auto-only recovery. For practice-side guidance on managing the lien stack, see our coverage of lien resolution strategy and workers' compensation subrogation where gig-economy employment status intersects with comp coverage obligations.
Demand Timing and Coverage Coordination
Unlike a standard auto claim where the at-fault driver's personal carrier is on notice from the first report, delivery platform claims often involve three potential insurers: the driver's personal carrier (Period A disputes), the platform's commercial carrier (Period B), and any umbrella layer. Sending a single demand that addresses all three policies simultaneously, with a deadline for coverage confirmation, often forces an internal coverage dispute that the platform's counsel must resolve before responding to you. That dynamic can accelerate settlement on serious-injury cases where the commercial policy limits are well above what the personal carrier could pay alone.