Delivery Driver Crashes on a Run: What to Do

The text lands at 7:40 on a Friday night, and it is always some version of the same sentence: "One of my drivers just hit somebody on a run." Ninety seconds later comes the question underneath it: "Is this on me, or is it on his insurance?" The panic is fair. Most operators have never had a serious auto claim, the coverage that answers it has a name nobody taught them, and the first hour is exactly when the decisions that shape the whole claim get made by whoever happens to be holding the phone. This article walks the first hour, the order in which the coverage layers actually respond, what a plaintiff's lawyer does with your reimbursement records long before anyone talks about a trial, and the 30 day repair that makes the next one survivable.

The first hour: people first, facts second, opinions never

Almost everything that goes wrong in the first hour goes wrong the same way: someone with good intentions says something helpful. A shift lead tells the other driver "we will take care of it." A manager tells the responding officer that the driver was hustling a late order. Neither statement is a lie, and both of them get read back to you two years later. The sequence below is short enough to tape inside the office door, which is where it belongs.

1. Safety and 911 come before the call to you

Your driver's first call is emergency services, not the store. People get medical attention, police get called even when the damage looks cosmetic, and a report number comes into existence. A police narrative written that night is worth more than any account your driver types out a week later. And if your driver is the one hurt, that is a workers' compensation claim from the moment it happens, not from the moment somebody gets around to filing it.

2. The driver reports facts, not fault

Train one sentence and repeat it at every orientation: exchange information, describe what happened, do not assign blame. "I was making a delivery for the shop" is a fact and your driver should say it. "I was hurrying because the order was already late" is an admission that your carrier will spend the next year paying for. Nobody from your company promises to cover anything, at the scene or on the phone that night. That call belongs to an adjuster, and making it early can complicate the coverage you have been paying for.

3. Photograph everything, including the delivery bag

Both vehicles, all four corners of each, the plates, the lane, the signals, the weather, the skid marks, the debris field. Then the inside of your driver's car, because whether a hot bag was riding in the passenger seat and whether a phone was mounted or loose are questions an opposing expert will ask. Timestamped phone photos taken at the scene beat a diagram drawn from memory in every deposition anyone has ever sat through.

4. Notify your broker the same day, even if nobody looks hurt

Late notice is one of the few ways an operator can genuinely damage a claim that was otherwise covered. Soft tissue injuries surface three days later and the demand letter shows up three months after that, by which point the scene is gone and the story has settled. Report it the same day, in writing, with the police report number attached. Reporting an incident is not the same thing as filing a claim, and your broker will tell you which one this is.

5. Freeze the run record before the shift closes out

Before the point of sale rolls the day, export what that run actually was: order time, dispatch time, delivery address, route, miles, the driver, and the reimbursement paid on it. This is the record that gets subpoenaed, and it is the one most likely to be gone in ninety days because a system quietly rotated it. Save it to a dated file along with the driver's license, motor vehicle record, and current personal auto certificate, and tell your manager it is not to be touched.

Who pays, and in what order: four layers and one file

Operators expect a single answer to "whose insurance is this." There are four, and they respond in sequence rather than all at once. Start with the one most operators assume will handle everything, and understand why it often will not: personal auto policies routinely exclude delivery use. Your driver's own insurer can deny the moment delivery driving is established, which leaves your business standing behind the accident with its general assets. Filling that gap is the entire job of hired and non-owned auto (HNOA) coverage. In plain operator language: when your employee drives their own car to deliver your pizza and injures someone, HNOA responds to the business's share of that claim. Our page on what HNOA costs for pizza delivery covers what moves the premium. The table below covers what each layer wants from you the week of a crash.

Read the last column again and notice what those four cells have in common. Not one of them asks you a question you can answer from memory, and not one of them can be assembled after the crash without it looking exactly like what it is. Every layer above is asking for a record that had to exist beforehand.

Workers' compensation is usually the first claim, not the second

Operators fixate on the third party, because the third party is the one with the lawyer. In practice the claim that opens first, costs first, and follows you into your renewal is your own driver's. A delivery driver with a fractured wrist is out for eight weeks, and the comp file is open before anyone has finished arguing about who had the green light. Report it the day it happens; a delayed comp report is the single most reliable way to turn a routine claim into a contested one.

This is also where classification bites. If you have been treating delivery drivers as contractors to avoid comp premium, a crash is the event that tests that theory in front of the people least likely to accept it. Comp carriers, state agencies, and injured workers' counsel all arrive at the same question at once, and they arrive with your pay records in hand. Our guide to paying delivery drivers legally covers the classification and pay side; treat it as the prerequisite, not the follow-up.

The plaintiff's lawyer reads your reimbursement file before your insurance file

