Call For A Free Consultation(602) 345-1818Free Case Review
-
Cities Served
-
T-Shirt Lawyer
Fighting Suits,
Not Wearing Them.Enter the universeStories, animation and community. Created by Impact Legal.
Call For A Free Consultation(602) 345-1818Free Case Review
Fighting Suits, Stories, animation and community. Created by Impact Legal.
We're Here To Help 24/7
(602) 345-1818You were on a delivery run when the crash happened. Now two insurers are pointing at each other, and neither one wants to be first in line. A delivery app driver accident claim in Arizona rarely looks like a normal car accident claim, because the coverage that applies can shift depending on what the app was doing at the moment of impact.
This article covers what “delivery status” does to your coverage, why your personal auto policy may deny the claim outright, how Arizona’s transportation network statutes structure platform coverage tiers, and why the route and timestamp data sitting on the app’s servers is often the most important evidence in the file. If your crash involved carrying a passenger instead, our page on rideshare and delivery accident claims in Phoenix covers that side.
One caveat up front. Every answer below depends on the specific policy language, the specific platform, and the specific facts. This is general information, not advice about a particular claim.
Start with an honest statement of what Arizona’s statute actually says, because this is where a lot of online content gets sloppy.
A.R.S. § 28-9551 defines “transportation network services” in passenger terms: the transportation of a passenger between points chosen by the passenger, beginning when the driver accepts a requested trip through the digital network and ending when the passenger exits the vehicle or the trip is canceled (A.R.S. 28-9551).
Read that again. The definition is built around a passenger. It says nothing about a food order, a grocery bag, or a package. That matters enormously for delivery drivers, because it means the statutory framework below does not automatically apply to every app-based delivery crash in this state.
So the first question in any delivery case is not “which tier applies.” It is this: does this platform’s coverage program work off the transportation network company framework at all, and if so, what does its own policy say about delivery-only trips? Some platforms are organized as transportation network companies and extend a tiered commercial policy to delivery work by contract. Some operate under different structures with different insurance programs. The certificate of insurance and the platform’s own driver-protection terms answer that question, not a statute read in isolation.
That said, the practical day still breaks into stages, and nearly every platform program is built around them:
The thirty seconds before you tapped “accept” and the thirty seconds after can sit in two different coverage worlds. Proving which side of that line you were on is a core part of the case.
Here is what most delivery drivers do not realize until the denial letter arrives. Most standard personal auto policies exclude coverage while the vehicle is being used to carry persons or property for a fee. Delivering food, groceries, or packages for an app commonly falls inside that exclusion unless you purchased a rideshare or delivery endorsement.
The Arizona Department of Insurance and Financial Institutions publishes consumer guidance on how auto policies, claims, and coverage options work in this state, and it is worth reading before you assume you are covered (AZ DIFI auto insurance guide).
Practical consequences of a commercial-use exclusion:
The exclusion is a policy-language question, not a general rule. Two carriers writing in Phoenix can word the delivery exclusion differently, and some endorsements cover the logged-in waiting period but not the active delivery period. Somebody needs to read your declarations page and the actual exclusion text line by line before drawing conclusions.
As a baseline, A.R.S. § 28-4009 sets Arizona’s minimum liability limits at $25,000 per person, $50,000 per accident, and $15,000 property damage for policies issued or renewed beginning July 1, 2020. Older policies, and holders of a self-insurance or partial self-insurance certificate under A.R.S. § 28-4007, can fall under the earlier 15/30/10 figures. Either way, that baseline exists separately from whatever the platform provides. It is a floor, not a ceiling, and it is frequently not enough for a serious injury.
A.R.S. § 28-4038 sets financial responsibility requirements and splits them by trip status (A.R.S. 28-4038).
Note the statute’s own predicate before relying on the numbers. Both subsections apply to a transportation network company that requires its drivers to accept rides booked and paid for exclusively through the company’s digital network or software application. If a given platform does not meet that description, these figures are not what governs, and the applicable coverage comes from the platform’s contractual insurance program instead.
Logged in, no accepted request. During this period the statute requires primary liability coverage of at least $25,000 per person for bodily injury, $50,000 per incident for bodily injury, and $20,000 for property damage.
From acceptance through completion. The required primary liability coverage rises to at least $250,000 per incident. The statute also sets a higher required figure, one million dollars per incident, but that higher number is triggered only when a passenger to whom the driver is providing transportation network services is occupying the vehicle. In a pure food, grocery, or package delivery crash there is no such passenger in the car, so the higher figure will generally not apply. Any source telling delivery drivers they sit under a million-dollar policy while dropping off a burrito is misreading the statute.
Two more warnings. First, these are statutory floors, not caps. The actual platform policy may carry higher limits, and the certificate of insurance is the document that tells you. Second, a floor does not mean automatic payment. The platform’s insurer will still evaluate liability, and it will still look for a reason to push the claim toward your personal carrier.
That is exactly why the coverage gap matters. If your personal policy excludes delivery use and the platform’s insurer says you were between orders, you can land in a stretch where nobody accepts the claim. Sorting out which tier applied at the moment of impact is often the most valuable work done early in a delivery case. Our page on how app status affects rideshare insurance coverage in Arizona breaks down the same tier logic on the passenger side, and getting injured while driving for Uber or Lyft covers the driver-side claim mechanics.
If the driver who hit you had no insurance or not enough, uninsured and underinsured motorist coverage becomes the question.
Under A.R.S. § 28-4038, for a platform that meets the statutory predicate above, the primary uninsured motorist coverage required during the period after a request is accepted is the greater of $25,000 per person and $75,000 per incident, or the bodily-injury figures set out in A.R.S. § 28-4009. Meaningful, but not a blanket million-dollar guarantee. Drivers are sometimes told otherwise.
Your own policy’s UM and UIM coverage is governed by A.R.S. § 20-259.01, which sets out how carriers must offer that coverage, how written selections and rejections work, and related subrogation and medical-payments lien rules (A.R.S. 20-259.01). Whether your personal UM coverage responds during a delivery run depends on the policy type and on whether a commercial-use exclusion reaches that specific coverage part. Those are two separate questions, and answering one does not settle the other.
Deadlines are different here too. A.R.S. § 12-555 imposes its own written-notice and suit or arbitration timing requirements for uninsured and underinsured motorist benefits, separate from the general personal injury limitation period. Do not assume the two-year rule covers a UM claim.
For the general framework, start with uninsured motorist claims in Arizona, then layer the delivery facts on top.
Delivery platforms generate a continuous record: the moment you went online, the moment an order was offered, the moment you accepted, GPS pings along the route, pickup confirmation, dropoff confirmation, and the moment the trip closed. Timestamped to the second. That record is the direct proof of which coverage tier applied.
NHTSA’s Special Crash Investigations program treats crash-scene documentation, vehicle inspection, interviews, medical records, and event data recorder downloads as complementary evidence streams, each with its own preservation demands (NHTSA SCI). App route data behaves much the same way by analogy. It is machine-generated, it is precise, and it does not survive on its own.
Three things drive whether that data is usable:
Your own phone helps. Screenshot the order screen, the map, and the delivery history before anything gets overwritten. Vehicle event data recorder information and any dashcam footage should be preserved on the same timeline. Our article on sending an evidence preservation letter explains the mechanics.
One more item. You are generally not required to give a recorded statement to the platform’s insurer or the other driver’s insurer before you have legal guidance. Your own policy’s cooperation clause may require you to cooperate with your own carrier, but “cooperate” and “give an unprepared recorded statement today” are different things. Get the adjuster’s name and direct line, and say you will respond after talking with an attorney. More on that in insurance adjuster tactics in Arizona.
Arizona applies comparative fault under A.R.S. § 12-2505 (A.R.S. 12-2505). In plain terms, a claimant’s recovery is reduced in proportion to that claimant’s share of fault: total damages multiplied by 100% minus the fault share. If damages are valued at $100,000 and the claimant is found 20% at fault, the recoverable figure drops to $80,000. That is arithmetic illustrating the rule, not a prediction about any particular claim.
The statute carries an important exception. There is no right to comparative negligence in favor of a claimant who intentionally, wilfully, or wantonly caused or contributed to the injury or wrongful death. That is a complete bar, not a reduction.
Allocation among multiple defendants is a separate question governed by A.R.S. § 12-2506, which addresses how fault is apportioned among several tortfeasors. In a delivery case the potential parties can include the other driver, a vehicle owner, and in some circumstances a property owner. Whether a platform itself bears any direct liability is fact-dependent and turns on the relationship and the specific conduct involved.
Expect fault arguments that ordinary cases do not draw. The other side may claim you were distracted by the app, rushing a delivery window, parked illegally, or making an unsafe maneuver near a dropoff point. Those arguments are not automatically correct, and route data sometimes cuts against them by showing actual speed and path. Our page on how fault is proven in Phoenix goes deeper.
In Arizona, personal injury claims generally must be brought within two years of accrual under A.R.S. § 12-542, subject to the exception referenced in A.R.S. § 12-551. Miss the deadline and the claim is usually barred regardless of how strong it is.
Delivery cases carry extra wrinkles:
Have every applicable deadline mapped early rather than near the end.
Arizona recognizes a tort claim against an insurer that unreasonably denies or delays payment on a valid first-party claim. The controlling formulation of the reasonableness standard comes from Arizona case law, and the precise authority and elements should be confirmed against the current opinions before anyone relies on them in a specific matter.
The tier structure in delivery claims gives insurers a convenient place to stall, so patterns worth documenting include:
Delay alone is not bad faith. The question is whether the insurer’s conduct was unreasonable measured against the facts it had, and that is a high bar. If you think you are seeing it, start with insurance bad faith in Phoenix and keep a dated log of every communication.
Often not. Most personal auto policies contain an exclusion for carrying property or passengers for a fee. Some carriers sell a delivery or rideshare endorsement that closes part of that gap. The only way to know is to read your policy’s exclusion language and any endorsements you purchased.
If the platform meets the statutory description in A.R.S. § 28-4038, meaning a transportation network company that requires drivers to accept rides booked and paid for exclusively through its digital network, the waiting-period liability requirements are $25,000 per person, $50,000 per incident, and $20,000 property damage. If the platform does not meet that description, its contractual insurance program controls instead. Your personal policy may also be implicated depending on its exclusions.
For a platform covered by A.R.S. § 28-4038, the primary liability requirement from acceptance through trip completion is at least $250,000 per incident. The statute sets a higher required figure, one million dollars per incident, only when a passenger receiving transportation network services is occupying the vehicle, which generally will not be the case on a food or package delivery run. Actual policy limits may exceed the statutory floor, and the certificate of insurance controls.
Usually yes, but it requires a timely request to the correct corporate entity, and retention windows are limited. Screenshot your own delivery history immediately, then have a preservation demand sent before the platform’s routine purge cycle runs.
Generally not without legal guidance. Your own policy may contain a cooperation clause, but that does not mean giving an unprepared recorded statement to a third party’s adjuster on the first phone call.
Personal injury claims are generally subject to a two-year period under A.R.S. § 12-542. Uninsured and underinsured motorist claims have their own deadlines under A.R.S. § 12-555. Claims against a public entity or employee require a notice of claim within 180 days of accrual under A.R.S. § 12-821.01 and suit within one year under A.R.S. § 12-821.
Delivery crashes get complicated fast, and the coverage question usually has to be answered before anything else moves. We handle car accident and gig-driver injury cases in Phoenix and across Arizona, and Jared works the file personally.
Free case review: (602) 345-1818. We answer 24/7. Fee and case-cost terms are set out in a written agreement.
Jared J. Pehrson is the lead attorney at Impact Legal Car Accident Attorneys, a Phoenix personal injury firm. He is licensed in Arizona, practices in personal injury law, and handles car accident and gig-driver injury matters personally rather than routing them through a high-volume intake process. Written for Arizona claims; New Mexico rules differ.
By Jared J. Pehrson | Impact Legal Car Accident Attorneys
A free conversation can help you understand your next step.