You are hurt in a crash involving an Uber or Lyft driver, and the coverage question turns out to be maddeningly slippery. One insurer says the rideshare policy does not apply; the driver’s personal insurer says it excludes rideshare entirely; and you are left wondering who is actually responsible for your injuries. It is a uniquely frustrating position: badly hurt, plainly not at fault, and yet unable to get any insurer to simply say yes. That runaround is not an accident — it is rideshare coverage denial, the way Uber and Lyft insurers, and the drivers’ personal carriers, use Massachusetts’s layered, period-based insurance rules to point at each other and pay as little as possible. Understanding how the coverage is layered by app period is what cuts through the runaround, because once you know which layer applies, the finger-pointing has an answer, and it is different from simply knowing who pays after a rideshare crash; this is about how the coverage is denied and how to answer it while protecting your personal injury claim.
How rideshare insurance is layered by app period
The single most important thing to understand is that a rideshare driver’s coverage is not one policy — it changes moment to moment depending on what the app was doing. Massachusetts law defines those layers. A rideshare driver is, in insurance terms, several different drivers over the course of a single shift, and which one they were at the moment of a crash is not a detail but the whole case.
The three periods
Under Massachusetts General Laws chapter 175, section 228, a rideshare driver moves through distinct insurance periods. When the app is off, the driver is just a private motorist. When the app is on but no ride has been accepted, one set of coverage applies. And once a ride is accepted — whether the driver is heading to the pickup or carrying a passenger — a much larger layer of coverage kicks in. Which layer is in force at the instant of a crash decides everything about the claim. The same collision, with the same injuries, can be a modestly covered claim or a fully covered one depending on a detail most people never think about — what a phone screen was displaying at the moment of impact. That is why, in a rideshare case, one of the first questions is not how the crash happened but what the app was doing when it did.
App off: personal policy only
When the driver is not logged on at all, section 228 treats the vehicle like any other private car: the driver’s own personal auto policy is what applies, and the rideshare company’s coverage is nowhere in the picture. This is the ordinary world of motor-vehicle claims, with the driver’s own personal insurer on the hook. If a driver rear-ends you while running a personal errand with the app closed, the rideshare companies have nothing to do with it, and the claim proceeds like any other car-accident case. The complication only truly begins the moment the app goes on. Up to that point everything is familiar; after it, the ordinary rules of whose-insurance-pays quietly stop applying, and most people never notice the switch until a claim forces the question. The driver may not even be thinking about it; the coverage shift is automatic and invisible, triggered by a tap, and it reshapes who is responsible without anyone deciding anything in the moment.
The higher the period, the more coverage
The coverage grows as the driver moves toward carrying a passenger. In the waiting period — logged on, available, but with no ride accepted — section 228 requires only lower, minimum liability limits. This is the driver circling a busy neighborhood hoping for a ping: on the clock in a sense, but not yet committed to a fare, and covered accordingly thinly. Once a ride is accepted and the driver is en route or has a passenger aboard, the statute requires a far higher liability limit. The jump between the waiting-period minimums and the on-trip coverage is not incremental; it is a leap to a different order of protection, which is exactly why so much rides on the timing. That escalating structure is exactly what makes the period question so contested: a great deal of money can turn on whether the app had just accepted a ride. A difference of a few seconds — tapping to accept a fare versus still waiting for one — can move a serious claim between coverage worlds, and both sides know it.
Which period the app was in
Because the available coverage changes so dramatically between periods, the fight in a rideshare case is very often not about who caused the crash but about what the app was doing when it happened. That is a strange thing to explain to an injured person who assumed the hard question would be fault; in rideshare cases, fault is often the easy part, and coverage is the real battleground.
The period decides the money
The gap between the waiting-period limits and the on-a-trip limits is enormous, so establishing which period applies can be worth more than any other single fact in the case. An insurer that can characterize the crash as happening during the low-coverage waiting period, rather than during an accepted ride, can cap its exposure at a fraction of what the higher layer would pay. That is a powerful incentive to read every ambiguous fact in the direction of the lower layer, and it explains why the period fight can feel so disproportionate to the simple question of what a screen showed. The period, in other words, is where the real dispute lives. It is a genuinely strange feature of these cases that liability — who actually caused the crash — is sometimes barely contested, while the fight over what an app was doing consumes everything, because that is where the money is decided.
How insurers dispute it
Expect the period to be contested. A driver heading to a pickup is in the high-coverage period, but an insurer may argue the ride had not truly been accepted yet, or that the app had logged off, or that the driver was between fares. Each of those is a plausible-sounding story that, conveniently, lowers the coverage, and none of them can be tested without the underlying data the company holds. These are not idle points — each one, if accepted, drops the claim into a lower-coverage layer. Framed as reasonable questions, they are really levers, and each one an injured person concedes without proof can quietly cost a large share of the available coverage. The ambiguity around the exact instant of acceptance is precisely the seam the denial playbook works. The transition from waiting to accepted happens in an instant on a screen, and reconstructing exactly when it occurred, against an insurer motivated to place it later, is often the crux of the whole claim.
The app data that settles it
The truth about the period lives in the rideshare company’s own records — the timestamps showing when the driver logged on, when a ride was accepted, and where the vehicle was. That data is the most powerful evidence in the case, and it is held by the very companies with an incentive to read it narrowly. That combination — decisive evidence controlled by an interested party — is exactly why getting the records through a formal, documented request rather than a friendly ask tends to matter. Securing the app records, before they become a matter of the company’s say-so, is often what decides which coverage layer the claim lands in. The data exists and is precise; the challenge is getting it in a form that cannot be quietly reinterpreted, which is why demanding it early and formally matters so much.
App-off, waiting, and on-a-trip coverage gaps
The layered structure creates seams between the periods, and the denial playbook lives in those seams. Each transition is a place where coverage can shrink or vanish. The law draws bright lines between the periods, but real crashes happen in the blurry moments around those lines — just as the app opens, just as a ride is accepted — and that is where disputes cluster.
The app-off gap
When the app is off, only the personal policy applies — but the moment the driver logs on to work, that personal coverage can disappear, because Massachusetts law lets personal insurers exclude rideshare use. The result is a hand-off: the driver leaves the protection of the personal policy and enters the rideshare layers, and a crash near that boundary can land in a dispute about which side of the line it fell on. A driver who just opened the app in a parking lot is technically in a different coverage world than the same driver thirty seconds earlier, and that invisible switch is exactly what insurers argue over. The framework for all of this sits in the state’s transportation-network-company law, Massachusetts General Laws chapter 159A½, section 2, which points to the insurance rules that then decide, period by period, who has to answer for a crash.
The thin waiting period
The waiting period — logged on, available, no ride yet — carries the lowest required coverage of the app-on layers. For a serious injury, those minimum limits can fall far short of the harm, and an insurer that can push a claim into this period limits its exposure sharply. This is the layer insurers most want a crash to fall into, and much of the period dispute is an effort to characterize the moment of the crash as the thin waiting period rather than an accepted ride. For an insurer, moving a claim from the on-trip layer down to the waiting period can shrink its exposure to a fraction, so the incentive to argue for the lower layer is intense.
The on-a-trip layer
Once a ride is accepted, the far higher coverage applies, and it generally covers the passenger, the other driver, pedestrians, and others harmed. This is the layer the whole system is built around — the moment a paying rider is in the car is when the law demands the most protection, for everyone the trip might touch. Passengers injured while riding are usually in this best-protected layer, which is one reason insurers scrutinize the exact instant of acceptance so closely. If you were in the back seat of an Uber when it crashed, you are almost always in the high-coverage period, and that is a strong position to negotiate from once the record confirms it. The same is true for a pedestrian or another motorist struck by a driver who was carrying a passenger — the on-trip layer generally reaches them as well. Whether the case is treated like an ordinary car crash or pulled into the rideshare layers, that timing sets the ceiling on recovery. A single fact — had the ride been accepted — can be the difference between coverage that fully answers a catastrophic injury and coverage that barely dents it.
When the driver’s personal policy excludes it
The most common surprise in these cases is that the driver’s own insurance may provide nothing at all. That is not a loophole — it is written into the law. The legislature, in setting up the rideshare framework, expressly allowed personal insurers to step back during rideshare use precisely so the company coverage would carry that risk instead.
The personal-policy exclusion
Section 228 expressly permits automobile insurers to exclude any and all coverage under a personal policy for a loss that occurs while the driver is providing rideshare services or on a pre-arranged ride. Liability, personal injury protection, uninsured and underinsured motorist coverage — all of it can be excluded during rideshare use, and most personal policies do exactly that. The exclusion is not buried fine print that only sometimes applies; it is a standard, permitted feature of Massachusetts auto policies, which is why counting on the personal policy is so risky. Assuming the driver’s familiar personal coverage will respond is one of the easiest mistakes to make and one of the costliest. People reasonably expect that a licensed, insured driver’s policy will cover a crash they cause; with rideshare, that expectation quietly fails the moment the app went on, and few people learn it until they need the coverage, at the worst possible moment.
The rideshare company’s backstop
The counterweight is that the rideshare company’s coverage is designed to fill the gap. When the driver’s required coverage has lapsed, failed to provide the coverage, or denied a claim, section 228 requires the company’s insurance to provide the required coverage beginning with the first dollar and to investigate and defend the claim. In plain terms, the rideshare company’s policy is built to catch the claim when the driver’s coverage falls through, so a gap in the driver’s insurance is not supposed to become a gap in your recovery. That backstop is a powerful protection, and it is one an injured person should not let a quick denial obscure. A denial letter can read like the end of the road when it is really just the first move, and the company’s obligation to step in from the first dollar is exactly the kind of protection a claimant needs to know exists.
No need to exhaust the personal policy first
Importantly, the law does not make the rideshare company’s coverage wait behind the personal insurer. Coverage under the company’s policy is not dependent on a personal insurer first denying a claim, and the personal insurer is not required to deny first. That removes a favorite stalling step, in which each insurer insists it cannot act until the other one has formally refused, leaving the injured person stuck in the middle indefinitely. That matters because a favorite delay tactic is to send an injured person bouncing between insurers; the statute cuts against that by not requiring the personal policy to be exhausted before the company’s coverage responds. Knowing that the law does not force you to lose a fight with the personal insurer first takes much of the air out of the bounce-around.
Rideshare coverage denial: how the delay playbook works
Put the pieces together and the tactics become predictable. The layered system gives insurers several ways to slow-walk or shrink a claim. None of the tactics require anyone to lie; they simply require reading the coverage layers in the way that costs the least, and leaving it to the injured person to prove otherwise.
Pointing at each other
The classic move is the finger-point: the personal insurer says the exclusion applies, the rideshare insurer says a different period governs, and the injured person is left with no one accepting responsibility. It is a coordinated shrug, and its power comes from making a claimant feel that pursuing anyone is hopeless when in fact the law points to a specific answer. The moment a claimant realizes the shrug is a tactic rather than a verdict, it loses most of its force. It can feel like a dead end, but it is usually a negotiating posture built on the coverage layers, and the law — which routes the loss to a specific layer — does not actually leave a serious injury uncovered as often as the runaround implies. Somewhere in the layers, coverage almost always exists; the tactic is to make finding it feel harder than it is.
Disputing the period
Because the money turns on the period, expect that to be where the energy goes: was the app really on, had the ride truly been accepted, was the driver logged into more than one platform. Each of these, argued the insurer’s way, moves the claim toward a lower layer. Answering it means getting to the objective record — the timestamps and location data — rather than accepting the insurer’s characterization of the moment. The facts about the period are not really in doubt; they are in the data, and the dispute is mostly about who controls access to it and how it gets read.
Squeezing the passenger in between
An injured passenger, who did nothing but accept a ride, can end up caught in a dispute between companies that has nothing to do with them. Delay pressures that passenger — out of work, facing bills, unfamiliar with the layers — to accept less to make it end. The passenger did nothing but choose a ride, yet they can bear the brunt of a coverage fight between two companies, and the discomfort of that limbo is itself part of what pushes a quick, low settlement. Understanding how an injury settlement is calculated, and that the higher on-trip layer usually applies to a passenger, is what keeps the pressure from working, along with knowing how PIP coverage and underinsured motorist coverage fit into the layers.
Deadlines and getting help
All of it runs against a clock, and the evidence that decides the period is the first thing to disappear. Between the filing deadline and the fading of the app record, a rideshare claim rewards early action even more than an ordinary crash case does.
The three-year deadline
A Massachusetts personal-injury claim generally must be filed within three years of the injury under Massachusetts General Laws chapter 260, section 2A. That deadline governs a rideshare claim just as it does any other, and the layered-coverage runaround can eat up time while the clock keeps running. Preserving the claim in time keeps every coverage layer available to be sorted out on the evidence. Let the deadline pass and it will not matter which layer applied, because the claim itself is gone; protect it, and the coverage question stays open to be won on the facts.
Preserve the app record early
The proof that fixes the period — ride receipts, app screenshots, timestamps, and the company’s trip data — is strongest when captured immediately. Memories and phone records fade, and the companies control much of the underlying data, so moving early to secure it is what keeps the period from becoming a matter of the insurer’s word. The sooner that record is locked down, the harder the denial playbook is to run. Once the timestamps and trip data are secured, the period is no longer a matter of argument but of record, and most of the runaround depends on the period staying arguable. Take away the ambiguity and you take away most of the leverage that the denial playbook relies on.
When to call a Boston injury lawyer
If you were hurt in a rideshare crash and the insurers are pointing at each other, that runaround is the coverage-denial playbook in action, and it is worth answering with someone who knows the layers. Our Boston injury attorneys handle Uber and Lyft crash claims where the period and the coverage are disputed, whether the case involves a passenger, another driver, or a larger vehicle, and these matters are handled on contingency, so there is no fee unless there is a recovery. If your rideshare claim is being bounced between insurers, you can reach out to have the coverage and the app record reviewed.
Reviewed and Approved By
This article was reviewed for legal accuracy by Daniel J. Larson, the founding attorney of Larson Law and a Massachusetts-barred personal injury lawyer in Boston. He represents individuals and families harmed by negligence in serious-injury matters arising from motor-vehicle collisions, unsafe property conditions, and other preventable incidents. Attorney Larson takes a litigation-first approach, building each case through detailed investigation, discovery, and expert development with the expectation that it may be tried. Before founding the firm, he defended doctors, hospitals, and other healthcare providers in malpractice litigation at a Boston firm — experience that informs how he anticipates the way insurers and defense counsel evaluate a claim. He is a member of the Massachusetts Bar Association and the Massachusetts Academy of Trial Attorneys.
Frequently Asked Questions
Why do the insurers keep pointing at each other after a rideshare crash?
Because a rideshare driver’s coverage changes by app period, and each insurer has an incentive to say a different layer applies. The driver’s personal insurer often excludes rideshare use entirely, while the rideshare company’s coverage depends on whether the app was on and a ride accepted. The runaround is a feature of the layered system, not a misunderstanding.
What are the app “periods” and why do they matter?
Massachusetts law recognizes distinct periods: the app off (personal policy only), the app on but no ride accepted (lower minimum limits), and a ride accepted or passenger aboard (a much higher limit). The available coverage differs dramatically by period, so which one was in effect at the moment of the crash often decides how much is available.
Does the driver’s personal insurance cover a rideshare crash?
Often not. Massachusetts law expressly lets personal auto insurers exclude all coverage for losses that occur while the driver is providing rideshare services or on a pre-arranged ride. That is why the rideshare company’s coverage becomes central once the app is on, and why assuming the personal policy will respond can be a costly mistake.
The rideshare company says its coverage does not apply. Is that the last word?
No. If the required coverage has lapsed, failed, or been denied, Massachusetts law requires the rideshare company’s own insurance to step in from the first dollar and to investigate and defend the claim. And that coverage does not depend on the personal insurer denying first. A quick denial is a negotiating position, not a final answer.
What should I do to protect a rideshare injury claim?
Preserve the evidence of what the app was doing — screenshots, ride receipts, timestamps — and get medical care documented promptly. The period dispute turns on records the companies control, so acting early to secure that proof, before it is filtered through an insurer’s reading, is the most important step you can take.
Results Disclaimer: Past case results, settlements, and verdicts mentioned on this website do not guarantee or predict a similar outcome in any future case. Every case is unique and depends on its own facts and legal issues.