In a serious injury case the other side is not only asking whether your driver was careless on that one turn. They are asking whether your system made careless driving rational: whether the pay structure rewarded speed, and whether drivers were effectively subsidizing your delivery business out of their own pockets. The exhibits for that theory are not crash exhibits. They are pay records: what you reimbursed per mile, whether that number had any documented basis, and how it compared to what the miles actually cost.

Reimbursement litigation has already built that record for them. Parker v. Battle Creek Pizza, Inc. (6th Cir. 2024) rejected both a flat per-delivery fee and automatic use of the IRS figure, requiring instead a reasonable approximation of a driver's actual costs; it is binding only in the Sixth Circuit, which is Michigan, Ohio, Kentucky and Tennessee, and it is persuasive authority everywhere else. Bradford v. Team Pizza, Inc. sits on the same ground in the same circuit, with the same limit on its reach. West v. BAM! Pizza Management (D.N.M., January 2026) shows the exposure is current rather than historical. None of these are crash cases, and that is precisely the point: they establish that your per-mile number is discoverable, comparable, and easy to make look indefensible if nobody wrote down why you chose it. The IRS standard mileage rate is $0.76 per mile, effective July 1 2026, and it is a safe harbor rather than a legal floor. What protects you is the basis you documented, not the number you happened to pick. None of this is legal advice.

The practical move is to run the audit the other side would run, while nothing is pending. Our driver reimbursement compliance audit walks the same records in the same order, and the mechanics of setting a defensible number are in mileage reimbursement for pizza delivery and the accountable plan rules. On the hiring side, the parallel exhibit is the motor vehicle record: a driver with a recent at-fault history and no MVR check on file is how a simple auto claim becomes a negligent hiring claim against the business itself.

What a crash actually costs: the honest answer, then the modeled one

What does a crash cost you? Honestly: it varies too much for any number here to be a quote. It moves with injuries, limits, venue, your deductible, what your renewal looks like afterward, what your comp experience modifier does for the next three years, and whether you lose a driver you cannot replace in a month. Any operator quoting you a single figure is selling something.

One piece of it is modelable, though, and it is the piece that shows up as an exhibit rather than an invoice. Every figure here is illustrative and modeled. Take a shop with 8 drivers running 220 miles a week each, reimbursed at $0.42 a mile while the IRS standard mileage rate sits at $0.76. That is 91,520 driver miles a year and a gap of $0.34 on each one, or roughly $31,100 a year, illustrative and modeled. In a demand letter that number is not framed as a reimbursement dispute. It is framed as the amount you saved by underfunding the vehicles you put on the road. Whether the shortfall is legally owed depends on your state and your pay rates; whether it reads badly to a jury does not depend on anything. If you are still weighing in-house delivery against the marketplaces on cost alone, our break-even calculator puts the insurance line where it belongs, next to the commission it replaces.

The 30 day repair: five things to fix before the next run

A crash is a bad way to audit your operation, but it is an audit. Here is the list, in the order a broker would work it.

• Confirm HNOA is in force and that delivery was disclosed. Not "we have commercial insurance." Pull the policy, find the hired and non-owned auto section, and confirm your delivery volume matches what was on the application. Undisclosed exposure is how a policy that exists still fails to respond.
• Collect a dated personal auto certificate from every driver. One per driver, with the renewal date, refreshed on a calendar rather than when someone remembers. A lapsed personal policy you did not know about is your problem the day it matters.
• Run MVRs on a schedule, not on suspicion. An annual pull for everyone, plus one at hire, plus a written standard for what disqualifies a driver. The standard matters as much as the check, because a check with no standard proves you looked and kept them anyway.
• Log every run at the run level. Order time, dispatch time, address, miles, driver, and reimbursement paid. Aggregate weekly totals do not survive a subpoena, and they do not tell you which driver is running which routes either.
• Write down the basis for your per-mile rate. One page: what the number is, what inputs produced it, when it was last reviewed, and what triggers a change. The rate matters less than the fact that a real method produced it, and that you can hand that method to somebody who is not inclined to believe you.

None of these five prevent a crash. All five decide whether the crash becomes a claim your carrier handles quietly or a file you spend two years rebuilding from memory, at the least convenient moment your business will ever have.

RatesReady was built for the file this whole article keeps pointing at. It sets and documents a defensible per-mile rate for each of your locations, updates that rate when the IRS number or your state's rules move, and keeps the rate basis, the per-run driver logs, and the reconciliation in one place you can hand to a broker, an adjuster, or opposing counsel without a week of scrambling. It is $49 per location per month. If you want to see what your current records would look like on the Monday after a crash, request a demo and we will walk your numbers with you.

This article is general information for delivery operators and is not legal or tax advice. Rules vary by state and change over time, and your facts matter; consult counsel or a tax professional licensed in your jurisdiction before acting on anything here.